techofficials
asked on
Terminal Server Login Issue after domain migration
Hello,
I am migrating a Windows SBS2003 with a Terminal Server 2003 to Windows 2008 with Exchange 2007. I am leaving the Terminal Server 2003 in the domain. I have used the following article to assist me in the process: http://www.itexpertmag.com/server/upgrading-small-business-server-2003-to-exchange-2007.
I have completed the mailbox migration, public folders, and uninstalled Exchange on the SBS2003 box. The W2K8 box is a GC and has all of the FSMO roles. I preformed a test by shutting down the SBS2003 box and noticed mail backing up. I realized that the DNS on the W2K8 box NIC was still pointing to the SBS box. I changed it point to itself. I also pointed the DNS for the TS NIC to the W2K8 box. I am now retesting. When I login to the Terminal Server, I am getting a usrlogon.cmd appear (never seen that before) and the desktop on the Terminal Server is very slow to respond to basic command like opening files, double clicking on My Computer, etc. Any sugesstions?
I am migrating a Windows SBS2003 with a Terminal Server 2003 to Windows 2008 with Exchange 2007. I am leaving the Terminal Server 2003 in the domain. I have used the following article to assist me in the process: http://www.itexpertmag.com/server/upgrading-small-business-server-2003-to-exchange-2007.
I have completed the mailbox migration, public folders, and uninstalled Exchange on the SBS2003 box. The W2K8 box is a GC and has all of the FSMO roles. I preformed a test by shutting down the SBS2003 box and noticed mail backing up. I realized that the DNS on the W2K8 box NIC was still pointing to the SBS box. I changed it point to itself. I also pointed the DNS for the TS NIC to the W2K8 box. I am now retesting. When I login to the Terminal Server, I am getting a usrlogon.cmd appear (never seen that before) and the desktop on the Terminal Server is very slow to respond to basic command like opening files, double clicking on My Computer, etc. Any sugesstions?
ASKER
Firebar,
Thanks for trying, but it did not solve the issue. I still have the usrlogon.cmd. I have also discovered that I have netlogon 5788 and 8789 errors in the event viewer of the terminal server since I shutdown the sbs2003 box (windows 2008 domain controller still running).
Thanks for trying, but it did not solve the issue. I still have the usrlogon.cmd. I have also discovered that I have netlogon 5788 and 8789 errors in the event viewer of the terminal server since I shutdown the sbs2003 box (windows 2008 domain controller still running).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Good to know. My next move would have been to check licensing.
ASKER
Problem solved, My Docs and moving TS to new OU and blocking policy of old DC solved the issue.
Try this. Goto regedt32 on the server to HKeyLocalmachine\Software\
It should look like C:\Winnt\system32\UsrLogon
/F