Loading
In the Virtual Machine Host History report, all of our VMs are showing that they have moved every day.

When reviewing the Virtual Machine Host History report, I'm noting that each VM (starting last month) has days between change of 1. There is a line for every day since the 12th of last month for all of our VMs in the Datacenter. The move however is showing the exact same Datacenter and Host Computer Name as the prior day. 

Not sure where to begin. I did try to edit the schedule on the external connector to once every 7 days (instead of once a day) as a test. However, all of the servers are still showing that they moved each and every day. 


  • To give on an update on the ticket status. Regarding the export to Excel, ...   Snow created a problem report (PRB0042407), all future communications/updates will be provided through the KB article KB0020775. You may subscribe the KB to get the automatic updates. Regarding the original issue that report shows a daily change, I finally yesterday had a meeting with support.    But root cause for this issue is still not clear.
    • Hi Carola, Did you see any progress on this issue of VMs reporting a daily change of host?
      • 1. The Export should be ok now. 2. For the issue of daily changes I asked last Friday for a status. It is classified as defect, but I don't know when it will be fixed. Did you also create a support ticket?
        • Thanks Carola, I didn't create a ticket yet because I am currently following up with Snow Support on a few other tickets and I prefer to limit how many tickets I handle in parallel I will create one when some of my current tickets get solved.
          • Hi Samuel, Unfortunately same for me. Too many tickets and so I also did not log a ticket for every issue. I just asked for the PRB number, then you can refer to this and the more customers will join, the better.
            • I might have missed something essential ... there is a way to follow a PRB? Is that on the Snow Support website?
              • No we can not see PRB's, only KB's (when they are not internal). But when you would add that to a potential ticket I think you would not need a zoom meeting to explain the issue. As far as I understand, Snow plan to create KB's for known issues, that customers can subscribe to. Then you would not need to open a ticket by your own.
                Expand Post
                  • One more question: In this Snow Article about Windows Server compliance , it says: The compliance engine will now perform the following calculation for each standalone server, or server hosting Windows Server Virtual Machines. 1) Assess the number of Windows Server Virtual Machines that could run on the server (we call this peak potential VMs in the reports discussed below) - this means also taking into account which Virtual Machines can move in a clustered environment and using the peak for each host in the cluster. 2) ... Since the tracking of the VM/Host relationship is broken, does it mean that the "peak potential VMs" (and thus the report and compliance figures) is wrong for all clusters? I assume so because In my Windows Server Assessment report all my quantities of Running Windows Sever VMs is always equal the the Peak Running Windows Sever VMs . Can someone confirm?
                    Expand Post
  • Hi Andrew, After I saw your post I also validated that in my environment. Unfortunately we have the same issue. That's a bug and we should create a support ticket for that. About 2 years ago the report had the same problem and then it was fixed For me it seems like it began for us with the migration to SLM 9. But I didn't check that report since migration.
10 of 16

Loading
In the Virtual Machine Host History report, all of our VMs are showing that they have moved every day.