I manage a PS4 farm of about 30 Win 2K3 servers. These are VMs running on ESX 3.01.
Recently I switched over from one WI server to a new one because the original one had several issues. Since the change some users are missing their X (Shared) and Y (Common) mapped drives when logging into five of the nine full desktop servers. The drives map fine for users when logging into the other four full desktop servers.
The drives are mapped by a login script that has not changed. The login script is run through a group policy that applies to all users in Citrix. All nine servers are in the same OU.
Tonight I am planning on recreating the LHC on the five servers with issues. Is there anything else I will want to try off-hours that might fix the problem if re-creating the LHC doesn’t resolve the issue? Thanks.
I will try unjoining and rejoining some of the servers tonight. I'll post the results. Thanks.
AD issues in general are often related to DNS issues, time sync issues that effect Kerberos auth (watch time zones), ntfrs issues, etc.
You'll need to carefully go through your DNS, DS, and FRS event logs on your DCs to see if there are any issues. You should also run dcdiag, netdiag, etc to make sure there are no issues on either the DC(s) or the CPS servers.
Alan OsbornePresident (MCSE, CCNA, VCP, CCA)VCIT Consulting - Citrix/Terminal Services Remote Desktop Solutions for SMBp: 604-288-7325c: 778-836-8025web: http://www.vcit.cablog: http://www.vcit.ca/wordpress
I unjoined and rejoined the servers that were not showing all GPOs. The new GPOs showed on most of them after rejoining. However, I noticed that after a couple of hours the new GPOs are missing again. The 1030 and 1058 Event IDs return and when I run GPRESULT I get the error "the user does not have RSOP data."
I also noticed that it is NOT machine specific like I previously thought. Because some that were fine before not do not show the policies. It seems as if a reboot fixes the issue for a couple of hours or more, but then the issue returns.
I will look more closely at the DC event logs and post any suspicious errors.
Anything else I should check? Thanks.
Alan's probably right on the money with time sync issues. I would look into that.