Windows 2003 Transfer of FMSO Roles and GC - Advice needed

We have a small network, with one Windows 2003 R2 based Active Directory DC. The controller generally works fine, but due to some other issues with the Server (that I won't bother you with here) I want to transfer all the FMSO roles and switch global catalogue to another Server, then demote this Server and format it for other uses. I've joined the New Server to the Domain as a DC, and have all the MS white papers on how to transfer the roles and switch on Global Catalogue on this new Server.

However, have I missed anything? Is there anything more than the 5 x FMSO roles (Schema Master, Domain Naming Master, Infrastructure Master, RID Master and PDC Emulator) & GC that need consideration?

I await any useful advice someone might be able to offer :)

Many thanks,

Bluemercury
LVL 2
bluemercuryAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

BusbarSolutions ArchitectCommented:
Be sure the replication is completed and DNS is working correctly then you will be fine.
also be sure that clients will point to the new server in the DNS section from the TCP/IP properties ir change the IP of the new server to be as the old IP

and you will be fine
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
bluemercuryAuthor Commented:
Many thanks for your prompt reply busbar - in terms of DNS working correctly, I'm setting up DNS on the new Server to hold a replicated copy via AD - I assume this is ok?

Yes, no worries about the IP thing - this is going be done over a weekend, and this new Server will ultimately be given the IP address of the old one, so all the clients will fall in line. I use DHCP anyway, so if things do change, a refresh of the clients will sort that.

Thanks again - any further help welcomed!!

Bluemercury
0
bluemercuryAuthor Commented:
Ok, I went ahead and did all the FSMO role changes and GC change. It all seems to work well. However, when I go into DNS on the new sole Domain Controller, I note it still contains AD relevant records that shoudln't be there - the old Server is till listed as a DC as one example. Is it safe for me to remove such records that pertain to the old server?

Many thanks.
0
Problems using Powershell and Active Directory?

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

BusbarSolutions ArchitectCommented:
the DC will still be listed until you remove it using the DCPROMO on the old server, don't remove the server my disconnecting it, run dcpromo and if the command failed use dcpromo /forceremoval
0
bluemercuryAuthor Commented:
Thanks for your post. Sorry I didn't outline everything I've done - I have already successfully run Dcpromo on the old Server, and demoted it without any issues. It claimed to be a sucess, and returned to being a member Server on the domain.

So you see, why didn't this process remove the DNS records that relate to the old Server as a domain controller? There were LDAP records, DC records and all sorts in there. As I'm working with a test network, I've manually removed these now - do you reckon this i ok?

Many thanks
0
bluemercuryAuthor Commented:
Didn't receive any further posts - all worked out fine though. Server ran great after transfering the roles to and forth from various servers, till I had the setup I wanted. Ultimately your first answer was correct about me being fine with the FSMO role transfers I suggested - I just had to make those DNS changes myself at the end of it all (it seems when I've tried dcpromo and demoted servers on other networks since that the DNS entries for demoted DCs always get left behind - is there any tool to clean this up?) I will award the points.

Thanks for your help!

Best wishes,

Bluemercury
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
Active Directory

From novice to tech pro — start learning today.