Thursday, January 10, 2013 10:47 AM
I'm running DPM 2012 - upgraded to the RTM SP1 (from Technet) then updated to SP1 UR1 (KB2791508).
I've tested this on both my production server and a lab VM and see the same results on both.
KB2791508 installs apparently without a problem. However it reports different version numbers depending on whether you click on the About DPM button in the admin console (4.1.3322.0 - I believe this is the correct version for UR1)
or go to Help -> About DPM (4.1.3313.0 I believe this is SP1 RTM)
The other thing I've noticed which seems odd is when I went to do a manual install
C:\Program Files\Microsoft System Center 2012\DPM\DPM\ProtectionAgents\RA\ contained only 4.1.3313.0
There is a folder C:\Program Files\Microsoft System Center 2012\DPM\DPM\agents\RA\4.1.3322.0
Does anyone know what the distinction between the ProtectionAgents and Agents folders is and whether it's ok to use the version from the Agents folder? Is it a cause for concern that there is a mismatch between the versions in these folders?
Friday, January 11, 2013 11:41 PMModerator
As noted, the C:\Program Files\Microsoft System Center 2012\DPM\DPM\ProtectionAgents\RA folder is the base agent for the product.
The C:\Program Files\Microsoft System Center 2012\DPM\DPM\agents\RA will be updated agents from each successive rollup package.
I can't comment on why the versions are different, they are usually the same, but always use the About DPM icon - that should always reflect the latest RU version installed.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights.
- Proposed As Answer by Mike JacquetMicrosoft Employee, Moderator Friday, January 11, 2013 11:42 PM
Monday, January 14, 2013 2:43 PM
Thanks, but having actually tried this on a couple of clients, if I try and install the up to date agent from \DPM\agents\RA\4.1.3322.0 I get an error "Protection Agent cannot be installed on a machine where DPM is installed", even on a fresh install of Windows.
Whereas the older agent from DPM\ProtectionAgents\RA\4.1.3313.0 installs ok. I can then update it to 4.1.3322.0 through the console.
Other than this it seems to be working - but it seems a bit odd.
Has anyone else updated to SP1 UR1 and can confirm if they are seeing the same behavior?
Monday, January 14, 2013 8:44 PM
I just installed and I'm seeing the same thing with the different versions. I have not tried installing the latest agent.
In addition, if I run windows update I don't see any available updates. If I click the "Check Updates" button in DPM however, I am take to a link for Update Rollup 3 for System Center 2012. I'm walking into DPM blind, so maybe this is normal, but I was under the impression that all updates would come through windows update.
Friday, January 25, 2013 10:47 AM
Thanks for the confirmation, it's reassuring (sort of) that it's not just me. Regarding the updates, the Check Updates button does seem hit and miss, it just points to a webpage that doesn't always seem to be updated. You'll find a lot of the "click here for more details" links you get in DPM relating to errors etc. also link to empty web pages - they don't seem to put enough effort into this product.
I think some updates do show up on Microsoft Update, the other place to look out for them is the DPM blog which is worth subscribing to.
Anyhow, they seem to have sneaked out a DPM 2012 SP1 UR1 (v2) on KB2802095 which takes it to version number 4.1.333.0. Download here.
I don't know what's changed in this, as of now Google returns no hits for KB2802095 and there is no page on the knowledgebase website for it. However it does fix the issue I saw when I started the thread of the inconsistent version numbers. So I'm going to go with this was a bug that's been resolved with a re-issued UR1.
- Marked As Answer by TimBoothby Friday, January 25, 2013 10:48 AM