News from MMS 2019

MBAM is being integrated into ConfigMgr.

CCMexec stops right after it has been started

I my environment, I suddenly had a lot of inactive clients. I thought that it was strange, so I dived into the issue.
Looking at a client, I found that the ccmexec service wasn't running.
I started the ccmexec service, but it stopped immediately (later I found that, on other client the service stopped after 5 minutes - they would start a repair, and then fail and stop).
Then I looked into the ccmexec.log and found this:
Service settings instance is missing from WMI.

Error loading service settings. Code 0x87d00218 Phase 0 initialization failed (0x87d00218). Service initialization failed (0x87d00218). Shutting down CCMEXEC
x

I tried a repair, but that didn't solve the problem.
Taking a deeper look into the log told me that the client had a problem with the ccm part of wmi.
I then tried to do a client push with the uninstall option checked - and now... Happy client again.

Looking at all my inactive clients - suddenly 10-15% og my environment - it seemed like this issue happened during the upgrade to 1602.

List of client "Installation Error"

When troubleshooting client health in SCCM 2012, looking into "Push Information" you will find "Last Installation Error".
Here is a list of known errors, to help identifying and solving the issues.

2	The system cannot find the file specified.
5	Access denied.
52	You were not connected because a duplicate name xists on the network. Make sure there is not a duplicate name in DNS and that 2 machines don’t have the same IP in DNS.
53	Unable to locate – http://support.microsoft.com/kb/920852 – cannot connect to admin$ – Computer Browser not started – add File/print sharing to Exceptions in Firewall – turn file and print on.
58	The specified server cannot perform The requested operation
64	The specified network name is no longer available. Source: Windows
67	Network name cannot be found.
86	Network password is not correct? Machine Name <> resolved name.
112	Not enough disk space
1003	Cannot complete this function.
1053	The service did not respond to the start or control request in a timely fashion.
1068	The dependency service or group failed to start
1130	Not enough server storage is available to process this command. Source: Windows
1203	The network path was either typed incorrectly, does not exist, or the network provider is not currently available. Please try retyping the path or contact your network administrator.
	An extended error has occurred. Source: Windows
1305	The revision level is unknown.
1396	Logon Failure: The target account name is incorrect. (NBTSTAT -a reverse lookup, duplicate IP address).
1450	Insufficient system resources exist to complete the requested service. Source: Windows
1789	The trust relationship between this workstation and the primary domain failed
2147023174	The RPC server is unavailable.
2147024891	Access is denied
2147749889	Generic WMI failure (Broken WMI).
2147749890	Not found – Source: Windows Management (WMI) – try repair WMI.
2147749904	Invalid class – Source: Windows Management (WMI).
2147749908	Initialization failure – Source: Windows Management (WMI).
2147942405	Access is Denied (Firewall rule? / MacAfee-HIPS?).
2147944122	The RPC server is unavailable. (Dcom is miss-configured for security (http://support.microsoft.com/kb/899965).
2148007941	Server Execution Failed.

Hope this will help you on your way.

SCCM 2012 SP1, adding additional SUP

From SCCM 2012 SP1 it is possible to add additional SUPs, ie. as failover.

I have a Standalone Primary Site server with co-existing sql server - all 2012 versions.
On the PS server I have installed almost all SCCM roles.
I now want to have failover SUP, installed on one of my DPs.

This is how I did it:

First, make sure that the SUP on the PS is working.
On the DP, add the "Windows Server Update Services" role.
As options, select "WID Database" and "WSUS Services".

When installation has finished, go to the SCCM console, and select "Add Site System Roles" for the DP.
Select "Software update point".
Configure WSUS for ports 8530 and 8531

Then just wait....
and suudenly, in Monitoring > Software Update Synchronization Status,
you will find your additional SUP listed, with the PS as Synchronization Source and Synchronization Status = Completed with Last Synchronization Error Code = 0X00000000

Part IV: Installing WSUS

Installing the WSUS is very simpel.
Go to Server Manger,
Select Manage, Add Roles and Features
In Roles, select Windows Server Update Services
and configure this to use the local SQL Server (not Windows Internal Database)
and store update locally.

Part III: Installing the Site Database

We have decided to install the Site Database on the Site Server.
This will reduce the number of devices that can be managed by the system, but in my estimate, this should be sufficient.

The installation of the SQL server is fairly simpel.
I install the program to c:\program files and changes the database files and log files to dedicated drives.
For SCCM it is only needed to install:
- Database Engine Service
- SQL Server Reporting Services
- Management Tools
A very important thing to remember: Install with the correct collation -  SQL_Latin1_General_CP1_CI_AS

I will use a domain account to run the services..
- then we shall remember SetSPN
- - setspn –A MSSQLSvc/SQL Sever netBIOS name:1433 domain\account
- - setspn -A MSSQLSvc/SQL Sever FQDN:1433 domain\account
-- you can verify by: setspn -L domain\account

SQL Server memory will have to be configured.
-- min 8GB for the SQL server
-- max (leave at least 4 GB for OS and applications)

Remember to configure the Firewall to allow traffic on TCP 1433 and TCP 4022 (this is for SQL replication)

Additional task:
Since the box has 16 cores, after installation of SCCM I will configure 16 database files for th CM database.

But now I will be ready to install WSUS.

Part II: Preparing the OS on the Stand-alone Primary Site Server

Well... this Server 2012... wonder if I'll ever get used to it !?

First, the usually server installation and configuration (IP, Timezone, locales, domain ao).
We use a proxy (I'll bet this will bring a lot of joy....) so I have to configure this as well.
As we don't have Proxycfg anymore, we will have to use NetSH
(Netsh -u proxy-server:port)

To add the required roles and features, I uses PowerShell.
Open a PowerShell prompt (as Administrator) and type:
Add-WindowsFeature Web-Windows-Auth,Web-ISAPI-Ext,Web-Metabase,Web-WMI,BITS,RDC,NET-Framework-Features,Web-Asp-Net,Web-Asp-Net45,NET-HTTP-Activation,NET-Non-HTTP-Activ,Web-Static-Content,Web-Default-Doc,Web-Dir-Browsing,Web-Http-Errors,Web-Http-Redirect,Web-App-Dev,Web-Net-Ext,Web-Net-Ext45,Web-ISAPI-Filter,Web-Health,Web-Http-Logging,Web-Log-Libraries,Web-Request-Monitor,Web-HTTP-Tracing,Web-Security,Web-Filtering,Web-Performance,Web-Stat-Compression,Web-Mgmt-Console,Web-Scripting-Tools,Web-Mgmt-Compat -Restart

(if you get amn error, this could be because there are no internet connection when installing .NET3.5.
Then install .NET3.5 through the Server Manager, but point to your installation media)

After installing these roles/features, you must register ASP.NET with IIS.  The simplest way is to open an elevated command prompt: C:\Windows\Microsoft.NET\Framework64\v4.0.30319>aspnet_regiis.exe –r

Next, you will install "Windows Assessment and Deployment Kit (ADK) for Windows 8"

http://www.microsoft.com/en-us/download/confirmation.aspx?id=30652

Select the following Features:

• Deployment Tools

• Windows PE

• USMT

Then we are ready for installing the SQL server.
(some would install wsus now, using the WID (Windows Internal Database), but I prefer to use the SQL server for WSUS as well)

Part I: Our SCCM 2012 environment

We have decided that we will build our SCCM 2012 on newest environment / versions, so
the (stand-alone) primary site server will be configured with:

Operating System:   Windows Server 2012, Std edt
SQL server: Microsoft SQL Server 2012 Std edt, SP1
and SCCM 2012, SP1 (and with the newly released CU1)

The two distribution points in the datacenter will also be installed on Server 2012.

Moving to SCCM2012

 

Finally

We are now starting to migrate to SCCM 2012.

First step is the design. This is not so complicated.
We are expecting approx. 20,000 agents, and we are supporting approx. 100 locations ww (some large, some very very small).

With these figures, I can avoid the CAS, and I will be able to support the organization from a single Primary Site Server (holding a lot of SCCM roles).

As we are running SCCM 2007r3 at the moment, the site servers at all locations will be “converted” to 2012 distribution point.

That will give this simple architecture:

I will continue blogging with my experince implementing SCCM 2012 and the migration from SCCM 2007.