If the DNS problems are with 2008 r2, then set up a DNS server that is separate from the DC. I would only rebuild/reboot the whole domain if I had a major domain wide issue.
Rick Gasper Manager, Network Services King's College 133 N. River St Wilkes-Barre PA 18711 PH: 570-208-5845 Fax: 570-208-6072 Cell: 570-760-0335 [email protected]<mailto:[email protected]> Don't become a phishing victim!! King's College and other reputable organizations will never use email to request that you reply with your password, Social Security number or confidential personal information. From: Jonathan Link [mailto:[email protected]] Sent: Monday, July 18, 2011 12:03 PM To: NT System Admin Issues Subject: Re: Clean & Pristine or Swing Migrations? +1 DNS problems are usually easily solved, much less work than recreating a domain from scratch... On Mon, Jul 18, 2011 at 11:44 AM, Steve Ens <[email protected]<mailto:[email protected]>> wrote: That's how I did it...worked fine. Mind you we don't have too many AD objects, only 150 or so users and a few dozen groups...but shouldn't make too much of a difference. On Mon, Jul 18, 2011 at 10:32 AM, Andrew S. Baker <[email protected]<mailto:[email protected]>> wrote: What was the problem you had with DNS? If the domain was well maintained, and there are no other reasons for building a new domain, I would be much more inclined to bring up new 2008 servers in the existing domain, and then decommission the older DC infrastructure. ASB http://about.me/Andrew.S.Baker Harnessing the Advantages of Technology for the SMB market... On Mon, Jul 18, 2011 at 4:40 AM, <[email protected]<mailto:[email protected]>> wrote: Hello all I am currently working on the migration project of our Windows Server 2003 domain to a Windows R2 2008 domain. Our single domain is small with about 160 user acounts. I've tried doing a swing migration but somehow could not get the DNS server to work on the R2 server. I am currently looking at the C&P migration option. With the C&P migration I know that users would have to re-create their passwords again, but this isn't an issue for me. What concerns me is whether user and machine accounts will get migrated across correctly. Also would I have to re-join the users' workstations to the new domain? Would Group Policies and Security Permissions be migrated across? I was thinking of keeping the same domain name and server name (including IP address), obviously the original domain server would be switched off. Any comments/advice would be greately appreciated. TIA Pierre ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
