SCCM 2016 Setup Created by Eddie
SCCM 2016 Setup Created by Eddie
By
Eddie Jackson
Version 1
1
IT Professional Research Lab
The following guide will take you through the installation of SCCM with a simple Primary Server approach
and with the SQL 2012 server located on the same device. Before installing SCCM, you will need to run
through some prep work to get Active Directory configured and extended, along with some application,
https://www.microsoft.com/en-us/download/details.aspx?id=29066
https://www.microsoft.com/en-us/download/details.aspx?id=49996
W10 ADK
https://developer.microsoft.com/en-us/windows/hardware/windows-assessment-deployment-kit
https://www.microsoft.com/en-us/evalcenter/evaluate-system-center-2016
Now, it is assumed you already have an AD DC with DNS, DHCP, etc. And, that a member server (for
SCCM) has been set up. I would also recommend having client computers ready to go.
Welcome to the heaven, the hell, and the purgatory—the best and worst experiences of your life—SCCM.
I hope this document will be useful to you. Email me at [email protected] for corrections, additions,
or questions. As this is only Version 1 of the document, I hope to continue adding to it. Good luck!
CONTENTS
Network Diagrams
Create the “System Management” Container in Active Directory
Extend the Schema
Add IIS Components
Configure IIS
Install Windows Assessment and Deployment Kit (Windows ADK) for Windows 10
Install SQL Server
Install SCCM {current build}
Discovery Methods and Boundary Configuration
Enable Automatic Client Push
Add Distribution Point to Boundary Groups
Updating SCCM Configuration Manager
Create a Package
Pre-Deploy a Package
Deploy Package
Monitoring a Deployment
WDS Setup
PXE Setup
Imaging Setup
Deploy Image
WSUS Setup
Deploy Updates
Report Setup, Reporting Services Point
Set up a Distribution Point at Another Site
Set up a WSUS at another Site
Deploying SCCM Clients Using Group Policy
Hierarchies and Sites
SCCM Scripts
Troubleshooting
Future topics: Capture Image, Customize Image, Dual Boot Menu Options, More Scripts, Harden Security, Reporting
EXTERNAL LINKS
Network Diagrams
Layout 1
COMPANY XYZ
SITE CODE: 001
SITE1-PC1
SITE1-PC2
SITE1-PC3 SQL DB
SITE1-PC4
SITE1-PC5
PRIMARY SITE
sccm1.DOMAIN.com
10.1.0.1
NEW YORK
Layout 2
SQL DB
SQL DB
Cloud
PRIMARY SITE
site1.DOMAIN.com
DMZ 10.1.0.1
DP MP SUP
REMOTE CLIENTS
PKI
NEW YORK
DISTRIBUTION POINT DISTRIBUTION POINT DISTRIBUTION POINT DISTRIBUTION POINT DISTRIBUTION POINT DISTRIBUTION POINT
site7.DOMAIN.com site6.DOMAIN.com site5.DOMAIN.com site4.DOMAIN.com site3.DOMAIN.com site2.DOMAIN.com
10.7.0.1 10.6.0.1 10.5.0.1 10.4.0.1 10.3.0.1 10.2.0.1
Connect to a domain controller and load ADSI Edit. Under the System OU create a new Object.
Next, launch Active Directory Users and Computers, Select View, Advanced, and then find System
Management.
Right-click on System Management, select Properties, and then the Security Tab. Add the SCCM admin
account and the SCCM server name --- Full control. Click OK to close.
Next, Delegate control to the SCCM site server (ex: SCCMServer) to System Management container in
Choose This folder, existing objects in this folder and creation of new objects in this folder. Click Next.
Check all Permission boxes and complete the wizard by selecting Next.
Schema Master Role. Ensure the account used is a member of the Schema Admins group in AD, right-
A log file ExtADSch.log will be generated on the root of the C: Drive (C:\ExtADSch.log). Check for the
The following roles and features need to be installed onto the SCCM Site Server prior to installation:
BITS (2 of 2 features)
IIS Components
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Redirection
WebDAV Publishing
Application Development
ASP
ISAPI Extensions
ISAPI Filters
HTTP Logging
Custom Logging
Logging tools
Request Monitor
Tracing
Security
Request Filtering
Basic Authentication
URL Authorization
Windows Authentication
Performance
Management Tools
Management Service
Configure IIS
Launch IIS from Server Manager Dashboard. Select Default Web Site, select Authentication, and make
Install Windows Assessment and Deployment Kit (Windows ADK) for Windows 10
Access the ADK source files you downloaded. You may have to mount the ISO to view the files.
SQL Server 2012 SP1 is being installed as the SCCM database. Note, I needed SP3 for SCCM 1606+; going
to SQL 2016, I did not need the patches. Run the setup.exe (I have included the 2012 and 2016
snapshots).
Click OK.
Click Next.
Click Next.
Select the accounts to run the SQL services, in this instance the defaults have been selected – then
configure the SQL Server Database Engine to use the SCCM service account (this must be a domain
Note: If you’re having SQL issues, ones that are privilege related, just use the SCCMAdmin account for
the top three services, and set service startup type to Automatic.
Choose the SQL Collation, used for backwards compatibility option and select
Use Windows authentication and Add the current user. Click Next.
Click Next.
Once installed, open up SSMS and limit the amount of RAM SQL can use to 50% of total RAM. Set the
value for both max and min (this is a critical setting, as SQL is a resource hog). Click OK.
If you forget to add the Reporting Services - Native, you’ll have to come back and install it before setting
up Reporting in SCCM.
https://go.microsoft.com/fwlink/?linkid=847722
Click Next.
Note: If you enter a license key on previous screen, it may skip this screen and go directly to accepting
Create a folder to store install updates and point the SCCM install to that location. Click Next.
Select language requirements for the SCCM server and click Next.
Choose whether to run the Primary as stand-alone site or join to an existing hierarchy. Click Next.
Use the database default configuration, do not enter an Instance name, and click Next.
Note, if the SQL DB is on another server, use that server name in the top field.
Specify the path to the SQL database file and log file. In this instance, it is the defaults. Click Next.
Set Configure the communication method on each site system role as a PKI infrastructure is not being
Select Yes, let’s get connected to take advantage of the new Service Connection Point feature. Click
Next.
Pre-requisite checks will run. Address any failed statuses. You may have to change the SQL Server
If you do have a SQL error, the SQL Server service should use a domain account.
You can continue on Warnings, but take a look at those post install. Click Begin Install.
Launch the SCCM Console. Ensure the site and database report as healthy in the Monitoring workspace
Once the Site Status is all green, now it is time to configure the Discovery Methods and Boundaries.
Now, in the right pane, we want to ‘enable’ System Discovery and User Discovery.
I selected IP address range, and entered the range of my network. Eventually, you’ll want to select by
Add Name of Group and click Add Boundary button, select the range, click OK.
If you need to add a domain suffix, just add suffix and check Discover sites and subnets.
Prompt a System Discovery (this will scan AD looking for devices). Right-click and select Run Full
Discovery Now.
Under Assets and Compliance, Devices, check devices for Client Type, Site Code, and Activity (this will
Next, click Site, then click the Client Installation Settings option on the ribbon and then choose Client
Push Installation.
Then, check the Enable automatic site-wide client push installation. The jury is out on whether or not
this is best practice. Some say this setting should not be used once you roll out to your enterprise; a
better solution is to use Group Policy to deploy the client. Though, in all honesty, if the AD schema has
been properly extended, and you don’t have other primary servers in your enterprise, automatic push
should be fine.
Add a check next to the device types to receive the client, click OK to continue.
NOTE: If the workstations are not receiving the client, make sure prestaged content has NOT been
checked under the Distribution Point (right-click on Distribution Point, select properties).
To add a Boundary Group to a Distribution point, click Administration > Distribution Points > right-click
on the configured distribution point and select Properties. Click the Add button.
Next, create a Distribution Group, and link the group to the managed Distribution Point. Click OK and
OK to finish configuring the Distribution setup.
Now, link the managed Boundary Group Site, to any Boundary Groups. Select the Boundary Group
(right-click and select properties), open the References Tab, and check the Use this boundary group for
site assignment.
Next, link Distribution Groups to Collections. Select Distribution Point Groups (right-click and
properties). Click Add.
Finally, under Administration, select Sites, right-click and select Properties. Check Use a fallback site
(useful for catching clients outside of boundaries) and Clients prefer to use management points in
boundary groups. OK to close.
Note, you may NOT want to select this option if you don’t want to manage machines that haven’t been
specifically added to boundaries.
Go to the Updates and Servicing under Cloud Services (or just below Overview). If there are any
updates marked Available, the updates can be downloaded and installed. To do this, right-click on the
update and select Install Update Pack.
Create a Package
To deploy a package, you must first Create the package in SCCM. To start, access Software Library.
Then, Application Management > Packages and right-click on Packages and select Create Package.
Then, check This package contains source files and select FQDN UNC path to source files. Click Next to
continue.
On the next screen, you can specify the estimated disk space and platform, then click Next to continue.
At this point, you have successfully created a package and program in SCCM. Click Close.
Pre-Deploy a Package
Once a package has been Created in SCCM, now you can set up a deployment. It is good practice to
make sure the package has been added to the distribution point (if it has not, it will not deploy). To do
this, right-click on the package, and select Distribute Content. You can then monitor the distribution
Select available distribution point. Click OK to continue. If no distribution is available, it means the
package is already available on the distribution point. In that case, just Cancel and move to Deploy
Package.
Click Next.
Click Next.
Click Close.
As a side note, packages are not stored in the distribution point in their original form, such as MSI or
EXE. Packages in the distribution point can be found in the following location:
SCCMContentLib\FileLib
Deploy Package
To Deploy a package, right-click on the package and select Deploy from the menu.
The Deployment has been successful. Click Close to exit deploy wizard.
Monitoring a Deployment
Once a package has been set to be delivered to a Collection, the deployment can be monitored from the
On the client, Task Manager can be used to track the installation process. Frontend Notifications can
also be sent, so the end user knows a package is being downloaded, installed, and completed. If you like
logs, check out C:\Windows\CCM\logs\AppEnforce.log, which records details about enforcement actions
(install and uninstall) taken for applications on the client. Client cache can also be monitored, to see if
On the SCCM Server, under Monitoring > Deployments, the package deployment status can be
A Successful Deployment
WDS Setup
Normally, you wouldn’t do anything after installing the WDS service from the Dashboard. But, if there
are errors or alerts, you’ll want to make sure you resolve those first, before moving on to SUP and PXE
setup in SCCM.
Click Next.
PXE Setup
Required
To begin PXE setup in SCCM, select Administration > Distribution Points > Distribution Point >
Properties.
Click Yes.
Click OK to continue.
Side Note
If there is another PXE server boot WIM currently in use, import the WIM into the SCCM Boot Images
section -- before configuring DHCP. You want the original boot WIM and the new boot WIM to be
available on the boot menu. Of course, you may not care about maintaining both the old and new
solution.
Configure DHCP
In DHCP,
(5) Check 066 Boot Server Host Name and type the PXE FQDN sccm.DOMAIN.com or 10.1.0.1 (Primary)
Imaging Setup
To deploy an operating system, you must first add an OS WIM to SCCM. To add a WIM, select Software
Library, Operating Systems, right-click on Operating System Images, and select Add Operating System
Image.
Click Next.
Click Next.
Click Next.
Click Close.
Now, you want to distribute the WIM. Right-click on the newly imported image, and click Distribute
Content.
Click Next.
Select appropriate distribution point. OK to continue. If no distribution is available, it could mean the
package is already available on the distribution point. In that case, just Cancel and move to Deploy
Steps.
You can monitor the Distribution Status under Administration > Monitoring > Content Status.
Deploy Image
To be deploy an image, start in the Operating Systems and Task Sequences. Right-click and click Create
Task Sequence.
Enter Task sequence name and select Boot image. Click Next.
Select the Image package/Operating System, and Enable and set admin password. Click Next.
Click the Set button to enter the account that will be used to join the domain. Test connection. Click OK
Click Next.
If this is an Upgrade, configure the state migration, otherwise uncheck these options. Click Next.
Click Close.
Distribute the Content to appropriate Distribution Points, and you’re ready to deploy. To start the
Browse to Collections.
Click Next.
Click Next.
Click Next.
Click Next.
Click Next.
Click Close.
WSUS Setup
To begin WSUS setup, launch the Add Roles and Features Wizard. Click Next.
Click Next.
Click Next.
Click Next.
Click Next.
Enter the local or UNC path where the Windows Updates will download to, and click Next to continue.
Enter path to the database, and click the Check connection. Click Next.
Click Close.
Click Next.
Click Next.
Click Next.
Click Next.
Click Next.
Click Next.
Select Next.
Select Next.
Click Next.
Click Next.
Click Close.
Wsyncmgr.log
WCM.log
Note, it will take a couple of hours to completely sync Windows Updates, perhaps longer depending on
your setup.
Side note, if you happen to have another primary SCCM server with the SUP role, it may conflict with
your server. For me, I noticed a different primary SCCM server in the server logs. So, I had to strip out all
the WSUS info, remove the CM Client from our server, block the other WSUS server (primary server) in
the host file, and rebuild WSUS and reconfigure the SUP role. After that, I monitored the WSUS logs and
saw my server syncing properly.
Deploy Updates
Click on the All Software Updates under Software Library > Overview.
Click Next.
Click Next.
Click Next.
Click Next.
Click Next.
Click Close.
The distribution status can be monitored under Monitoring > Distribution Status > Content Status.
Once the content has been distributed, right-click on Device Collection, select Deploy, and select
Software Updates.
Click Change to software update groups. Choose the update(s). Click OK. Note, you could have already
created a software group. In that case, just select the group, there is no need to change.
The group name will be populated (you can rename this). Click Next.
Select Download software updates from a location on my network. Enter FQDN path. Click Next.
Once a client has received and completed the installation, the device will appear under Compliant.
Set up base server. Set static IP. Add server name into the Administrators group. Add SCCM service
account into the Administrators group. For testing purposes only, disable the firewall.
Download current SCCM build (it should be the same build as the primary server).
If .NET 3.5 isn’t installed, you will have to add a role and select the 3.5 features.
IIS Configuration
Application Development: ISAPI Extensions
Security: Windows Authentication
IIS 6 Management Compatibility: IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility.
WDS/PXE
To support PXE or multicast role on DP, the WDS role is required. WDS installs and configures
automatically when you configure a distribution point to support PXE or Multicast on Windows Server
2012.
Now, extract the SCCM files and begin the SCCM installation by selecting Install Configuration Manager
console.
Select Next.
I do recommend installing the Configuration Manager on a different drive than your boot/system drive,
if the environment permits; but for a lab, this is fine.
Click Next.
Click Next.
Click Install.
Click Finish.
In the console, navigate to Administration > Overview > Site Configuration. Right-click on Sites and
select Create Site System Server.
In the Create Site System Server Wizard, click Browse and select the server name on which the DP role
is to be installed.
Click Next.
Configure the distribution point settings, and then click Next to continue.
Click Next.
Click Next.
Click Next.
Click Next.
Click Next.
Add the Boundary Group for the location. Click Add, and select the appropriate boundary group.
Click OK.
Verify that the distribution point is working by looking at Site Status under Monitoring. You want white
check marks on green.
Also check to see if the Distribution point folders have been generated.
Finally, if you want this distribution to ‘pull’ content from a primary distribution point (which in most
cases you do), launch the distribution point properties and check Enable this distribution point to pull
content from other distribution points. The source distribution point should be the primary server.
On the second server hosting the SUP role, SUP2, install WSUS with the Database option (no need to
install SQL). Click Next.
On the Store updates in the following location, enter the FQDN to the new SUP2 server. Click Next.
Specify the database server (from SUP1). Click Check connection. Click Next.
Click Install.
If you see another Configuration required --- remove the SUP role (if it exists) from the second server,
and look at the steps below.
On the second server, launch the WSUS services from Server Manager Dashboard > Tools and enter the
FQDN for the second WSUS.
At this point, you should see a Configuration completed for Windows Updates Services at ServerName.
If there are still errors, remove SUP, remove the WSUS service, delete the WSUS site in IIS, and reboot
and start over.
Next, install the SCCM SUP role on the second site server. Go to Administration > Servers and Site
System Roles > right-click on new server, and click the Add Site System Roles option.
Click Next.
Click Next.
Click Next.
Click Close.
You can verify that the SUP role installation and configuration was a success by viewing the status under
Monitoring > System Status > Site Status.
The current status can also be viewed under the Software Update Point Synchronization Status. Notice
how the primary SUP (top line) points to Microsoft Update, and SCCM2 (SUP2) points to SCCM (SUP1).
First, uncheck the option Enable Automatic site wide client push installation.
Sites > Settings > Client Push Installation > General Tab.
Next, create a new group policy, in GPMC, find the SCCM GPO and click Edit.
Expand Computer Configuration, Policies and right-click on Administrative Templates and click on
Add/Remove Templates.
Import both templates. Once imported, access the configuration under Classic Administrative
Templates (ADM) > Configuration Manager > Configuration Manager Client.
Enable and configure Site Assignment. Click Apply and then OK.
Enable and configure Client Deployment Settings. Click Apply and then OK.
Next, go to Policies > Software Settings > right click Software installation and select Package.
You can choose to apply this policy at domain level or at the OU level. If you apply it at the domain level,
then every computer in the domain will receive the SCCM client installation the next time GP syncs. To
link the policy to an OU (suggested for testing), right click on the Test OU, click Link an existing GPO,
choose the GPO Test-DefaultDomainPolicy (or whatever you named the policy) and click OK.
Design
A site is the core role of Configuration Manager. A Configuration Manager hierarchy consists of sites that
are linked directly or indirectly and have a parent-child relationship. The Configuration Manager 2012
infrastructure is simplified from earlier versions of the product, and consists of three different site types,
Central Administration Site, Primary Site and Secondary site (1).
• A central administration site as the top-level site that has one or more primary child sites.
The primary sites can each support secondary sites.
CAS is the recommended location for all administration and reporting for the hierarchy, if you choose to
deploy a hierarchy with a CAS. Central Administration sites are used in scenarios where you need more
than one Primary Site, such as when you need to manage more than 100 000 clients. The maximum
number of clients supported for an entire Configuration Manager 2012 hierarchy is 400 000. The CAS
supports only primary sites as child sites. It has limited site roles available, has no clients assigned, and
doesn’t process client data. The CAS requires SQL Server for data that is gathered from the hierarchy.
Primary Site
A required site that manages clients in well-connected networks. All clients are assigned to a primary
site. Primary sites cannot be tiered below other primary sites. Each Primary site can support up to 250
secondary sites, 100 000 clients and 10 management points (for load balancing). A SQL server is required
for primary sites. If an organization has less than 100 000 clients, it should only use a single stand-alone
primary site.
Secondary Site
Secondary sites can be used to service clients in remote locations where network control is needed.
General recommendation though is to avoid usage of secondary sites in such scenarios, and rather
deploy Distribution Points in remote locations, because they allow controlling, or throttling, network
bandwidth for content distribution between a site and a remote distribution point. Secondary sites are
installed through the Configuration Manager console. A management point and distribution point are
automatically deployed when the site is installed. SQL Server Express or a full instance of SQL Server is
required for a secondary site. If neither is installed when the site is installed, SQL Server Express is
automatically installed.
Secondary sites must be direct child sites below a primary site, but can be configured to send content to
other secondary sites. They also receive a subset of the Configuration Manager database. Clients cannot
be assigned directly to secondary sites.
Because administrative consoles can connect only to a central administration or primary site, secondary
sites are typically used in locations that do not have administrators, or in locations where you need
clients to scan for software updates compliance without needing to talk to a primary site server. The
latter can be achieved by installing the software update point role on a secondary site server.
Site System Roles are roles that can be installed on Configuration Manager 2012 R2 site servers. Any
computer hosting a site system role is referred to as a site system server. You can assign multiple roles
to one site system server. There are five site system roles that must exist in each site and must be
configured during installation of a CAS or a Primary site, while the rest of the site system roles are
optional.
Component Server
Any server running the Configuration Manager Executive service. It is automatically installed with all site
system roles except the Distribution Point, and is used to run Configuration Manager services.
Server with Microsoft SQL Server installed, hosting the Configuration Manager site database. This
database is used to store information about assets and site data.
Site Server
Contains components and services required to run a central administration, primary, or secondary site.
Site System
Supports both required and optional site system roles. Any server (or share) with an assigned role
automatically receives this role.
SMS Provider
A WMI provider operating as an interface between the Configuration Manager console and the site
database. Secondary sites do not install SMS providers.
Publishes software information from the software library to the Application Catalog Website.
Publishes the available software for a user on the Application Catalog Website.
Synchronizes Asset Intelligence data from System Center Online by downloading Asset Intelligence
catalog data and uploading custom catalog data. This role can only be installed on the CAS or a stand-
alone primary site server.
Communicates with the server that runs the Network Device Enrollment Service of Active Directory
Certificate Services to manage device certificate requests that use the Simple Certificate Enrollment
Protocol (SCEP).
Distribution Point
This role stages packages (source files), such as application content, software packages, software
updates, operating system images, and boot images to clients. A Distribution Point cannot be connected
to a CAS, it always communicates with a primary site or a secondary site. A single Distribution Point is
capable of supporting up to 4000 clients. A site can hold up to 250 Distribution Points.
This role is configured at the Central Administration Site or a stand-alone primary site. With the System
Center Endpoint Protection role, you can secure your clients and servers from viruses and malware by
deploying (and managing) Microsoft System Center 2012 Endpoint Protection to clients. Microsoft
System Center 2012 Endpoint Protection provides an antimalware and security solution for the
Microsoft platform.
Enrollment Point
Facilitates enrollment of Intel’s Active Management Technology (AMT)-based computers and mobile
devices.
Provides an alternative location for clients to send up status messages during installation when they
cannot communicate with their management point.
Management Point
Facilitates communication between a client and site server by storing and providing policy and content
location information to the client, and receiving data from the client such as status messages and
inventory. One Management Point can support up to 25 000 clients.
Used to integrate reporting through SQL Server Reporting Services and is required if using reports.
Provides software update management for Configuration Manager clients by integrating with Windows
Server Update Services (WSUS).
When using OSD, the state migration point holds the user state data for migration to the new operating
system.
When implementing Network Access Protection (NAP) a system health validator point validates the
Configuration Manager NAP policies. The role must to be installed on the NAP health policy server.
When managing mobile devices via Windows Intune you need to install the Windows Intune connector
to be able to retrieve status messages and inventory messages from the mobile devices that are
enrolled in Windows Intune.
SCCM Scripts
Policy: VBScript
On Error Resume Next
Dim oCPAppletMgr
Set oCPAppletMgr = CreateObject(“CPApplet.CPAppletMgr”)
Dim oClientActions Set oClientActions = oCPAppletMgr.GetClientActions()
Dim oClientAction
For Each oClientAction in oClientActions
If oClientAction.Name = “Request & Evaluate Machine Policy”
Then oClientAction.PerformAction
End If
Next
'restart process
objShell.Run "C:\Windows\CCM\CcmRestart.exe",0,true
'import certificate
objShell.Run "cmd /k certutil.exe -addstore Root ""C:\Windows\ccmsetup\certificate.cer"" ", 9, True
objShell.Run "cmd /k certutil.exe -addstore TrustedPublisher ""c:\Windows\ccmsetup\certificate.cer"" ",
9, True
'repair
objShell.Run "cmd /k C:\Windows\CCM\ccmrepair.exe",9,true
'repair policy
objShell.Run "cmd /k msiexec /x c:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi /qn",9,true
objShell.Run "cmd /k msiexec /i c:\Windows\ccmsetup\MicrosoftPolicyPlatformSetup.msi /qn",9,true
'restart process
objShell.Run "cmd /k C:\Windows\CCM\CcmRestart.exe",9,true
if(!$siteServer)
{
"Provide the CAS site server name."
Return
$WmiObjectSiteClass = "SMS_SCI_SiteDefinition"
$WmiObjectClass = "SMS_SCI_Component"
$WmiComponentName = "SMS_DMP_DOWNLOADER"
$WmiComponentNameUpdateRing = "UpdateRing"
$SiteCode = $providerMachine.SiteCode
$ProviderMachineName = $providerMachine.Machine
$WmiObjectNameSpace="root\SMS\site_$($SiteCode)"
#Get component
$WmiObject = Get-WmiObject -Namespace $WmiObjectNameSpace -ComputerName
$ProviderMachineName -Class $WmiObjectClass | Where-Object { $_.SiteCode -eq $SiteCode -and
$_.ComponentName -eq $WmiComponentName }
if (!$props) {
$EmbeddedProperty =
([WMICLASS]"root\SMS\site_$($SiteCode):SMS_EmbeddedProperty").CreateInstance()
$EmbeddedProperty.PropertyName = $WmiComponentNameUpdateRing
$EmbeddedProperty.Value = 1
$EmbeddedProperty.Value1 = ""
$EmbeddedProperty.Value2 = ""
$WmiObject.put()
}
else
{
$props = $WmiObject.Props
$index = 0
ForEach($oProp in $props)
{
if($oProp.PropertyName -eq $WmiComponentNameUpdateRing)
{
$oProp.Value=1
$props[$index]=$oProp;
}
$index++
}
$WmiObject.Props = $props
$WmiObject.put()
}
%windir%\system32\wbem\winmgmt /clearadap
%windir%\system32\wbem\winmgmt /kill
%windir%\system32\wbem\winmgmt /unregserver
%windir%\system32\wbem\winmgmt /reserve
%windir%\system32\wbem\winmgmt /resyncperf
net stop winmgmt /y
if exist %windir%\system32\wbem\repository.old rmdir /s /q
%windir%\system32\wbem\repository.old
rename %windir%\system32\wbem\repository
%windir%\system32\wbem\repository.old
regsvr32 /s %systemroot%\system32\scecli.dll
regsvr32 /s %systemroot%\system32\userenv.dll
mofcomp %windir%\system32\wbem\cimwin32.mof
mofcomp %windir%\system32\wbem\cimwin32.mfl
mofcomp %windir%\system32\wbem\rsop.mof
mofcomp %windir%\system32\wbem\rsop.mfl
cd wbem
for /f %s in ('dir /b /s %windir%\system32\wbem\*.dll') do regsvr32 /s %s
for /f %s in ('dir /b /s %windir%\system32\wbem\*.mof') do mofcomp %s
for /f %s in ('dir /b %windir%\system32\wbem\*.mfl') do mofcomp %s
net start winmgmt
net start ccmsetup
%windir%\system32\wbem\wmiprvse /regserver
Troubleshooting
Question
Answer
If the device has no client installed, then the icon will appear as it does today in CM12 and CM1511
(current branch). If a client is installed but no data is yet available a gray question mark will appear. If a
client is installed and online, it will appear as in the screenshot above with a white tick in a green circle.
If the client is completely offline, a gray X will appear.
Question
Answer
Question
Answer
Question
How do I enable or fix Control Alt Delete in Remote Control when it is not working?
Answer
There is a group policy option for this simulation of keys. Look under Computer policies > Admin
Templates > Windows Components / Windows Logon Options and then set "Disable or enable software
secure attention sequence" to `enabled' You must then change "Set which software is allowed to
generate the secure attention sequence" to "Services and Ease of Access applications".
Error
Solution
Check boundary for the client. Make sure the Admin$ share is accessible on the client. Make sure the
machine responds to ping. The machine must have a valid service or client installation account added to
the Administrators group---should be the same account used in SCCM > Sites > Client Installation
Settings > Client Push Installation > Accounts.
Error
Failed to receive CCM message response. Status code = 500. Found in Logs\ccmsetup.log when trying to
install the CM client.
Solution
This problem occurs because the ApplicationHost.config file or the Web.config file references a module
that is invalid or that does not exist. To resolve this problem: In the ApplicationHost.config file or in the
Web.config file, locate the module reference or the DLL reference that is invalid, and then fix the
reference. To determine which module reference is incorrect, enable Failed Request Tracing, and then
reproduce the problem.
For above specific error (mentioned in this example), DynamicCompressionModule module is causing
the trouble. This is because of the XPress compression scheme module (suscomp.dll) which gets
installed with WSUS. Since Compression schemes are defined globally and try to load in every
application Pool, it will result in this error when 64bit version of suscomp.dll attempts to load in an
application pool which is running in 32bit mode.
Remove/Disable the XPress compression scheme from the configuration using the command below:
Error
Solution
Computer object is missing from OU (the computer has not been added to OU in AD). So, add the
computer to the proper OU, or change the OU in SCCM.
Error
SCCM Client is not installing on clients.
Solution
Make sure ‘Prestage’ is disabled: Under Security > Distribution Points > Properties of distribution point.
Error
Cannot install or repair Configuration Manager; cannot start SMS or SCCM services. Error 1053. Error
1053: "The service did not respond in a timely fashion".
Solution
Try running the sitecode.exe manually, and look at any errors. One error that can cause these issues is:
"MSVCP120.dll is missing from your computer." Fix by reinstalling 64 bit Visual C++ Redistributable
Packages for Visual Studio 2013.
Note, sitecode.exe file can be found in the default installation folders of SCCM:
C:\Program Files\Microsoft Configuration Manager\bin\x64
D:\Program Files\Microsoft Configuration Manager\bin\x64
Error
Upon a first time a SCCM setup, ‘Unable to connect to SQL Server with connection information’.
Solution
Error
Solution
Error
Solution
Error
Gray X on devices; devices are offline or they appear to be offline. Beginning in version 1602 of
Configuration Manager, this status indicates if the computer is online or not. A computer is considered
online if it is connected to its assigned management point. To indicate that the client is online, it sends
ping-like messages to the management point. If the management point does not receive a message in 5
minutes, the client is considered offline.
Solution
Installing/Reinstalling hotfixes did not work. What worked: Load SQL Server Configuration Manager.
Enable Named Pipes under SQL Server Network Configuration, Protocols for MSSQLSERVER. Reset
services using the Start Menu Configuration Manager Setup tool.
Error
SMS_NOTIFICATION_SERVER Error 1020, 4951, Site Component Manager failed to reinstall this
component on this site system.
Solution
Remove all roles but the default ones and reset services using the Start Menu ‘Configuration Manager
Setup’ tool. Also see the next error (SQL Server connection issues will affect components).
Error
Upon repairing or reinstalling SCCM, you receive Setup is unable to connect to SQL Server with the
connection information provided.
Solution
Load SQL Server Configuration Manager. Enable Named Pipes under SQL Server Network Configuration,
Protocols for MSSQLSERVER. Reset services using the Start Menu ‘Configuration Manager Setup’ tool.
Error
Solution
On the client, go to Start / Run and type control schedtasks to open the scheduled tasks control panel.
Open Microsoft, then Configuration Manager and delete all listed entries. Initiate the install client with
the always install option checked in the SCCM console. The scheduled tasks should be recreated when
the agent installs and the computer will start checking in appropriately to the SCCM server. Check the
local computers ccmeval.log file for more details.
Error
Solution
Switch both the distribution point and the management point to HTTP.
GP can mess with the results in testing and setting up WSUS/SUP. Make sure GP is exactly what you
think it is. If you have doubts, block GP to your test devices.
Also, you may want to check the relative WSUS registry key.
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate]
"WUServer"="YOUR WSUS SERVER PATH"
"WUStatusServer"="YOUR WSUS SERVER PATH"
"TargetGroupEnabled"=dword:00000001
"TargetGroup"="THE TARGET GROUP"
If there is no SUSDB, that means there are DB creation problems; most likely related to user rights.
Something important to note, a botched WSUS setup can affect the DB and IIS.
Other options
Something important to note, if IIS is not configured with the instance ID of 1, you may also receive
invalid path.
Go to IIS manager and right click on the web site and select properties.
On the Web Site Tab click properties in the logging section.
At the bottom it shows you the log file name
It starts with W3SVCx where x is the instance ID. Make sure it contains 1.
Check Logs
These two logs will contain most of the successes and errors of Windows Updates:
-- Wsync.log
-- WCM.log
The server is configured to use pass-through authentication with a built-in account to access the
specified physical path. However, IIS Manager cannot verify whether the built-in account has access.
Make sure that the application pool identity has Read access to the physical path. If this server is
joined to a domain, and the application pool identity is NetworkService or LocalSystem, verify that
<domain>\<computer_name>$ has Read access to the physical path. Then test these settings again.
Set the application pool identity to a custom account (IIS Manager->Click your application pool->Click
Advanced Settings… on the Actions panel->Process Model section). Then, grant the account permissions
on the physical path.
-- Uninstall IIS
-- Reboot system
-- Uninstall WAS (Windows Process Activation Service)- WAS feature package is the dependent package
for the IIS feature package.
-- Reboot system
-- Reinstall IIS
Go to Task Manager > Processes and manually stop the W3SVC process. After doing this the process
should start normally when restarting IIS
Run > appwiz.cpl > Turn windows features on or off > Uncheck Internet Information Services and
Windows Process Activation Service.
Run > appwiz.cpl > install both Internet Information Services and Windows Process Activation Service
1. Verify that Windows Management Instrumentation is started and its startup type is set to
automatic.
2. Also make sure the following dependency services are started for World Wide Web Publishing
Service:
-- Double click on Start and change value data from 4 (disabled) to 3 (automatically).
-- Delete "NoRun" key if this key exists.
4. Uninstall Internet information Service and Windows process activation service. Restart computer.
6. Reinstall Internet information Service from Turn windows feature on or off (or System Manager).
7. Make sure these two services running and their startup type is automatic. If they are disabled and not
running right click on them and go to properties and change them.
8. Start IIS and websites will start; no more "w3svc service is not running error."
9. Restart computer.
Notes
netstat -a -o|findstr 80
sc config http start= auto
sc config http start = auto
net start w3svc
Navigate to Application Pools, then select WsusPool, and select Advanced Settings. In the Advanced
Setting window, scroll down to Recycling. Originally the Private Memory Limit (KB) is set to 1843200.
Change that to 0. Once the change is made, recycle the WsusPool. The IIS Worker Process will quit
spiking and the WSUS console should begin working without issue or crashing.
When you select to run the WSUS cleanup task, it will run at the next software updates synchronization.
The expired software updates will be set to a status of declined on the WSUS server and the Windows
Update Agent on computers will no longer scan these software updates.
When you select to run the WSUS cleanup task, it will run at the next software updates synchronization.
The expired software updates will be set to a status of declined on the WSUS server and the Windows
Update Agent on computers will no longer scan these software updates.
General Troubleshooting
When the active software update point is installed on a remote site system server, the Windows Server
Update Services (WSUS) Administration console must be installed on the site server.
The port settings configured for the active software update point must be the same as the port settings
configured for the WSUS Web site in Internet Information Services (IIS).
When there is a proxy server between the active software update point and the upstream update server
or Microsoft Update, the proxy server and the software update point proxy server account must be
configured, if credentials are required.
The computer and Administrator accounts must be able to access virtual directories under the WSUS
Web site in IIS from the site server.
The active software update point at the central site should be configured to synchronize with Microsoft
Update. This setting is automatically configured when you first create the software update point on the
central site, but if the setting is modified in the WSUS Administration console, WSUS Configuration
Manager does not reset this setting as it does for other WSUS settings.
Check the port settings configured for the active software update point, and make sure they are the
same as the port settings configured for the Web site used by WSUS running on the active software
update point.
Check to make sure the fully qualified domain name (FQDN) for the active software update point site
system server is correct.
When the Configuration Manager site is in native mode, the WSUS Web site and virtual directories must
be configured for Secure Sockets Layer (SSL) because the active software update point is automatically
configured to use SSL, but WSUS is not automatically configured. When a Configuration Manager site is
in mixed mode, you have the option to configure the active software update point to use SSL. In both
cases, you must manually configure the WSUS Web site and virtual directories.
Check to make sure that WSUS running on the active software update point for the child primary site is
not configured to be a replica. The following procedure provides the steps to check whether WSUS is
configured to be a replica.
-- Open the WSUS console on the active software update point for the site.
-- Verify that This server is a replica of the upstream server is not selected unless you are in the WSUS
console on the active software update point for a secondary site. Child primary sites should never be
configured as a replica of the upstream server.
Check the proxy settings configured for the active software update point, and make sure they are
configured correctly. When there is a proxy server between the WSUS server and the upstream update
source, the proxy settings must be configured. When credentials are required, you must specify the
correct account information for the proxy.
When the proxy settings are configured correctly in the ConfigMgr software update point properties,
you can open the WSUS console to check the proxy settings to make sure they match the settings in
Configuration Manager. When the proxy settings are configured correctly, you can review the
synchronization status in the WSUS console, which might provide more information about why WSUS
synchronization failed.
This issue can also be caused by any number of network issues that prevent the URL address for the
upstream update source from being resolved. If configuring the proxy settings does not resolve the
issue, troubleshoot this issue like any other name-resolution issue on your network.
Check the permissions on the ApiRemoting30 virtual directory under the WSUS Web site in IIS. The
computer and Administrator accounts must have appropriate rights to this virtual directory. The
following procedure provides the steps to check the permissions on the ApiRemoting30 virtual directory.
To check the permissions on the ApiRemoting30 virtual directory
Following are possible solutions for the Unable to connect to remote server error:
Check to make sure the IIS Admin Service and World Wide Web Publishing Service services are running.
Check the connection to the active software update point where WSUS is running.
Check the IIS permissions on the DssAuthWebService virtual directory for the WSUS Web site in IIS. The
virtual directory must be enabled for anonymous access. By default, the IUSR_<ComputerName>
account is used for anonymous access. Check that this account has appropriate rights—for example,
whether this account is a member of the Guests group where access has been denied. The following
procedure provides the steps to configure the directory permissions for the virtual directory.
To configure anonymous access on the DssAuthWebService virtual directory
Expand Web Sites, and then expand the Web site for the WSUS server. It is recommended that the
WSUS custom Web site be used, but the default Web site might have been chosen when installing
WSUS.
Click the Directory Security tab, and then click Edit in the Authentication and access control section.
Verify that Enable anonymous access is selected and that the IUSR_<ComputerName> account is
specified.
To work around changes not taking effect immediately, follow these steps:
Go to the Software Update Component properties and deselect all Products and Classifications which
are enabled out-of-the-box.
Force the Software Update Synchronization to run. Monitor the WCM.log and WsyncMgr.log to validate
the synchronization is now running successfully. Note that no updates will be synchronized at this point,
but the products and classifications catalog will be synced as part of the process.
Enable the required Products and Classifications that were disabled previously, and run the
synchronization again.
Sync Tip
On the Select the products that you want to synchronize screen place a checkmark in All Products and
then remove it again, this will deselect everything before the first synchronization (recommended).
Yes, there are going to be times you just have to start the Win Updates setup and config over again.
2. Uninstall WSUS
5. Restart Server
9. Start WSUS Admin Console and ran Wizard (also choose to connect for the catalog sync) up to the
Point where you select the products. Then, cancel the wizard without choosing any products.
10. Install SUP role in SCCM and configure the right Settings (WSUS on Server 2012 Defaults to its own
admin Website and ports 8530 and 8531) and select the products you require.
11. Check following log file if WSUS does not sync with SCCM.
-- WCM.log
-- wsyncmgr.log
Tips
Use the computer account for the Software Distribution Component. If it fails, you can try the service
account. That will tell you something is wrong with how System Management is set up in AD.
When repairing SCCM---using the SCCM Wizard---[backup] delete the logs, just to clear everything out.
The SCCM server log files are located in the >INSTALL_PATH>\Logs or SMS_CCM\Logs folder. IIS logs can
be found in %WINDIR%\System32\logfiles\W3SVC1 folder.
● DmpDatastore.log – Records all the site database connections and queries made by the Device
Management Point.
● DmpDiscovery.log – Records all the discovery data from the mobile device clients on the Device
Management Point.
● DmpFileCollection.log – Records mobile device file collection data from mobile device clients on the
Device Management Point.
● DmpHardware.log – Records hardware inventory data from mobile device clients on the Device
Management Point.
● DmpIsapi.log – Records mobile device communication data from device clients on the Device
Management Point.
● dmpMSI.log – Records the MSI data for Device Management Point setup.
● DMPSetup.log – Records the mobile device management setup process.
● DmpSoftware.log – Records mobile device software distribution data from mobile device clients on
the Device Management Point.
● DmpStatus.log – Records mobile device status messages data from mobile device clients on the
Device Management Point.
● FspIsapi.log – Records Fallback Status Point communication data from mobile device clients and
client computers on the Fallback Status Point.
● discovery.log – Provides detailed information about the Service Modeling Language (SML) processes.
● sdmagent.log – Provides information about downloading, storing, and accessing configuration item
content.
● sdmdiscagent.log – Provides high-level information about the evaluation process for the objects and
settings configured in the referenced configuration items.
● WUSSyncXML.log – Provides information about the Inventory Tool for the Microsoft Updates
synchronization process. This log is only on the client computer configured as the synchronization
host for the Inventory Tool for Microsoft Updates.
more...
0 Success
6 Error
7 Reboot Required
KB920852
NBTSTAT -a reverse
lookup
1618 MSI This error is caused by a multiple Stop all related MSI
client.msi installation at the same install process
time
8007045D MSI Setup was unable to create the Delete all SCCM
WMI namespace CCM folders and rebuilt
WMI Repository
McAfee-HIPS
Dcom is miss-
configured for security
There are a number of checks that are performed by CCMEval and remediation can range from enabling
a service to reinstalling the client:
Verify CCMEval task has run Launch CCMEval from CCMExec Check if the scheduled task has
days
prerequisites. ccmsetup.xml
WMI Repository Integrity Reinstall Configuration Manager Check the existence of some CM’s
classes/namespace/instance
Verify/Remediate SMS Agent Restart SMS Agent Host Service Checks SMS Agent Host status
Host status.
WMI Event Sink Test. Restart CCMExec Check whether CM’s related WMI
installation.
WMI Repository Read/Write Reset WMI repository and Performs WMI repository read/write
client
type.
Verify/Remediate Windows Reset service startup type to Checks Windows Update service
Verify/Remediate SMS Agent Reset service startup to Checks SMS Agent Host startup type
Verify/Remediate WMI Reset service status to Running Checks WMI service status
service status.
Verify/Remediate SQL CE CCMEval on next run will notice Checks if CCMStore.sdf exists, can be
database is healthy. flag and repair client, thereby opened and calls the SQL CE Verify DB
data
Verify/Remediate Microsoft Reset service status to Manual Check Lantern Service Startup type
startup type.
Verify/Remediate BITS Reset service startup to Checks BITS service startup type
Verify/Remediate Network Reset service startup type to Checks if Network Inspection service is
Verify/Remediate WMI Reset service startup to Checks WMI service startup type
Verify/Remediate Windows Reset service startup type to Checks Windows Update service
on Windows 8.
Verify SMS Agent Host No Remediation Check for SMS Agent Host service
service exists.
language packs.
Verify/Remediate Windows Reset service status to Active Checks Windows Update service status
startup type
status
Hardware Requirements
Site Servers
Use the following recommendations for each Configuration Manager site server.
Because disk allocation and configuration contributes to the performance of System Center 2012
Configuration Manager, disk space requirements can be greater than for previous product versions.
Use the following information as guidelines when you determine the amount of disk space
Configuration Manager requires. Because each Configuration Manager environment is different, these
values can vary from the following guidance.
For the best performance, place each object on a separate, dedicated RAID volume. For all data
volumes (Configuration Manager and its database files), use RAID 10 for the best performance.
Reference
(1) shabaztech.com
https://docs.microsoft.com/en-us/sccm/core/get-started/set-up-your-lab
https://sccmentor.com/2014/01/08/sccm-2012-r2-step-by-step-installation-guide/
https://social.technet.microsoft.com/wiki/contents/articles/25696.how-to-uninstall-or-remove-sccm-
client.aspx
http://www.sqlservercentral.com/blogs/rocks/2012/01/09/revised-difference-between-collation-
sql_latin1_general_cp1_ci_as-and-latin1_general_ci_as/
https://technet.microsoft.com/en-us/library/hh427342.aspx?f=255&MSPPError=-2147217396
Other Notes