1)We have One single AD Forest and Single Domain, and DC & SCCM Servers are in DMZ Zone with network 10.x.x.x. and clients are in 192.168.7.x & 192.168.8.X. While setting up boundaries in SCCM, i defined ADSite it's working but incase if i defined IP subnet i have to include all the network or just 192.168.7.x & 192.168.8.X. 2)Confusion One more, client compare their IP address with site boundaries configured in the hierarchy . If suppose i am using AD Site bpundaries, then how this process happens since i am using single AD Forest and Single Domain Model

Hi,1. You need to provide the subnets you want to manage with ConfigMgr. If these subnets already are included in the AD site then there is no need to define them again.2. Client will look at the subnets that belong to that AD site. If there is a match the client will be assigned to the site hosting the boundary.Most important with boundaries is that you don't make any overlappings in them between the multiple sites. Follow me through my blog and Twitter!

Hi, As i wrote in question no 2 . i am using single AD Forest and Single Domain Model & Single Site & ALL DC's are in DMZ Zone , then how it is identifying IP Subnet , If i want to identify, how i will check it. When i Open AD site and services, i Don't see any subnet address, just Single Site with name "Default-First-Site" which ofcourse is my domain model

Default-First-Site is just the site name. In AD Sites & Services you can browse to the folder Subnets. Here you can create new subnets and assign them to your Default-First-Site.These subnets will then be used as the boundary for the site.Follow me through my blog and Twitter!

Jannes thanks for replying, As you said, I need to add subnet in AD Sites & Services, then i have to add all subnets of client and also the subnet of DC's or just the client subnets.

Maybe in your case it is more easy of just adding all the subnets directly as boundary.The technology used between AD site as boundary or subnet directly is the same. One of the advantages with AD site is that when the subnets are changing you only have to edit the subnets in AD Sites & Services. Follow me through my blog and Twitter!

I mean in my previous reply, in my AD Sites & Services & single Site , i haven't yet added any subnet. So i have to add all subnets of client and also the subnet of DC's or just the client subnets. When i checked boundaries in System managemnt container, all the boundaries are published as Roaming boundaries & mSSMSsiteBounadries=<notset> i am getting, Is this due to not adding any subnet in AD Sites & Services

TWO SITES, Site A & Site B , Both Sites DC’s are in DMZ zone Clients are behind the firewall in both the sites Site A Subnet Address Defined in AD Sites & Services 10.1.X.X, client Subnet Address 192.168.7.X, 192.168.8.X Site B Subnet Address Defined in AD Sites & Services 10.2.X.X, client Subnet Address 192.168.1.X, 192.168.2.X According to Autosite assignment, “During client deployment, clients that are configured to use auto-site assignment compare their own IP address with the site boundaries configured in the Configuration Manager 2007 hierarchy. When the client IP address falls within the boundaries of a site, the client is automatically assigned to that site.” So if client compare their IP address with AD boundaries which will be actually subnet boundaries, will it be successful Suppose ConfigMgr site in Site A with AD Boundary defined & client with address 192.168.7.68<!-- [if gte mso 10]> <mce:style> compares then what will happen.

Hi,There is no need for double posting: http://social.technet.microsoft.com/Forums/en-US/configmgrgeneral/thread/d0059c1b-48e5-4602-a47c-bae060963869Like I already said, just add all the subnets directly to make it less confusing. In your example the client with 192.168.7.68 will belong to site A. Follow me through my blog and Twitter!

Jannes, I got that if i add all client subnet as bounadaries, it will be successful. i am very much clear with it. I am sorry if am annoying you but here i am giving a different scenario, subnet boundaries are different than client actual ipaddress

Are you saing that the subnets 192.168.X.X are not defined in AD? Or are you saying that AD site "Site A" has three defined subnets: 10.1.x.x, 192.168.7.x and 192.168.8.x?

Eirik, Yes, subnets 192.168.X.X are not defined in AD. DC's DMZ Zone:10.X.X.X Client Subnets: 192.168.7.X, 192.168.8.x They all are connected through firewall, I have defined Only 10.X.X.X as subnet.

....

You have to define the client subnets as boundaries in ConfigMgr.There is nothing wrong with mixing AD sites and subnets as boundaries. In your case it seems like you need three boundaries:1: AD site, Default-First-Site2: Subnet, 192.168.7.0/255.255.255.03: Subnet, 192.168.8.0/255.255.255.0If you only want to manage clients and nothing in the DMZ then adding boundaries 2 and 3 is good enough.

Clients that are not within defined boundaries are not managed in any way. Why not? You can even have a ConfigMgr site without any boundaries defined at all and it will work (with limited roaming and content location functionality).

Ok, I see your point, I've removed that sentence now.

Eirik I am using only AD site boundaries in my case, clients are getting discovered and they are getting installed also(Client push/autosite assignment), only 10.X.X.X is added as subnet in AD site and services. but then how auto site assignment is getting succeed. Since its compare ip address with Adsite boundary

The discovery processes do not relate to boundaries. When it comes to automatic site assignment, that's another story. This only happens if a client is included in the site's boundaries. This leaves two scenarios in your case: Either the client subnets are defined as boundaries, directly or through the AD site, or the client is assigned to a site by being defined in the installation properties.

BTW, I copied this from microsoft.com. It might be relevant to you case:If a domain controller or client has an address that is not included in any site, then the client or domain controller is contained within the initial site created(Default-First-Site). All activity is then handled as though the client or domain controller activity is a member of Default-First-Site, regardless of actual IP address or subnet location.

Special Thanks Eirik for replying and finding information , so incase of autosite assigment and Default-First-Site, it is being treated as same subnet regardless of Client & ADsite subnet. And could u send a link from where u got this information.

Of course :)Auto asignment: http://technet.microsoft.com/en-us/library/bb681005.aspxAD-sites: http://www.microsoft.com/windows/windows2000/en/advanced/help/sag_ADsite_concept_1.htmThe last one is written for Win2k, but it's still treated the same way.