OU Structure

Good afternoon!

Dumb question of the day...let's get it out of the way for everyone!

OU Structure in SBS-land: if we modify it does it create problems,
specifically when creating user account objects via the Wizard?

Reason that I ask: I just created two user account objects in an SBS2003
Standard environment. Naturally, I went to use the Wizard to do this. I
received the error message:

The required organizational units do not exist and are required by the
wizard. Run the Small Business Server Setup again and reinstall the
administration compnonent.

Now, I can create the user account objects via the ADUC and then ensure that
they are members of the correct Security / Distribution Groups. But,
SBS2003 is wizard-centric. Why not let it do all the work for me, right?

Anyway, I looked at the OU Structure and noticed that the OU "MyBusiness"
has been renamed to "ClientNameHere" and that under the sub-OU "COMPUTERS"
the two sub-OUs (SBS Computers and SBS Servers) are not there and, probably
more pertinent to this case, the sub-OU (under USERS) SBS-USERS has been
renamed......

So, in doing this the person who did this broke the functionality of the
Wizards?

Thanks,

Cary


.

Relevant Pages

  • Re: RWW
    ... I manually moved the user account objects to ... I guess that I have not seen that wizard. ... someone else and none of these clients were set up using the wizards. ... And, I did not know if there was any certain order (okay, over thinking ...
    (microsoft.public.windows.server.sbs)
  • Re: OU Structure
    ... specifically when creating user account objects via the Wizard? ... I went to use the Wizard to ... The required organizational units do not exist and are required by the ... Yes, and Group Policy. ...
    (microsoft.public.windows.server.sbs)