Sometimes it is necessary to exclude some updates from automatically distribute to clients.
When using Automatic Deployment Rule (ADR) in sccm 2012, all updates that meet the criteria that was configured will added to the associated software updates group, and will be eventually distribute to clients.
Exclude updates from ADR
Find the desire ADR, under Software Library node go to Software Updates -> Automatic Update Rules.
In the ADR properties, go to Software Updates tab and add a Title with - (minus) and the name of the update you would like to exclude.
Wednesday, May 7, 2014
Sunday, May 4, 2014
Failed to execute SQL cmd exec [sp_CP_CheckNewAssignedMachine] - SCCM 2012 client push fail to start
Recently i faced an issue with SCCM 2012 R2 server and client push installation. (From my research it can be relevant to SCCM 2012 SP1 too).
Environment:
Environment:
- SCCM 2012 R2
- SQL installed separately on cluster environment
Issue:
When configuring client push installation to servers and workstations as in the picture below, an error in CCM.Log stared and client fail to start installation on server type objects.
When configuring client push installation to servers and workstations as in the picture below, an error in CCM.Log stared and client fail to start installation on server type objects.
Exclude Computers From Automatically Push SCCM Client
In many situation i was needed to exclude specific computers (mostly servers), from getting SCCM client to be installed after configuring site-wide automatic client push installation method.
There is an option for editing the registry and add ExcludeServers list with all computers names that SCCM client shouldn't be install.
Basically, adding the ExcludeServers list with computer names will sets the install flag for that resource which prevent from the client to be installed automatically.
There is an option for editing the registry and add ExcludeServers list with all computers names that SCCM client shouldn't be install.
Basically, adding the ExcludeServers list with computer names will sets the install flag for that resource which prevent from the client to be installed automatically.
Sunday, April 13, 2014
SCCM 2012 client push configure installation and troubleshooting
SCCM client push requirement
Disable firewall or open the necessary ports:
Disable firewall or open the necessary ports:
Port
|
Remark
|
||
80
|
TCP
|
||
443
|
TCP
|
native
mode management point
|
|
445
|
TCP
|
||
135
|
TCP
|
UDP
|
In addition, the following needs to be open as well:
o
ICMP (ping) from server to client.
o
BITS service needs to
enable.
o
Add the following as exceptions to the Windows
Firewall:
Outbound and inbound: File and Printer Sharing
Inbound: Windows Management Instrumentation (WMI)
Outbound and inbound: File and Printer Sharing
Inbound: Windows Management Instrumentation (WMI)
For complete list of ports used by the
client:
Monday, March 3, 2014
Create Custom XML For OSD In SCCM
Lately I was needed to deploy
custom Windows 7 image with SCCM 2012 (2007 should be the same).
In my search over the internet I didn't found any full guide that goes through all the required steps, so I decided to document it.
In my search over the internet I didn't found any full guide that goes through all the required steps, so I decided to document it.
The requirements was:
·
Upgrade Windows XP with new
Windows 7 image.
·
Backup domain profiles only
(except My Documents).
·
Do not backup files on
drive D.
·
Backup printers.
·
Format hard drive
·
Configure additional
language.
·
Move computer to different
OU.
Subscribe to:
Posts (Atom)