Quantcast
Channel: Ivanti User Community: Message List - OS Deployment and Provisioning
Viewing all articles
Browse latest Browse all 3345

Re: Dealing with setup based drivers in HII

$
0
0

Per your instructions I moved the location of my script to pass 6 AuditUser and put it exactly where yours is.  Thanks for the example XML, BTW.

 

I also eliminated the WinSAT component from the script so that my unattend.xml file simply calls the wmi_model.EXE file.  So far this has not resulted in success for me.  Though I believe I know the source of the problem.

 

My script calls a batch file which is stored on a network share.  THAT batch file copies the setup files from the same share.  I'm ~98% certain that the script is not running during minisetup because I have not supplied any credentials with it which would grant access to the share.  As minisetup restarts the computer multiple times I don't see a way of providing the credentials via provisioning-I've already done that and it has no affect on minisetup.

 

I believe that I need to supply credentials in the unattend.xml file. ?Do you know how to do this?

 

I found the following information in one of the sysprep log files (attached) and it leads me to believe supplying credentials is possible within minisetup.

 

 

So that log clearly shows that minisetup is aware of credentials...

 

In terms of watching a newly provisioned machine, I see it reboot during minisetup and I see the instance where the script is supposed to run; it gets a green check immediately and then sysprep runs the OOBE thing.  My script also creates a "I'm Done" file for checking purposes; this file does not exist on a newly provisioned machine nor do the driver folders, so I know it isn't running correctly.

 

Can you tell me how to provide credentials to minisetup?  I already have a pair of variables for this in provisioning and I could slip them into the unattend file if I knew where.


Viewing all articles
Browse latest Browse all 3345

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>