I have been using the 'debugprint' command to troubleshoot some NSL
Windows scripts, and it's actually quite difficult to interpret the
output sometimes due to the fact that you will have multiple copies of
the script being launched simultaneously by SecureLogin and any debug
messages you see may be out of order.

To help identify which instance of the script is doing what, I first
initialize a random local variable at the start of the script, and add
this to the output of every 'debugprint' command.

So the first few lines of the script are similar to this:

Local ?ThreadID
RestrictVariable ?ThreadID threadpol
ChangePassword ?ThreadID random

This will generate a local variable for per instance of the script
following my password policy. I tend to set the policy to be an 8
character alpha-numeric so that it's fairly easy to differentiate the
various scripts' output.

I then add the variable to the 'debugprint' command such that it has
the following format:

DebugPrint "[" ?ThreadID "] - <whatever helpful debug message you want to see goes here>"

Hopefully you will find this as useful as me !

clovercne's Profile: https://forums.netiq.com/member.php?userid=1699
View this thread: https://forums.netiq.com/showthread.php?t=42694