Client Management Blog by Dominik Heinz - All Comments

re: SCCM PXE Network Boot Process

skyman — Fri, 26 Apr 2013 19:36:21 GMT

The handshake is flawed.

Everything below the following line look rushed and not correct, must have been a last minute deadline and nobody verified this as correct.

"DHCP Ack

· Server ack from PXE server including options 66 and 67 (send WDSNBP) "

Since when do DHCP servers send files...or did they forget to mention this was sent via tftp?

re: Deploying Custom .MSU Updates with SCCM (and SCUP)

CoreyC — Tue, 19 Feb 2013 03:00:54 GMT

Was there ever an answer as to why DISM is used instead of WUSA?

re: SCCM Report Cannot be Displayed–Error 500

sccm reports error 500 — Mon, 04 Feb 2013 20:45:20 GMT

this poet was very helpful, it worked for me but I make changes in "Default Web Site / ASP / limits Properties / Response Bufferung Limit. and the SMSReporting-SiteName / ASP/limits Properties / Response Bufferung Limit.

now no more error 500.

re: Deploying Custom .MSU Updates with SCCM (and SCUP)

OdgeUK — Thu, 22 Nov 2012 11:58:04 GMT

My Bad. Cab file, when run properly using DISM, will populate the Installed Updates Control Panel details.

re: Deploying Custom .MSU Updates with SCCM (and SCUP)

OdgeUK — Wed, 21 Nov 2012 13:54:19 GMT

Make sure that you populate the namespace field (above the wmi query) with root\cimv2.

re: Deploying Custom .MSU Updates with SCCM (and SCUP)

OdgeUK — Tue, 20 Nov 2012 09:50:35 GMT

Further to the above, it seems that if you use iExpress to install your newly created EXE, it will remove the CAB file once run. The problem with this is that if you then need to uninstall the update, you need to run DISM remove-package against the Cab file, which no longer exists. Any workaround?

re: Deploying Custom .MSU Updates with SCCM (and SCUP)

OdgeUK — Mon, 19 Nov 2012 14:00:42 GMT

Have noticed that when installing Updates using this method, no entry is place under "Installed Updates" under Control Panel> Programs and Features. I guess that's something to do with the work-around method of installing using DISM? Can make it a little tricky to prove that the install is completed once the EXE is run and not ideal for support people who use that GUI to confirm if updates are installed.

re: SCCM PXE Network Boot Process

sipp — Mon, 08 Oct 2012 15:44:37 GMT

What if the DHCP Option 250 is missing from the DHCP Request going to the SCCM PXE SP? What could be the reason for this?

We currently have this issue at one location. The SCCM PXE SP is used successfully at other locations as well as the client.

Any help is appreciated....

re: SCCM PXE Network Boot Process

James McDonald — Fri, 14 Sep 2012 15:58:09 GMT

What if everything goes well, until it tries to download the pxeboot.n12 file, and all it does is this:

TFTP Download: smsboot\x64\pxeboot.n12

over and over, and it never downloads.

re: DHCP & PXE basics

Santosh Bhandarkar — Sun, 02 Sep 2012 09:20:48 GMT

Nice article