Hi all,

I'm currently having issues while deploying a new B&C image to a VM. Everything goes well to the step "Setup Windows and ConfigMgr".

After this step, the TS tries to install the first package, but this step fails. I've done some troubleshooting and checked the logfiles, and this error is caused by the fact that the client couldn't resolve the server to get the content from.. The main cause is due to not having a correct IP Address. The NIC is assigned an APIPA address. Strange part: When I do an "ipconfig /renew", I'm given a good address immediatly.

After doing some more troubleshooting, I found that a newer bootimage  was active and this bootimage is causing this.. When I change to the old boot image ==> Everything works flaweless.

Checking devmgmt and the driver being used for NIC, I can conclude that the same driver is used. So I've no idea why this is giving me headaches.. Also, I thought the NIC driver in the bootimage was only important in a Windows PE stage..

Changelog of boot image: Added 1 driver for new HW model since WinPE wouldn't start and removed some very old drivers since the sourcecontentpath was still refering to the old SCCM server which was decommisioned during the SCCM migration. This content was not transferred to new server (my guess would be since these HW models weren't supported anymore. I haven't done this migration, so I can only guess.)

Could you guys give me some advise what I should test or what may fix my problems?

Thanks in advance!

Kr,

Sven

Hi,

What is the version of the new boot image? Check if this discussion help

https://social.technet.microsoft.com/Forums/en-US/4feead2f-cbe4-41eb-9ed8-7a0037ddf32f/why-is-task-sequence-rebooting-during-client-install-its-failing?forum=configmanagerosd

Hi,

Thanks for your reply! The version of the new boot image is the same as the old image: 6.2.9200.16384.

I've checked the forum, but can't figure out something that might help me with problems with boot images.. Am I overlooking something?

Thanks for your suggestion!

Kr,

Sven

Does anyone else have an idea what might be causing this? Thx!

Nobody who can point me in the rights direction to start troubleshooting this issue? Thx a lot in advance!

I can just keep using the old boot image, but really want to learn why this is happening.. Thx!

What OS are you building and what  version your ConfMgr is? With Windows 10, upgrade your system to R2 SP1 CU1 or SP2 CU1, and start using newest boot image from ADK 10.

With, B&C, keep your machine in workgroup. During setup and config - step, use FQDN for your primary ConfMgr site server. With workstation machines, you must use SMSMP=FQDN.site.server.domain.dom and also FSP is preffered.

Hope this helps.

Thanks for the reply, Yannara.

We're still building Windows 7 Pro x64 for this customer. So upgrading to the new ADK won't be needed.

All these settings are already configured. The problem is just that after booting in Full OS, the NIC doesn't get assigned an IP Address, so installation of applications is failing.. Even writing error logs to the server.

After doing a simple "ipconfig /renew", the APIPA address is changed to a correct IP Address. With the previous boot image, this wasn't a problem.. Any idea why?

Today I did some additional troubleshooting in the hope to fix this issue..

1. Created a new boot image (ADK 8.0) and uploaded to SCCM + used this in deployment ==> Same issue
2. Created a new boot image in SCCM (based on the clean image) + used this in deployment ==> Same issue
3. Downloaded intel drivers + added to both bootimages + used this in deployment ==> Same issue

I really have no idea anymore why the previous boot image (of which I don't know how it's been created) works in B&C scenarios...
When using the same boot image in regular deployments to physical + virtual machines ==> No issue!

After installing the OS + Configuring the CM agent, the TS would normally install the first package (Kernel Framework) which fails since no connection to file share.
It's caused by having an APIPA address... Refreshing the IP Address works instantly..

Can someone shed some light on this issue? Thx in advance!

What is your ConfMgr version? ADK 8.0 sounds weird, it should be 8.1.

APIPA does not ring a bell to me, does this mean you dont have traditional Windows server based DHCP server?

Thanks for your reply. This "problem" is happening on SCCM 2012 SP1 so ADK 8.0 (winPE 4) is still the standard tooling..

APIPA is an automatically assigned IP-address when no IP-address could be retrieved from the DHCP-server.. This happens after installing Windows in the B&C Task Sequence.

Okay, APIPA=169. now it rings a bell.

Is there differense between VM or physical Computer, how fast it will receive real IP?

I once witnessed this, that during PXE boot, in WinPE IP was not received fast enough, but this was also noticable with physical Computer, containing real OS, so the problem was purely in Network infra.

Additionally, if you would be missing NIC drivers in Boot image or B&C image, you would get empty Ipconfig results. Having 169. IP displayed tells, that NIC is present, but IP is not received.

Hi Yannara, correct it's the 169... address. No there is no difference. I've just tried to Build & Capture a physical machine in another location and this faces the same problem. Performing the same test with the old boot image succeeded..

Indeed, the correct driver is loaded since I'm having an IP Address.. Not the correct one, but ipconfig isn't empty.. Still the only difference in the bootimages are the drivers.. I"ve checked every checkbox/option in the GUI of the bootimage ==> All the same..

Any other ideas? Thx for the support btw!!

Before investingating any futher, I would highly recommend to upgrade your CM inviroment to the latest versions, including ADK 10. Apply new 10-based boot images and start playing with them.

This is rather difficult since I'm not the administrator of this environment.. I'm just the "deploy & packaging"-guy.. The administration is in the hands of another team. Upgrading to SP2 (since R2 isn't possible due to license restrictions) would only be done when there is an official business trigger: moving to w10 since this needs the new SP2 + ADK 10..

Any other suggestions besides this?