Old server was a 2003 (64), running Exchange 2007 - PDC, no workstations connected. 100+ users accessing email using http/rpc. We had some other services on this server as well. very small 'webpage' for users to access over a vpn connection, and Symantec Corporate server as well. Things worked very well, no issues - unfortunately, the server was multihomed, which apparently caused some problems when we upgraded.
New server is a vm, on ESX - 2008r2, Exchange 2010. Everything came accross and worked ok, except we had a strange problem. the old server needs to be on to add users. Microsoft worked with us to resolve some issues with DNS and such, caused by the multihomed enviroment. Lots got resolved but this server was a production server, and we wanted to wait until we had replication setup before finishing off the job.
So, the other day, we finished off as per discussions with Microsoft, rebooted the new server, and poof. complete failure. Eventually reverted back to the replica. The replica actually works without the old server, but there are issues - often when you open Active Directory users and groups, it gives you an error.
Naming information cannot be located because:
the specified domain either does not exist or could not be contacted. contact your system administrator to verify that yoru domain is properly configured and is currently online.
If you play arround you can get this working. Because the server is working, we run replicas at night, and try and correct the replicas, if it fails we revert back to the original.
Replicas - Vconverter does a poor job of 'replicating' and we have to redo the network settings every time, and setup Routing and Remote Access. After we get that working, we do some Metadata cleanup tasks and such, as per various kb articles. We leave Exchange services off while we correct Directory Services. There are quite a few reoccurrent problems in DCDIAG - sample errors;
DsGetDcName (NewServer) call failed. Error 1355 The location could not find the server.
.................NewServer faield test Advertising
There are warning or eror events within the last 24 hrs after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems.
Starting Test KccEvent
A warning event occured. EventID: 0x80000b46 Event String
the security of this directory server can be signifantly enhanced by configuring the server to reject SASL.....
A Global Catalog Server could not be located - All GC's are down
A Time Server could not be found.
Mark Smed, NPA Network Support Technician msmed@northerncomputer.ca Northern Computer l Your trusted partner. Ph: 250.762.7753 Ext. 1803 www.northerncomputer.ca