Hello everyone,
I have installed Hyper-V connector on SNOW Inventroy Server version 5. In the Management and Configuration Center, the Hyper-V configuration is not displayed under All Devices. I would now check the logs. Unfortunately, I can't find the location of these logs.
Does anyone know the file location?
Hi Julian,
you can simply check this Location when you open the SIM Properties
Hi Detlev,
thanks for your reply.
I found the log, thank you for your answer.
Now I have the following problem that I can see the Office 365 Connector and SCCM connect.
But I don't see any Hyper-V connect, although this Connect seems to be running.
I see in the License Manager that the client configuration has the name of the Hyper-V connector, but I don't see the connection in the log.
Are there any other logs where Hyper-V connector is listed?
Best regards
Julian
please Check this one in Inventory SMACC
Can you see your Hyper v Server here
Hi Julian,
just be sure: in the documentation "User Guide: Microsoft Hyper-V Connector" you can find in the Support Portal knowledge base there are prerequisites for this connector on the Server side of Hyper-V:
When running Snow Integration Manager on Windows 7 or Windows Server 2008, Windows
Management Framework 3.0 must be installed.
▪ Logon credentials for standalone Hyper-V servers:
◦ Use either a domain user account or a local user account.
◦ The user account must be member of the Hyper-V Administrators group of the
Hyper-V server.
◦ The credentials must have access to the server’s WMI interface.
▪ Logon credentials for VMM servers:
◦ Use a domain user account.
◦ The user must be member of the local Administrators group of the VMM server.
◦ The user must be assigned a role that has the Read-Only Administrator profile with
the All Hosts scope assigned to it.
To create the role and set the scope, open the Virtual Machine Manager Console on
the VMM server, and then go to Settings|Security|User roles.
▪ For VMM servers: Make sure that PowerShell Remoting is enabled on the server.
Example of PowerShell script:
Enable-PSRemoting -Force
If the connection fails to a server that is not a member of the domain, or if connection by IP
address is used, the server’s IP address (or name) might need to be added to “TrustedHosts” on
the local computer. Example of PowerShell script:
set-Item wsman:\localhost\Client\TrustedHosts -Value “xxx.xxx.xxx.xxx,
xxx.xxx.xxx.xxx, …”
Did you already cross check all the prereqs?
Hope this leads somewhere for you.
Best regards,
Michael
Hi Marcel & Michael,
A host is displayed via the connector. The host on which the VMM is installed.
In total, more than 470 VMs should be inventoried.
The agent used for inventory is installed on all hosts.
I would like to know which VMs are synchronized via the connector. Is there a log or transfer file in which you can see which VMs can be reached via the connector?
The SMACC displays the connection via agent, does this mean that the quantities are consolidated or that only one data source is used?
Hi Julian,
I think there is a misunderstanding. The Hyper-V connector will not inventorize any virtual machine. It will show the host-guest relation of the VMs to their hosts in Snow License Manager. This means that this connector will serve the Discovery part of the DINROS approach: Know what you have.
For inventory of the VMs, i. e. to know what is installed on the VMs, you will need to install Snow Inventory Agent on each VM according to the running operating system on the VM.
Hope this helps.
Best regards,
Michael
Okay, great. Then the connection works. But then I don't understand why the Hyper-Vs and the agents are displayed individually.
Are they not consolidated?
Thank you for your help
Best regards
Julian
[Edit]: Hostname-Only Mode is configured for all Devices
Hi Julian,
the Snow Integration Connector for Hyper-V is used for gathering of datacenter
information into Snow License Manager, not for inventory the guest VMs.
Maybe this is the misunderstanding.
regards Siggi
Hi Siggi,
thanks for your Answer.
So the gathered information from the Agent and the Connector won`t be merged ?
Hi Julian,
no, the data won't be merged. Agent data and Connector "Datacenter" data have two different topics.
regards Siggi
Hi Siggi,
Thanks, that explains the behavior.
Best regards & beautiful Easter
Julian
Hi Julian,
some additional information.
Data coming in via SIM Hyper-V connector will be showed in SLM – Computer – DataCenter and Cluster, see attached screenshot.
In my case the virtual machine “Computer 11007” is also inventoried with Snow Agent, see attached screenshot.
Back to your question “So the gathered information from the Agent and the Connector won`t be merged ?”
The data will not really merged but the computers will be linked together. Snow SLM linked the inventoried data to collected DataCenter data. If you want you can tell it "merged".
Hopefully it helps a bit.
Regards Siggi
on Mar 1, 2018
Hi Julian,
just be sure: in the documentation "User Guide: Microsoft Hyper-V Connector" you can find in the Support Portal knowledge base there are prerequisites for this connector on the Server side of Hyper-V:
When running Snow Integration Manager on Windows 7 or Windows Server 2008, Windows
Management Framework 3.0 must be installed.
▪ Logon credentials for standalone Hyper-V servers:
◦ Use either a domain user account or a local user account.
◦ The user account must be member of the Hyper-V Administrators group of the
Hyper-V server.
◦ The credentials must have access to the server’s WMI interface.
▪ Logon credentials for VMM servers:
◦ Use a domain user account.
◦ The user must be member of the local Administrators group of the VMM server.
◦ The user must be assigned a role that has the Read-Only Administrator profile with
the All Hosts scope assigned to it.
To create the role and set the scope, open the Virtual Machine Manager Console on
the VMM server, and then go to Settings|Security|User roles.
▪ For VMM servers: Make sure that PowerShell Remoting is enabled on the server.
Example of PowerShell script:
Enable-PSRemoting -Force
If the connection fails to a server that is not a member of the domain, or if connection by IP
address is used, the server’s IP address (or name) might need to be added to “TrustedHosts” on
the local computer. Example of PowerShell script:
set-Item wsman:\localhost\Client\TrustedHosts -Value “xxx.xxx.xxx.xxx,
xxx.xxx.xxx.xxx, …”
Did you already cross check all the prereqs?
Hope this leads somewhere for you.
Best regards,
Michael