+1 From: [email protected] [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Thursday, November 21, 2013 10:51 AM To: [email protected] Subject: RE: [mssms] SCCM 2007 - Control versioning
Correct. I usually create a custom directory under C:\Windows in which I store a build marker as well as a subdirectory for any install logs (msiexec verbose logs, etc.). For the build marker, I just use something like Win7x64-1.2.3.4.20130724.exe with the numeric portion being a tracked version number and the last number in the series being the image creation date/patch level. I do it as an EXE because it’s automatically inventoried by ConfigMgr without any additional configuration. Lots of ways to do it, this is just my personal preference. -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]> [mailto:[email protected]] On Behalf Of Daniel Ratliff Sent: Thursday, November 21, 2013 5:57 AM To: '[email protected]'; '[email protected]' Subject: RE: [mssms] SCCM 2007 - Control versioning There was a chain on this a few months back. I'll see if I can find it when I get in. I know Phil Schwan was doing an .exe method I think, dropping files in c:\Windows or something like that. -Daniel Ratliff -----Original Message----- From: Craig Andrew (OIZ) [[email protected]<mailto:[email protected]>] Sent: Thursday, November 21, 2013 05:20 AM Eastern Standard Time To: [email protected]<mailto:[email protected]> Subject: AW: [mssms] SCCM 2007 - Control versioning This at end of TS: REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformation /v Model /t REG_SZ /d "%_SMSTSPackageName%" /f REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformation /v LastStagingEndTime /t REG_SZ /d "%date% %time%" /f REG ADD HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\OEMInformation /v LastStagingMethod /t REG_SZ /d "%_SMSTSLaunchMode%" /f Add to Configuration.MOF, edit Client Settings and inventory with HINV to obtain the results for reporting. ****Please do not simply add this to the MOF. Create the registry keys on a test machine, use RegKeyToMOF, compile the MOF on test machine, test before activating. If at all unsure how to do this, read here http://myitforum.com/cs2/blogs/skissinger/archive/2009/04/13/mark-cochrane-s-regkeytomof.aspx http://myitforum.com/cs2/blogs/skissinger/archive/2010/12/01/march-cochrane-s-regkeytomof-v2-5.aspx Think this is the latest version: http://myitforum.com/cs2/files/folders/proddocs/entry152945.aspx #pragma namespace ("\\\\.\\root\\cimv2<file:///\\root\cimv2>") #pragma deleteclass("Maintenance_OEM_Information_64", NOFAIL) [DYNPROPS] Class Maintenance_OEM_Information_64 { [key] string KeyName; String Manufacturer; String Model; String SupportHours; String SupportPhone; String SupportURL; String LastStagingEndTime; String LastStagingMethod; }; [DYNPROPS] Instance of Maintenance_OEM_Information_64 { KeyName="OEM_Information_64"; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\OEMInformation|Manufacturer"),Dynamic,Provider("RegPropProv")] Manufacturer; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\OEMInformation|Model"),Dynamic,Provider("RegPropProv")] Model; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\OEMInformation|SupportHours"),Dynamic,Provider("RegPropProv")] SupportHours; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\OEMInformation|SupportPhone"),Dynamic,Provider("RegPropProv")] SupportPhone; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\OEMInformation|SupportURL"),Dynamic,Provider("RegPropProv")] SupportURL; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\OEMInformation|LastStagingEndTime"),Dynamic,Provider("RegPropProv")] LastStagingEndTime; [PropertyContext("Local|HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\OEMInformation|LastStagingMethod"),Dynamic,Provider("RegPropProv")] LastStagingMethod; }; Von: [email protected]<mailto:[email protected]> [mailto:[email protected]] Im Auftrag von Dean Cunningham Gesendet: Donnerstag, 21. November 2013 09:54 An: [email protected]<mailto:[email protected]> Betreff: [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 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. ________________________________ 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. ________________________________ 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.
<<inline: image001.jpg>>
<<inline: image002.jpg>>
<<inline: image003.jpg>>
<<inline: image004.jpg>>
