Table of Contents

WDS initialization process

Sms executive component is responsible to start all the components.

It starts pxe component, pxe component is responsible for starting WDS service, WDS uses pxe as its provider, pxe component initializes the boot images which are present under

remoteinstallsmsimagessmspkg<pkgid>,

once that initialization completes successfully, its copies the boot files out of these boot images,

these files get copied under c:windowstemppxebootfiles, and from here it gets copied to c:remoteinstallsmsbootx86 or x64 folder, if we have replicated both boot images, then we can see boot files under both the folders i.e.

1: remoteinstallsmsbootx86

2: remoteinstallsmsbootx64

PXE Boot Process

Once files get copied, we can do the pxe. Client will contact DHCP, and will also send the request to WDS as well, once both of them replies, client gets the IP.

(if WDS is not replying to the client, then client fails to get the IP),

Client gets the IP address, and it downloads wdsnbp.com (first file to download through pxe),

this file will do the architecture detection (x64 or x86),

once it is done it will see whether client has got any advertisement targeted on it,

if it did not get any advertisement, we will get error message abortpxe.com.

If it is mandatory assignment, we will see pxeboot.n12 file initiating.

If it is optional, we will see pxeboot.com file initiating

(In optional advertisement, we have to press F12 to do the pxe, and to get the boot image).

Or else if advertisement is optional then pxeboot.com will load and you have to press F12 to load boot image.

Once boot image is loaded then system will contact MP and show available task sequence targeted to it.

Share this post

Share on facebook
Share on google
Share on twitter
Share on linkedin
Share on pinterest
Share on print
Share on email