Windows Server 2008 Thread, Windows 2008 File Share with xp sp3 clients in Technical; Due to a unrecoverable hardware failure on one of our w2k3 DC's-hostname-Matthew(not the operations master) which also was the FileShare(G: ...
11th October 2011, 07:35 PM #1
- Rep Power
Windows 2008 File Share with xp sp3 clients
Due to a unrecoverable hardware failure on one of our w2k3 DC's-hostname-Matthew(not the operations master) which also was the FileShare(G: drive user home folders) server, I used RoboCopy(with parms to include the security) to copy the file share folders to a new server running w2k8 (standard edition)-hostname-Thomas. Changed the login scripts to point to Thomas.
The resulting new issue is that it takes several minutes to populate the WinXP desktop icons. The bootup and domain login process goes quickly. During the 7-10 minutes of waiting the desktop screen is blue with no icons. When the desktop icons do finally load, on My Computer the mapped drives (on Thomas) defined in the login script are missing. On the same single segment network Windows7 machines display the deskop and mapped drives quickly. A reboot of Thomas(w2k8) solves the slow startup process for 24 hours sometimes. Sometimes a couple days, other times maybe 12 yours before needing to reboot.
I have since built a new w2k8r2 server as the new DC with the operations masters. Demoted the old w2k3 DC and removed DNS from it. DNS seems to be working ok, as the Win7 desktops have no issues. Using local profiles on the clients.
Have a couple basic/simple Group Policies that worked fine before restoring the home folders from the old w2k3 server Matthew to the new w2k8 server Thomas.
Thanks in advance for any help.
St. Mary's School
12th October 2011, 03:19 PM #2
From how I read it, your domain was replaced and the primary issue is the load times for users on XP machines now. If this is the case, I would be surprised to see a newly imaged XP machine freshly joined to the domain have long load times (besides the initial local profile creation). If this solves the issue, you then know it's the issue of the local machine and not your DC. Best of luck to you, I think we've all been in a mysterious situation like yours before.
By Frazer in forum Windows Server 2000/2003
Last Post: 30th July 2010, 01:36 PM
By SYNACK in forum Windows 7
Last Post: 29th April 2009, 03:27 PM
By cookie_monster in forum Windows
Last Post: 13th August 2008, 05:32 PM
By noser in forum Windows
Last Post: 6th June 2008, 12:39 PM
By maschenazi in forum Windows
Last Post: 22nd May 2008, 02:27 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)