Hi Daniel,  We added this security feature in the 6.x days for just this reason so that a PIT file couldn’t be stolen from a machine and run somewhere else with a user’s credentials. The credentials saved inside PIT files are encrypted with information from the local machine so they can only be used from that machine.  If you are in control of the USB stick and have some way to secure the USB stick, you may find this useful. You can run PNTSC with arguments to achieve SSO on any machine. Try this command:   PNTSC mypitfile.PIT –username myusername –password mypassword  To make this work as a clickable icon, I guess you’d have to create a CMD to launch each PIT.  Hope this helps.  Marc
I'm pretty sure I got this working ages ago but am having some issues...  I've created a custom .PIT file with PNTSC.exe to make a connection to a desktop and am embedding the login details. This PIT file needs to transfer to several machines (non managed - via USB) but SSO fails when the PIT is initiated on a device other than the one created.  You can edit the .PIT on the other devices and manually enter the password again, save and launch and Single Sign On works..  Any ideas?  UPDATE: Same issue if I include the .PIT in a sysprep image (even on the same device it was created on). - Just testing - not actually trying to do it that way.
Embedded credentials in .PIT not roaming devices