It’s out now –
A lot of good VMM fixes in there – which I will be testing soon. Bulk host agent update script is in Charbel’s blog here: https://charbelnemnom.com/2017/05/update-rollup-3-for-system-center-2016-is-now-available-sysctr-systemcenter-scvmm/
Details of SCOM fixes in Kevin’s blog here: http://kevingreeneitblog.blogspot.co.uk/2017/05/scom-2016-update-rollup-3-ur3-now.html
I’m a little disappointed to see DPM missed an update in UR3. VMware support is still missing from 2016 – but all will be forgiven if this turns up in UR4 along with fixes for woes experienced with UR2 currently:
Tape Library Sharing – 2012 OS cannot remove TL sharing & re-establishing 2016 OS TL required a manual DB cleanout (with Premier Support).
Console Crashing on PG alteration – requires DLL from MS (see my previous posts)
Mount points, whilst supported for the storage (see my other posts) uncover a known issue with DPM mouting the VHDX files for Modern backup Storage – the workaround for this is to add a drive letter to the storage.
If you dont urgently supported SQL 2016 backups / sharepoint 2016 protection from DPM, I would serously condider sticking to UR1 for now.
Roll on UR4! 🙂
Take the pain away from manual deployment – grab the agent and put it into SCCM. The command lines for agent install (2016 UR2) are:
DPMAgentInstaller_KB3209593_AMD64.exe /q /IAcceptEULA
DPMAgentInstaller_KB3209593.exe /q /IAcceptEULA (for x86)
Just make sure all the agent pre-reqs are in place (WMF 4.0 for 2008 R2 etc…) and make the detection of those a pre-req for the SCCM deployment.
If you know what DPM server you are going to protect with – simply add the server name to the install above – that will open the ports and make the agent ready to be attached.
If you dont just yet – then run a second SCCM task to call a batch file running the setdpmserver.exe (in the DPM agent Bin directory) to configure the agent.
Run an “Application deployment type compliance details” report in SCCM, using your target collections, application, deployment type and status of “Success” to generate a CSV file of the installed agents.
Take the computer name column in excel, append your domain name (using concatenate) and put the resulting list into a .txt file (no headings or any other info required)
Open the DPM console – select Install, Attach Agents, click add from file and point to your txt file.
Output from SCCM report, manipulate and import in ~10 mins saving many hours of manual config.
An excellent feature of 2016 and not to be missed. Gone is the LDM limitation and the volume mess of 2012. This is by far the best improvement on the table for DPM.
I followed some guides to test – mounting 64tb of backup storage as drive letters to windows makes it a target for temporary storage – VERY IRRITATING INDEED
You will quickly find your DPM volume has attracted itself as a temporary dumping ground for hotfixes and patches. This is not acceptable.
To avoid this – simply create yourself a folder on C: – in this case ‘MountPoints’, create yourself two empty folders – then mount your backup storage in there – rather than assigning a drive letter.
Open DPM, refresh disks and click add – you will see the two volumes available for use.
Windows wont see them in it’s drive letter searches and thusly – they will remain clutter free and available for DPM use only!
As long as you make sure they have a volume label – SCOM will happily monitor the health of drives mounted in this manner.
Just a quick snippet from Technet as it’s easily overlooked. When installing DPM 2016 RTM, you need to make sure that SQL 2016 does NOT have SP1 installed.
Once DPM is installed and you have applied UR2, you can patch SQL to SP1.
Don’t forget to enable browser service, named pipes (for Library sharing) and clear all pending reboots…
Once you are running DPM 2016 UR2 – you may experience console crashes (services unaffected) with event ID’s 999:
The description for Event ID 999 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
An unexpected error caused a failure for process 'mmc'. Restart the DPM process 'mmc'.
19009/05/2017 13:29:28DpmThreadPool.cs163TrueNullReferenceExceptionObject reference not set to an instance of an object.System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.Inquiry.MultiDatasourceSizeInquiry.ResultUniquePath(InquiryPath junctionlessPath, InquiryPath startNodeRelativePath, String serverName)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.Inquiry.MultiDatasourceSizeInquiry.ProcessResults(InquiryTaskInformation taskInfo)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.Inquiry.MultiDatasourceSizeInquiry.OnInquiryResultsArrival(InquiryResult result)
at Microsoft.Internal.EnterpriseStorage.Dls.UI.ObjectModel.Inquiry.MultiDatasourceSizeInquiry.rornTaskDef_TaskProgress(Object sender, EventMatchedEventArgs eventEntry)
at Microsoft.Internal.EnterpriseStorage.Dls.EngineUICommon.RORN.RornTaskDef.Task_TaskProgress(Object sender, EventMatchedEventArgs e)
at Microsoft.Internal.EnterpriseStorage.Dls.EventManagement.BaseEventFilter.Send(EventMatchedEventArgs args)
at Microsoft.Internal.EnterpriseStorage.Dls.EventManagement.EventManager.PollingThreadProc(Object data)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart(Object obj)
the message resource is present but the message is not found in the string/message table
These occur when adding secondary protection (DPM to DPM) to an existing Protection Group, as soon as you reach the storage calculation screen – bang, MMC crashes.
The issue resides with objectmodel.dll (in the BIN directory) – a replacement from MS was supplied and immediately resolved the issue.
If this is the case, currently the fix exists as a private hotfix only and must be obtained by logging a call with MS support.
I have asked if it will be made public and will update the blog when I hear back.
Update 10 May 2017
Premier Support have advised that the fixed DLL will be part of a future UR pack, but could not confirm if it would be UR3 or 4. So my advice is you test your environment with a few machines and see if you encounter the error – if you do, contact support and request the fixed DLL before you proceed into full production use.