[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 302
  • Last Modified:

Active Directory Migration Preperation

Alright, I am preperaing to migrate one companies AD into our Company.  However, we USE TO BE a Small Buisness Shop.  So I have the My Buisness folder in AD that contains folders called Computers, Distribution Groups, Security Groups, and Users.  The Computers has sub folders of SBSComputers and SBSServers, and the USers folder has SBSUsers under it.  SBSUsers is where all of my users are located and created.

What I want to do is create OU's per Office (3 Offices) and move the appropriate users into the proper OU.

Basically I want to get out of the SBS umbrella and be in a true 2003 AD enviroment.  Is there anything that would make the transition funky?

Thanks.
0
Goofdru
Asked:
Goofdru
  • 3
  • 3
2 Solutions
 
Hypercat (Deb)Commented:
There is nothing inherently different between using the SBS OU's and using your own customized OU's.  The reason for the existence of those OU's in SBS is that part of the SBS preconfigured environment is a set of group policies and file system permissions to control access and enhance the security of the system.  That said, I'm assuming that you will be either completely wiping and reinstalling your OS, or migrating to new hardware (which of course would be the preferred method).  So, on your new server, you would create your own custom OU's, security groups within those OU's, and group policies for those OU's and then migrate the user accounts to the new server.

Also, you need to consider file/folder permissions as well as membership in organizational units.  You will probably need to create customized security groups on your new domain and add the users to the appropriate security groups on the new server after they've been migrated.  Also, you will need to set your file and folder permissions carefully before and during migration of your files so that the access control lists are properly configured for your new security groups to have the right permissions to the right sets of files and resources on the new server.
0
 
drchristopheCommented:
Sorry if i'm not getting you right but do you mean moving objects from one OU to another OU in the same forest/domain?

If you do then there is not much to worry about as OU's are administritive bounderies, a virtual filing cabinet if you will.

One think you may need to be aware of is Group Policies. Different group polices can apply to different OU's and the objects within them, So if you move a pc out of SBSComputers into Computers they will not get the policy that was applied to the orginal OU.

You can check which GPO's apply by using gpmc.msc (Group Policy Management Console).

On the other hand I may have got the wrong end of the stick totally ;)
0
 
GoofdruAuthor Commented:
Well I won't be moving to new hardware or reinstalling any OS.  I have already applied the Transition pack over a year ago, then because of a disaster all roles were moved to an Enterprise server and off the "Old SBS server".  

I think I am on the right track and doing what you are suggesting.  I have since created the OU's that I want and GP that I want.  I have been hesitant to move any users because of fear that I will cause my self a headache because of something that SBS had done to their user id during creation.

I am restructuring the network drives/shares as well as migrating another domain into ours and thought it would be good to do them both (migrate and change network drives) at the same time.
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
GoofdruAuthor Commented:
No Christophe your are on the right track.  I am looking to move with in the same forrest/domain.  Testing will be done first, I am just putting together a document explaining what I am trying to do and accomplish.  Of course the document is in layman terms because I am the only technical minded person in the whole company it seems.

I did all of this in class about 7 years ago (2000 AD, the OS not the year).  It is just I haven't had to do this since then and I am affraid I may be a little rusty.
0
 
Hypercat (Deb)Commented:
So, are you talking about upgrading from SBS to full Windows 2003 Server, or are you going to stay with the SBS OS but just try to set it up like a standard Windows 2003 server?  There's a lot of difference between those two choices technically, so we need to know which you are talking about.  And of course there's the maximum number of users (75) which you cannot exceed if you want to continue to use SBS.
0
 
Hypercat (Deb)Commented:
Never mind - I missed your post above where you explained this....
0
 
GoofdruAuthor Commented:
I apologize, the only reason I mentioned SBS was for background.  Yes the transition has already been done so it release all the restrictions of SBS.  

Honestly I could just keep the users where they are now, but I was looking to do some cool stuff with GPs per office, per location, and all that.

I guess I was looking more for reassurance than I was 'How to'.

Thanks for both of you guys help.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now