cvusd-do-dc3 now do-dc3

The emergency transition from cvusd-do-dc3 to do-dc3 has gone smoother than I had expected it to.

The IP for do-dc3 is the same as cvusd-do-dc3: 10.40.55.5

For the user’s computers, the people affected will mostly be at the district. as their workstations may have been pointing to cvusd-do-dc3 as their LOGONSERVER.  If you receive any calls from the users with weird issues, like i: drives not mapping, or weird profile errors, first action would be to ask the user to reboot their machine, and it is very likely that all the problems will go away.

The Citrix servers will all have to be rebooted, especially the ones that were pointing to cvusd-do-dc3 prior to the crash.

I have done some initial testing with some users that were reporting the inability to get the i: drive mapped, and the i: drives have started mapping after rebuilding the domain controller.

Please keep me posted of any issues that you may still see. As there may be some services that I may have not known about that may stop functioning due to the disappearance of cvusd-do-dc3.

• This change was made on 09/10/2009 @ 4:30pm