Unable to build new machines through SCCM on a new site

Jump to latest Follow Reply
C

Cornholio

Ars Scholae Palatinae
812
  • #1
    We have a multi site network across various wan networks. Currently the 4 main sites work fine. We can use the SCCM OS deployment process to build new machines on all the networks without issue with either PXE boot or the USB build media.

    We have recently brought online a few more sites via VPN (rather than leased line) and we are trying to build machines there, but its failing claiming that theres No Task Sequence available.

    This is building onto the same machine, with the same build stick that works on a known good site.

    We have checked the boundary IP ranges, and the settings in the build stick, and distribution points.

    There's also nothing being blocked on any of the firewalls as far as we can see.

    Does anyone have any suggestions where else we might look?
     
    T

    tremere98

    Smack-Fu Master, in training
    29
  • #2
    It’s been a really long time since I’ve been into the weeds with configmgr but 2 things come to mind -
    1. Generally when I can’t get something at one of our vpn sites it’s thanks to my colleague not adding those particular vlans/routes to that vpn interface. May be worth a check if you happen to have a Steve on your team too, or happen to have your CM environment on its own vlan.

    2. In addition to the boundaries in sccm I believe the subnets for your sites need to be added into Active Directory Sites and Services also.

    Again, it’s been a while but I know I’ve run into both over the years.
     
    T

    tremere98

    Smack-Fu Master, in training
    29
  • #4
    Well, that’s good news at least. We have vlans coming out of our ears so every once in a while some app won’t work on a new remote site and sure enough, that subnet isn’t in the ACL.

    Something else to check - I feel like we had to add some IP helpers to some of our subnets so they could properly PXE. And when I say “some” I mean every subnet that wasn’t the one the PXE server is sitting on. Presuming your remote has a different range that could be your issue too.
     
    C

    Cornholio

    Ars Scholae Palatinae
    812
  • #7
    So there was no IP range for the affected subnet in AD so I have added one (along with the other new remote sites) however it doesnt appear to have fixed the issue.

    Do i need to do something in sccm to tie it together? I would have though that was what the boundaries themselves are for? Do you think its worth recreating the boundaries?

    Do i need to re-run a detection process of some kind? Maybe reboot sccm or restart a service?
     
    T

    tremere98

    Smack-Fu Master, in training
    29
  • #9
    Well, unfortunately we aren’t coming up with much else that it could be. Most of our headaches with remote site deployment have been to do mainly with being able to pxe at the smaller sites - we rolled distribution points at our bigger remotes. If the Sccm server/DP can be seen at the remote and you’re bypassing pxe completely with usb booting you’ve taken care of most of those headaches. Sorry I couldn’t be more help on this one.
     
    You must log in or register to reply here.
    Jump to latest Follow Reply
    Jump to latest Follow Reply