I create my .WIM file via MDT and deploy it as part of an SCCM task sequence. I just discovered ZTITattoo, but I'm having problems putting it to good use because the information in HKLM\SOFTWARE\Microsoft\Deployment 4 reflects the settings that were in effect when the .WIM was created. Not when the OS was deployed via SCCM. Can I run ZTITattoo again? If so, how?

why not just create your own tattoo, a simple script to set a reg key is all you need and the reg settings can change every version of the image you release My step by step SCCM Guides I'm on Twitter > ncbrady

You know, sometimes I just can't see the forest for the trees! I'll give that a whirl!

Easier said than done. I took a script that would dump all of the task sequence variables to a text file and added that to my script so that I could determine what was going on. I was able to output these variables and their data to a text file, but now I want to up the ante and write a couple of these values to the registry. I want to, but I don't know what I'm doing. I have modified the script so that will (or at least I thought it would), update the registry, but its not working. The real source of my confusion is that this program runs in a an environment that I can't really see or touch (can I?). How can I debug this when it has to run during the task sequence? BTW - this is my script: Dim WshShell Set WsShell = WScript.CreateObject("WScript.Shell") Set env = CreateObject("Microsoft.SMS.TSEnvironment") vstrRegKey = "HKLM\SOFTWARE\Hunt\Windows 7\" WshShell.RegWrite vstrRegkey & "InstallDate",DATE,"REG_SZ" For each v in env.GetVariables If v = "_SMSTSPackageName" Then WshShell.RegWrite vstrRegKey & "PackageName",env(v),"REG_SZ" End If If v = "DeploymentType" Then WshShell.RegWrite vstrRegKey & "DeploymentType",env(v),"REGSZ" End If Next

pressing F8 during deployment will allow you to debug your session (command prompt) you can even type Regedit to verify the registry settings are taking place (or not) during that time, what i would do is try running the script using psexec as system to see what errors if any are output on the command line My step by step SCCM Guides I'm on Twitter > ncbrady

I'll try F8 - I'll try anything! BTW - I re-ran my script via my Task Sequence and had direct its output to a text file. All it the text file contained was; Microsoft (R) Windows Script Host Version 5.8 Copyright (C) Microsoft Corporation. All rights reserved. I'll let you know what comes from my experimentation.

As it turns out, I have fat fingers, or I just can't type and/or read. Here is the finished product: Dim WshShell Wscript.Echo "Creating the WScript Shell" Set WshShell = WScript.CreateObject("WScript.Shell") vstrRegKey = "HKLM\SOFTWARE\Hunt\Windows 7\" WScript.Echo "vstrRegKey = " & vstrRegKey WshShell.RegWrite vstrRegkey & "InstallDate",DATE,"REG_SZ" WScript.Echo "Wrote to " & vstrRegKey & "InstallDate" Set env = CreateObject("Microsoft.SMS.TSEnvironment") WScript.Echo "Created the Microsoft.SMS.TSEnvironment object" For each v in env.GetVariables WScript.Echo "Scanning the TS environment" If v = "_SMSTSPackageName" Then WScript.Echo "_SMSTSPackageName = " & env(v) WshShell.RegWrite vstrRegKey & "PackageName",env(v),"REG_SZ" End If If v = "DeploymentType" Then WScript.Echo "DeploymentType = " & env(v) WshShell.RegWrite vstrRegKey & "DeploymentType",env(v),"REG_SZ" End If Next I also discovered that it is important to wait until the system has booted to the full OS before tattooing. Just when I thought I had nailed it, I discovered that I had modified the WinPE registry and my tattoo was gone as soon as the system rebooted.

nice result, good work and thanks for sharing are you doing the tatoo at any specific stage in your ts ? My step by step SCCM Guides I'm on Twitter > ncbrady

After the "Setup windows and ConfigMgr" task runs, I take care of a little housekeeping. I set the SMSErrorDialogTimeout to infinity (actually 9999999), then Use Toolkit Package, Gather Local Data, then tattoo the system. Of course as will everyting else I do, I'm starting to second guess myself. Previously, I would create an executable named ImageVer.exe. The file version was always set to match the task sequence version. This way I have something I can inventory via SCCM. I'm thinking of adding ImageVer.exe back into my task sequence. If I do, I doubt I'll ever use the tattoo!