Moving from domain to workgroup

I am setting up a new Windows 2003 server.  There are 3 workstations that will connect to the server.  The three workstations were in a domain and have been moved to a new network with this new server.  The new network is being setup as a WORKGROUP instead of a domain.  What is the best way to transition the workstations to the new workgroup without losing user profiles.
ddawsonwAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:
Why take a step backward?  You lose manageability, profiles, permissions, and make it more difficult in the future.  I would STRONGLY advise AGAINST using a workgroup, especially when you already have a domain.  

To do what you want you'll need profile migration tools that can copy one profile to another.  I have a link to one on my web page http://www.lwcomputing.com/tips/static/techtoolkit.asp
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ddawsonwAuthor Commented:
If I use a domain:  Currently, the workstations are on domainA.  I would be moving them to domainB on a different network.  What process would I use to migrate the workstations to the new domain without losing profiles?
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
Why would you move them to a different domain?  What's wrong with the existing domain?  If you can provide more details, we can better help you (why not just add this server as a second domain controller then demote the first one.  Done (after some relatively minor additional adjustments)... and your accounts and profiles are preserved; though I'd keep the first Domain Controller for redundancy if possible).
0
Newly released Acronis True Image 2019

In announcing the release of the 15th Anniversary Edition of Acronis True Image 2019, the company revealed that its artificial intelligence-based anti-ransomware technology – stopped more than 200,000 ransomware attacks on 150,000 customers last year.

ddawsonwAuthor Commented:
Two companies are sharing a server and network. One of the companies is splitting off and will have a new server and separate network.  I need to move three workstations to the new network/server leaving the existing network/server intact.  
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
Ok, when I have all the details, I can provide you a better solution.

Two options:
1.  Use the Active Directory Migration Tool (ADMT).  Setup a NEW domain using the new server.  Then use the ADMT to migrate the users AND computers you want to put in the new domain.  this should preserve the user profiles and security information.

2. (option 1 is preferred, but this could work as well) So long as these servers/companies would NEVER rejoin the same network, then do the following -  Add the new server as a DC in the original domain.  Then disconnect it from the network.  Then Seize the FSMO roles on the new domain controller.  After that, you'll need to clean up AD on both servers, removing the other server from each (Remove Old DC from New Server, remove New DC from Old server).   Frankly, there's more to it but as I think about it, this is the more complicated and less appropriate method - I would use option 1.  I'll further detail this option if you want, but really, use 1.
0
ddawsonwAuthor Commented:
Option 1 sounds promising. The new domain will have a different name than the old domain. After moving the AD profiles to the new domain what do I need to do on the workstations?  Old domain was Windows SBS 2003. New domain will be Windows 2003 Server.  Only files will be moved and servred.  No exchange on either server.  
0
Lee W, MVPTechnology and Business Process AdvisorCommented:
ADMT SHOULD still work with SBS - I've seen many references to it having been done so - but you didn't mention SBS until now.  If you can't get option 1 working, then option 2 should definitely work - not as clean, but it should work.  If they aren't using Exchange, why do they have SBS?  The CALs are more expensive in part because they allow use of Exchange.  They really should be using exchange.

That said, a new domain name AND server name would be required in the option 1.  In theory, you would migrate the selected users and computers from one domain to the other.  Once the domains are split, remove the departed users and computers from the SBS server.

0
Lee W, MVPTechnology and Business Process AdvisorCommented:
I object.  What "better" solution was found?  The solutions presented are valid.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.