did you transfer all the FSMO roles when you changed the DC? http://support.microsoft.c
Also if you did transfer the FSMO then the server that held the roles should be removed from the network (disconnected)
eb
Main Topics
Browse All Topicshere is the quick layout:
Have had Exchange server 2007 up and running for about 2 months. Recently I put new Domain Controllers up and demoted the the old ones. In addition to being DC's, 1 was a WINS server. About this same time it started taking a very long time to open the EMC and EMS for exchange 2007 (upwards of 2 minutes). Finally you will recieve a "end snap in" error, however if you press cancel, you can do what you need to do.
By searching around, I have already tried lowering the amount of users that are "preloaded" upon opening, however this did not help...additionally we only have 300 objects.
The reason I believe it is WINS is because we ran into this error when we first started setting up exchange is a test environment. We found that by turning on the "enable netbios over tcp/ip" within the network adapters settings that this problem stopped. However now that I have brought down the old WINS, and now even brought up a new WINS and pointed this to the correct IP, this is still happening.
I would like to phase netbios/wins out all together, however it seems as though some things are still relying on it. I have also looked at the binding settings for the network cards and NETBIOS is not even listed as a protocol to place lower in the chain....
Any thoughts?
Travis
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
did you transfer all the FSMO roles when you changed the DC? http://support.microsoft.c
Also if you did transfer the FSMO then the server that held the roles should be removed from the network (disconnected)
eb
Thank you EBJERS, however I did transfer all FSMO succesfully and then promoted the other DC's.
however when I do a dcdiag on the new DC's, I do get an error:
Starting Test: Machine Account
Warning : Attribute userAccountControl of "DC" is: 0x82020 = blah blah blah.......
This may be affecting replication?
I assumed this is a different problem.... maybe not though?
From tgrizzel in Community Support (http://www.experts-exchan
"I ran across this while working another issue... In the Windows DNS servers, my integrated AD DNS was listed to "Load Zone on startup from: The Registry" I changed this to "Active Directory and the Registry" and this issue went away. I know that there were a few other people who had this issue and never found a solution, I was hoping that this could be posted as a solution and sent to the other users.....
Thanks "
modus_operandi
EE Moderator
I ran that command, but again everything was working fine till this recent issue, where we fixed some wrong dns enteries and also transfered the fsmo roles to this 2nd server, although both servers are online, but the management console is veeeeery slow to load even if i go into shell mode its faster but still slow to load when it says connecting to (servername)
Business Accounts
Answer for Membership
by: PakaPosted on 2008-03-19 at 12:11:55ID: 21164775
It's probably a DNS issue. Is your Exchange server IP stack pointed at the new DNS server? Do you have multiple sites and is the DC to site coverage mapped correctly. Had this same problem and it was related to the stand-up of a new DC that went off-site.