I'm trying to find out if there is a report or way to track revisions of an OS Image. I want to be able to track which system got which image and version. The idea being that if a system needed a fix for something that didn't work right in image we would be able to provide a retroactive fix. Hopefully the ability to create collections based on that type of information and so on. Any ideas would be greatly appreciated.

It's tattoo'd in the registry. You can report on it. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Hi David, You can Tatoo your custom image version number into the registry as part of the image installation process. The information can be picked up by the hardware inventory phase. With the information you can create reports and collections based on the image version.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

Thanks for the ideas. How would I tatoo or read from the registry to get this information? I'm searching reports and find nothing helpful.

I keep seeing stuff about MDT has a TS that will Tatoo. Is there a way to use this in SCCM?

Sure, you can integrate MDT into ConfigMgr and use the same steps.Kent Agerlund | http://scug.dk/ | The Danish community for System Center products

Just so I understand. Do I need to install MDT on the server hosting PXE and WDS? I have the MDT on my PC and I integrated from there. I don't know if that is the same thing. My setup is a single primary SCCM Server and several secondaries at sites. Each Secondary Server is the PXE Server. Does MDT need to be at all Secondaries? Also the help file give the setup but shows %SCRIPTROOT% as a variable. During the OS Deployment is this already available? Settings Name Value Command line cscript.exe "%SCRIPTROOT%\ZTITatoo.wsf" Start in Not specified Run this step as the following account Not specified

So far this is a great article for the basics of what needs to happen. http://myitforum.com/cs2/blogs/cnackers/archive/2009/12/04/microsoft-deployment-toolkit-tattoo-information.aspx I just installed the MDT on the Primary Site. I've created an MDT Package that contains the Tatoo.wsf. I'll get to see what happens soon. I'm still not sure about the %SCRIPTROOT% variable. Anyone?

The article I mentioned above talks about creating a report. Do I need to edit the sms_def.mof file to be able to collect the information created by the Tatoo.wsf?

Anyone know how to make a report after Tatooing?

Bump

Does anyone know how to make a report after Tatooing?

David, have a look in the reporting forum, especially for Sherry Kissinger's stuff, and/or checkout Sherry's blog http://myitforum.com/cs2/blogs/skissinger/ if your sms_def.mof isn't grabbing the tattoo regkeys for inventory, then no report is going to help cos the data aint in the db ;)tesgroup

Hello, I am using the Tatto script in my Task Sequence for OSD. The Tatto task is configured to "cscript.exe "%deployroot%\scripts\ztitatoo.wsf"" and set as the last task in the Statestore Task, as pr MDT default. I have not yet edited my sms_def.mof, as I first want to manually verify what kind of information that is stored in WMI & Registry before I enabling this intoy my Hardware Inventory process. When I verify regsitry at: HKLM\Software\Microsoft, I can't find the "Deployment 4" key and the relevant strings. When I verify WMI at NameSpace: root\cimv2\ and the class Microsoft_BDD_Info, only following columns are populated: - DeploymentMethod - DeploymentTimestamp - DeploymentType - InstanceKey - OSDAdvertisementID - OSDPackageID - OSDProgramName The columns below are not populated: - BuildID - BuildName - Build Version - TaskSequenceID - TaskSequenceName - TaskSequenceVersion. Does anyone know what I am doing wrong here, as I would speacially like to have the TaskSequences columns populated? Thanks for your kind effort! Best Regards Anders HorgenBest Regards Horgster

I still haven't gotten the report working. I'm uncertain as to how to modify the MOF file. I've read a ton but I've not seen any good examples on making this work. I don't feel comfortable modifying files unless I fully undertstand what I'm doing.David Jenkins

Also I feel that Microsoft documentation on the subject is short on info and even less so on examples. I'd say 90% of my understanding comes from seeing good examples.David Jenkins

Hello David, I am sorry to hear that. Suggest that you read this article: "What is a sms_def.mof and why do I care? - http://www.myitforum.com/articles/1/view.asp?id=8629" I hope that you, understand the idea and concept of sms_def.mof, as this is an definition file used by the SCCM Client, inorder to decide what WMI data shall be extracted by the Hardware Inventory process. This data is so sent back to the SCCM Database, which allows you to create reports, collections based on the data that is discovered/exported from the client's WMI. Example: Operative System version, Software Updates patches etc. For Tatto, you must modify your existing SMS_DEF.mof at your Primary Site (located at: \SMS\Inboxes\Clifiles.src\Hinv folder), and add the part mentioned for Tatto Blog: http://myitforum.com/cs2/blogs/cnackers/archive/2009/12/04/microsoft-deployment-toolkit-tattoo-information.aspx, inorder to have the SCCM Agent to report this data to SCCM DB. Once you have edited SMS_DEF.mof, SCCM will automatically push this file out to all SCCM Agents. Next time the SCCM Agent runs Hardware Discovery it will extract all the information in the WMI at NameSpace: root\cimv2\ and the class Microsoft_BDD_Info and report it back to the SCCM Database, based on the new SMS_DEF.mof. SCCM will create an new table in the SCCM Database, which you can use to create SCCM reports or Collections Queries :) In this case, SCCM will create the SQL Tables (Microsoft_BDD_Info_DATA and Microsoft_BDD_Info_HIST). The table Microsoft_BDD_Info_DATA contains current status for the client whereas the Microsoft_BDD_Info_HIST conatins previous history about this client status. Hope I have helped you and hope someone can answer on by questions above :) Best RegardsBest Regards Horgster