We have SEP server running on a Server 2003 x86 box, running version 11.0.4202.75 and our clients are on the same version.
We use group policy to push out "pushprinterconnections.exe" for use with print management on a Server 2003 R2 box. This works for about 50 client PCs, but fails on about 10 of them. The error logs on the failing PCs are follows:
Event ID 1030:
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
followed by
Event ID 1058:
Windows cannot access the file gpt.ini for GPO cn={73A559D8-A303-406A-A7D4-EEA225B76119},cn=policies,cn=system,DC=(domain name),DC=corp. The file must be present at the location <\\(domain name)\SysVol\(domain name)\Policies\{73A559D8-A303-406A-A7D4-EEA225B76119}\gpt.ini>. (The specified network name is no longer available. ). Group Policy processing aborted.
I found the following article:
http://social.technet.microsoft.com/Forums/en-US/winserverGP/thread/ff7a6be8-28d0-4100-bf38-8087fbac6f6d
and tried uninstalling the symantec client. Bam, works instantly on the PC's that had failed with the formerly mentioned Event ID's.
Any idea why this is happening?
We've also been having a lot of problems with users not having their drives mapped when they login, the home drive and a few other network drives that we map via login script will occassionally just not map. I had no clue what could've been causing this until now- now I think it might be the SEP client.
Any info on this issue would be greatly appreciate, thank you.