UR3 for OpsMgr 2012 SP1 has been released and is available for download. This update rollup contains fixes for a variety of both Operations Manager as well as UNIX and Linux monitoring issues. You can get all the details as well as a download link here:
KB2836751 - Description of Update Rollup 3 for System Center 2012 Service Pack 1 (http://support.microsoft.com/kb/2836751)
J.C. Hornbeck | Knowledge Engineer | Microsoft GBS Management and Security Division
Get the latest System Center news on Facebook and Twitter:
System Center All Up: http://blogs.technet.com/b/systemcenter/ System Center – Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ System Center – Data Protection Manager Team blog: http://blogs.technet.com/dpm/ System Center – Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ System Center – Operations Manager Team blog: http://blogs.technet.com/momteam/ System Center – Service Manager Team blog: http://blogs.technet.com/b/servicemanager System Center – Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm
Windows Intune: http://blogs.technet.com/b/windowsintune/ WSUS Support Team blog: http://blogs.technet.com/sus/ The AD RMS blog: http://blogs.technet.com/b/rmssupp/
The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/ The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/ The Forefront TMG blog: http://blogs.technet.com/b/isablog/ The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/
Hi, happy to see that Operations Manager SP1 UR3 is out. Unfortunatly, I wasn't able to locate the download for SCOM, all other SC components seems to be available but not SCOM... Do you have a hint to find it?
use the below URL for SCOM 2012 CU3
use the below URL for SCOM 2012 SP1 CU3
Installed this on our DPM server - but get the 301 error when trying to update any of the DPM agents on protected computers. Now have to delete and recreate all our protection groups, uninstall the agents and then install again. Pain.
After install on DPM server, I get error 301 on updating agents. Manual updating works fine.
I have feeling that every new version of software you publish needs a lot more quality control.
I'm also getting Error 301, and have to uninstall and re-install. I'm also then getting an error 337 when I re-install so have to do it twice. This is ridiculous, Microsoft - we need to be able to trust your update rollups. If you can't test your code properly don't release it.
In case anyone else has been hit by this, a workaround seems to be to run the agent install on each affected client manually from the DPM server. <DPM Server>\c$\Program Files\Microsoft System Center 2012\DPM\DPM\agents\RA\4.1.3415.0\amd64\1033\DPMAgentInstaller_KB2853210_AMD64 <DPM Server>. substituting i386 for amd64 if required. Way easier than remove from PGs, uninstall, reinstall, add back to PGs - but it still adds up if you're doing a bunch of servers.
Or use SCCM I guess, although for this fix /q doesn't seem to do a silent install and you still have to accept the license, not completely sure about that though, I'm just doing mine by hand.
Musta been the B team that built this rollup.
What about Service Manager? Any update to be expected in the next few days?