OS Installs From Wrong DP
My task sequence is ran from boot media. The computer is within a boundary for only one protected branch DP. This DP does not have the OS image installed on it. That is only on another DP (a standard) which uses an AD site boundary of which
the computer isn't within yet since still in workgroup. However, the installation completes fine for the OS install. Question is, why would it be getting that image from the other distribution point if its not within the protected boundary?
May 14th, 2012 10:30am
There are a couple of options for the advertisement (on the distribution points tab) related to accessing content from remote and non-protected DPs. Do you have them checked?
Free Windows Admin Tool Kit Click here and download it now
May 14th, 2012 11:04am
The following flowchart outlines the process of selecting a DP:
http://technet.microsoft.com/en-us/library/bb932150.aspx
Also, note that a protected DP doesn't mean that clients in that boundary cannot use other DPs, it means clients outside of that boundary cannot use the DP -- a subtle but very distinct difference.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
May 14th, 2012 11:40am
right, but if fallback isn't enabled, it can't run from any unprotected right? All mine are protected so are you saying it can run from another protected DP?
Free Windows Admin Tool Kit Click here and download it now
May 14th, 2012 11:43am
No, not at all. If all of your DPs are protected, then there is no real fallback path for clients. AD site boundaries may be the culprit here -- I always recommend using IP Address boundaries because you completely any ptoential ambiguity in how ConfigMgr
handles AD site boundaries.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
May 14th, 2012 12:58pm
No, not at all. If all of your DPs are protected, then there is no real fallback path for clients. AD site boundaries may be the culprit here -- I always recommend using IP Address boundaries because you completely any ptoential ambiguity in how ConfigMgr
handles AD site boundaries.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 14th, 2012 12:58pm
Jason is right. If you make IP Boundries (i use ranges) and assign them to the Site servers the client booting in the Site Servers Subnet will be pointed to that server. You can also assign ranges for a different subnet to specific Site servers. For Example
SCCMServer1 : IP Boundry Range 10.150.0.1-10.150.0.254
SCCMServer2 : IP Boundry Range 10.150.1.1-10.150.0.254
If client with IP address of 10.150.0.2 boots or is trying to access content it will connect to SCCMServer1 and will not connect to SCCMServer2. If there is a client outside both those ranges it will not access either since they are protected boundries.
So client IP 10.150.3.2 will not work, but if you add range 10.150.3.1-10.150.3.254 tp either server it will boot to assigned server.
Hope this makes sense.
May 14th, 2012 2:07pm
Jason is right. If you make IP Boundries (i use ranges) and assign them to the Site servers the client booting in the Site Servers Subnet will be pointed to that server. You can also assign ranges for a different subnet to specific Site servers. For Example
SCCMServer1 : IP Boundry Range 10.150.0.1-10.150.0.254
SCCMServer2 : IP Boundry Range 10.150.1.1-10.150.0.254
If client with IP address of 10.150.0.2 boots or is trying to access content it will connect to SCCMServer1 and will not connect to SCCMServer2. If there is a client outside both those ranges it will not access either since they are protected boundries.
So client IP 10.150.3.2 will not work, but if you add range 10.150.3.1-10.150.3.254 tp either server it will boot to assigned server.
Hope this makes sense.
Free Windows Admin Tool Kit Click here and download it now
May 14th, 2012 2:07pm
do you recommend ip address range or subnet boundaries then?
May 15th, 2012 8:57am
I use IP address range since you can put a start/stop ip address. I will elaborate a little more. If you have a larger subnet that one server will control you can add the whole range so for instance you have IP ranges 10.150.0.1 to 10.150.15.254 you could
add the start IP : 10.150.0.1 and end IP 10.150.15.254 so that any client with any IP 10.150.0-15.1-254 will connected to said server.
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2012 9:04am
Subnet boundaries are pure evil. IP Address Range boundaries always.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
May 15th, 2012 11:43am
Subnet boundaries are pure evil. IP Address Range boundaries always.Jason | http://blog.configmgrftw.com | Twitter @JasonSandys
Free Windows Admin Tool Kit Click here and download it now
May 15th, 2012 11:43am