I relate to open source, which is why I publish most things here or on my site.. Just can't with this anymore since its now in use in some large financial environments.

Login.bat isn't needed - just "Kix32.exe Kixtart.kix" in the profile. The resource records will control drive and printer mapping before any commands are run, so all network resources will be available.

You can easily call Kent's script from my login script by creating a COMMAND resource record:
 Code:
[CreateOutlookProfile]
CLASS=COMMAND
PATH=\\domain\netlogon\Outlook\MkOProfile.kix
METHOD=CALL

This will call the MkOProfile kixtart script from the same environment as the login script, which means you don't have to load another copy of Kix32.exe. It assumes the script is in the netlogon share, but you can put it anywhere that the user has read access. The MkOProfile script is basically Kent's script with a little bit of wrapper logic to decide if a profile needs to be created - if not, it just exits. The MkOProfile can launch any other commands needed to complete the profile creation.

If the current version of Kent's Outlook.kix will exit if a profile already exists, then just replace the MkOProfile.kix with Outlook.kix in the above example.

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