I was expecting problems after my previous experience with DPM but I can see the potential in the product and refuse to give up, plus this is a Beta version so I will be fair.
The initial upgrade of DPM 2007 SP1 to DPM 2010 Beta went fairly smoothly (Win 2k8 64bit) just one thing needed to be done and that was powershell v1 had to be removed and powershell v2 installed. The install progressed and finished and I checked my agents -- all needed updating. That’s to be expected and so is clicking on the update link and having it fail with error code: dpmagentinstaller failed with error code 80070534
I remembered this one from last year and manually removed the agents from the servers, rebooted and did the manual install method. You must use the FQDN when connecting to the DPM server! When the install fails you get messages and popup as you would expect informing you of the error and paths to logs etc, it would be nice to see a similar system used after a successful install. The window just vanishes and leaves you wondering what the hell just happened.
One nice thing now though is that a system reboot after agent install doesn’t seem to be necessary anymore. Next step is just consistency checks all around for the servers and everything should be up and running as per usual. The interface looks pretty much the same apart from some new reports and other small things.
Next step is to test this system on some Windows 7 clients as it is supposed to work really nicely alongside shadow copy.....
