RVTools 3.9.3 vSphere 6.5 Supported

Version Info

Version 3.9.3 (March, 2017)

  • Bug fix: unhandled exception in decrypt function solved

Version 3.9.2 (February, 2017)

  • Migrated RVTools to use .NET Framework version 4
  • Migrated RVTools to use NPOI 2.1.3.1
  • Support for vSphere 6.5
  • Improved logon performance
  • RVTools will no longer write messages to the Windows eventlog
  • All VM related tab pages now have a new column: OS according to the VMware Tools
  • All tab pages now have a new column: VI SDK Server
  • All tab pages column vCenter UUID renamed to VI SDK UUID
  • vInfo tab page: new column VI SDK API version
  • Export to Excel will now use xlsx format
  • Export to Excel all columns are now auto sized
  • Excel worksheet names will use same name as the tab page names
  • Annotations fields can now be excluded! See preference window
  • vPartition tab page new column: Consumed MB
  • vHealth _replica directories are excluded for zombie checks
  • *_sesparse.vmdk files are excluded for zombie checks
  • New tab page with license information
  • New PasswordEncryption application added with which you can encrypt your password
  • RVTools command line interface accepts now encrypted passwords
  • Bug fix: URL Link to online version info issue solved.

http://www.robware.net/rvtools/

PowerCLI: Migrate VM’s to another VLAN/Portgroup

Suppose you have several Virtual Machines running in a VLAN of which you decide they should be migrated to a new VLAN because of infrastructural changes in your network. This is only handy if the machines you are about to migrate use DHCP to get their network addresses.

The first is to configure all the network adapters of all VM’s from the old to the new VLAN/Portgroup and the second is to do exactly the same but to shortly disconnect/reconnect the network adapters of the Virtual Machines to initiate a DHCP request for your VM’s.

First method:

Get-Cluster "Your Cluster" | Get-VM | Get-NetworkAdapter | Where { $_.NetworkName -eq "Old VLAN" } | Set-NetworkAdapter -NetworkName "New VLAN" –Confirm:$false

Second method:

Get-Cluster "Your Cluster" | Get-VM | Get-NetworkAdapter | Where { $_.NetworkName -eq "Old VLAN" } | Set-NetworkAdapter -NetworkName "New VLAN" -Connected:$false | Set-NetworkAdapter -Connected:$True –Confirm:$falsen

When you use the second method the vm’s must be powered on!!!!!

Special thanks to: Laurensdekoning

No tags for this post.