Troubleshooting SCVMM: Resolving Error 415 When Adding Hosts

Table of Contents

Adding hosts to System Center 2012 Virtual Machine Manager Service Pack 1 (SCVMM SP1) can sometimes be a challenging task. One common issue encountered during this process is Error 415. This error typically indicates a problem with the agent installation when attempting to add a host to SCVMM. This article provides a comprehensive guide to troubleshoot and resolve Error 415, ensuring a smooth host addition process to your SCVMM environment.

Symptoms¶

When attempting to add a host to SCVMM SP1, the process may fail, and Error 415 might be visible in the VMM job history. The detailed error message usually appears as follows:

Error ( 415 )
Agent installation failed copying C:\Program Files:\Microsoft System Center\Virtual Machine Manager\agents\I386\3.1.6011.0\msiInstaller.exe to \\servername\ADMIN$\msiInstaller.exe.

Recommended Action

1. Ensure <servername> is online and not blocked by a firewall.
2. Ensure that file and printer sharing is enabled on <servername> and it not blocked by a firewall.
3. Ensure that there is sufficient free space on the system volume.
4. Verify that the ADMIN$ share on <servername> exists. If the ADMIN$ share does not exist, reboot <servername> and then try the operation again.

In addition to the primary error message, an optional Details section might provide further insights into the root cause. These details can be crucial for pinpointing the exact problem. Examples of detail messages include:

Details: The process cannot access the file because it is being used by another process
Details: The target account name is incorrect

These detail messages can hint at issues like file locking, incorrect credentials, or other underlying problems that are preventing the agent installation from completing successfully. Analyzing both the main error and the detail messages is crucial for effective troubleshooting.

Cause¶

Error 415 in SCVMM host addition typically arises from networking or permission related issues that hinder the successful installation of the VMM agent on the target host. Specifically, this error can occur if the necessary network ports for VMM agent installation are not open on the target host’s firewall. These ports are essential for communication between the VMM server and the host during the agent deployment process.

Another potential cause is the absence or misconfiguration of the File Server role on the target host. The File Server role is fundamental for enabling file and printer sharing, which is a prerequisite for SCVMM to copy the agent installation files to the target machine. If this role is not enabled or is improperly configured, the VMM server will be unable to access the necessary administrative shares on the host, leading to the Error 415.

In essence, Error 415 signifies a blockage in the communication pathway required for agent installation, stemming from either firewall restrictions on critical ports or the lack of file sharing capabilities due to the File Server role not being enabled. Addressing these potential roadblocks is key to resolving the error and successfully adding hosts to your SCVMM environment.

Resolution¶

Resolving Error 415 involves a systematic approach to verify network connectivity, permissions, and necessary Windows features on the target host. The following steps provide a structured troubleshooting process to identify and rectify the underlying cause of the error.

Step 1: Verify that the Admin$ share is present and accessible by the VMM Run As account¶

The first step is to ensure that the Admin$ administrative share on the target host is accessible and that the VMM Run As account has the necessary permissions to access it. This share is essential for SCVMM to remotely manage the host and copy the agent installation files.

To verify this:

1. Log in to the VMM server using the credentials of the Run As account that is being used for the host addition job. This is crucial because you need to test the connectivity and permissions from the perspective of the account SCVMM is using.
2. Open File Explorer and in the address bar, type \\\\<servername>\\admin$, replacing <servername> with the actual hostname or IP address of the host you are trying to add. Press Enter.
3. If the Admin$ share is accessible, you should be prompted for credentials if you are not already logged in with an account that has administrative access. If you are using the correct Run As account, you should be able to access the share without being prompted.
4. Try to create a new text file within the Admin$ share. This will verify both connectivity and write permissions. If you can create a file, it confirms that the Run As account can access and write to the Admin$ share.

If you encounter any issues accessing the Admin$ share, such as an error message indicating that the network path is not found or that you do not have permissions, it indicates a problem with network connectivity or account permissions. Proceed to the next steps to investigate further. If this step fails, it is a strong indication of a fundamental connectivity or permission issue that needs to be resolved before proceeding with host addition.

Step 2: Verify that the Run As account is a local administrator on the target machine¶

The VMM Run As account must be a member of the local administrators group on the target host for successful agent installation and management. This is because administrative privileges are required to install services, modify system settings, and perform other management tasks on the host.

To verify the Run As account’s membership in the local administrators group:

1. Log in directly to the target host machine. This can be done via Remote Desktop or physically at the server console.
2. Open Computer Management. You can do this by right-clicking on the Start button (or pressing Windows Key + X) and selecting “Computer Management.”
3. In the Computer Management window, navigate to Local Users and Groups and then select Groups.
4. Double-click on the Administrators group.
5. In the Administrators Properties window, check if the VMM Run As account is listed as a member. If it is not listed, you need to add the Run As account to the local administrators group.
6. To add the account, click the Add… button. Enter the name of the Run As account and click Check Names to verify the account. Once verified, click OK to add the account to the Administrators group. Click OK again to close the Administrators Properties window.

After adding the Run As account to the local administrators group, you should retry adding the host in SCVMM. Ensure that you have correctly specified the Run As account credentials during the host addition process in SCVMM. Incorrect credentials or insufficient privileges are common causes of Error 415.

Step 3: Open the required ports¶

Firewall restrictions on the target host can block the necessary communication ports required for VMM agent installation. Specific inbound firewall rules must be enabled to allow SCVMM to communicate with the host and deploy the agent. The key rule groups that need to be enabled are related to Windows Management Instrumentation (WMI) and Windows Remote Management.

To open the required ports by enabling the necessary firewall rules:

1. On the target host, open Windows Defender Firewall with Advanced Security. You can search for “Windows Firewall” in the Start Menu and select “Windows Defender Firewall with Advanced Security”.
2. In the left pane, click on Inbound Rules.
3. Scroll down through the list of inbound rules to locate the groups: Windows Management Instrumentation (WMI) and Windows Remote Management. These groups contain multiple rules related to WMI and WinRM functionalities.
4. For each of these groups (WMI and Windows Remote Management), check if the rules within the group are enabled. Rules are typically enabled if they have a green checkmark icon next to them. If the icon is a grayed-out circle or another indicator of being disabled, you need to enable them.
5. To enable a rule group, right-click on the group name (e.g., “Windows Management Instrumentation (WMI)”) and select Enable Rule Group. Do this for both “Windows Management Instrumentation (WMI)” and “Windows Remote Management” groups.

Visual Representation:

Initially, you might find that only some rules, like “Windows Remote Management,” are enabled, while WMI rules are disabled.

After enabling all necessary groups, both “Windows Management Instrumentation (WMI)” and “Windows Remote Management” rule groups should be enabled.

Automating Firewall Rule Enabling:

You can also use command-line commands to enable these firewall rule groups. Open Command Prompt as an administrator and run the following commands:

netsh advfirewall firewall set rule group="Windows Management Instrumentation (WMI)" new enable="Yes"

netsh advfirewall firewall set rule group="Windows Remote Management" new enable="Yes"

These commands will enable all rules within the specified rule groups, ensuring that the necessary ports for WMI and WinRM are open through the Windows Firewall. After enabling these rule groups, retry adding the host in SCVMM. Properly configured firewall rules are critical for successful agent deployment and host management.

Port Summary Table:

Rule Group	Description	Ports (Default)	Protocol	Direction
Windows Management Instrumentation (WMI)	Enables remote management and monitoring using WMI.	135 (RPC Endpoint Mapper), Dynamic RPC Ports	TCP	Inbound
Windows Remote Management (WinRM)	Enables remote management using WS-Management protocol.	5985 (HTTP), 5986 (HTTPS)	TCP	Inbound

Ensuring these ports are open is crucial for SCVMM communication and agent installation.

Step 4: Enable the File Sharing role¶

The File Sharing role, specifically the “File and Printer Sharing” feature, must be enabled on the target host. This feature allows the host to share files and folders over the network, which is essential for SCVMM to copy the agent installation files to the target machine. If this role is not enabled, SCVMM will be unable to access the necessary administrative shares, leading to Error 415.

To enable the File Sharing role:

1. Open Server Manager on the target host. You can find Server Manager in the Start Menu or by searching for it.
2. In Server Manager, click on Add roles and features. This will open the Add Roles and Features Wizard.
3. In the Before you begin page, click Next.
4. Select Role-based or feature-based installation and click Next.
5. Select Select a server from the server pool and choose the local server from the server pool. Click Next.
6. In the Server Roles page, you do not need to select any server roles for enabling File Sharing. Click Next to proceed to the Features page.
7. In the Features page, scroll down and locate File and Printer Sharing. Check the box next to File and Printer Sharing to select it.
8. A pop-up window might appear indicating required features. Click Add Features to confirm adding any dependencies.
9. Click Next through the remaining pages of the wizard until you reach the Confirmation page.
10. On the Confirmation page, review your selections and click Install to begin the installation of the File and Printer Sharing feature.
11. Once the installation is complete, click Close to exit the Add Roles and Features Wizard.

After enabling the File and Printer Sharing feature, retry adding the host in SCVMM. Enabling this feature ensures that the target host can act as a file server, allowing SCVMM to copy the necessary agent installation files to the host, which is a critical step in resolving Error 415.

By systematically following these steps, you should be able to identify and resolve the root cause of Error 415 when adding hosts to SCVMM SP1. After implementing these resolutions, attempt to add the host again in SCVMM. In most cases, addressing these common issues will lead to successful host addition.

If you continue to experience issues, double-check the VMM job history for any additional error details that might provide further clues. Review the event logs on both the VMM server and the target host for any related errors or warnings that could indicate other underlying problems.

We encourage you to share your experiences and any additional troubleshooting steps you may have taken in the comments below. Your insights can be valuable to other users facing similar challenges.