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.
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.
OS deployment using USB key to boot the new device. Just after the .wim file had finished copying received this error: 0x80070570.
Research suggested corrupt or unreadable disk. Ran the relevant DISKPART commands to clean the disk. Same error occurred several times.
Fixed by removing the USB key from the device before the Task Sequence started to apply the image.
Tried to install an all new SCCM infrastructure using SQL Server 2014 SP1 as the site database platform and after passing the SCCM install prerequisite checks I got an error message stating the version of SQL Server was not supported (SQL Server 2014 SP1).
Seen this a few times now. If the SCCM Client Agent can’t access the Management Point during the install a Windows Task Schedule is created to ensure the Client install will keep retrying even if the device is rebooted.
To stop the situation where the client is working OK but the reinstall keeps occurring every five hours – delete the scheduled task – it’s tucked away under the second Microsoft node in the Task Scheduler console (and not in the first Configuration Manager node you may see under the first Microsoft node!).
Error Code 0x87D00708 means that the software update the error refers to is now not required by the device.
To remove the update from Software Center and prevent systray notification run a Software Updates Scan Cycle of the affected device(s).
Error Code: 0X87D00664 is an indication that the the installation of the software update has timed out. To fix:
- In the SCCM console access the Software Library workspace.
- Access the Software Updates node.
- Search for the update.
- Select the Properties for the update.
- Select the Maximum Run Time tab.
- Change the time to 60 minutes for example.
- Retry the install of the update.
If you use a SCCM 2012 Automatic Deployment Rule (ADR) to deploy software updates, over time the package can become quite large. This procedure details the steps taken to link a new package to an existing ADR. A good time to do this is early January (before Patch Tuesday) as this will result in packages/folders for each calendar year.
- Create a new folder for the package source files, typically under a shared folder containing all your software update source files (needs to be referenced by a UNC later in this procedure).
- In the SCCM Admin Console, open the Properties dialogue for the relevant ADR.
- On the General tab select the Create a new Software Update Group.
- On the Deployment Package tab select Create a new Deployment Package.
- Give the package a meaningful name.
- Browse to the package source folder created earlier to set the Package Source.
- Run the rule so it creates the new software update group and new package.
- View the RuleEngine log file on the SCCM server to monitor the actions instigated by running the ADR.
After the Running of the Rule is Complete
- Access the Deployment Packages node, right-click the new package that has just been created by the ADR and select Distribute Content.
- Access the Software Update Group node.
- Rename the group the ADR has just created so it reflects the fact it is the software update group created by the ADR, e.g. Server-2012-ADR-SUG.
- Return the properties page of the ADR just changed.
- On the General tab select Add to an Existing Software Update Group. This ensures that next time the rule is run it uses the group just created and does not keep creating a new group every month.
Note: When editing an ADR the link to the deployment package is not maintained thus the need to distribute the package. This step will be automated next time the rule is run.
Note: Be careful if you run an ADR manually as the deadline will be set based on the Specific time setting on the Deployment Schedule tab of the ADR. The automatic rule probably sets this to the early hours of the morning, e.g. the rule runs at 05:00 and the deadline is 05:00 seven days later. If the ADR is run manually the deadline will be exactly seven days from when the rule is run and this may be during the working day which you probably don’t want.
In order to allow users to run the SCCM 2012 Compliance 1 – Overall compliance report without the need to enter the two required parameters the following procedure was completed.
Obtain the Required Parameters
- Obtain the Collection ID of SCCM collection to run the compliance report against. In my case I used SMSDM003 which is the generic ID for the All Desktop and Server Clients SCCM collection.
- Obtain the Software Update Group ID to run the compliance report against. This can be obtained by exposing the CI Unique ID column in the SCCM console, using ctrl+c to copy the data and then ctrl+v into Notepad.
- Access the SSRS home page.
- Create a new folder called Custom Reports.
- Create a subfolder called Compliance Reports.
Link the Report
Note: You need to link the report rather copy the report otherwise the secondary reports will not run.
- Navigate to the Software Updates – A Compliance report folder.
- Click the Compliance 1 – Overall compliance report and select Manage from the dropdown.
- From the menu bar click Create Linked Report.
- Give the report a name, e.g. Overall Compliance Report.
- Click the Change Location button.
- Navigate to the Compliance Reports folder just created and click OK at the bottom of the page.
- Click OK again to save the new report.
Adding the Parameters
- Navigate to the Compliance Reports folder and the newly saved report should be visible.
- Select the Overall Compliance Report and Manage from the dropdown.
- Click the Parameters button on the left.
- Clear the two checkboxes in the Prompt User column.
- Tick the two checkboxes in the Has Default column (adjacent to AuthListID and CollID labels).
- Enter the Collection ID in the CollID text box and the Software Update Group ID in the AuthListID text box.
- Click the Apply button.
Running the Report
- Back at the folder list run the Overall Compliance Report. It should now run without the need to enter any parameters.
- When the report opens in Internet Explorer copy the URL of the report.
The URL can now be distributed to users who will be able to run the report without the need to enter the parameters (subject to appropriate permissions).
Link to a detailed list of all SMS/SCCM version and build numbers:
SMS – SCCM Version Numbers
SCCM 2012: SCCM 2012 Version Numbers