|I've seen people remove the ability for the computer to hold a network share to remove the admin shares. If that's the case, using a startup script won't do anything.|
I've seen people use startup scripts to remove the shares. While I no longer remember what order, if any, Windows applies its startup scripts, I'd assume it would apply the GPO supplied scripts last. If that's the case, a startup script wouldn't do anything.
Windows 2003 introduced a registry key to disable the admin shares. This would be the preferred way to kill the shares, but would require the environment to be post Win2K3 (ie Vista and Win7).
Your first step should be to figure out how he disabled the shares. Once you know, you can undo it.
If he used that registry key, thaw the system and remove the key. The removal can be scripted.
If he disabled the required services, you'll need to thaw the system, restore the network providers / services. The enabling can be scripted.
If he has a local startup script, you'll need to thaw the system and delete the script. The deletion can be scripted.
If he's pushing a script though GPO, make two computer groups. In one group, leave the offending startup script. Any PC you put in this group will have their admin shares deleted. In the other group, remove the script. Any PC you place in this group will have their admin shares restored after they reboot. This can be scripted, but it's probably faster if you just use the GUI.
EDIT: Also, I've seen people use the firewall. It doesn't kill the share so much as access to the share. Firewall settings can be scripted, but the workstation would need to be thawed.
How To Ask Questions The Smart Way