Does active directory always have to create a new use client on existing machines?

I have a simple network. 35 machines connecting to a novell 5.1 file server that we are replacing with a Server 2008 R2 machine. I have the luxury of tweaking the 2008 box and experimenting with it until we're sure it's ready to go. I've installed DNS, Active Directory and file server options. My first XP machine logged into the domain I created but then created a new user account on the Cliient (my original user name was scott and the log into the Server 2008 R2 created scott.IDS. Is there a way in Active Directory to use the existing users account name on their individual computers, without have to create a new client name on each box when they connect to the 2008 domain server for the first time? If not, am I then faced with migrating all date from their old user names to the new one created by the domain server on the employees machine? Hope this is clear.
Thanks,
Scott

AD distinguishes between domain accounts and local computer accounts. Domain accounts are good anywhere in the domain. Local accounts are good on the machine on which they are created.

To answer your question: no. In your case, you'll probably have to create domain accounts for everyone who currently has a local computer account. When they log in to their computer using their domain credentials for the first time, the computer will create a new profile for the domain account. Once that is done, you should be able to copy all the items from the local profile to their new profile, change ownership and they can just keep trucking.

0

Featured Post

Managing Active Directory does not always have to be complicated. If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…