#110680 - 2003-12-19 05:38 PM
Executing an encrypted KiXtart script
|
RayF
Fresh Scripter
Registered: 2001-05-04
Posts: 6
|
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?
|
|
Top
|
|
|
|
|
#110682 - 2003-12-19 06:02 PM
Re: Executing an encrypted KiXtart script
|
RayF
Fresh Scripter
Registered: 2001-05-04
Posts: 6
|
Good point and thanks.
But you know, I tried simulating what the 2K admins did and I can't get BUSINESS.EXE to work in the NT domain using a batch file. When I run the executable from the Login script path, no problem. But when I sub in the batch file, TEST.BAT, using the commandline BUSINESS.EXE, it doesn't work. In my NT domain, KIX32.EXE and BUSINESS.EXE are in the root of the NETLOGON share. The only thing that changed in this experiment was the value in the Login script path.
|
|
Top
|
|
|
|
|
#110683 - 2003-12-19 06:32 PM
Nix my previous reply...
|
RayF
Fresh Scripter
Registered: 2001-05-04
Posts: 6
|
Actually, I screwed up. I used TEST.CMD instead of TEST.BAT in the Login Script Name path. That explained one part of why BUSINESS.EXE didn't work from a batch file within the NT domain. The other part involved adding the "%0\..\" parameter. After I changed the commandline to "%0\..\BUSINESS.EXE", TEST.BAT and BUSINESS.EXE worked normally.
However, I still have one other question. Since I tested this on 2000 Professional, what are the ramifications for XP Professional? I thought XP had a problem with "%0\..\" parameter. And if so, would the 2000 domain administrators have to test for the OSes in their batch file?
|
|
Top
|
|
|
|
#110685 - 2003-12-19 09:27 PM
Thanks again...
|
RayF
Fresh Scripter
Registered: 2001-05-04
Posts: 6
|
|
|
Top
|
|
|
|
Moderator: Jochen, Allen, Radimus, Glenn Barnas, ShaneEP, Ruud van Velsen, Arend_, Mart
|
0 registered
and 323 anonymous users online.
|
|
|
