Deploying SCCM Part 2 with Wally Meade
SCCM Central server can handle 200k client
SCCM Primary server connected to a central server can handle
100k cleints
SHAPE \* MERGEFORMAT
![]()
Installing Clients
Supported Client Platforms
- 2k sp4
- XP SP2
- Vista
Buissness, Enterprise,
Ultimate
Supported Server Client Platforms
- Server
2k SP4
- Server
2003 SP1,2 and R2
- Server
2008
Supported Mobile Client
Platforms
Deployment Methods
- Client
Push
- Logon
installation for high rights
- No
longer support for low rights- Must be an Admin
- Software
Distribution
- Manual
New Methods
-
GPO
- Install
client as an MSI with CCMSetup.MSI
- 2
ADM Templates are provided
§
Located in Tools folder
-
SUP
- Client
distributed as a patch
Client Installation Process
All of the following will install automatically when the
client is installed. You can stage it but there is no need. The CCMsetup.exe
will asses the system and decide what is needed.
This is the sequence of installation for the client:
- CCMSetup.exe
- bandwidth aware
- Bits
2.0- 3.0
- 2.0
- windows 2000 requires a reboot
- 2.5
- XP only needs a reboot if client is installed via the SUP
- 3.0
- is built into Vista
- Windows
installer 3.1v2
- Windows
Update Service
- Core
XML 6.0 Sp1
- MSRDC-
needed to create a branch DP but it installs during the client install so
it is not needed later.
- WIMGAPI.MSI
To uninstall use CCMSetup.exe /Uninstall
Note:
- Client.MSI
can not run Solo anymore. You must run CCMSetup.exe
- Site
code is validated before installation so if it is wrong it will tell you
- If AD
is not extended then you will need an SLP other wise it is not needed.
- Client
Registration
- Mixed
mode client uses a personal certificate
- Native
mode the client uses the Server Certificate
- Client
Must get approved
- 3
ways to get approval
- Manual
- Auto
approval if on domain (Default)
- Auto
Approve all systems that make request
- Do not
change the FSP time window in production
- Install
default is now SMSSITECODE=Local Site Code
- No
longer uses remote registry
- Client
Push is published to AD
- When
you put the command line into the Client Push section it is published to
AD so you no longer need to have the command line every time you install
a client. The CCMINSTALL.exe will check AD for the switches before it
installs.
- To
turn on Verbose logging for the client install in the DDM.LOG change the
following key to Verbose Logging =1
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Components\SMS_DISCOVERY_DATA_MANAGER]
"Verbose logging"=dword:00000001
SUP Installation
- Remove
the GPO for WSUS
- Install
WSUS 3.0 SP1 on your SCCM Server
- Install
the SUP
- Publish
to AD the location of the WSUS server
- This
will allow you to install the clients via WSUS
- Once
client is install it will change the WSUS entries in the policy to reflect
the changes from the SUP.
- Note:
if the client is installed VIA the SUP it will get rebooted because
Windows update is doing the install so there is not way to stop the
reboot.
- With
the FSP you get 7 reports that will allow you to track client installation