Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.Login to AccountCreate an Account

Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.

Winpeshl.ini help

madpro

Posted 13 November 2012 - 09:40 AM

I have a batch file that kicks off diskpart to ready a drive for installation, then it goes on to copy a wim from one network location to another, than applies that wim

This process works manually, so I can boot winpe, then I change drive to D: and kick of the batch file from here, diskpart runs, then closes and the wim copies over and is applied to the HDD, on reboot it boots to windows

I want to automate this process using winpeshl.ini, so so far I have

created winpeshl.ini and copied it to windows\system32 on the boot.wim
copied the batch file and diskpart text file to same folder

Now what happens is diskpart runs ok but then the process falls over at the stage where I am maping the network location, it says it cant start the workstation service

Tripredacus

Posted 13 November 2012 - 09:54 AM

I'd recommend doing your automation testing with startnet.cmd, and after you get all your commands down, switch it over to winpeshl.ini. The syntax is different for winpeshl.ini. Can you post the contents of it? (obfusicate things like server names, usernames, passwords). Also what version of WinPE are you using and what packages did you add during the build process?

madpro

Posted 14 November 2012 - 12:38 PM

I tried mapping the drive first, but get an error about workstation service not being started

I added this to the batch file but get another error saying the servbice cant be started

I assume it is because winpe hasnt fully loaded when the mapping is trying to run

The reason I say this is cause if the batch and txt file are just at the root of the winpe folder and I dont use winpeshl, when winpe has loaded it is at an x prompt, I can then do D: and run the batch file from there and it all works fine

I personally do not use winpeshl.ini for any boot images that connect to the internet. Note, the InitializeNetwork command may or may not be required. The ping is in place because not all NICs are immediately usable after being enumerated.