locked
SCCM 2012 OSD - WDS RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Guys,

    I have Lab setup and trying to Deploy OS to new VM.

    Server1 : AD, DNS, DHCP

    Server2: SCCM 2012 R2 (DP not enable for PXE)

    Server3: WDS(PXE Server)

    Unfortunately Build getting failed to load, able to contact PXE server but Unable to get the DP information for content. Believe have to publish SCCM management Point in WDS. Can someone please share the details where we have to publish?

    Jaya Chandra


    Tuesday, July 5, 2016 8:10 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Any specific reason why you use Server 3 for WDS and not use DP on Server 2 with PXE support?

    I would;

    1. Drop Server 3 out and use DP PXE and WDS on server 2.

    or

    2. Install DP with PXE on Server 3.

    Tuesday, July 5, 2016 8:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    That's not directly possible or supported. To PXE boot a system in ConfigMgr, you must use a PXE enabled DP.

    Why would you not want to use your DP for this?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, July 6, 2016 8:47 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Sounds like it might be a boundary issue.  If you go to Administration > Hierarchy Configuration > Boundary Groups and bring up the properties for the Boundary Group that applies to the server your building and go to the "References" tab do you see the DP in the list of "Site system server"?  If not, add it.  Also, make sure at least one of your boundary groups that applies to the server being built has the "Use this boundary group for site assignment" checked.  Depending on your setup it might be a different boundary group used for site assignment than the one used for site system servers.
    Tuesday, July 5, 2016 8:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Any specific reason why you use Server 3 for WDS and not use DP on Server 2 with PXE support?

    I would;

    1. Drop Server 3 out and use DP PXE and WDS on server 2.

    or

    2. Install DP with PXE on Server 3.

    Tuesday, July 5, 2016 8:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Both Connor and Yannara have valid recommendations here.

    The root of your issue here is that whatever content the task sequence is looking for though is depending on your DP. The smsts.log will clearly show you which package it is looking for. Once you determine this, then you need to distribute the content to your DP and also make sure that your boundaries and boundary groups are correct.

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Tuesday, July 5, 2016 10:10 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for All suggestions!

    I'm able to deploy through SCCM DP with PXE but my intention to deploy with out enabling the PXE on DP with the help of WDS which is located on separate server

    Jaya Chandra

    Wednesday, July 6, 2016 8:42 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for All suggestions!

    I'm able to deploy through SCCM DP with PXE but my intention to deploy with out enabling the PXE on DP with the help of WDS which is located on separate server

    Jaya Chandra

    Why? :) ... do you know, that when you enable PXE on DP, it actually installs WDS role and uses it?
    Wednesday, July 6, 2016 8:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    That's not directly possible or supported. To PXE boot a system in ConfigMgr, you must use a PXE enabled DP.

    Why would you not want to use your DP for this?

    Jason | http://blog.configmgrftw.com | @jasonsandys

    Wednesday, July 6, 2016 8:47 PM