Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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'm helping a small charity move away from an Active Domain setup. They will be using Google Apps and Dropbox to replace the main functionality and their new office will just have a router providing DHCP on a local subnet.

What steps should I take to to convert the accounts on each machine from Domain accounts to simple local user accounts? Or is that even the best thing to do?

I'm a Linux guy so not even sure if I am asking the right question...

share|improve this question
up vote 1 down vote accepted

Active Domain? You mean Active DIRECTORY? I believe the User Profile Wizard from ForensIT can convert the profiles to local profiles (you're losing centralized management and logon by leaving the domain structure). Or you could just use local accounts and copy the data from the old accounts (MAKE SURE you know the local administrator password before removing the machines from the domain).

Honestly, if they have a Windows server, I do not see the point in leaving it. Use google apps and dropbox if you want. But keep the server for centralized management and account database.

share|improve this answer
Active Directory? Cool, I'll get the there, like I said I normally manage Linux networks :) They are moving office and won't have any kind of server at the new location. So the important point seems to be to make sure there is a local admin account on each machine. – aychedee May 19 '12 at 7:44

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.