I have a very simple domain that consists of 1 server, 15 pc's and that is it. We have no email server since it is hosted at office 365. I am thinking that demoting the server, the promoting it back to a domain controller in the new domain would be the easiest way to accomplish what I am trying to do. Since there is only 15 computers I do not see a problem re-adding them to the new domain and moving the users files to their new profile. Just looking for suggestions. thanks, Dave Barkley

Hello, I don't think that demoting your DC will be the best option since here actual local profiles for domain users will be lost, access to resources based on the use of SIDs will be lost ... You can rename your domain based on that: http://technet.microsoft.com/en-us/library/cc738208%28v=ws.10%29.aspx Since you don't use Exchange then just check that domain based applications in use supports that. If you don't then you can just rename it. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

Just clone the DC or back it up, and if the image is ok you demote the DC. Just be sure to isolate your DC when you will be dooing it. After that you just re-join the new domain, and you will have to copy back the user data from their old profile by hand or with migwiz. On my side I prefer that way if it's a small domain, already done the domain rename path, and you will loose a lot more time, and if you do a error the GPO, or some AD part might not work ok. Not to tell that your downtime will be less too, as a dcpromo, and joining 15 computer is a easy/fast job. MCP | MCTS 70-236: Exchange Server 2007, Configuring

Hello Yagmoth555, please do NOT suggest images/clones for domain controller backup. THIS IS NOT SUPPORTED AND MAY RESULT IN USN ROLLBACKS.Best regards Meinolf Weber MVP, MCP, MCTS Microsoft MVP - Directory Services My Blog: http://msmvps.com/blogs/mweber/ Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

Hello, if you demote the server you loose all access to the local machine profiels after readding to the new installed DC. Why must you rename it? I can see no reason at the moment and you should re-think if the work is really required.Best regards Meinolf Weber MVP, MCP, MCTS Microsoft MVP - Directory Services My Blog: http://msmvps.com/blogs/mweber/ Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

Sorry, my point was just he need a really good "parachute" before all those step. Use ntbackup or any other backup tool to make sure you can go back.MCP | MCTS 70-236: Exchange Server 2007, Configuring

Check that thread, kinda the same debate as your thread; http://social.technet.microsoft.com/Forums/en/winservergen/thread/621eb7df-a574-4412-b685-ed02ce5bb317MCP | MCTS 70-236: Exchange Server 2007, Configuring

For a little more detail. This domain is a child domain and this company was sold. I have broken the connection to the parent domain and now must create a new domain for all the users, computers and such. Since this is a one server domain I thought the best approach was to demote and then promote back to a DC with the new domain name.

On my side I would simply re-do the domain. USMT can migrate the data, and other trick do it.MCP | MCTS 70-236: Exchange Server 2007, Configuring

Hi, I would like to confirm what is the current situation? If there is anything that I can do for you, please do not hesitate to let me know, and I will be happy to help. Regards, Arthur Li TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here.Arthur Li TechNet Community Support

When I posted the question I phrased it wrong and I am still looking for advice. What I need to do is convert this child domain to a parent domain in its own forest. This small business was sold which was a child domain of the parent company. It is a single server environment with about 15 user accounts and 15 pc's on the network. There is no email server to contend with as it is hosted online. My thoughts on this were to demote the single server domain controller and then re-promote it to a domain controller in its own forest. Just looking for the best way possible to accomplish this. Since there are not many user or computer accounts, I am not worried about manually moving them over to the new domain when it has been created. folder access and such, they really dont have that many folders with special rights so that is not a big concern either. Thanks for any information yo ucan give me

Hi, Do you consider to create a new domain and migrate the data to the new domain? For more information, please refer to the following Microsoft TechNet article: ADMT Guide: Migrating and Restructuring Active Directory Domains http://technet.microsoft.com/en-us/library/cc974332(v=WS.10).aspx Regards, Arthur Li TechNet Subscriber Support If you are TechNet Subscription user and have any feedback on our support quality, please send your feedback here. Arthur Li TechNet Community Support