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

There are about 10 computers in this office and they are all laptops because we all use our computers on-site. For the most part everyone manages their own computer.

We want to set up Active Directory just for the single sign-on stuff and managing the permissions to shares on the NAS. I don't care about storing user data on a central machine, or probably most of the AD features.

But in my limited tests, joining the the domain means rebooting and logging in as a new user with new User directory, which is not going to fly with most of the people. I found some really hacky looking ways to copy over the local account, but doing that 10 times (and possibly breaking someone's computer) is not going to fly with me.

share|improve this question
BTW, AD doesn't get you single-sign-on. It gets you a single set of credentials you can use. To get true SSO, you need something like shibboleth. SSO and unified credentials are two terms that are frequently mixed up. – EEAA Sep 8 '11 at 2:12

Microsoft's User State Migration Tool is built exactly for this situation.

share|improve this answer

In addition to ErikA's fine answer, you might consider impementing Microsoft Small Business Server 2011. In addition to making user and resource management easier, SBS also facilitates "migrating" local user profiles to domain profiles as part of the process of joining the computers to the domain.

Here's a brief video that illustrates the process:

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.