What about using ZTITatoo.wsf and ZTITatoo.mof, found in MDT?  You could 
modify/copy from this to make your own solution.

All the work is already done :)

Troy L. Martin | Principal Consultant
1E | Empowering Efficient IT
US Mobile: +1 678-898-6147
UK Mobile : +44 758 530 0940
[email protected]<mailto:[email protected]> | www.1e.com<http://www.1e.com/>

Facebook<http://www.facebook.com/1eglobal> | 
Twitter<https://twitter.com/1e_global/> | 
YouTube<http://www.youtube.com/1enews> | Blogs<http://blogs.1e.com/> | 
RSS<http://blogs.1e.com/index.php/feed/>
Please consider the environment before printing this e-mail

From: [email protected] [mailto:[email protected]] On 
Behalf Of Dean Cunningham
Sent: Thursday, November 21, 2013 8:54 AM
To: [email protected]
Subject: [mssms] SCCM 2007 - Control versioning

Hi!

I would like to put something in the main WIM build (Major version) and 
something in the task sequence (minor version) so I can keep track of the build 
version of the SOE.
The idea is that I can run a SCCM report against al systems and work out the 
build level of servers and workstations.
The idea is that if there is a known problem with a certain build, we can 
identify all affected machines and remediate
I was looking at doing something like this and tweak the registry at the end of 
the task sequence
http://www.techrepublic.com/blog/user-support/change-the-oem-information-in-the-windows-system-properties-panel-to-your-own/

but , out of the box SCCM does not appear to report on this.
How can I get it to report on this?
or alternatively...

How do the rest of you keep track of versions?

I want to stamp the version at the task sequence level, not at the WIM

SCCM 2007 SP2 (yes I know) and MDT

cheers






________________________________


DISCLAIMER: This is a PRIVATE AND CONFIDENTIAL message for the ordinary user of 
this email address. If you are not the intended recipient, please delete 
without copying and kindly advise us by e-mail of the mistake in delivery. 
NOTE: Regardless of content, this e-mail shall not operate to bind 1E to any 
order or other contract unless pursuant to explicit written agreement or 
government initiative expressly permitting the use of e-mail for such purpose.



Reply via email to