Stop the virtual machine of comments using command line on esx 3.5

Similar Questions

• I get an error "the disk hard virtual parent is in a saved state. Discard the saved state or stop the virtual machine and try again. "during the installation of XP mode.

  I have Win7 Pro SP1 x 64.  I downloaded WindowsXPMode_en - us.exe (from Microsoft downloads) and run it.  The installation seems to work OK (I've specified a different location for the parent virtual hard disk file).  Then, installation happening and I provide the information requested (name of user and password for the XP Mode), updates Windows and OK to the issue of sharing.  The installation program then reports the following error:

  The disk hard virtual parent is in a saved state.  Discard the saved state or stop the virtual machine and try again.

  I get the error even if I try manually configure XP Mode (use the Setup Wizard).  I downloaded the installer XPMode (3 times) and reinstalled several times, always with the same result.  If it helps, I can't locate anywhere .vsv file.

  Any idea what's going on?

  Original title: XP Mode Setup error

  Hi smithnr10,

   

   

  You must post your question in the TechNet forums because it caters to an audience of it professionals.

  To do this, you must consult the link-

  http://social.technet.Microsoft.com/forums/en-us/w7itprovirt/threads

   

  Hope this helps!

• Stop the virtual machine

  I'm looking for a script to stop vm...

  Script works fine, but I have a few Questions or details

  $csv = import-csv C:\xxx.csv

  Foreach ($line in $csv)

  {

  Write-Host “====================================================================”

  Write-Host "$line treatment".

  $vminfo = get-view-Id ($line.vm) USER.USER

  Write-Host "checking the VMware Tools on $line... »

  # If we have the VMware tools installed

  If ($vminfo.config.Tools.ToolsVersion - eq 0)

  {

  Write-Host "($line.vm) don't have vmware tools installed, strong power this one.

  # Hard power off.

  Stop-VM ($line.vm)-confirm: $false

  }

  on the other

  {

  write-host "I'll try to stop $vm.

  # Turn off with elegance

  Get - VM ($line.vm) | Stop-VMGuest-confirm: $false | Out-Null

  }

  }

  1. my code below what I'm missing / or hurt?

  $vminfo = get-view-Id ($line.vm) USER.USER

  Write-Host "checking the VMware Tools on $line... »

  2. Tools a lot of combination

  Tools installed - but not running

  tools not install

  Are that both will have to stop-vm?

  3.

  I got a simple code, it will cover the tools stuff?

  $vm = Get-VM
  $vm | where {$_. Comments . State -eq "Running"} | Shutdown-VMGuest -confirm:$false
  $vm | where {$_. Comments . State -eq "NotRunning"} | Stop-VM -Confirm:$false

  
  

  4. I want to stop 50 virtual machines simultaneously, how the

  
  

  Your script seems to be ok.

  When the VMware tools are installed you can do a gracefull shutdown (Stop-VMGuest) within the guest where OS the obligation for the VMware tools.

  The next option is to stop the virtual machine (VM-Stop), with what would be the power button on a physical computer.

  No phasing out of the BONES and a potential risk on the corruption of the OS.

  With switch RunAsync that the cmdlet returns immediately, it will not wait until the underlying vSphere method is complete.

  The method will continue, but in the background.

  You should check these tasks to background (Get-task), to monitor the successful completion.

  To manage VMS in batches of 25 and wait 60 seconds between batches, you could do something like that

  $vms = get - VM

  $step = 25

  $start = 0

  for ($loop = 0; $loop - the ([math]: ceiling ($vms.)) Step Count / $)-1); $loop ++) {}

  $vms [$start... ($Start+$Step-1)] | where {$_.} Guest.State - eq "Running"} | Stop-VMGuest-confirm: $false - RunAsync

  $vms [$start... ($Start+$Step-1)] | where {$_.} Guest.State - eq "Keep"} | Stop-VM-confirm: $false - RunAsync

  sleep 60

  $start += $step

  }

• script to stop the virtual machine

  I am writing a script to stop all the virtual machine as follows:

  1. The list of the VM

  VMLIST ='/ usr/bin/vmrun list '

  for a virtual machine in '$VMLIST '.

  do

  echo '$VM '.

  1. stop the virtual machine

  / usr/bin/vmrun stop '$VM' trysoft

  sleep 2

  fact

  But he failed, the news of the error:

  / root/vmware/Windows NT / Windows NT.vmx

  Error: Could not open the virtual machine: unknown suffixNT/Windows NT.vmx file

  the feedback by the command "echo $VM" is the correct path, but why it says file unknown?

  Please refer to the attachment.

  See if that helps...

  vmlist ='/ usr/bin/vmrun list '

  printf "$vmlist" | egrep '\.vmx$ ' | while reading vm; echo '$vm '.

  / usr/bin/vmrun stop soft "$vm".

  sleep 2; fact

• Could not enumerate the virtual machines that are used as models

  Hey guys,.

  I have a simple script that collects information from a virtual computer. Unfortunately, I'm getting a lot of mistakes, he doesn't pull out information if the virtual machine is used as a model.

  $date = get-Date-format-M - d - yyyy

  Import-Csv C:\test\servers_mate.csv - UseCulture | %{

  Get-VM-name $_. Name |

  Select Name,

  @{N = 'Center'; E = {Get-Datacenter - VM $_______ |} {{Select - ExpandProperty name}}.

  @{N = "Cluster"; E = {Get-Cluster - VM $_______ |} {{Select - ExpandProperty name}}.

  Host, NumCpu, MemoryGB,

  ProvisionedSpaceGB, Powerstate,

  @{N = "Path"; E = {}

  $current = get-view $_. ExtensionData.Parent

  $path = $_. Name

  {}

  $parent = $current

  if($parent.) Name - only "vm") {$path = $parent. {Name + "\" + $path}

  $current is get-view $current. Parent

  } While ($current. Parent - no $null)

  [channel]: join ('-',($path.)) Split('\') [0.. ($path). Split('\'). (Count-2)]))

  }},

  FolderId,

  @{N = "Manufacturer"; E = {(Get-VMHost-Name $_.)} Host). Manufacturer reference}},

  @{N = ' model'; E = {(Get-VMHost-Name $_.)} Host). Model}},

  @{N = "ProcessorType"; E = {(Get-VMHost-Name $_.)} Host). ProcessorType}}

  } | Export-Csv "C:\test\servers-vcenter-servers-vmpath-$date.csv" - NoTypeInformation - UseCulture

  the output current is like that.

  Name

  Data Center

  Cluster

  Host

  NumCpu

  MemoryGB

  ProvisionedSpaceGB

  PowerState

  Folder path

  FolderId

  Manufacturer

  Model

  ProcessorType

  I just also want to collect the same information, even if the virtual machine is used as a model. Introduction 1 additional column is perhaps something like below. So we can clearly identify if it is a virtual machine or be used as a model? Thank you.

  Name

  Data Center

  Cluster

  Host

  NumCpu

  MemoryGB

  ProvisionedSpaceGB

  PowerState

  Folder path

  FolderId

  Manufacturer

  Model

  Type of processor

  Virtual MACHINE or template

  Erros I receive.

  Get - VM: get-VM VM with name 03/08/2015-12:40:44

  "xxxx" was not using the specified

  filter (s).

  Online: 2 char: 5

  + Get-VM-name $_. Name |

  +     ~~~~~~~~~~~~~~~~~~~~

  + CategoryInfo: ObjectNotFound: (:)) [Get - VM], VimException)

  + FullyQualifiedErrorId: Core_OutputHelper_WriteNotFoundError, VMware.VimA

  utomation.ViCore.Cmdlets.Commands.GetVM

  Try something like this

  Import-Csv C:\test\servers_mate.csv - UseCulture | %{

  Notice-EEG - ViewType VirtualMachine-filter @{'Name' = $_.} Name} | %{

  $esx = get-view-Id $_. Runtime.Host

  $_ | Select Name,

  @{N = 'Template'; E={$_. Config.Template}},

  @{N = 'Center'; E = {Get-Datacenter - VM $_.} Name | {{Select - ExpandProperty name}}.

  @{N = "Cluster"; E = {Get-Cluster - VM $_.} Name | {{Select - ExpandProperty name}}.

  @{N = 'Host'; E = {$esx. Name}},

  @{N = "NumCpu"; E={$_. Config.Hardware.NumCpu}},

  @{N = "MemoryGB"; E = {[int]($_.)} Config.Hardware.MemoryMB/1KB)}}.

  @{N = "ProvisionedSpaceGB"; E = {($_.Summary.Storage.Committed+$_.Summary.Storage.Uncommitted)/1 GB)}},

  @{N = "Powerstate"; E={$_. Runtime.PowerState}},

  @{N = "Path"; E = {}

  $current = get-view-Id $_. Parent

  $path = $_. Name

  {}

  $parent = $current

  if($parent.) Name - only "vm") {$path = $parent. {Name + "\" + $path}

  $current is get-view $current. Parent

  } While ($current. Parent - no $null)

  [channel]: join ('-',($path.)) Split('\') [0.. ($path). Split('\'). (Count-2)]))

  }},

  @{N = "FolderId"; E={$_. Parent.ToString ()}}.

  @{N = "Manufacturer"; E = {$esx. Hardware.SystemInfo.Vendor}},

  @{N = ' model'; E = {$esx. Hardware.SystemInfo.Model}},

  @{N = "ProcessorType"; E = {$esx. Hardware.CpuPkg [0]. Description}}

  }

  }

  The error you see seems to indicate that there is an entry in the CSV file for a nonexistent VM.

• Could not start the virtual machine after you use vmkfstools to resize - HELP!

  I thought I knew what I was doing, but apparently not...

  I tried to increase the size of a VM over 36 GB drive and now I can not start the server. Here's the change front of directory list:

  -rw - 1 root root 16781312 Sep 20 19:46 PJAEast-DL01-000001 - delta.vmdk

  -rw - 1 root root 325 28 August to 01:52 PJAEast-DL01 - 000001.vmdk

  -rw - 1 root root 4096 9 February 14:55 PJAEast-DL01-000002 - delta.vmdk

  -rw - 1 root root 277 9 February 14:55 PJAEast-DL01 - 000002.vmdk

  -rw - 1 root root 28201 28 August to 01:52 PJAEast-DL01 - Snapshot1.vmsn

  -rw - 1 root root 28267 9 February 14:55 PJAEast-DL01 - Snapshot2.vmsn

  -rw - 1 root root 131604480 26 August at 08:04 PJAEast-DL01 - flat hard

  -rw - 1 root root 8684 25 August at 21:03 PJAEast - DL01.nvram

  -rw - 1 root root 589 25 August at 15:18 PJAEast - DL01.vmdk

  -rw - r - r - 1 root root 1042 28 August to 01:52 PJAEast - DL01.vmsd

  -rwxr-xr-x 1 root root 2779 Feb 9 15:10 PJAEast - DL01.vmx

  -rw - r - r - 1 root root 267 Feb 9 15:10 PJAEast - DL01.vmxf

  -rw - 1 root root 9898631168 9 February 14:54 PJAEast-DL01_1-000001 - delta.vmdk

  -rw - 1 root root 331 28 August to 01:52 PJAEast-DL01_1 - 000001.vmdk

  -rw - 1 root root 73728 9 February 14:55 PJAEast-DL01_1-000002 - delta.vmdk

  -rw - 1 root root 283 9 February 14:55 PJAEast-DL01_1 - 000002.vmdk

  -rw - 1 root root 36322836480 28 August at 01:41 PJAEast-DL01_1 - flat hard

  -rw - 1 root root 597 25 August at 15:18 PJAEast - DL01_1.vmdk

  -rw - r - r - 1 root root 78710 25 August at 16:06 vmware - 1.log

  -rw - r - r - 1 root root 68108 25 August at 20:43 2.log - vmware

  -rw - r - r - 1 root root 122302 28 August at 01:41 vmware - 3.log

  -rw - r - r - 1 root root 90557 Sep 20 19:54 4.log - vmware

  -rw - r - r - 1 root root 69453 9 February 14:54 vmware.log

  Then, I run the command:

  vmkfstools x 256g PJAEast - DL01_1.vmdk

  And now the virtual machine does not start, return an error: "the virtual disk parent has been changed since the child was created."

  The directory listing is now ("BOLD" indicates the change of information post-vmkfstools):

  -rw - 1 root root 16781312 Sep 20 19:46 PJAEast-DL01-000001 - delta.vmdk

  -rw - 1 root root 325 28 August to 01:52 PJAEast-DL01 - 000001.vmdk

  -rw - 1 root root 4096 Feb 9 16:12 PJAEast-DL01-000003 - delta.vmdk

  -rw - 1 root root 277 Feb 9 16:12 PJAEast-DL01 - 000003.vmdk

  -rw - 1 root root 28201 28 August to 01:52 PJAEast-DL01 - Snapshot1.vmsn

  -rw - 1 root root 28267 9 February 14:55 PJAEast-DL01 - Snapshot2.vmsn

  -rw - 1 root root 131604480 26 August at 08:04 PJAEast-DL01 - flat hard

  -rw - 1 root root 8684 Feb 9 16:12 PJAEast - DL01.nvram

  -rw - 1 root root 589 25 August at 15:18 PJAEast - DL01.vmdk

  -rw - r - r - 1 root root 1015 28 August 01:52 PJAEast - DL01.vmsd

  -rwx - 1 root root 2779 Feb 9 16:12 PJAEast - DL01.vmx

  -rw - 1 root root 267 Feb 9 16:12 PJAEast - DL01.vmxf

  -rw - 1 root root 9898631168 9 February 14:54 PJAEast-DL01_1-000001 - delta.vmdk

  -rw - 1 root root 331 28 August to 01:52 PJAEast-DL01_1 - 000001.vmdk

  -rw - 1 root root 73728 Feb 9 16:12 PJAEast-DL01_1-000003 - delta.vmdk

  -rw - 1 root root 283 Feb 9 16:12 PJAEast-DL01_1 - 000003.vmdk

  -rw - 1 root root 274877906944 28 August 01:41 PJAEast-DL01_1 - flat hard

  -rw - 1 root root 599 9 Feb 16:11 PJAEast - DL01_1.vmdk

  -rw - r - r - 1 root root 68108 25 August at 20:43 2.log - vmware

  -rw - r - r - 1 root root 122302 28 August at 01:41 vmware - 3.log

  -rw - r - r - 1 root root 90557 Sep 20 19:54 4.log - vmware

  -rw - r - r - 1 root root 69453 9 February 14:54 5.log - vmware

  -rw - r - r - 1 root root 39510 Feb 9 16:12 6.log - vmware

  -rw - r - r - 1 root root 39411 Feb 9 16:12 vmware - 7.log

  -rw - r - r - 1 root root 39410 Feb 9 16:14 vmware.log

  I can't do anything else until I get comments. Can anyone recommend a way to solve this problem?

  I thought I knew what I was doing, but apparently not...

  I agree

  Two a problem with the new drive.

  1. You get the error message comes from the basic disk with a different size than the disks of the snapshot.
  2. With a size of 256 GB, you will not be able to create snapshots of the disk (on ESXi prior to 5.0 with a block size of 1 MB)

  What you can try to do is to edit the file PJAEast - DL01_1.vmdk :

  • 536870912 VMFS 'PJAEast-DL01_1 - flat hard' RW--> RW 70943040 VMFS 'PJAEast-DL01_1 - flat hard. "
  • DDB. Geometry.Cylinders = "33418'-> ddb.geometry.cylinders = '4416.

  After that, I would recommend to clone the virtual disk to a new one, replace the virtual disk in the virtual machine settings and resize it to a maximum of 254GB (see "calculates the time system required by the snapshot files" at http://kb.vmware.com/kb/1012384)

  • vmkfstools-i PJAEast-DL01_1 - 000003.vmdk PJAEast - DL01_1a.vmdk

  André

• ESX patch.  "Stop the virtual machine.

  It has been a long day and a night so far and I plan just to weird things.

  Then a stupid question: patch when ESX year screaming 'VM Shutdown & Reboot host' such as the impact on the system, they really mean shutdown (aka put off the power) of the virtual machine? Or is specifically referring to VMware tools that need to be installed which requires essentially a reboot the virtual machine hot. I have run in a few recent scenarios where the particular SMV .vmx file must be updated and, for some reason, cannot be done when turned on. I have worked on 400VMs during the last year and I can honestly say with VMotion and Storage VMotion, can't believe more than 50 of them have actually been actually turned off (EX: increase of the Ram/CPU), even if we patch our windows every month environment that almost always requires a reboot.

  Fun as stuff that keeps me in the night

  RyanWI wrote:

  It has been a long day and a night so far and I plan just to weird things.

  Then a stupid question: patch when ESX year screaming 'VM Shutdown and Reboot host' such as the impact on the system, they really mean shutdown (aka put off the power) of the virtual machine?

  Reboot the host means that the ESX host must be rebooted after the patch is installed.

  Stop the VM means so to patch your ESX host all VMS on host must be stopped or migrated off the power before patching.

• Can not copy VM UM VCenter para outro sem desligar a uma machine virtual (I can copy a virtual machine to one vCenter to another without stopping the virtual machine)?

  Pessoal, boa is late,

  Hello

  Gostaria of sabre to e possible copy of VM uma um VCenter para outro sem ter as desligar a Máquina. Is a possibility?

  I wonder if it is possible to copy one Virtual MACHINE a vCenter to the other without power off duty the machine. There is a possibility?

  Obrigado desde ja

  Thank you

  My brother, fazer o um escopo clone or por exemplo um deploy um model e no mesmo vCenter, or seja, por vias normais, voce nao do clonar OU fazer deploy model vCenter para um um o outro.

  Very, sempre exists uma saida, e no seu caso, você pode fazer o seguinte:

  1 cloned an atual VM (as pode ser feito com an origem watch VM);

  2 copy os archives da VM clonada para o outro datastore vCenter;

  3. no data store don't do novo vCenter, service one pasta da VM e clicar com direito button no land e .vmx selecionar didn't add to the inventory.

• Stop and restart the virtual machines in the remote server

  I need to close virtual machines running guests 4 1 ESX from a remote server (IBM System i).

  The remote server in fact control the storage used by ESX and VM OS, so I'll have to scripts running on the remote server that:

  Stop the virtual machine

  Performs maintenance

  Reboot the virtual machine

  I tried to understand the big picture of the reading discussions here, but I'm still confused.

  VMA is to provide the best way for the virtual machines of withdrawal from a script running on a remote server?

  Scripts can I use SSH to connect to the vSphere environment to run scripts or issue the command?

  Thank you.

  vCLI (really its vSphere SDK for Perl), PowerCLI, VI Java, etc are all vSphere SDK to correct and they are a of the client-side bindings different scripts and programming languages which bind to the vSphere API. When I say 'API', I mean using one of these SDK is you use the vSphere API to perform the work.

  The SDK is initiated on the remote server, this can be windows, linux, etc as long as it supports one of these boxes to tools. In general, for admins, you will use either vCLI (vSphere SDK for Perl) that supports Linux and Windows, or if you are more windows-oriented, you can use PowerCLI.

  Documentation has been referenced in my first post, please take some time the documents because they provide much more detail on the use cases for each + a lot of examples with orders. Yet once, there no involved SSH if you use the vSphere API. As I told, vMA is a virtual appliance, you can download and start using if you do not want to install vCLI or PowerCLI on a remote system, this is assuming that you are comfortable in a Linux environment. If you're not, then I highly recommend using PowerCLI, who will need a remote server for Windows.

  Here are a few started getting additional resources:

  vSphere SDK for Perl + vMA:

  Getting started with vSphere SDK for Perl

  Introduction to the vMA (tips/tricks)

  PowerCLI:

  http://www.VMware.com/support/developer/windowstoolkit/

  http://www.virtu-al.NET/2009/11/10/PowerCLI-where-do-i-start/

  =========================================================================

  William Lam

  VMware vExpert 2009

  Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

  Twitter: @lamw

  repository scripts vGhetto

  Introduction to the vMA (tips/tricks)

  Getting started with vSphere SDK for Perl

  VMware Code Central - Scripts/code samples for developers and administrators

  VMware developer community

  If you find this information useful, please give points to "correct" or "useful".

• No network on the virtual machine after the use of converter

  I was running a basic vm (WinXP) on an esxi4.1 host running short of disk space.

  So I ran the vCenter Converter Standalone client to copy the original VM on a new - the only thing that I changed the size of the disc thin provisioned avaiable.   The copy/convert seemed to work your.

  I started in the new virtual machine, and it came exactly as the old one (with the largest disk).

  ... but the network on the works of more than vm.

  I can still use vSphere to connect to the esxi server and bring up the VM console (which tells me that the network the server works very well).  When I look at the configuration of the virtual machine, it looks exactly like the old (complete with a network powered).   But on the virtual machine, I can't even ping the router, much less get to the dhcp server.

  I even went so far as to stop the virtual machine, remove the network card, restart the virtual machine (if the network has been removed from the virtual machine), stop the virtual machine again, add a NEW network adapter.

  Still the problem remains.  The virtual machine has a network card - but has no network.

  A few thoughts:

  You use a managed physical switch? If so, check if the MAC address of the VM is seen on one of the uplink ports.

  The network management and the virtual machine using the same IP subnet? You could probably try (if possible) is to create an another vSwitch and attach the XP VM to it to see if there is a problem with the virtual machine and the management on the same vSwitch network.

  André

• Block of VMWare workstation to restart the virtual machine

  Hi all...

  I use vmware workstation 9.0.2 on a machine running windows 7 Professional (64 bit) on any domain.

  the problem is that: when I reboot whole VM (windows/linux), vmware stop working a present the home screen (with options F2, F12, ESC)... at this time, all orders (average, suspend, reset) does not work... I need to manually complete the vm procecess - ware.exe, remove *.lck items and restart the physical machine...

  If I stop the virtual machine, all work without problems...

  any ideas?

  Hi riccimaticand welcome to the VMware communities!

  Try disconnecting the virtual CD/DVD drive.  It seems that there are situations in which problems arise to restart a guest, operating system while its virtual optical drive is connected.  The most common cause is using MagicDisc/MagicISO on the host, which is known to cause exactly the problem you describe.

  See you soon,.

  --

  Darius

• Connect physical hard disks to the virtual machine (and leave the data intact)

  Hello

  I'm looking to virtualize a SOHO headless server, that I use mainly for secure file storage.

  Currently, the system runs Linux installed on a small disc and has two drives 1.5 TB, used exclusively for data, in a cluster of ZFS mirroring. (I use the ZFS-fuse Linux-based application).

  I want virtualization for two reasons. One is to make administration easier and safer - avoid having to connect a keyboard and the physical monitor to the box from time to time. The other is that the machine is a bit more powerful to handle the load, and I'm hoping to make it work on other, more challenging tasks.

  Now, there is a catch. These discs are as highly important. I mean the data on them. What I need is to convert the current Linux system to a virtual machine, or re - install Linux on a virtual machine (don't like that), then connect the physical disks to the virtual machine as if they were actually connected.

  I certainly don't want to vmware touches those disks somehow.

  I've read the documentation, but I'm a noob when it comes to server virtualization and system engineering and don't quite understand if this is possible or not. These discs are not a SAN, they are physically connected to the server, I want to install vSphere on. (Of course, I'll log out when I run the setup of vSphere. But I need plug them again later, and they need to be sure that vmware will leave them alone and pass them to the virtual machine transparent.)

  Sigmoid wrote:

  Oh yes, the cluster mirrored ZFS. It is essentially a software RAID type thingie.

  http://en.Wikipedia.org/wiki/ZFS

  A material, or the point of view of virtualization, it appears two hard drives with a single huge partition on each that is not transparent to anyone, except the implementation of ZFS.

  OK, means that you can break the RAID, connect the drives to different host and configure RAID once again, right?

  Let's do it this way

  1. We will need a disc player more for VM, cause on flash, we install ESXi
  2. I will share ZFS :-), all you need to do with that before you install ESXi
  3. make the BACKUP!
  4. Disconnect the data host drives
  5. install ESXi 4.1 U1 free version on flash
  6. Download the site VMware vSphere client
  7. Connect the VM disk to ESXi
  8. customer help create the virtual machine and install the OS on it
  9. stop the virtual machine and esxi
  10. connect DATA drives to the ESXi host
  11. begin to ESXi
  12. See how to add RDM on youtube, after client use, change first hardware VM--> add a new hard disk--> choose Raw Device Mapping--> (physical or virtual) mode--> store it with folder VM - FACT
  13. Start the virtual machine, now your VM should see both drives, with good data course :-)

  I have just made this procedure (add ROW with data in Linux VM) on ubuntu VM, works well

  See you soon
  Artur
  

  Please, do not forget the points of call of the "useful" or "correct" answers

• Store the virtual machines folder has incorrect name

  We have a few VM servers that are stored in directories with incorrect names.  I'm looking on suggestions on repair to the top and go ahead.  When we build a new VM server to replace an existing one, we install and test on the day of migration that we rename the server and the new server, so this causes incorrect storage files.

  (1) what other people do to in this type of situation

  (2) how can I fix misnamed storage files?

  Thank you

  Ryan

  Hello.

  (1) what other people do to in this type of situation

  The same thing here.

  (2) how can I fix misnamed storage files?

  Rename the virtual computer, stop the virtual machine and then cold migrate.  This will make the names correspond to all levels.  OR rename the virtual computer and use Storage vMotion.

  Good luck!

• Can I download can imagine them in the data store when the Virtual Machine is running

  or do I have to stop the Virtual Machine first and then download?

  Rgds

  Chris

  If you want to have a consistent state, Yes.

  If you just need a consistent state to the accident, you can create a snapshot, download the base vmdk files and then validate once again the snapshot operation.

  You cannot download files in use (except the read-only).

  André

• Automatic shutdown of the virtual machines in the Update Manager

  Is it possible to automatically stop the virtual machines as part of the Update Manager?  We have our virtual machines configured for auto power off/start with the host.  But when we apply a lot of patching ESX using the Update Manager, he waits for us to stop manually before putting the host in maintenance mode.

  Any way to automate that? Thank you!

  But when we apply a lot of patching ESX using the Update Manager, he waits for us to stop manually before putting the host in maintenance mode.

  Lol WHA each fails to accomplish is ESX is an enterprise product, it must be used with vMotion.  If the Update Manager is designed to make this easy and pain free, so if you have the shared storage, your VM will migrate to another host, maintenance is done, and the virtual machine back.

  ESX is essentially a hands on environment.  I know everyone can't afford a SAN, but ESX caters to these large enterprise systems that do not have SAN.

  By making a patch, so we are now toward the Windows stand alone everyday server where you have done EACH server, or do it manually power off / closure of EACH virtual machine is EVEN easier to do this 1 by 1 on EACH physical host.

  Consider so it cannot be the best option, it isn't that hard to select ALL VM under tension and click "shut down guest.  Besides that if you plan for a breakdown, you can stop the VM remotely (if windows) by using a shutdown script.

  There are a lot of options to do this, but there is no stopping the VM before update, you must do it manually.