I tag both the core build and capture image and the deployment with a build marker. For both, I use a simple command to create the build marker.
Example: cmd /c echo "Buildmarker" >> %windir%\Options\Company-%BUILDNUMBER%.exe That was for the B&C for the core image. I do it as an EXE so that it will automatically get picked up by Software Inventory without any special customizations. The EXE is prefixed with a static text to make querying easier. I use a similar command for the deployment: cmd /c echo "TSmarker" >> "%windir%\Options\TS-%_SMSTSPackageName%.exe" I use a revisioning process for both the core image and the deployment TS, so coupling the build marker with the deployment TS name, I know exactly what the deployed image looked like. I've been meaning to put together a blog post on this and just haven't gotten to it yet. Hope that helps give you some ideas. -Phil _________________________________________________________________ Phil Schwan | Technical Specialist, Enterprise Windows Services Project Leadership Associates | 2000 Town Center, Suite 1900, Southfield, MI 48075 Lync: 312.756.1626 Mobile: 419.262.5133 www.projectleadership.net<http://www.projectleadership.net/> [Description: Description: Description: Arrow email]Lead with Strategy. Leverage Technology. Deliver Results. [linkedin_logo-19x20]<http://www.linkedin.com/in/philschwan>[Twitter-Logo1-20x20]<https://twitter.com/philschwan> [wordpress-logo3] <http://myitforum.com/myitforumwp/author/philschwan> From: [email protected] [mailto:[email protected]] On Behalf Of Stephen V Jameson Sent: Tuesday, October 1, 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 ________________________________ PRIVILEGED AND CONFIDENTIAL. This email and any files transmitted with it are privileged and confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender. If you are not the named addressee you should not disseminate, distribute or copy this e-mail or any of its attachments.
<<inline: image001.jpg>>
<<inline: image002.jpg>>
<<inline: image003.jpg>>
<<inline: image004.jpg>>
