Jump to content


destiny31

OSD VSTASP1 following the guide, trouble with PXE-Point in SCCM

Recommended Posts

i following you excellent guide (Vista SP1 OSD SCCM) and are struggeling in part 1.

 

firstly i installed the WDS role on server 2008, reboot and make everything analog to your guide and the screenshots. (wds pxe timing, ports etc.)

 

after install the MDT package at the same machine and do the "integration into sccm button", i click the pxe-point button (mdt) to configure the .vbs, but there is a red sign

on the screen, that tell me "no correct installation"....

 

 

any hints about that? because i can do a new pxe-point inside the sccm, but with no functionality.

 

sorry for this bad english :-)

Share this post


Link to post
Share on other sites

remove the PXE filter and add it again, if its windows server 2008 start the action by right clicking and choose to Run the MDT PXE filter with ADministrative priviledges

Share this post


Link to post
Share on other sites

there is one more proplem with the (WDS and PXE-Point) section.

 

finishing your "OSD Vista" guide with all steps, many thanks for that, but when i start the target computer,

 

the SCCM 2007 R2 machine is running, logs are well, and the target computer get a IP from it, but after this the PXE message said:

 

"Proxy DHCP service did not reply to request on port 4011" ...

 

any suggestions?

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...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.