Best Practices Analyzer - Unable to scan
-
Monday, June 30, 2008 1:45 PMI am just starting with MDM and have deployed the Device Management server - 2003 R2 Enterprise x64 SP2 on VMWare ESX 3.5. I have installed MBCA, PowerShell 1.0, and the MDM Best Practices Analyzer. It can find my SQL server and Certificate Authority, but then when I run the pre-deployment scanner it says Scan Failed - Unable to run scan for all servers. I have tried this from the MDM server and from a WinXP SP2 PC with the same result. I can ping all the servers from each other and the PC, and I am running this logged on with my domain admin account.
Can anyone offer suggestions on how to get this to work?
Thanks in advance...
All Replies
-
Monday, June 30, 2008 4:03 PMWe have received your question on MDM BPA tool. We'll follow up with an answer within the next few days.
-
Monday, June 30, 2008 5:40 PM Hi,
Can you please confirm if you have followed the below mentioned step for setting execution policy before running BPA.
* Before you run MDM Best Practices Analyzer Tool, you must enable remote-signed Windows PowerShell scripts to run on your computer. To set the PowerShell execution policy to allow remote-signed scripts, in the PowerShell command window, run the following command:Set-ExecutionPolicy RemoteSigned
Thanks
Arvind Maurya- Marked As Answer by CosmoCat Tuesday, July 01, 2008 4:17 PM
-
Tuesday, July 01, 2008 4:15 PMThat was it!
How did I miss that in the 200 or more pages of planning and deployment guides that I've been wading through?
Thanks for your help! -
Tuesday, July 01, 2008 6:14 PMThis instruction is in readme document of BPA.
Thanks
Arvind Maurya
.png)
