https://community.hpe.com/t5/server-management-systems/vpm-cannot-get-scan-to-work-for-second-server/m-p/3471090#M9298 Hi All,<BR />A step on from not working at all.<BR />After a reboot I can now scan the HPSIM/VPM Server.<BR />But, I cannot scan the second licensed server, I get "No file or registry access".<BR />I have tried a number of variants on the WBEM settings. <BR />The documentation suggests that WBEM Global properties needs to be set for just the account name if HPSIM &amp; VPM share the same Server which is true here. The Account I've used is a Domain Account. But I've also tried with the Domain\Account format as well.<BR />I can successfully scan the HPSIM/VPM Server but continue to get a problem with the second Server. Both are accessible by the Domain Account.<BR />Any authoritativve guide as to what the settings should be?<BR />It seems the System Settings don't have much impact.<BR />In the Global Settings I've even tried using the local Administrator Account that I've checked as having the same password on both Servers. Still VPM cannot access the Server.<BR /><BR />At the moment this has precluded me from testing / evaluating this product. Tue, 25 Jan 2005 20:31:36 GMT Rob Buxton 2005-01-25T20:31:36Z https://community.hpe.com/t5/server-management-systems/vpm-cannot-get-scan-to-work-for-second-server/m-p/3471090#M9298 Hi All,<BR />A step on from not working at all.<BR />After a reboot I can now scan the HPSIM/VPM Server.<BR />But, I cannot scan the second licensed server, I get "No file or registry access".<BR />I have tried a number of variants on the WBEM settings. <BR />The documentation suggests that WBEM Global properties needs to be set for just the account name if HPSIM &amp; VPM share the same Server which is true here. The Account I've used is a Domain Account. But I've also tried with the Domain\Account format as well.<BR />I can successfully scan the HPSIM/VPM Server but continue to get a problem with the second Server. Both are accessible by the Domain Account.<BR />Any authoritativve guide as to what the settings should be?<BR />It seems the System Settings don't have much impact.<BR />In the Global Settings I've even tried using the local Administrator Account that I've checked as having the same password on both Servers. Still VPM cannot access the Server.<BR /><BR />At the moment this has precluded me from testing / evaluating this product. Tue, 25 Jan 2005 20:31:36 GMT https://community.hpe.com/t5/server-management-systems/vpm-cannot-get-scan-to-work-for-second-server/m-p/3471090#M9298 Rob Buxton 2005-01-25T20:31:36Z https://community.hpe.com/t5/server-management-systems/vpm-cannot-get-scan-to-work-for-second-server/m-p/3471091#M9299 I've now tried redeploying the Agent to this Server. It fails trying to logon to a local account that doesn't exist. I want to use the domain account.<BR />I've tried changing WBEM Global to a Domain\Account setup, I've tried using System specific WBEM Paramaters for this Server. But the deployment continues to try to deploy to a Server\Username account. I've rerun the device Identification task in between each change.<BR />Where does it get the logon information, the docs suggest line 1 of the WBEM Settings for Windows Servers. Well it doesn't appear to be.<BR /><BR />I have set the changed password for the account in the VPM Credentials GUI. That also has the domain listed. Wed, 26 Jan 2005 17:50:20 GMT https://community.hpe.com/t5/server-management-systems/vpm-cannot-get-scan-to-work-for-second-server/m-p/3471091#M9299 Rob Buxton 2005-01-26T17:50:20Z