Perimeter Host communication fails after successful connection with a System Center Virtual Machine Manager 2008 or System Center Virtual Machine Manager 2008 R2 server

Article translations Article translations
Close Close
Article ID: 971825 - View products that this article applies to.
Expand all | Collapse all
Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

Symptom



A Host on a Perimeter Network that was previously able to communicate with the System Center Virtual Machine Manager 2008 server no longer can. A manual refresh of the host will result in a job failure as shown here:

Error (2910)

VMM does not have appropriate permissions to access the resource C:\Windows\system32\qmgr.dll on the %computername% server.

(Access is denied (0x80070005))

Recommended Action

Ensure that Virtual Machine Manager has the appropriate rights to perform this action.

Cause

The password used by the VMMAgent Service Account has expired, or the Service Account itself has been disabled or deleted. This may more frequently in a workgroup environment where password expiration default is set to 48 days. Additionally, if the policy ‘User must change password at next logon’ is enforced there will be an initial successful connection between the Perimeter Host and the VMM Server, followed by subsequent communication failure.

Resolution

  1. On the Perimeter Host server, right-click My Computer and the click Manage.
  2. Open Local Users and Groups, and then open Users.
  3. In the right-hand pane, locate the service account for VMMAgent that begins with 'SCVMM*****’.
  4. Right-click the service account and then select Properties.
  5. Click to clear the User must change password at next logon check box.
  6. Click to select the Password never expires check box.
  7. Click OK to close the ‘SCVMM***** Properties’ window.
  8. Refresh the Perimeter Host in the SCVMM Admin console again.

DISCLAIMER

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, RELIABILITY OR ACCURACY OF THE INFORMATION CONTAINED IN THE DOCUMENTS AND RELATED GRAPHICS PUBLISHED ON THIS WEBSITE (THE “MATERIALS”) FOR ANY PURPOSE. THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE.

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.

Properties

Article ID: 971825 - Last Review: August 9, 2010 - Revision: 2.0
APPLIES TO
  • Microsoft System Center Virtual Machine Manager 2008
  • Microsoft System Center Virtual Machine Manager 2008 R2 Workgroup Edition
Keywords: 
kbrapidpub kbnomt KB971825

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com