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 don’t urgently need supported SQL 2016 backups / SharePoint 2016 protection from DPM, I would seriously consider 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.
Recent installs of VMM 2016 have shown nice improvements over 2012, especially a much needed performance boost with storage operations through SMI-S.
Our latest SMI-S provider from NetApp (for ontap 9.1) in combination with VMM 2016 – seems to be light years ahead of 2012 R2. It’s responsive and carries out tasks in a tenth of the time that VMM 2012 took with ontap 8.
All issues with the SMI-S provider going unresponsive have been found to be due to a little service running in windows:
This little chap seems to randomly keel over – with system and application logs revealing nothing as to why.
- Log Name: Application
Source: Application Error
Date: 28/04/2017 17:44:20
Event ID: 1000
Task Category: (100)
Faulting application name: svchost.exe_MSStrgSvc, version: 10.0.14393.0, time stamp: 0x57899b1c
Faulting module name: concrete.dll, version: 10.0.14393.0, time stamp: 0x57899a8c
Exception code: 0xc0000005
Fault offset: 0x0000000000002eb0
Faulting process ID: 0xe38
Faulting application start time: 0x01d2c03e31b6c56d
Faulting application path: C:\Windows\system32\svchost.exe
Faulting module path: c:\windows\system32\concrete.dll
Report ID: 1bc955fe-6a3b-469b-8c0c-de7992f3858d
Faulting package full name:
Faulting package-relative application ID:
I have logged it with premier support – they know about it, but a fix isn’t available as yet. Frustrating, but not the end of the world – just start the service again, wait 2 mins, then refresh the provider in SCVMM – all is good!
As soon as a fix is available – I will post an update here.
- WinCXE is planning of hotfix for Windows 10 version 1607. The KB article ID is going to be 4019472.
This should be available towards the end of May 2017.
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.
Update – Aug 2017
Currently under UR2, we experience errors pertaining to DPM being unable to mount certain files under the mount points. It’s a known issue and current workaround is to also add a drive letter to the disks (can be added along side the mount point, no need to change anything else).
This should be resolved in further updates.