During the logon process, the NetLogon folder is in the System PATH, thus, Kix scripts run without issue. After logon, this folder is not in the path.

There's no issue with @SCRIPTDIR if you're calling Kix locally but specifying the path to the scripts.. It's the directory where you called kix from, not where Kix or scripts are. For that, you need @STARTDIR.

Try running from the netlogon share directly:
\\DOMAIN\NetLogon\Kix32 \\DOMAIN\NetLogon\MainKixScript.kix
where "DOMAIN" is your local AD domain name.

My login script dumps info when debug mode is active, and you can see the results of these macros:
During logon:
 Code:
       Logon Mode: 1
           Laptop: 0
     Detected O/S: Windows 8 Professional Edition / Version 6.2
        Privelege: USER
  Local Privelege: User
        ScriptDir: C:\Windows\system32 / C:\Windows\system32
         StartDir: \\Ihwiadcp01\netlogon
CMD Prompt after logon:
 Code:
       Logon Mode: 0
           Laptop: 0
     Detected O/S: Windows 8 Professional Edition / Version 6.2
        Privelege: USER
  Local Privelege: User
        ScriptDir: \\itcg\netlogon / \\itcg\netlogon
         StartDir: \\itcg\netlogon
This should properly set the @STAPTDIR macro because you're calling kix32 from the same place as your scripts. The @SCRIPTDIR isn't even relevant during logon! Note that @SCRIPTDIR is effectively the same - when logging in, it's the specific DC that processed the logon, while run later, it's the DOMAIN path (Any DC).

Thus - STARTDIR is what you should use to call your scripts from the NetLogon folder. \:\)

Glenn
_________________________
Actually I am a Rocket Scientist! \:D