Jump to content


anyweb

How can I check for network connectivity before starting a task sequence in System Center 2012 R2 Configuration Manager ?

Recommended Posts

Sure,

 

Th first time I modified the boot image the Task Sequence completed the step "Setup Windows & Configuration Manager" and after that it stated "Initializing Hardware Devices" and after that "Windows is starting up" and started looping within these messages.

 

The second time around I modified the boot image, I made a copy and used that one. I modified the boot.wim file according to your guide and after that I added only the requiered drivers to be able to boot the winpe within VMware. I started the task sequence and the Task sequence completed the step "Setup Windows & Configuration Manager" and after that the Task Sequence fails with an error visible. I click ok on the error and behind the error popup message there is the window of "Initializing Hardware Devices" and after that "Windows is starting up", and after this the error pops up again. I click ok on the error to finish the TS but behind it the window of "Initializing Hardware Devices" is present and after that "Windows is starting up"....and so it continues in an endless loop: TS error, click ok on error, initializing hardware devices, windows is starting up, TS error...... the only way to end this is to shut down the machine.

 

The only difference between the first time and the second time is the error message of the TS, otherwise same behaviour. Did I manage to explain it?

 

/A

Share this post


Link to post
Share on other sites


Hi Nial,

 

Thanks for an awesome guide. I'm wondering if there is a diffence in using your technique with the registry to run custom scripts in WinPE vs using a modified unattend.xml to run custom scripts in WinPE?

 

Does it accomplish the same goal? If so would it be better to use the unattend.xml way run the .vbs script because you could then use the SCCM "add extra directories" way to add the extra files instead of manually mounting the boot image to do it?

 

 

 

 

 

Share this post


Link to post
Share on other sites

i didn't try the method you are referring to (this one ?), as i'm pretty sure it won't work with SCCM, but you are welcome to try it and let me know. This method occurs even before WinPEinit

Share this post


Link to post
Share on other sites

So this methode with a WinPE registry hack will run before the wpeinit ????

I have an issue wit deploying a Dell (E7370) without a NIC and which i boot using a Dell USB3 to Ethernet dongle.....

 

The problem is that the dongle is not recognized during startup :-(

I am wondering if I can do a devcon /rescan action which will rescan the hardware and maybe then it will work again....

 

I know that when I plug in the adapter when the starting WinPE and the "starting windows" message is appear, the hardware is detected and installation can be initiated through SCCM....

 

So i hope that a retrigger of the hardware devices (same as putting in USB3-Ethernet dongle) before wpeinit will help me out on this one...

 

Any idea ?

Share this post


Link to post
Share on other sites

So this methode with a WinPE registry hack will run before the wpeinit ????

I have an issue wit deploying a Dell (E7370) without a NIC and which i boot using a Dell USB3 to Ethernet dongle.....

 

The problem is that the dongle is not recognized during startup :-(

I am wondering if I can do a devcon /rescan action which will rescan the hardware and maybe then it will work again....

 

I know that when I plug in the adapter when the starting WinPE and the "starting windows" message is appear, the hardware is detected and installation can be initiated through SCCM....

 

So i hope that a retrigger of the hardware devices (same as putting in USB3-Ethernet dongle) before wpeinit will help me out on this one...

 

Any idea ?

 

try it and see what happens, this script kicks off

wpeinit -winpe

so yes you can try to insert your commands prior to this, or simply insert them then kick off the init again

Share this post


Link to post
Share on other sites

thanks so much for this script, works top notch (using winpe 10 x64 from mdt 2013 integrated in sccm 1606 & adk 1607 here.)

 

only suggestion would be to add a detection or an ignore button in the case of a standalone media, so that the same boot image could be used for online or offline imaging. But yeah that will help tremendously for the new models!

Share this post


Link to post
Share on other sites

this version of the script not only checks for network but storage too, and it offers a retry option on network, can you please explain why you see the need to have an ignore switch ?

Share this post


Link to post
Share on other sites

Works perfect with x86-based boot image. With x64 images black window doesnt hide

 

it will hide if you use the correct version (architecture) of windowhide.exe for those boot images.

Share this post


Link to post
Share on other sites

I am having an issue with USB NIC adapters not being recognized after the computer reboots during OSD,  this has solved the problem in WinPE since I can now disconnect the adapter, reconnect it, and hit ok to continue on, any way to apply this fix to Windows so that I can continue to check after we have left PE and moved into windows?

 

Thanks.

Share this post


Link to post
Share on other sites

Followed the instructions to the T, the script appears to work only the behaviour I get is that I'm not presented with any of the message boxes relating to it not being able to find a connection, no message or progress windows on the System Center Configuration Manager screen. So it is partially working, if I then connect the cable the Task Sequence continues. Any ideas?

Also, is it possible to add a power cable check for a laptop device to the script please?

Share this post


Link to post
Share on other sites

Hi all,

If any one still having trouble with this even after updating NIC driver please follow the steps below.

Copied boot.wim to c:\Mount (boot image that you selected for bootable media creation - Location :- Click on boot image properties and then the location will be in 'data source' tab) 

start the Deployment Imaging and Tools Environment cmd prompt (Run as Administrator)

Created new directory C:\WinPEMount\x64 and mount the boot.wim to this directory using the following command

dism /mount-wim /wimfile:c:\mount\boot.wim /index:1 /mountdir:c:\winpemount\x64

Open the folder c:\winpemount\x64 and check whether it has sms folder available. If it has SMS folder then it should have bin, boot and data folder under it. 

If one of these folders missing, you need to copy it from the bootable usb and paste it in the root of sms folder. Please follow steps below

Created a sccm bootable media usb from which task sequence can be run and image the machine successfully.

Explore the USB and copy date folder (in my case data folder wasn't available in mounted directory) and paste it to the root of the sms folder in mounted boot.wim

unmount the boot.wim using command below

dism /unmount-wim /mountdir:c:\WinpeMount\X64 /commit

copy the c:\mount\boot.wim and paste it on the location where you copied the original boot.wim from (you need to rename existing boot.wim to boot_old.wim befor pasting the new boot image)

Update the boot image to the distribution point and thats it.

PXE boot shouldn't fail on 'preparing network connection' stage now.

Happy imaging!!!!!

Edited by Muhsin

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...

×
×
  • Create New...