Because you're running it in ConfigMgr.  If in ConfigMgr, it populates the 
three OSD items, otherwise it populates the three Task Sequence items:

                                                
'//----------------------------------------------------------------------------
                                                '//  If this is Lite Touch, 
populate the task sequence details
                                                
'//----------------------------------------------------------------------------

                                                oInfo.TaskSequenceID = 
oEnvironment.Item("TaskSequenceID")
                                                oInfo.TaskSequenceName = 
oEnvironment.Item("TaskSequenceName")
                                                oInfo.TaskSequenceVersion = 
oEnvironment.Item("TaskSequenceVersion")


                                                
'//----------------------------------------------------------------------------
                                                '//  If this is ConfigMgr, 
populate the package ID and program name
                                                
'//----------------------------------------------------------------------------

                                                If 
oEnvironment.Item("_SMSTSPackageID") <> "" then

                                                                sValue = 
oEnvironment.Item("_SMSTSSiteCode") & ":" & oEnvironment.Item("_SMSTSPackageID")
                                                                oShell.RegWrite 
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CM_DSLID", 
sValue, "REG_SZ"

                                                                
oInfo.OSDPackageID = oEnvironment.Item("_SMSTSPackageID")
                                                                
oInfo.OSDProgramName = "*"
                                                                
oInfo.OSDAdvertisementID = oEnvironment.Item("_SMSTSAdvertID")

-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 Marcum, John
Sent: Wednesday, October 23, 2013 10:42 AM
To: '[email protected]'
Subject: [MDT-OSD] MDT tatoo missing "Task Sequence Name" data

What would cause the Task Sequence Name, Task Sequence ID and Task Sequence 
Version to be missing from the MDT tatoo info?

[cid:[email protected]]


________________________________
John Marcum
Sr. Desktop Architect
Bradley Arant Boult Cummings LLP
________________________________


________________________________

Confidentiality Notice: This e-mail is from a law firm and may be protected by 
the attorney-client or work product privileges. If you have received this 
message in error, please notify the sender by replying to this e-mail and then 
delete it from your computer.
________________________________

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.png>>

<<inline: image002.jpg>>

<<inline: image003.jpg>>

<<inline: image004.jpg>>

<<inline: image005.jpg>>

Reply via email to