How do I control the client-push Installation of SCCM 2007 under a simple installation?

I really want to test SCCM 2007 RS in our small company but we do not have a budget for a lab. I have a server ready for this but I want to control what clients it sees at the beginning to ensure I do not "screw" up our network.

I was reading In Mastering SCCM 2007 R2 by Chris Mosby and it states on page 72 that with the simple installation for SCCM 2007 R2 "It also configures the site for automatic client-push installation, which means that any system that is discovered will have the client installed. You have no control over the installation — only that once discovered, the client will be automatically installed during the next discovery cycle."

Is there a way to control what clients are discovered and "inventoried" and when the client agent is pushed out?
LVL 1
habanagoldAsked:
Who is Participating?
 
merowingerCommented:
You can configure the AD System inventory and restrict it to a specific ou, so there will be only dicovered them. Also by default the client push installation is only initated on servers and clients within your configured boundaries. So e.g. you configure the AD discovery to scan the whole domain and your boundaries only to a specific subnet or ad site. In this case all systems will be discovered and only those installed where the boundaries are matching. See here more information about this:
http://technet.microsoft.com/en-us/library/bb632380.aspx
0
 
habanagoldAuthor Commented:
To merowinger:
Thanks for the quick response.
I just have a single AD domain. In fact it is a SBS 2003 server with 4 servers and one acting as a "BDC". (We have outgrown SBS and am planning to move to a full domain model in the future).
I guess I need to understand the "boundaries" concept. It appears to mean that in a simple installation, the whole AD is set as a boundary? If that's the case, then all systems will be affected when the SCC7 is installed? Or, do you have a chance to set up these "boundaries" after the installation is complete?
I was thinking you could deploy the client service via GPO by specifying specific OU's. That would seem to be the most logically approach to me.
I just want to get SCCM 2007 up and running without affecting all of my staff in the beginning until I am sure it is not going to produce any ill affects to my production commnuity.
If what you are telling me confirms that then, that's great.
0
 
merowingerCommented:
You have to set the boundaries manually after the installation, else you will not be able to manage a system. To boundaries define which system shell be managed.
There are different types of boundaries
- AD Site - So each system of your domain would be within the boundaries
- IP Subnet - e.g. 192.168.10.0/24 so each system with an ip in this subnet would be within the boundarie
- IP Range - e.g. 192.168.10.11 - 192.168.10.20 affects only clients in this range.
For an ip range you can also define the same ip as start and end of the range to add a single computer. But this makes only sense in your case, as you first makes some tests

Summary: You have to configure boundaries like you they need. BUT you have not to configure the client push installation option. You can also install the ccmsetup.exe within a group policy over with WSUS update deployment. Or manually by executing the exe

My suggestion:
- Disable client push installation
- Create one ip range boundarie to a single ip address
- install the ccmsetup.exe manually to see what happens
- if your sure all it's ok, include the exe in your policy to affect more clients
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Batuhan CetinCIOCommented:
"It also configures the site for automatic client-push installation, which means that any system that is discovered will have the client installed. You have no control over the installation — only that once discovered, the client will be automatically installed during the next discovery cycle."

This is not correct or is not clear. If this was how it works, we wouldn't have a chance to do PoC or Test deployments.

Client-Push Installation cannot do anything before you define a boundary and discover machines. A simple installation cannot push clients to your environment. After installation, just go to the agent installation methods and disable push installation. Then you are free to define boundaries and discover machines. You will be able to discover machines and do manual client installation by right-clicking a specific machine from the collection.
0
 
habanagoldAuthor Commented:
Thanks for the responses. I plan to proceed with the testing and will award the points based on the recommendations being proven. Should know next week.
0
 
habanagoldAuthor Commented:
I have decided to postpone the testing of SCCM 2007 for now since being in a SBS 2003 environment does not afford me much in testing scenarios. I just can't afford to risk our current production environment with too many red flags that seem to come up with SCCM 2007 without testing.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.