Take a look at this
http://trevorsullivan.net/2012/11/14/vbscript-export-task-sequence-variables/

You write the output to a text file >> file.txt

On Tue, Mar 15, 2016, 2:04 PM Pollard, Eric <[email protected]> wrote:

> So I think I figured out the cause of my issue, however I have no idea why
> it is happening.  I am using the same iso image to boot both servers to be
> imaged.  So it looks like when a G6 is booted it doesn’t set *SMSTSMP TS
> environment variable *correctly. Does anyone know how to export the
> variables being set while in WinPE so I can possible setup a custom
> variable on the boot image to fix this problem?
>
>
>
> Log from G7+
>
>
>
> Loading Media Variables from "E:\sms\data\variables.dat"
> TSMBootstrap   3/15/2016 4:58:17 PM   1096 (0x0448)
>
> Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
> TSMBootstrap   3/15/2016 4:58:17 PM   1096 (0x0448)
>
> *Setting SMSTSMP TS environment variable         TSMBootstrap   3/15/2016
> 4:58:17 PM  1096 (0x0448)*
>
> Setting _SMSMediaGuid TS environment variable             TSMBootstrap
> 3/15/2016 4:58:17 PM   1096 (0x0448)
>
>
>
> Log from G6
>
>
>
> Loading Media Variables from "D:\sms\data\variables.dat"
> TSMBootstrap   3/15/2016 4:22:25 PM   1668 (0x0684)
>
> Succeeded loading resource DLL 'X:\sms\bin\x64\1033\TSRES.DLL'
> TSMBootstrap   3/15/2016 4:22:25 PM   1668 (0x0684)
>
> *Setting CNG00093 TS environment variable        TSMBootstrap   3/15/2016
> 4:22:25 PM  1668 (0x0684)*
>
> Setting _SMSMediaGuid TS environment variable             TSMBootstrap
> 3/15/2016 4:22:25 PM   1668 (0x0684)
>
>
>
>
>
>
>
> Thanks,
>
>
>
> Eric Pollard
>
>
>
>
>
>
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Daniel Ratliff
>
> *Sent:* Friday, March 11, 2016 4:19 PM
>
>
> *To:* [email protected]
> *Subject:* [MDT-OSD] RE: Failed to Run Task Sequence - Either SMSTSMP or
> SMSTSLocationMPs environment variable has to be defined
>
>
>
> Oh, those are a pain. We have done some G8s and G9s and had a heck of a
> time getting static IPs to work. Found out it was a service issue in WinPE.
> You aren’t seeing the same failure, but might be worth checking.
>
>
>
> *In order to get the IP/DNS info to enter, I did have to change one thing.
> In the logs the error ‘Enter the DNS server IP address’ came back with the
> below hit:*
>
>
> *https://social.technet.microsoft.com/forums/en-US/8df4b017-6142-449d-ab97-c1b9fcfe6e1a/network-configuration-window-in-winpe-says-enter-the-dns-server-ip-address-even-if-there-is-a-dns*
> <https://social.technet.microsoft.com/forums/en-US/8df4b017-6142-449d-ab97-c1b9fcfe6e1a/network-configuration-window-in-winpe-says-enter-the-dns-server-ip-address-even-if-there-is-a-dns>
>
>
>
> *The last comment references: *
> *https://msdn.microsoft.com/en-us/library/windows/desktop/aa393295(v=vs.85).aspx*
> <https://msdn.microsoft.com/en-us/library/windows/desktop/aa393295(v=vs.85).aspx>
>
>
>
> *The logs show we were getting error 96, Unable to notify the DNS server.
> The DnsCache service was stopped, started it, and the NIC config worked!*
>
>
>
> *Net start dnscache*
>
>
>
>
>
> *Daniel Ratliff*
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Pollard, Eric
> *Sent:* Friday, March 11, 2016 3:34 PM
> *To:* [email protected]
> *Subject:* [MDT-OSD] RE: Failed to Run Task Sequence - Either SMSTSMP or
> SMSTSLocationMPs environment variable has to be defined
>
>
>
> It fails right after I manually set the IP address information and push
> next, it fails before I even get to select a task sequence.  The boot image
> is the same we use on all other servers, and no on the HTTPS for MPs.
>
>
>
> Eric
>
>
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Daniel Ratliff
> *Sent:* Friday, March 11, 2016 3:28 PM
> *To:* [email protected]
> *Subject:* [MDT-OSD] RE: Failed to Run Task Sequence - Either SMSTSMP or
> SMSTSLocationMPs environment variable has to be defined
>
>
>
> Where does it fail in the TS? Are you using HTTPS MPs? Any chance you have
> a different boot image for these servers?
>
>
>
> *Daniel Ratliff*
>
>
>
> *From:* [email protected] [
> mailto:[email protected] <[email protected]>] *On
> Behalf Of *Pollard, Eric
> *Sent:* Friday, March 11, 2016 3:23 PM
> *To:* '[email protected]'
> *Subject:* [MDT-OSD] Failed to Run Task Sequence - Either SMSTSMP or
> SMSTSLocationMPs environment variable has to be defined
>
>
>
> So I am having an odd issue trying to image HP DL380 G6 servers.  I have
> the task sequence deployed to the unknown computer group, which works with
> other generation HP servers, just not Gen6.  The computer accounts are not
> being prestaged, and the error I get in the smsts.log is below.  I am able
> to ping the MP, and also map a drive from the PE environment.
>
>
>
> Root CA Public Certs=    TSMBootstrap   3/11/2016 3:13:21 PM   1776
> (0x06F0)
>
> Missing root CA environment variable from variables file
> TSMBootstrap   3/11/2016 3:13:21 PM   1776 (0x06F0)
>
> sSMSTSLocationMPs.length() > 0, HRESULT=80004005
> (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,910)
> TSMBootstrap                3/11/2016 3:13:21 PM   1776 (0x06F0)
>
> Either SMSTSMP or SMSTSLocationMPs environment variable has to be defined.
> TSMBootstrap   3/11/2016 3:13:21 PM         1776 (0x06F0)
>
>
>
>
>
>
>
> Thanks,
>
>
>
> Eric Pollard
>
>
>
>
> ------------------------------
>
>
> CONFIDENTIALITY NOTICE: This email contains information from the sender
> that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise
> protected from disclosure. This email is intended for use only by the
> person or entity to whom it is addressed. If you are not the intended
> recipient, any use, disclosure, copying, distribution, printing, or any
> action taken in reliance on the contents of this email, is strictly
> prohibited. If you received this email in error, please contact the sending
> party by reply email, delete the email from your computer system and shred
> any paper copies.
>
> Note to Patients: There are a number of risks you should consider before
> using e-mail to communicate with us. See our Privacy & Security page on
> www.henryford.com for more detailed information as well as information
> concerning MyChart, our new patient portal. If you do not believe that our
> policy gives you the privacy and security protection you need, do not send
> e-mail or Internet communications to us.
>
>
> 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.
>
>
> 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.
>

Reply via email to