Verified with the client yesterday that the updated script did work in their production environment.
So, as promised.... http://myitforum.com/myitforumwp/2013/10/15/restoring-the-smsdp-variable-in-configmgr-2012/ If the SMSDP variable is going to live on in the future, looks like the ZTIGather.wsf script will need to be modified. -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 Chris Nackers Sent: Friday, October 11, 2013 11:24 AM To: [email protected] Subject: [MDT-OSD] RE: SMSDP Variable Cool! Chris Nackers Microsoft MVP - Enterprise Client Management Email: [email protected]<mailto:[email protected]> Nackers Consulting Services, LLC From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Friday, October 11, 2013 9:04 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: SMSDP Variable Well, the modification worked in the lab. I just need to see if it works in the client environment. If so, I'll throw a blog post up about it. -Phil From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Nackers Sent: Friday, October 11, 2013 8:44 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: SMSDP Variable All know is I spent a bunch of time trying to get it to work in 2007, including talking with the MDT dev team at the time. Ultimately I quit using it, so take it as you will :) Chris Nackers Microsoft MVP - Enterprise Client Management Email: [email protected]<mailto:[email protected]> Nackers Consulting Services, LLC From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Friday, October 11, 2013 6:56 AM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: SMSDP Variable I have a client who was leveraging that variable in their CM07 environment to differentiate between sites for the purpose of customization. Basically, using the DP to determine which CS.ini to process with the Gather, as well as some other tie-ins to OSDAppTree. I wanted to verify my understanding of how and where that variable came from before I break the news that there's some re-engineering coming. Looking at the available variables, I do see that there is a corresponding _SMSTSHTTPPS10000C variable set to http://CM01.lab.local/SMS_DP_SMSPKG$/PS10000C. So, in theory, if one were to modify the ZTIGather.wsf file to reference that variable instead of _SMSTSBootImageID for parsing the DP name, it should work. I'll give it a run in the lab and see what happens. -Phil From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Chris Nackers Sent: Thursday, October 10, 2013 5:09 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: SMSDP Variable It's still there, but I wouldn't use it with any but SMS 2003.. :) It's "left-over" as far as I know... and it's been a few years, but I know looked at using it in 2007 and it doesn't work the same way that it did with 2003, so I stopped using it. What are you trying to accomplish as the total result, might be an easier way to do it? Chris Nackers Microsoft MVP - Enterprise Client Management Email: [email protected]<mailto:[email protected]> Nackers Consulting Services, LLC From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Thursday, October 10, 2013 3:55 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] RE: SMSDP Variable To update, I'm looking at the ZTIGather.log file (the script is what sets the SMSDP variable), and it's not retrieving the DP because the TS variable for the boot image doesn't provide it... _SMSTSBootImageID = PS10000C and _SMSTSPS10000C = <blank> so ZTIGather doesn't have anything to parse out. Any ideas why that would not be populating? -Phil From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Schwan, Phil Sent: Thursday, October 10, 2013 4:38 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] SMSDP Variable I know there's a %SMSDP% variable usable in MDT integrated Task Sequences that basically returns the DP that the boot image was downloaded from (which would also typically correspond to the DP the machine would be downloading the rest of the content from). Running through a TS in my lab (CM2012 SP1 CU3, MDT2012U1) it doesn't appear this variable exists or is being populated. Can somebody verify that this is still a valid Task Sequence variable? Thanks, 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> ________________________________ 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>>
