Ghost - problem with access to GPO location

Ok
You guys were such a great help last time lets try this.
We are using symantec Ghost version 7.
We ghost about 700 machines 4 times a year.
On this last image when users open my network places they see a shared drive to our DC01\NETLOGON. This is were they get log on scripts from so we cant take away permissions. I know a little about user profiles, default user and all users but I cant see were this is coming from. We need to be able to stop the image from placing this the image or maybe a GPO that removes it or somthing.
Any ideas?
Do you need any more info?
Ok
Thanks

 

Hi Damq,

I've moved this thread to the server system forum as this is more likely to be a server problem that an XP problem, and less likely to get lost in amongst the XP posts.

The netlogon folder needs to be accessible by each client PC so that they can access their logon scripts. However, it should usually be mapped. The mapping is probably assigned in log on script. First step I think is to check through each of the scripts and see if you can spot where the mapping is being made.

This article gives an overview of GPO including links to logon script related items:

http://technet2.microsoft.com/Windo...bf91-4b0e-96e1-e25b1a23a33d1033.mspx?mfr=true

Just spotted a typo "However, it should usually be mapped" should read "However, it should not usually be mapped "

 

Half way there

Ok
so our administrator figuered out that clearing the recent documents list clears up the mapping for the NETLOGON. But ( there is always a but) we have a few different images. We descibe them by processor 933, 1600 and 3200. the 1600 image is the one we use the most and it is the hardest to get right. The 933 is fixed with this but the 1600 still shows a mapped share in My Network Places that maps to my machines C:\ drive. This is okay because only IT have permissions to it. We found a GPO setting is supposed to hide mapped drives in My Network Places but my drive still shows.
Any ideas?
Thanks

 

A small point, but perhaps one that will stop you looking up a few blind alleys:

Drive mapping is a specific process of providing a dedicated connection to a network resource and usually assigning a drive letter to that connection. Drive mappings do not appear in Network Neighbourhood. Rather they appear as additional drives in the "My Computer" area of Windows Explorer. What you see in Network Neighbourhood is a shortcut rather than a mapping.

Unfortunately, that makes it more difficult to remove as Windows automatically generates shortcuts in Network Neighbourhood to network shares you've visited recently. You are not looking for a bit of code that is creating a mapping. Instead you are looking for system flag somewhere, that is "remembering" that the system connected to your C: drive a lot recently.