hi, thanks for the note. i didn't explain myself very well, did i.

i have had a script kicking off from the Policies\Windows Setting\Scripts\Logon for quite a while. ever since Win7 we've slowly had workstations unable to run this. not all Win7 machines and very random on which ones it doesn't work on. my temporary fix was to just drag a Shortcut to the User's Startup to get them running.
now that we have this new RODC in another branch i've really got to nail down why i can't get certain scripts to run. so in the past we just had to start kix32.exe from \\server\netlogon\kix32.exe and if no script is defined it would just look for kixtart.kix file and run it. now that i have a different name for our RODC server i need to run kix32.exe in a batch to run a script against it. if i setup a batch, that is when it complains about running it from a UNC path.
@echo off
%0\..\kix32.exe kixtart_RODCserver.kix
pause

now if i just run the \\server\netlogon\kix32 kixtart_RODCserver.kix from the Run on the local workstation it runs fine.

so in the end what can i put in the GPO to start up the above? what should it look like? should i use the Logon in Policies\Administrative Template\System\Logon instead??

Edited by swixtt (2012-11-30 04:25 PM)