- Discovery and Boundaries
- Site Roles
- Client Settings
- Client Installation
- Endpoint Protection and Antimalware Policies
How to add a user for SCCM console access.
SCCM Console error – user has insufficient permissions.
System Center DPM 2018
How to fix the SCDPM 2018 install error SQL mgmt tools are not installed. While installing SCDPM 2018 I received an error that the SQL mgmt tools were not installed even though I did install them. Turns out, SCDPM version 1801 requires a specific version of the SQL mgmt tools or the install will fail. See the video below for the fix.
You can safely delete these .errlog files but first you need to investigate the most recent ones and take the appropriate actions. If you need to recover space immediately then copy the most recent few logs to an alternate location and then you delete all of them on the DPM server.
SCCM server C drive almost full?
If you log in to your SCCM server and one day see that your C drive is almost full then you have several places to check. Could be your SQL logs or your inetpub logs. In this case it was the inetpub logs.
Check your inetpub logs:
Browse to C:\inetpub\logs\LogFiles.
In my environment, when I first right clicked the log files folder and looked at the properties – it showed no disk space being used. This almost had me moving on to check another possible location. This is deceiving as there should be some space being used. Once I double clicked to open the actual folder it then prompted for permission and afterward I could see the true amount of disk space being used.
Here I had about 20 gigs of space being used up on my SCCM server C drive. You can archive the log files to another location incase you need to review them later or remove them if they are no longer necessary. I arranged by date, and deleted all the log files older then 3 months which allowed me to recover almost 20 gigs of space for my C drive.
Install SCCM 1511 on Server 2012 R2:
To prepare for SCCM 1511 installation you need to first extend the Active Directory Schema: Log on to a system as an account that is a member of the schema admins (I used the domain admin account). From your SCCM 1511 ISO or other file/folder location – open PowerShell and browse to .\SMSSETUP\BIN\X64\extadsch.exe
Create the System Management Container
Configuration Manager does not automatically create the System Management container in Active Directory Domain Services when the schema is extended. The container must be created one time for each domain that includes a Configuration Manager primary site server or secondary site server that publishes site information to Active Directory Domain Services.
Click Advanced, select site server computer account, then click Edit
In the Applies to list, select This object and all descendant objects
Click Apply and OK and close the ADSIEdit console
Moving to the SCCM Server.
No_sms_on_drive.sms (placed on the sccm server).
To make this file – make a txt file and rename it no_sms_on_drive.sms
Use control panel folder options and remove the check mark from hide file extentions so you can now see the file.txt and rename it no_sms_on_drive.sms
Windows Server – Add Features
On the Primary site server, the following components must be added/installed before SCCM installation can begin:
.Net Framework 3.5 Features
.Net Framework 3.5 Features (includes .NET 2.0 and 3.0)
HTTP Activation – click Add Features to the box that pops up from this selection.
.NET Framework 4.5 Features (2 of 7 installed)
.NET Framework 4.5 (Installed)
BITS – click Add Features to the box that pops up from this selection.
IIS Server Extension
Remote Differential Compression
Remote Server Administration Tools
Feature Administration Tools – BITS Server Extensions Tools
Windows Process Activation Service
.NET Environment 3.5
Click Next to move on to the Web Server Role (IIS) Role services selections:
Web Server Role (IIS)
Common HTTP Features
Default Document, Directory Browsing, HTTP Errors, Static Content, HTTP Redirection
Health and Diagnostics
HTTP Logging, Logging Tools, Request Monitor, Tracing
Static Content Compression, Dynamic Content Compression.
Request Filtering, Basic Authentication, IP and Domain Restrictions, URL Authorization, Windows Authentication
.NET Extensibility 3.5, .Net Extensibility 4.5, ASP, ASP.NET 3.5, ASP.NET 4.5, ISAPI Extensions, ISAPI Filters
IIS Management Console
IIS 6 Management Compatibility
IIS 6 Metabase Compatibility, IIS 6 Management Console, IIS 6Scripting Tools, IIS 6 WMI Compatibility
IIS Management Scripts and Tools, Management Service.
So I did a search for Microsoft SQL Server 2014 Feature Pack and downloaded that. When you do, it gives you an option with several choices of what parts of the feature pack you want.
Choose: ENU\x64\SQLSysClrTypes.msi and install it:
Accept the agreement, install it and finish:
Now you can install Report Viewer 2015:
Accept agreement, next and complete the installation.
Click next after installation rules are checked.
In Reporting Service Configuration, Select Install only – we will configure this later. In Error Reporting, uncheck the box if you want then click Next. On the Installation Configuration Rules, verify Operation completed and Passed then click Next.
Configure SQL Memory settings: Set the SQL Min and Max memory to 8192 and 8192 MB (or you will get an warning during SCCM setup later).
Open SQL Server Management Studio
Right click the top SQL Server instance node
Launch the Prereqchk tool in order to verify if all components are configured correctly. You can launch this from the SCCM install DVD or folder where you copied the install files as in my example:
Open an Administrator command prompt Browse to .\SMSSETUP\BIN\X64
Run the following command : prereqchk.exe /AdminUI
Enter to run the Prereqchk.
Click Check connection and it should return “Successfully connected to server” if you have everything configured properly.
Click Install on the confirmation page to confirm installation selections.
Click close when it completes.
Install WSUS and database setup:
Once it is completed – reboot your sccm server that has the wsus installed and then be sure to run the post installation task to allow WSUS to complete the setup. You do not need to do the WSUS configuration just the post installation task. Otherwise, the SUSDB is not created in SQL (I found this out the hard way).
To do this – open server manager – dashboard and then click the yellow triangle with the !
Install hotfix KB3095113:
After the post install task finishes you need to install the hotfix KB3095113 to enable Windows 10 feature upgrades.
Download Microsoft https://support.microsoft.com/en-us/kb/3095113
Install the update and restart the SCCM server after it finishes.
Now you are ready to being the SCCM 1511 installation.
Install Configuration Manager Primary Site:
Install a Configuration Manager primary site – click next.
Enter your license key or select evaluation:
Agree to the terms and click next.
Accept the Prerequisite Licenses or you can’t continue…
Set SMS Provider Settings (Accept defaults):
Usage Data – click next:
Open the Configuration Manager Console:
On your sccm server, search configuration and open the CMC
Now you can begin creating your site boundaries, discovering clients, etc.
In my next post, I’ll go over boundaries, clients and upgrades to SCCM.