Built-in OSD Tattoo Steps \ Registry Edits
We currently have custom scripts that run during an OSD Task Sequence that Tattoo the registry with the computer name, technician who started the TS, date, TS name, TS Version, etc. etc. I would like to see a built in step where you could fill in these values whether it be a static value in or a variable. This built in tattoo could also already be in the hardware inventory by default so we can build collections around task sequence versions.
We also have a TS that we use primarily for a kiosk w/s and is set to AutoLogon to windows. At first we just ran a command line step and imported a registry file with the u/n,p/w, & domain. This worked but left the password in plain text in the registry. We have since started using Sysinternals Autologon.exe in the TS since it encrypts the PW. It would be nice to build in some obfuscation when entering passwords so they do not show in logs or the registry.
Thanks for your feedback, updating status to Noted.
In our 1902 release we added a new variable OSDDoNotLogCommand which hides the output of the command line action or SWD Program to mask any secrets.
Would using that variable solve your ask for hiding passwords?