I have an encrypted (KiXCrypt) script, BUSINESS.EXE, which is located in the NETLOGON share of an NT domain and executed via the user's Login Script Name path. No problem there, it works just fine. But, because all of the users are being migrated from the NT domain to a separate 2000 domain, I have to comply with the other administrators' requirement of running the executable from a batch file instead of the Login Script Name path. The executable and the KIX32.EXE files are now located in the NETLOGON\COB share of the new domain. According to the 2000 administrators, the commandline for the script is simply BUSINESS.EXE.

Since the script isn't working at all, what can I do to get it working? Using the commandline, KIX32.EXE BUSINESS.SCR, really isn't an option. I need to maintain the advantage of encryption as a form of security.

Any thoughts?