SCCM 2012 – Installation of New Distribution Point Fails


Saw the message below in the Distribution Point Configuration Status window in the SCCM Admin Console when trying to install a new SCCM 2012 R2 SP1 Distribution Point.  Target server running Windows Server 2012 R2 Update.

Failed to install DP files on the remote DP. Error code = 1722

  • Copy smsdpprov.mof from ..\Program Files\Microsoft Configuration Manager\bin\X64 on the Site Server to the server where the DP install has failed.
  • Open an Command Prompt as Administrator and run mofcomp.exe smsdpprov.mof.

When a DP install fails SCCM will try again every 20 mins.  Kept an watch on the DistMgr log file and the DP installed OK after the above command was run and subsequent content distribution worked as expected.

SCCM 1511 Installation Notes

Done a couple of upgrades from SCCM 2012 R2 SP1 to SCCM 1511 and they were straight forward as the prerequisites were in place already.  The notes below were taken doing a new install of SCCM 1511,  albeit into a Active Directory domain that already had the schema extended and appropriate user accounts in place.  In general the preparation required is very similar to doing a SCCM 2012 install.

  • All servers running Windows Server 2012 R2 RTM.
  • 1 x Standalone Primary Site Server
  • 1 x SQL Server 2014 Database Server (used for SCCM and WSUS databases)
  • 1 x Software Update Point Server
Preparation – all servers

As the servers were not to be exposed to the existing SCCM 2012 environment, including the 2012 SUP,  the following updates were applied to the servers in the stated order:

  • KB2919442  – this is a prerequisite for Windows Server 2012 R2 Update and should be installed before attempting to install the following updates
  • KB2919355
  • clearcompressionflag.exe
  • KB2919355
  • KB2932046
  • KB2959977
  • KB2937592
  • KB2938439
  • KB2934018

Site Server
  • Server Features – .Net 3.5, .Net 4.5, Remote Differential Compression, BITS and WSUS 4.0 Remote Server Admin tool (Software Update Point going on a remote server so need Admin Tools on the Site Server).
  • IIS Settings
    • Common HTTP Features – Default Document, Static Content.
      Application Development – ASP.NET 3.5, .NET Extensibility 3.5, ASP.NET 4.5, .NET Extensibility 4.5, ISAPI extensions.
    • Security – Windows Authentication.
      IIS 6 Management Compatibility – IIS Management Console, IIS 6 Metabase Compatibility, IIS 6 WMI Compatibility, IIS
    • Management Scripts and Tools.
  • AD Schema already extended – add permissions against the Systems Management container for the new SCCM 1511 Site Server account (remember to allow for descendant objects).
    Obtain the SCCM 1511 source files.
  • Download the SCCM 1511 Install prerequisite files (manually by running ..\SMSSETUP\BIN\X64\setupdl.exe SaveLocation from the SCCM 1511 source files)
  • Obtain and install WADK 10 (not the 1511 version as there is a widely reporting issue with this version). Features required:
    • Deployment Tools, Windows Preinstallation Environment, Imaging and Configuration Designer and User State Migration Tool.
  • Obtain license key.
  • Add the Site Server account to the Database Server and SUP Server local admins groups.
SQL Server
  • Collation – SQL_Latin1_General_CP1_CI_AS
  • SQL Services – run as Local System, not defaults offered.
  • SQL Features – Database Engine and Management Tools (Reporting Service will be on remote server at a later time)
  • Allow the required SQL Server ports in Windows Firewall (1433 and port 4022)
Software Update Point Server
  • Server Role – Windows Server Update Services
    During install point to remote database and not Windows Internal Database.
  • After initial install, reboot and run Role Configuration from Server Manager (this bit creates the database etc.)
  • Do not configure WSUS itself – just do the automated Role Configuration.
  • Reboot and install KB3095113 –
Install Notes
  • Ignore SQL Server-related warnings – only 4GB RAM allocated to my DB server in my lab.
  • No to new Service Connect Role (want to do this later)
  • Point to existing install prerequisites.
  • Don’t use a Site Code that has been used before in the test lab domain!
  • Ensure the account used to run the install has the appropriate permissions on the Site Server, DB Server and within SQL Server.

Acknowledgements and thanks for continued contributions to the SCCM community.

SCCM 2012 OSD – There are no task sequences available for this computer

Seen this error message appear a few times during OSD.

  • Is the device in a SCCM Collection that has a valid Task Sequence available?
  • Check your boundaries – is the device within a configured boundary?
  • Is this device an existing SCCM client that is being rebuilt using the same Task Sequence?  If so delete the existing object from SCCM using the Admin Console.
  • Has the device existed in SCCM but you do not know the original name?  Look in the smsts.log – you will see the SMSBIOS GUID for the device that can then be searched for in the Admin Console and then deleted.
  • If it is an existing device that has never run the Task Sequence, clear Required PXE deployments using the device context menu in the SCCM Admin Console.

Installing the WSUS 4.0 Admin Console Manually on Windows Server 2012 R2 for SCCM 1511 Software Update Point

SCCM 1511 Site Server requires WSUS Admin Tools to be installed if the SCCM 1511 Software Update Server (SUP) is running on a remote server.

User PowerShell:

  • Install-WindowsFeature -Name UpdateServices-Ui

Or from the GUI.

  • Server Manager
  • Manage menu # Add Roles and Features
  • Expand Remote Server Admin Tools
  • Expand Role Admin Tools
  • Select Windows Sever Update Services Tools

VMware vSphere – Adding Disk to a new VM Fails – A general system error occurred: Failed to create journal file

Received this error when trying to add an additional disk to a VM.

A general system error occurred: Failed to create journal file providerFailed

Various other vSphere actions also failed with the same message including vMotion.

Problem – the vCenter server was running low on disk space on the drive containing this file: %PROGRAMDATA%\VMware\VMware VirtualCenter\journal.