Manual Mapping of VMs with Host Computers in DCC

Portal User asked a question.

March 27, 2019 at 7:00 AM

Hello,

We have auto generated DCC where some VMs are not connecting with Host Computer.

In SLM while we editing computers there manual mapping with Host Computer is available and doing same VMs map with Host but after DUJ running same is resetting in previous state i.e. VMs without host.

Also available VMs count increased for respecting DC (inventoried and non-inventoried) no. of VMs we mapped manually with Hos Computer.

Can any one suggest, How we can get rid this situation without loss of change made for VMs those are outside Host?

Thanks,

Kishan Pant

Viktors
7 years ago
Hi Kishan! When you manually assign VM to an appropriate host, make sure, that "Disable auto editing" option is checked. This setting allows you to save manual changes for computers/users and DUJ will not affect. BR, Viktors
Expand Post
- Portal User
  7 years ago
  Thanks a lot Viktors Vasilonoks , I have one more query here after doing manual assignment of Host computer to VM, there one additional count added for ex. 10 VMs become 11 and inventoried become 7 from 6 and also Power state is showing blank for inventoried one(after manual assignment). Can we handle this situation? Thanks, Kishan Pant
  Expand Post
- Portal User
  7 years ago
  Hi Viktors Vasilonoks , After doing steps you suggested and running DUJ. Assigned host no more available in VM where we assigned same. Is there other things need to take care for same? Thanks, Kishan Pant
  Expand Post
carolai
7 years ago
Hi ‌ I don't know if I can help you. What I can say is: We also have virtual VMWare machines and I also noticed that some inventoried virtual machines could not be automatically assigned to their host. Meanwhile we have nearly all the host assignments, but we had to do following We noticed that for several virtual machines that were moved to another host the information in Inventory were refreshed but also the old information was kept. So we now have a custom procedure in DUJ, that checks that and remove the old entries in Inventory. But I think this is special and cannot be posted here. Also VSphere scanner sometimes collected IP-Adresses for the virtual machines, that were not really valid. Because the virtual machimes were matched to their hosts by the IP Adress, that did not work After I installed SIM 5.13 this worked better. SIM 5.14 already should be released now. I would recommend that you upgrade to the latest SIM, then presumably the IP Adress matching should be better. I also noticed that our poweredoff virtual machines also lost their host information, although they had it before. As far as I know, this will presumably improved in SLM 9.2 I don't know if the appended SQL may help you. But I use this to compare information we get from VSphere (Hosts and their hosted VM's) against information we got from Snow Agent (InventoriedComputers) This SQL compares computers only based on the hostname (not by ip-Adress like Snow needs to do it) I use this to see the virtual machines in VSphere and can see if that computers are inventoried (when InventoriedComputername is not ), and if they are matched to a computer in SLM (when InventoriedComputerID is not ) SELECT distinct vm.[MachineID] ,vm.[PowerState] ,vm.[UpdatedDate] as VSphereLastScandate ,vm.[HostComputerID] , c2.hostname as Host ,vm.[Name] as VSphereVMName ,vm.[ComputerID] as InventoriedComputerID ,c.HostName as InventoriedComputername, c.LastScanDate ,vm.[IPAddress] as VSphereIPAdress, c.IPAddress as InventoriedIPAdress ,vm.[OperatingSystem], c.OperatingSystem as computerOS ,vm.[OverallStatus] ,ci.DisableAutoEditing FROM [SnowLicenseManager].[dbo].[tblInventoryVirtualMachines] vm left outer join tblcomputer c on vm.name=c.HostName join tblcomputer c2 on vm.HostComputerID=c2.ComputerID join tblcomputerinfo ci on ci.ComputerID= c2.ComputerID join tblOrganization o on o.OrgChecksum=ci.OrgChecksum --where c.HostName is not and vm.[ComputerID] is When you remove the comment (--) before the where condition then you can see computers, that presumably should be inventoried but don't have the host information. This is only to check the status and find possible problems, but it will not change anything.
Expand Post
- Portal User
  7 years ago
  Hello Carola, Thanks for this. However I am facing the issue with 5.13 also where still lots of VMs not connecting with Host but I will try with latest release also i.e. 5.14. There is situation where VMs name in vCenter is different with hostname of VMs but even most of the VMs connecting with Host but some of the VMs not able to connect. For above situation ticket logged with Snow and waiting for response. I raised the concern in Snow Community for we have the functionality in SLM where we can manually assigning Host computer for VMs which unable to connect automatically but same is also not working after DUJ mapping loss. Thanks, Kishan Pant
  Expand Post