+1 You can also make a copy,, modify it and add your own tags copy the tatto step and call your scrip.
I also like the idea what others do (cant remember names), create an executable so its easy to inventory On Oct 1, 2013 7:52 AM, <[email protected]> wrote: > MDT already tatoo’s the registry.**** > > ** ** > > http://systemscenter.ru/mdt2012.en/ztitatoowsf.htm**** > > ** ** > > ** ** > > *Christopher Catlett* > > Consultant | Detroit**** > > *[image: MCTS_2013_small]* > > * * > > *Sogeti USA* > > Office 248-876-9738 |Fax 877.406.9647 **** > > 26957 Northwestern Highway, Suite 130, Southfield, MI 48033-8456**** > > www.us.sogeti.com**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Daniel Ratliff > *Sent:* Tuesday, October 01, 2013 10:45 AM > *To:* [email protected] > *Subject:* RE: [MDT-OSD] Tagging MDT/OSD build with a version number**** > > ** ** > > Yes, I run a PowerShell script to grab the date/time and brand that in the > registry. I do it in the image itself as well as at deployment time.**** > > ** ** > > > http://www.potentengineer.com/using-powershell-to-set-osd-task-sequence-variables/ > **** > > ** ** > > *Daniel Ratliff* > > ** ** > > *From:* [email protected] [ > mailto:[email protected] <[email protected]>] *On > Behalf Of *Stephen V Jameson > *Sent:* Tuesday, October 01, 2013 10:41 AM > *To:* [email protected] > *Subject:* [MDT-OSD] Tagging MDT/OSD build with a version number**** > > ** ** > > I have a requirement to tag the MDT/OSD client installation with some sort > of version number. How has anyone else done this? > > Steve**** > > > The information transmitted is intended only for the person or entity to > which it is addressed > and may contain CONFIDENTIAL material. If you receive this > material/information in error, > please contact the sender and delete or destroy the material/information.* > *** >
<<image001.jpg>>
