Hi,

I have an old windows 2003 server x64 protected by DPM 2012 Sp1. After DPM upgrade to 2012 R2 I cannot update DPM Agent on server. If I try to update agent manually error message is : agentsetup.exe is not a valid win32 application.

Mihai

Same problem with Windows 2003 server 32 bit, i have installed vc 2010 redistributable x86 and i use the x86 agent installer.

DPM 2012 R2 does not support 2003 ? But i do not see anything about that.

Having exact same problem. Installed the agent on a 2012 and 2008r2 server. Fail to install the agent on a 2003 x64  server (std edition SP2).

I have found a log file "setupapi.log" in c:\windows and it shows:

#W361 An unsigned, incorrectly signed, or Authenticode(tm) signed file "c:\program files\microsoft data protection manager\dpm\bin\dpmfilter.inf" will be installed (Policy=Ignore). Error 0xe0000244: The software was tested for compliance with Windows Logo requirements on a different version of Windows, and may not be compatible with this version.

After check this :

http://technet.microsoft.com/en-us/library/jj860400.aspx

Seems that Windows server 2003/2003 R2/Vista is not supported by DPM in System Center 2012 R2 !!!!

• Edited by Cestbienmoi Friday, October 18, 2013 1:23 PM
• Proposed as answer by Tom Drought Saturday, November 02, 2013 2:02 AM
• Marked as answer by BuchatechMVP, Moderator Monday, November 04, 2013 5:25 AM

Damn you Microsoft.

So now I need to roll back to DPM 2012 somehow.

Thanks a bunch.

My main SQL database server is on 2003 R2 x64 and there is no plans to upgrade it as it is running fine. So we are stuck with DPM 2012 and cannot move forward now. Great.

After the disaster that is Windows Server 2012 (touch interface on a server HAHAHAHAAH!!!!!?!?!?!) and now this I am seriously looking to move away from MS products.

• Edited by Kaonix Friday, October 18, 2013 2:00 PM

After check this :

http://technet.microsoft.com/en-us/library/jj860400.aspx

Seems that Windows server 2003/2003 R2/Vista is not supported by DPM in System Center 2012 R2 !!!!

That is correct. 2012 R2 no longer supports 2003. We have given feedback to Microsoft that DPM needs to continue supporting 2003.

I like things like that

This Is not a valid win32 application

The Programmer cannot make a Query with "This is not a supportet OS" !!!

Very hard Work for MS and not so Helpfull?!?!

Thanks for stolen our time!

After check this :

http://technet.microsoft.com/en-us/library/jj860400.aspx

Seems that Windows server 2003/2003 R2/Vista is not supported by DPM in System Center 2012 R2 !!!!

That is just disgusting.... Seriously. 

Thank you just very F.....G much Microsoft DPM Team !

D@mned if you do upgrade - d@mned if you don't. 

If you don't upgrade you can't back up your new servers (no 2012 R2 Hyper-V support as an example)

If you do upgrade you can't back up your old servers (2003 R2)...

Thanks MS for that well thought out strategy - and for not supporting your own OS that is in your own catalog as being officially fully supported until 2015! 

Wow... Just Wow.... and they wonder.... why are we losing market share every day? 

• Proposed as answer by Meitzi Thursday, December 12, 2013 9:26 AM

Here is the mess that Microsoft have created for me:

Cannot run Exchange 2013 on Server 2012 R2

Cannot Backup Server 2003 R2 with DPM 2012 R2

Cannot use Dynamics CRM 2011 with Exchange 2013

Cannot backup Server 2012 R2 with DPM 2012

Cannot in-place upgrade my 2003 R2 database server to 2012 so that I can then back it up with DPM 2012 R2

Cannot use POP3 on Microsoft Surface RT

Cannot do this cannot do that!!!

Seriously the left hand does not know what the right hand is doing.

It used to be an easy choice for a small business to use Microsoft products. Now it is jumping through hoops just to get Microsoft own products working on Microsoft own server platforms!!!

When can we expect DPM 2012 R2 to put support back  for 2003 server?!

This is crazy. I can't believe they've dropped support for a product that's allegedly supported until 2015!

I've upgraded my hyper-v cluster to 2012 R2, but as loosing the capability to back up my 2003 servers is not an option, I'm going to stick with 2012 SP1 and just install the DPM client inside each of the Hyper-V guests.

I suggest others do the same until Microsoft fix the problem. Looking on the bright side, I don't have to spend money upgrading to DPM 2012 R2.

• Edited by fusiongroup Monday, December 02, 2013 2:03 PM

Yep, this is a total mess.  Not everything can be upgrade from 2003.  I have an old ERP that requires a specific version of SQL 2005 that is not able to run on 2008.  That said, our only option is run it on 2003.  The problem is all of our new Hyper-V hosts are 2012 R2 which requires DPM 2012 R2.  How is this possible?  I might have to fire up Backup Exec just for this one server.  Talk about dropping the ball here.

Most larger companies that run large amounts of Hyper-V and DPM are almost guranteed to have some 2003 servers around.  Are these companies supposed to decide on Windows Server 2012 R2 for its Hyper-V benefits or should they say hell with it, we need support for 2003 via DPM.

Ou man I'm pissed off right now.

Where's the feedback on Microsoft Connect regarding this issue? 

Anyone have a plan on how to downgrade?

This is really unacceptable.  DPM already has so many shortcomings (for example, it wastes hard drive space like mad and it's quite difficult to reclaim once it's been allocated to a volume), but the one thing I could count on was that it had amazing built-in support for Everything Microsoft.  With DPM 2012 R2, that's no longer the case.  Only 2008 R2 or newer?  In my wildest dreams could I migrate all my workloads out of 2003 R2 and 2008, but fact is I can't, whether or not the OS is supported by Microsoft.  Of course, the fact that 2003 R2 is supported into 2015 certainly makes this decision more dubious.  Plus... this is a removal of a feature.  It's not like VSS doesn't exist in 2003 anymore or that a new feature was introduced to 2003 that isn't being added.  This is just taking out something that worked because they want their support matrix to be smaller so there's less QA time needed.

• Edited by Timothy Carroll 15 hours 23 minutes ago

Is anyone from Microsoft listening? That was a real shoot in the own foot.

Put back Windows server 2003 backup support via DPM 2012 R2!

This is really unacceptable.  DPM already has so many shortcomings (for example, it wastes hard drive space like mad and it's quite difficult to reclaim once it's been allocated to a volume), but the one thing I could count on was that it had amazing built-in support for Everything Microsoft.  With DPM 2012 R2, that's no longer the case.  Only 2008 R2 or newer?  In my wildest dreams could I migrate all my workloads out of 2003 R2 and 2008, but fact is I can't, whether or not the OS is supported by Microsoft.  Of course, the fact that 2003 R2 is supported into 2015 certainly makes this decision more dubious.  Plus... this is a removal of a feature.  It's not like VSS doesn't exist in 2003 anymore or that a new feature was introduced to 2003 that isn't being added.  This is just taking out something that worked because they want their support matrix to be smaller so there's less QA time needed.

• Edited by Timothy Carroll Tuesday, January 14, 2014 8:52 PM

Is anyone from Microsoft listening? That was a real shoot in the own foot.

Put back Windows server 2003 backup support via DPM 2012 R2!

Hi Thomas,

I can re-assure you Microsoft is listening. The right teams have seen this thread and they have heard all the feedback here loud and clear.

We all have to wait and see what they do.

This is crazy! Prerequisites state if the protected computer is running Windows 2003 you need to download KB975759. Doesn't say anything about not supporting it.

Article here.

http://technet.microsoft.com/en-us/library/dn296603.aspx

Microsoft.  This is needed, please help.  I like a poster above have several servers that are running an older ERP system that is running Windows 2003 and SQL 2005.  I don't have a choice right now to upgrade.  Requirements of Sarbanes Oxley require this to be backed up.  I do not want to roll back.  This is really unacceptable.