asked on

2003 Server FSMO Transfer

Hello all,

I am sure this will be a simple one for most.

I have two servers, one windows server 2003 as domain controller and second with windows server R2 setup as AD replication and secondary DNS.

I am retiring the main domain controller and will replace it will domain controller 2. I followed the process to transfer the FSMO roles, all 5 of them to the 2nd domain controller. It was successful.

I then turned off the 1st domain controller and removed it from the site.

Now I am getting errors that the global catalog server cannot be contacted. Also, the FMSO was successful, but not yet validated.

I am not sure what I need to do next. Any help would greatly be appreciated.

Thanks in advance!

SOLUTION

Tony Massa

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

itsupportmd

ASKER

tmassa90,

Thanks for the quick response. I ran the dsquery commmand and the roles are with the current server, so they transferred successfully.

I looked in AD Site and Services and under Servers, the other domain controller is listed. Should I delete it from there?

Then what?

Thanks,

Bill

ASKER CERTIFIED SOLUTION

Andrew Oakeley

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Tony Massa

Yes, delete the object from AD sites (and ADUC) if it's still there, then perform the Metadata cleanup. make sure your DC is a global catalog...all of your DCs should be global catalogs.

SOLUTION

Awinish

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

itsupportmd

ASKER

All,

Thanks for your input. I have successully transferred the FSMO roles and make the new domain controller the Global Catalog server. I have also deleted the old domain controller from the AD sites and services.

I also did a metadata cleanup. Is there anything that I need to do? Users are reporting very slow login process.

I did not do anything with the time server. Is this an absolute must or is it optional?

Thanks

Awinish

Its a must to configure new DC as time Server holding PDC role else there will be issue.

itsupportmd

ASKER

Awinish,

Thanks. So according to the link, I should configure the domain controller with an internal time source and not an external one. Is that correct?

Should I follow the steps in the link that you sent?

Thanks,

Andrew Oakeley

Awinish

PDC has to sync from external source & all other clients/server/DC's from PDC server.

Awinish

I prefer time.windows.com, 0x1 for PDC & others with PDC DC

Andrew Oakeley

Slow login is almost always a function of incorrect DNS.

Confirm
A) that dns on the workstations points ONLY to a domain DNS server (no ISP dns)
B) all dns entries for the old DC are removed (including "same as parent" entries

itsupportmd

ASKER

All,

Thank you very much for you assistance with my server transistion. I appreciate everyone's time and input. It made my transition go nice an smooth and was a great resource to check myself.

Thanks to all.

itsupportmd

ASKER

Thanks again!