Dear JDisc friends,

nowadays, virtual machines can be migrated with nearly no downtime from one physical server to another. But do you really know what that implies to your license compliance?

Most users are not aware of license implications caused by moving VMs around. For instance, Microsoft only allows the migration of servers with volume licensing only once every 90 days (unless it is for HA reasons when a server has an outage). That’s why it is essential to know how often you migrate VMs from one physical server to another.

We have added a feature to track virtual machine migrations for VMware and for Hyper-V environments. Starting with build 3355, we collect virtual machine migration events and store them within our database. Each virtual machine as a new tab within its device details which lists all motion events for this virtual machine.

With this information, it is easy to track how often, when and why a virtual machine has been moved. Additionally, we have moved all settings regarding virtualization to a separate virtualization tab. That should make the configuration easier to understand.

Hope you like this new feature. This feature is included in build 3355.

Thomas

Thomas Trenz

I own and manage JDisc and its network inventory and discovery products. Before I started JDisc, I worked quite a long time for Hewlett-Packard developing software for network assessments and inventory projects. Feel free to contact me on Linked-In or Xing.

See Full Bio

Dear JDisc friends,

nowadays, virtual machines can be migrated with nearly no downtime from one physical server to another. But do you really know what that implies to your license compliance?

Most users are not aware of license implications caused by moving VMs around. For instance, Microsoft only allows the migration of servers with volume licensing only once every 90 days (unless it is for HA reasons when a server has an outage). That’s why it is essential to know how often you migrate VMs from one physical server to another.

We have added a feature to track virtual machine migrations for VMware and for Hyper-V environments. Starting with build 3355, we collect virtual machine migration events and store them within our database. Each virtual machine as a new tab within its device details which lists all motion events for this virtual machine.

With this information, it is easy to track how often, when and why a virtual machine has been moved. Additionally, we have moved all settings regarding virtualization to a separate virtualization tab. That should make the configuration easier to understand.

Hope you like this new feature. This feature is included in build 3355.

Thomas

Thomas Trenz

I own and manage JDisc and its network inventory and discovery products. Before I started JDisc, I worked quite a long time for Hewlett-Packard developing software for network assessments and inventory projects. Feel free to contact me on Linked-In or Xing.

See Full Bio