Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I currently have about 50 different work stations, all running windows xp who are part of various workgroups. These machines were all setup by different people with no communication between them. I honestly, don't know what to expect when I dive in to them. I'm working on migrating them over to a Domain. I have the DC set up and it seems to be working well.

What do I need to do and in what order to make this all happen?

How do I lock down these machines ? Group Policy? Do you know of any good resources for wrapping my head around what Group Policy is?

Can switching from 50 machines using NETBIOS and workgroups to a domain make the network run faster or no?

share|improve this question
up vote 5 down vote accepted

Heh, well the good thing is that you're certainly heading in the right direction!! Not sure how much speed benefit you'll notice, but you will certainly improve the efficiency of things.

I would do things in this kind of order:

  1. Lock your door so the users can't get to you to gripe about locking them down (haha)
  2. Make sure you have Active Directory containers configured how you want them. This should't be too bad with only 50 PC's.
  3. Create domain user accounts for your users in AD
  4. Create home network shares if you want to use them
  5. Configure the domain's Group Policies in AD
  6. Write login scripts if you want to use them
  7. Configure your PC's to use your DC as the dns server if they're not already (or whatever dns server holds your AD SRV records). You might consider setting up DHCP at this point if you don't already have it in place. NOTE based on comments: DO USE DHCP! The prior wording was supposed to say that, but admittedly was not clear. Set up DHCP and configure your clients to use it.
  8. Back up your users' profiles on their PC's. They will get new user profiles with their domain accounts.
  9. Join your PC's to the domain

Some of that can be switched around a little but basically it's

  1. Set up your domain and group policies
  2. Set up your user resources
  3. Migrate the PC's

Do this with a handful of PC's in a a lab before you do this in production until you are comfortable with the process. You'll also benefit from a workstation naming standard when joining your PC's to the domain (from a sanity perspective).

Here's the site to start learning about group policy.

share|improve this answer
+1, especially for item 8. Far too many admins skip that step and create a whole lot of unnecessary work and annoyance for the users. A person who has their machine set up just the way they want it is going to be real peeved if you make them start all over. As an admin you don't need the grief that would bring either. – John Gardeniers Sep 14 '09 at 23:28
+1 - I'll second this strategy, except that I'd encourage you to implement "Folder Redirection" and learn how to migrate the local user profiles into roaming user profiles (see… for a very, very brief description). You can create a completely seamless experience for the user if you give a bit of attention to detail. Even if you don't bring over their personal registry hive, at least bring over their files from the local profile into their new redirected folders. – Evan Anderson Sep 15 '09 at 1:34
Great point about the roaming profiles. Word of caution, though, is that they get exceedingly cumbersome when dealing with remote access users who like to keep an inordinate amount of crap on their desktop. – squillman Sep 15 '09 at 2:43
Excellent suggestions - except the DHCP suggestion shouldn't be a maybe, it's a must if you want any kind of control over the workstations networking. Can you imagine administrating all those PCs manually if you decide to change DNS server, or anything else of that nature? Furthermore, if they're all statically assigned, there's no DNS registration (yes this can be set up via GPO, but it's messy). +1 for the excellent suggestions, -1 for the DHCP suggestion, net 0! – Izzy Sep 15 '09 at 5:02
@Izz: True dat re: DHCP. Students often asked me "How many client computers would you have in a LAN to consider using DHCP?" My answer was always "more than one". As soon as you have more than one computer to deal with your configuration labor becomes a multiple of the time taken to do the work once. – Evan Anderson Sep 15 '09 at 13:30

A domain will sure allow for better management, and better network performance too (no more NETBIOS broadcasts all around).

Steps to bring all of this into a domain:

  • Give each computer (and your DC, of course) an IP address/subnet mask pair so that all of them are on the same subnet.
  • Make each computer use your DC as its DNS server.
  • Make each computer use the default gateway for your network.
  • Make sure your DNS server can resolve Internet names (it does, by default; but you should configure forwarders for better performance).
  • Join each computer to the domain.
  • Create user accounts for your users.
  • If needed, give users local administrator rights on their computers.

This should get you going.

For group policies, you can start here.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.