I have been working in IT since 2001 for companies such as Computacenter and Getronics. I started out as a first line support analyst supporting heterogeneous networks but rapidly worked my way up the ranks expanding my knowledge as I went to include areas such as system builds, deployments, networking, and security to name a few.In 2008 I decided to concentrate on the monitoring and management of large enterprise networks using Microsoft's System Center Operations Manager (OpsMgr) 2007 of which I have extensive knowledge. As testament to this the Windows Management User Group (WMUG), invited me to join their ranks as a Community Leader where I have been invaluable in helping to bolster the OpsMgr skills to the benefit of the group and it's members.I have now moved into an OpsMgr 2007 consultancy role to do what I like most - working with OpsMgr and sharing my knowledge and experiences with the community.
If you try to run DPM cmdlets in the DPM Management Shell on a computer other than the DPM server after installing SP1 you will probably see this error.
And, after following the instruction in the error to reboot you will continue to receive this error. What is actually causing this fault is that the DPM Management Shell on the computer you are running it on has not been upgraded to SP1. Download and install SP1 for the DPM Management Shell from http://www.microsoft.com/dpm and your ability to run PowerShell scripts for DPM from a remote computer will be back.