Hi,
I'm having a lot of problems with joining several hosts to VMM.
When I try to add a server to VMM I always get this errormessage:

Error (415)
Agent installation failed copying C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\I386\2.0.4273.0\msiInstaller.exe to \\[FQDN of the server]\ADMIN$\msiInstaller.exe. 
 (The network path was not found) 

Recommended Action
1. Ensure [FQDN of the server] is online and not blocked by a firewall. 
2. Ensure that file and printer sharing is enabled on [FQDN of the server] 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 [FQDN of the server] exists. If the ADMIN$ share does not exist, reboot [FQDN of the server] and then try the operation again.

and this warning:

Warning (10444)
The VMM server was unable to impersonate the supplied credentials.  

Recommended Action
To add a host in a disjointed domain namespace, ensure that the credentials are valid and of a domain account. In addition, the VMMService must run as the local system account or a domain account with sufficient privileges to be able to impersonate other users.

I tried to open the admin$ share from the vmm with the same credentials that I provided to add the hosts and that seems to work perfectly. Both machines are in the same domain.
Has anyone seen this before? Any idea what is the best way to troubleshoot it?
Thanks in advance for any help.

Thanks for posting your question here.  First, make sure that the credentials entered during the Add Host wizard are in the local administrators group on the sever intended to become a managed host.  That is the most common cause of the above error. 

Next, make sure that you can access the Admin$ from the VMM server on the host-to-be.  Try this via UNC path.  Example:  \\server1\admin$

http://technet.microsoft.com/en-us/library/cc917954.aspx
http://technet.microsoft.com/en-us/library/cc917923.aspx

Is your host-to-be on a perimeter network?  If so, you'll need to follow these steps:  http://technet.microsoft.com/en-us/library/cc917968.aspx

I hope this helps.


Thanks,

Mike Briggs [MSFT]

Hi Mike,
Thanks for your answer. I forgot to mention it but I did try opening the admin$ share with the same Domain admin useraccount that I use when I start the "Add Host" wizard and that works flawless. The host is not in a perimeter. It's in the same domain.
I tried several things. Including turning off the firewall completely. Apart from this one I'm having similar problems with other hosts. I think the warnings and errormessages are not really reliable.
I have the idea that something is wrong with WinRM. Because I did notice when the server (that I was talking about here) reported a warning when starting up saying:
EventID 10154 (Warning)
=========== The WinRM service failed to create the following SPNs: WSMAN/SERVER01.test.com; WSMAN/SERVER01. 
 Additional Data   The error received was 8235: %%8235.
 User Action   The SPNs can be created by an administrator using setspn.exe utility. ===========
Afterwards it reports:
EventID 10148 (Information)
=========== The WinRM service is listening for WS-Management requests. 
 User Action   Use the following command to see the specific IPs on which WinRM is listening: 
 winrm enumerate winrm/config/listener ===========
When I do run the "winrm enumerate winrm/config/listener" in a elevated cmd window I don't get any output. Don't know how to interpret that. Should there be something. If so, I don't really know how to fix that

And finally when I run setspn -L SERVER01 I get this:
===================== Registered ServicePrincipalNames for CN=SERVER01,OU=Updates on Sunday ev,OU=Memberservers,DC=agr,DC=ad10,DC=intern,DC=kuleuven,DC=ac,DC=be:         Microsoft Virtual Console Service/SERVER01.test.com         Microsoft Virtual Console Service/SERVER01         Microsoft Virtual System Migration Service/SERVER01.test.com         Microsoft Virtual System Migration Service/SERVER01         WSMAN/SERVER01.test.com         WSMAN/SERVER01         RestrictedKrbHost/SERVER01.test.com         RestrictedKrbHost/SERVER01         MSSQLSvc/SERVER01.test.com:3491         TERMSRV/SERVER01         TERMSRV/SERVER01.test.com         vssrvc/SERVER01.test.com         vssrvc/SERVER01         vmrc/SERVER01:5900         vmrc/SERVER01.test.com:5900         HOST/SERVER01         HOST/SERVER01.test.com =================
So I assume WSMAN/SERVER01 exists. Should there be something else?
I also tried to disjoin and rejoin the machine to the domain with no result.
Thanks for your help.

Just a quick addition:
I found this article saying that when you get no output from "winrm enumerate winrm/config/listener" it means winTM is not running. Even though I checked that the service is running.
I tried running winrm quickconfig saying:
============= WinRM already is set up to receive requests on this machine. WinRM is not set up to allow remote access to this machine for management. The following changes must be made:
Create a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine. Enable the WinRM firewall exception.
Make these changes [y/n]? y
WinRM has been updated for remote management.
Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this  machine. WinRM firewall exception enabled. =============
Afterwards running winrm enumerate winrm/config/listener says
================ Listener     Address = *     Transport = HTTP     Port = 5985     Hostname     Enabled = true     URLPrefix = wsman     CertificateThumbprint     ListeningOn = 10.0.0.134, 10.33.84.195, 127.0.0.1, ::1, fe80::5efe:10.33.84. 195%12, fe80::d0e2:bc7:1dd0:7eed%13 ================
Even after doing this I get the same error message when adding the host in VMM.
Has anyone had this happening before?
Is there a way to get more verbose logging in VMM of what is actually going wrong?
greetz,

Just from looking at the above it appears that WinRM was not configured.  Running "winrm quickconfig" or "winrm qc" will auto configure WinRM on that particular server.  VMM depends heavily on WinRM for communication to various VMM role holders.  If for some reason WinRM is not functioning correctly VMM will definitely have problems.  This could be the reason for the errors that you're seeing.

One additional thing that I would try, is to remote-ping using WinRM from the VMM server to the host-to-be using the following command:

     winrm id -r:server_1 (where server_1 is the name of your host-to-be)

This will basically pull the version information of WinRM from the remote server.  The idea here is that we are verifying that WinRM is working correctly between these two servers.  Please reply back with the results.

And finally, if you capture a vmm_trace I'd be glad to look at the results.  Download and run the VMM_MPSReports from the link below.  The instructions are included, but basically you install it on each server where you want to capture data, enable tracing, reproduce the problem, and then capture the logs.  Then you can email that to me for analysis.  Here is my email:  mbriggs@microsoft.com

http://www.microsoft.com/downloads/details.aspx?FamilyID=4e3dc013-c299-4b80-9735-64a8b9fa60c7&displaylang=en


Thanks,

Mike [MSFT]

Hi Mike,
Thanks for your reply. A few strange things going on. When I try the command you suggested on the VMM server I get:
=========== C:\Windows\system32>winrm id -r:agr-srv-t417 WSManFault     Message = The WinRM client cannot complete the operation within the time spe cified. Check if the machine name is valid and is reachable over the network and  firewall exception for Windows Remote Management service is enabled.
Error number:  -2144108250 0x80338126 The WinRM client cannot complete the operation within the time specified. Check if the machine name is valid and is reachable over the network and firewall exce ption for Windows Remote Management service is enabled. ============
I could believe that indeed that server was not communicating properly. The strange thing is that I get the exact same error message when I try the command to all the other servers that are succesfully added to VMM. So that seems kind of contra-intuitive to me. VMM is properly communicating with the other machines.
I'll run the diag tool and send it over.
Gert

Did this issue get resolved?  If so, please share with community how you resolved.  Otherwise, re-activate post if you still require assistance.

Hi Carmen,

Unfortunately the issue is not resolved yet. Currently I'm working together with PSS to try to resolve it. There seems to be a few things wring with WinRM. When I find the solution I will post it.

Gert

Just to add my 2 penneth on this one. Stumbled across this thread as I had the same issue, but it has turned out to be a DNS issue. Hyper V host registered a NIC in DNS before I made it a VM only NIC. Ensure the correct NIC is registered in DNS

Maybe something worth checking?

I am using VMM 2008 R2 and am having a similar issue, except that the error is 414, "Agent installation could not access the ADMIN$ share on server." I can manually access \\host\admin$ as the VMM service account or with my account that I am using to run the job.

I ran a trace and see the following in the logs on the VMM Server. It appears to be able to copy the x86 bits to admin$ but it can't copy the x64 bits.

Here are my logs, (I replaced my servername that i am pushing the agent out to with the name "Host")

00000073 45.72019577 [4912] 1330.08A8::09/14-18:10:35.359#09:AgentInstall.cs(306): RemoteExecute called 
00000074 45.72024536 [4912] 1330.08A8::09/14-18:10:35.359#09:LocalFileUtils.cs(82): Copying <C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\I386\2.0.4275.0\msiInstaller.exe> to <\\Host\ADMIN$\msiInstaller.exe> 
00000075 45.81734848 [4912] 1330.08A8::09/14-18:10:35.453#09:AgentInstall.cs(312): File copy complete 
00000076 45.81740570 [4912] 1330.08A8::09/14-18:10:35.453#09:ServiceManager.cs(66): Connecting to WMI for server IADPHV3N08.corp.avanade.org. Service name is VMMInstallDetector 
00000077 45.90902328 [4912] 1330.08A8::09/14-18:10:35.547#09:ServiceManager.cs(94): connection to WMI for server IADPHV3N08.corp.avanade.org. Service name is VMMInstallDetector was successfull 
00000078 45.90908051 [4912] 1330.08A8::09/14-18:10:35.547#09:ServiceManager.cs(201): Removing [VMMInstallDetector] 
00000079 45.95578003 [4912] 1330.08A8::09/14-18:10:35.594#09:ServiceManager.cs(304): RemoveService encountered ManagementException: ignore 
00000080 45.95625305 [4912] 1330.08A8::09/14-18:10:35.594#09:ServiceManager.cs(304): System.Management.ManagementException: Not found   
00000081 45.95625305 [4912]    at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)  
00000082 45.95625305 [4912]    at System.Management.ManagementObject.InvokeMethod(String methodName, ManagementBaseObject inParameters, InvokeMethodOptions options)  
00000083 45.95625305 [4912]    at Microsoft.VirtualManager.Engine.Adhc.WmiBasedServiceManager.RemoveService() 
00000084 45.95636749 [4912] 1330.08A8::09/14-18:10:35.594#09:ServiceManager.cs(119): Created service [VMMInstallDetector] bin=<%SystemRoot%\\msiInstaller.exe> 
00000085 45.97612762 [4912] 1330.08A8::09/14-18:10:35.609#09:ServiceManager.cs(162): [VMMInstallDetector] creation exited with code 0 
00000086 45.97617722 [4912] 1330.08A8::09/14-18:10:35.609#09:ServiceManager.cs(322): Starting [VMMInstallDetector] 
00000087 46.08958817 [4912] 1330.08A8::09/14-18:10:35.734#09:ServiceManager.cs(333): [VMMInstallDetector] start exited with code 0 
00000088 48.08767700 [4912] 1330.08A8::09/14-18:10:37.735#09:ServiceManager.cs(345): Waiting for [VMMInstallDetector] to stop 
00000089 48.10171509 [4912] 1330.08A8::09/14-18:10:37.735#09:ServiceManager.cs(392): Service exit code is 1066 
00000090 48.10184097 [4912] 1330.08A8::09/14-18:10:37.735#09:ServiceManager.cs(201): Removing [VMMInstallDetector] 
00000091 48.11468124 [4912] 1330.08A8::09/14-18:10:37.750#09:ServiceManager.cs(220): Waiting for [VMMInstallDetector] to stop 
00000092 48.14260101 [4912] 1330.08A8::09/14-18:10:37.782#09:ServiceManager.cs(271): Trying to delete the service now 
00000093 48.14905930 [4912] 1330.08A8::09/14-18:10:37.782#09:ServiceManager.cs(275): [VMMInstallDetector] deletion exited with code 0 
00000094 48.14915085 [4912] 1330.08A8::09/14-18:10:37.782#09:LocalFileUtils.cs(180): Deleting <\\Host\admin$\msiInstaller.exe> 
00000095 48.15351105 [4912] 1330.08A8::09/14-18:10:37.797#09:HostLibInstall.cs(134): Ready to Update agent 2.0.4275.0 (Amd64) 
00000096 48.15359116 [4912] 1330.08A8::09/14-18:10:37.797#09:AgentInstall.cs(306): RemoteExecute called 
00000097 48.15365601 [4912] 1330.08A8::09/14-18:10:37.797#09:LocalFileUtils.cs(82): Copying <C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\Amd64\2.0.4275.0\vmmAgent.msi> to <\\Host\ADMIN$\vmmAgent.msi> 
00000098 48.37271881 [4912] 1330.08A8::09/14-18:10:38.016#09:LocalFileUtils.cs(82): Copying <C:\Program Files\Microsoft System Center Virtual Machine Manager 2008 R2\agents\Amd64\2.0.4275.0\msiInstaller.exe> to <\\Host\ADMIN$\msiInstaller.exe> 
00000099 48.37866592 [4912] 1330.08A8::09/14-18:10:38.016#09:LocalFileUtils.cs(101): Copy failed! will retry... 
00000100 50.37714767 [4912] 1330.08A8::09/14-18:10:40.017#09:LocalFileUtils.cs(101): Copy failed! will retry... 
00000101 52.38796616 [4912] 1330.08A8::09/14-18:10:42.017#09:LocalFileUtils.cs(101): Copy failed! will retry...

 

Any help would be much appreciated.

Regards,

Andy

 

The reason why i had this problem is to do with a multiple entrys on my nics , does it take a long time to contact the host after you restart the job? if so

1. I made sure the adapter binding order is set so the ip addr related to the hyperv host ,which is the same ip_addr registered in dns & moved it to the top of the list in network advance settings .
2. I have scvmm on a server running hyper v with 2 nics both with dns entrys, I removed the dns entry on the mgnt nic & the did the same for the host mgnt nic, that i wanted to add and bingo !! in went in no problem.

It might have been the issue. i'm not quite sure. We had some DNS issues on this host. But so far this problem is solved. I was never able to exactely fing out what the prob was...

Thanks for you comment.

Can you try to add the host after starting "Application Experience" (AeLookupSvc) service?

Thanks for the suggestion!!!  An old DNS entry was causing my issue. I removed the DNS entries and everything worked perfectly. It happened because the IP address was being assigned by DHCP instead of being a static address. I then assigned a static address and then tried adding the host to SCVMM. It was referencing the old DHCP assigned address but the static address was different. This is because I was setting up the server in my main office but it will eventually go to a different office with a different subnet.

Hi,

    I am also facing the same problem. here i have attached the screenshot of WINRM command.

   

Please help me.

Thanks,

Vishwajeet.

This seems very easy. Find the following steps
1) Launch a NSLookup from your DNS and mention the host you are looking for
2) If the results match with the actual IP address of the host , then there is no issue with DNS
3) If it doesnt match make sure to delete the wrong DNS entry and register the DNS of the Host again

This should resolve the issue