|
In Active Directory, you right-click the domain, go to Properties, click the Group Policy tab. Here you can edit a group policy object, let's say we edit the default domain policy. If you expand User Configuration, then expand Windows Settings, then click 'Scripts (logon/logoff)'. If you double-click Logon you see the Properties page. You click the Add button, browse to \\server\netlogon where you select your login batch file, let's call it logon1.bat. Please note that within this netlogon folder you also have your kixtart files. Within the login batch file you have the command kix32.exe system1, with system1 being your kix file. When a user logs onto the domain the black batch file window appears with the error "Script error: failed to find/open script !.
So, you go back to your logon1.bat and try the following variations of calling the script. Let's say you tried
\\servername\netlogon\kix32.exe \\servername\netlogon\system1.kix
kix32 \\servername\netlogon\system1.kix
kix32.exe \\servername\netlogon\system1.kix
%0\..\kix32 system1
Basically, these and every other variation under the sun that you could come up with. And still, the error persists. Please note that \\servername\netlogon is a valid directory.
At this point you start to think to yourself if you're lacking an understanding of active directory/group policy. This same logon1.bat file was successfully used on a Windows NT domain. If you had gone into User Mgr for Domains for the NT domain, selected a user and looked at the profile tab you would see logon1 as the batch file to execute.
Can anyone tell me what this person has done wrong? This person being me, of course! I would appreciate a walk though of what it takes to execute a kix32 script in Active Directory utilizing a BAT (batch) file.
| 
