custom oenvironment variables not carrying over

myITforum.com Community Forum

Home Forums Blogs Live Support chat Search Articles Wiki FAQ Email Lists Register Login My Profile Inbox Address Book My Subscription My Forums

Photo Gallery Member List Search Calendars FAQ Ticket List Log Out

All Forums RSS Feed Subscription:

custom oenvironment variables not carrying over

View related threads: (in this forum | in all forums)

Logged in as: Guest

Printable Version

All Forums >> [Management Products] >> Operating System Deployment >> custom oenvironment variables not carrying over

Page: [1]

Message

<< Older Topic Newer Topic >>

custom oenvironment variables not carrying over - 6/3/2008 12:52:44 PM

sounddoc

Posts: 41
Score: 0
Joined: 11/15/2007
Status: offline

Hi all,

I have a custom HTA that comes up during my pre-install phase, in fact just after the wizard.hta finishes, which queries the tech for a username that the machine is being built for. I believe I am declaring the custom made variable the right way:
<snip>
oenvironment.Item("CLIENTID") = strClientID
<snip>
The HTA closes without any errors, and I assume that the environment variable is set. I looked through ZTIUtility.vbs and found this part on line 720:

           If Item <> "" then
               SetOSDV4 sVariable, Item
           End if

From what I can decipher this says that if the item name doesn't exist in variables.xml, then create it using the setOSDV4 function.

However, once the drive format portion is done, bdd.log shows restoring environment variables, and my custom variable doesn't exist. Am I doing this correctly?

_____________________________

-P

Post #: 1

RE: custom oenvironment variables not carrying over - 6/5/2008 9:59:56 AM

sounddoc

Posts: 41
Score: 0
Joined: 11/15/2007
Status: offline

I think I figured it out on my own: I added the custom variable in customsettings.ini to the Properties section, and I'm seeing this in bdd.log:

Added new custom property CLIENTID

_____________________________

-P

(in reply to sounddoc)

Post #: 2