6.1 VDP on vSphere WebClient 6.0 fails to display the status of recent tasks (VICLIENT shows something completely different... real information!)

Similar Questions

• Error during extraction of the vSphere Webclient 5.5 msi installer vCenter

  Get quite desperate here... I try to self-study vSphere, based on a configuration of VMWare Workstation 9 version 5.5. All this on my laptop RAM 16 GB quadcore. And after two days of fighting, I can't even begin because a simple simple installation does not work!

  The error that I'm stuck on whenever that occurs during the installation of the Web Client:

  1152: error is C:\Users\Administrator\AppData\Local\Temp\{378E4D59-A095-46BC-BB1B-A1BCF7013AC5}\vSphere Webclient.msi in the temporary location

  In fact, I notice everything first in the 'easy install' stops after successful installation of SSO and warns that I have to manually install the other components. When I do that with the Web Client, I can see the InstallShield Wizard check it out apparently with success, creating the subfolder randomness with an STD, some files of configuration and "VMWare vSphere Web Client.exe. A "decompression" begins, which is about 75%, then gives error.

  -first time this happened on a Win2008 R2 VM I had installed from a template

  -J' then tried on a freshly installed Win2012 RTM VM, same problem

  -then tried on a Win2012 R2 RTM, here things end with another problem (mentioned in another forum, some missing file on 2012R2 and have to install manually LDS, but 2012R2 'not supported' so I'm not going to try this)

  BUT! : when I start a manual installation of the Web Client on 2012 R2, the "1152 error extraction" does not happen, it passes 'unzip '! So I thought I'd be smart and just copy the folder uncompressed to the other server. Unfortunately, trying to launch the installation of these files you get a message that it only works when the VirtualCenter installation program Initializes the installation... It's to square 1 the vCenter Installer handles all the steps in a 'transaction' and I don't think you can say that you have prepared a subfolder with unzipped "VMWare vSphere Web Client.exe.

  -Then, I thought since the decompression has worked on 2012 R2, but not on my 2012, it had to be some essential Windows which were published between 2012 GTR and 2012R2 update, which affected Windows Installer. So I downloaded more than 600 MB of updates on the 2012 RTM server, installed to get 100% updated (took a few hours).

  Result: no difference...

  I tried other things: installation under local administrator (understand that the path of the temporary folder may have something to do), Safe Mode Setup (impossible since Windows install is not available), VM more memory of a madman 13 GB (compared to 4 GB), through 'run as administrator', race through "Troubleshoot compatibility", choose a different installation language in the drop-down list box when you start the installation...

  I obviously also re-downloaded the iso file of 3.3 GB, but it has not made a difference. And I think that the decompression would also cause an error on 2012R2 then as well, if this part were corrupt.

  I'm totally ideas now... Better, I tried to download and evaluate a different version perhaps? Hope someone has other suggestions.

  TIA

  Hello and welcome to the communities.

  May be wondering the obvious here, but you check checksums for this download to ensure that it was not corrupt?

• Save multiple vCenter Server 5.1 with vSphere WebClient 5.1

  How to save multiple vCenter Server 5.1 with vSphere WebClient 5.1?

  simple enough... on your vCenter > https://localhost:9443 / admin-app / > registry vCenter Server... that's all

  Greetings from Munich, Ralf

• Unable to connect with vSphere WebClient on https

  Hello

  After the upgrade of tot ESXi 5.5 5.5 ESXi update 2 that I can't connect to the host with vSphere Web Client.

  I get the following message:

  RSL https://localhost:9443/vSphere-client/locales/RSL/Flex-common-lib-5.5.0.swf Failed to load. Error #2032

  I already tried this: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US & cmd = displayKC & externalId = 2060114

  I am able to connect with VMWare vSphere Client

  
  

  Can someone point me in the right direction to solve this problem?

  
  

  Thanks in advance,

  
  
  Eric

  Hello

  It seems that the solution to this question is very simple. Just search with the right criteria.

  Sorry for that.

  The solution is to delete the cache of the browser you are using to connect to the host.

  But now the following problem occurs.

  Once connected using a windows session. I do not see my host, nor of the vm on it.

  I hope someone can help.

  Eric

• vSphere 5.5 U1a force upgrade of the hardware version to 9 instead of 10?

  Is there a way to force vSphere to upgrade the version of VM hardware to 9 instead of 10, when you select upgrade virtual hardware?  Main reason is that I don't think we are ready to start using the web console purely or PowerCLI.

  Is there a way to force vSphere to upgrade the version of VM hardware to 9 instead of 10, when you select upgrade virtual hardware?

  No, there are none. It will always improve to the latest version available for the ESXi host on which the virtual machine is currently registered. If it is registered on a 5.5 host it will move to v10, on a multitude of 5.1 to v9, on 5.0 in v8 etc. Apart from that it is impossible to control which version you want to upgrade virtual machine to.

  Main reason is that I don't think we are ready to start using the web console purely or PowerCLI.

  What is the problem with either? OK, I don't really like the service WebClient is but VMware clearly is the future (sad) and I don't think it's something you need to do very often.

  And it's a simple one-liner of PowerCLI Set - VM - VM MyVM-Version v9 - confirm: $false to perform the upgrade.

  If you are unhappy with this, then you probably don't want to use the ESXi shell that way or the other I guess:

  # vim - cmd vmsvc/upgrade [ID VM previously acquired via vim - cmd vmsvc/getallvms] vmx-09

• vSphere high availability 'Élection' fails at 99% 'operation timed out' to 1 of the 2 hosts

  Hello

  We had a system with 1 host ESXi 5.1 with local disks.

  Now, we install redundancy by adding a 5.5 U2 ESXi host and a device of vCenter 5.5.

  After having installed and any addition to vcenter, we went the ESXi 5.1 to 5.5 U2 ESXi. The SAN works correctly (vMotion works on the own NETWORK card).

  Now, if I try to activate the high availability, both servers will install the HA Agent and start "Election".

  All the warehouses of data (4) on the SAN are chosen for the HA heartbeat, response of isolation is "keep it turned on" by default.

  A server will always be this process done, and the other will keep "elect" until it reaches 100% and errors on the operation "election timed out.

  I've seen this problem on both servers, so I think that the 'master' elected does not have the problem, only the "slave".

  I have checked these items and executed, but not worked:

  VMware KB: Reconfiguration HA (FDM) on a cluster fails with the error: operation timed out

  -The services were running

  VMware KB: Configuration HA in VMware vCenter Server 5.x does not work, error: Operation Timed out

  -All the MTU has been set at 1500

  VMware KB: VMware High Availability Configuration fails with the error: unable to complete the configuration of the ag of HA...

  -the default gateway is not the same on the two hosts, but I fixed that. There is no itinerary changes. HA the setting is "leave power." After correction and deactivation/reactivation HA, the problem is always the same.

  VMware KB: Check and reinstall the correct version of the VMware vCenter Server agents

  -J' ran "Reinstall ESX host management agents and HA on ESXi" agent of HA, and I checked that it was uninstalled and reinstalled during the reactivation of HA.

  CP /opt/vmware/uninstallers/VMware-fdm-uninstall.sh/tmp
  chmod + x /tmp/VMware-fdm-uninstall.sh
  /tmp/vmware-FDM-uninstall.sh

  I did this for two guests. This fix makes the problem of the election and I was still able to run a HA test successfully, but when after this test, I turned off the 2nd Server (in order to test the PA in the other direction), HA has no failover to 1 and everything remained low. After pressing 'reconfigure HA', the problem of the election appeared again on 1 hosts.

  Here are a few extractions of newspapers:

  -L' availability vSphere HA of that host State became election info 29/11/2014 22:03 192.27.224.138

  -vSphere HA agent is healthy info 29/11/2014 22:02:56 192.27.224.138

  -L' availability vSphere HA of that host State became Master info 29/11/2014 22:02:56 192.27.224.138

  -L' availability vSphere HA of that host State became election info 29/11/2014 22:01:26 192.27.224.138

  -vSphere HA agent is healthy info 29/11/2014 22:01:22 192.27.224.138

  -L' availability vSphere HA of that host State became Master info 29/11/2014 22:01:22 192.27.224.138

  -L' availability vSphere HA of that host State became election info 29/11/2014 22:03:02 192.27.224.139

  -Message "host vSphere HA State" on 192.27.224.139 changes from green to red info 29/11/2014 22:02:58 192.27.224.139

  officer of HA - vSphere for this host has an error: vSphere HA agent may not be properly installed or configured WARNING 29/11/2014 22:02:58 192.27.224.139

  -L' availability vSphere HA of that host State became info error of initialization of 29/11/2014 22:02:58 192.27.224.139

  -L' availability vSphere HA of that host State became election info 29/11/2014 22:00:52 192.27.224.139

  -DSMD3400DG2VD2 data store is selected for the storage heartbeat controlled by the HA agent vSphere on this info host 29/11/2014 22:00:49 192.27.224.139

  -DSMD3400DG2VD1 data store is selected for the storage heartbeat controlled by the HA agent vSphere on this info host 29/11/2014 22:00:49 192.27.224.139

  -Firewall configuration has changed. 'Enable' to rule the fdm value successful.  29/11/2014 info 22:00:45 192.27.224.139

  -L' availability vSphere HA of that host State became not initialized info 29/11/2014 22:00:40 reconfigures vSphere HA 192.27.224.139 root host

  -vSphere HA agent on this host is disabled info 29/11/2014 22:00:40 reconfigures vSphere HA 192.27.224.139 root

  -Reconfigure HA vSphere host 192.27.224.139 operation has timed out.     root of HOSTSERVER01 29/11/2014 22:00:31 29/11/2014 22:00:31 29/11/2014 22:02:51

  -Configuration of vSphere HA 192.27.224.139 operation has timed out.     System HOSTSERVER01 29/11/2014 21:56:42 29/11/2014 21:56:42 29/11/2014 21:58:55

  Can someone give me please with help here?

  Or the extra things that I can check or provide?

  I'm currenty running options.

  Best regards

  Joris

  P.S. I had problems with cold Migration during the implementation of the SAN. After setting up all (vMotion, ESX upgrade), these problems have disappeared.

  When you search for this error, I came to this article: KB VMware: VMware vCenter Server displays the error message: unable to connect to the host

  And this cause could make sense, since the server vCenter changed and IP addressing has been changed during the implementation.

  However, in the file vpxa.cfg, the < hostip > and < serverip > is correct (verified by using https://< hostip > / home).

  Tried this again today, no problem at all.
  

  P.P.S. I have set up several of these systems from scratch in the past without problem (if it is an 'upgrade').

  OK, so the problem is solved.

  I contacted Dell Pro Support (OEM offering the license) and they checked the logs (fdm.log) and found that the default IP gateway could not be reached.

  The default gateway is the ip address by default host isolation, used by HA.

  Because it is an isolated production system, the front door provided proved only for future purposes.

  Now, I've changed the default gateway address of management on the switch plugged into both hosts, namely the ping requests.

  This solved any problem.

• vCloud connector 2.5 - copy the model of vSphere to vCloud Director fails

  Hi all

  I'm trying to make a copy of the model of the private Cloud for vSphere (e.g. my instance of vCenter lab) the vCloud Director private cloud (my instance vCD lab, which is deployed and registered with the same instance of vCenter mentioned above) with vCloud connector 2.5.

  I have deployed the server component of vCC, configured and deployed two nodes of vCC - a to connect to vCenter for private cloud config vSphere and another to connect to the vCloud Director org for the basic cloud vCD config private. Moreover, the vCloud Director is registered to the same instance of vCenter which is used for vSphere cloud.

  I then tried to open a copy of the model from the vSphere cloud node to the node of vCD. The task to export the OVF template will start, and the task of SCR plugin will also display the copy task. This vCD instance also model any TIME if you go to the properties of the VDC organization selected during the SCR copy Wizard.

  After about 18%, the percentage remains stuck there for a little bit before the 'Export OVF Template"task fails with"Operation timed out ". After that, the task indicated in the vCC plugin will fail also later with (OVF Export failed. Null message) and the import of VAPP model in vCD job will fail also - VAPP failure will take upward of space inside the affected storage however profile until I have manually remove the failing through vCD VAPP model object.

  Anyone else having this problem? I've seen this problem on both environments so far: vCenter 5.1 update 1 with vCD 5.1.2 and vCenter 5.5 with vCD 5.5. If the problem seems to be specific to the version of vSphere. The logs generated by server SCR bee all that useful for me to understand what went wrong did not.

  Thank you

  You can consult this KB, if you haven't done so yet:

  http://KB.VMware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalID=2078110

  I hope this helps.

• vSphere 5.1 installation failed for the SSO

  vSphere 5.1 on Windows 2012

  _________________________________________
  MSI (s) (24:78) [19:02:00:087]: op to run: CustomActionSchedule (Action = VM_UpdateSSOTomcatServerXMLFile, ActionType = 1025, Source = BinaryData, target is VMUpdateSSOTomcatServerXMLFile, CustomActionData = d:\Program Files\VMware\Infrastructure\SSOServer\\conf\server.xml)
  MSI (s) (24:54) [19:02:00:087]: call for a custom action to distance. DLL: C:\Windows\Installer\MSIB987.tmp, point of entry: VMUpdateSSOTomcatServerXMLFile
  Error 20020.Failed to update the values in the server.xml file.
  _____________________________________________________
  If installation path to SSO is changed - at least the c: d:
  SSOServer way SSOServer\conf\server.xml have double "------" and failure - installation causing
  solution is to leave the default path - it remains unchanged for SSO component only

  Here's how to fix it:

  1 enable 8.3 name generation on your filesystem (IE NtfsDisable8dot3NameCreation = 0)

  2 delete the directory C:\Program Files\VMware\Infrastructure\SSOServer

  3 reset

  4. repeat - worked for me.

  The thread of VMware years have failed to understand that the 8.3 file names are not available during the install and they always relying on them.

• vSphere Webclient authentication takes 3-5 minutes to complete

  Hey there,

  I have a vCenter Server Appliance here where the vSphere Client connection authentication step takes 3-5 minutes each time that a user wants to connect. When the user finally logs, what's up.

  vSphere Client c# works very well.

  Any source of identity the user comes from. localos, vsphere.local or advertising. Even when you are disconnected from the AD there are still local users a few minutes to connect.

  I upgraded the device, but it's the same behavior on both version (5.1 and 5.5U1).

  I suspect some sort of timeout network for certain parts of the web client (connection works and the works of customer Web thin after that, so the essential ports seem to be open)

  Has anyone seen this behavior or got a tip which saves VCSA could help me?

  Thank you

  
  Tim

  Hey Jason,

  Thanks for your reply,

  I found the same errors in my logs, but it wasn't the problem.

  I just had a call with the GSS from VMware team and they found an old plugin registered in vCenter, who wait for a timeout for each connection. Only in the web even though customer as c# client disabled the plugin on its own.

  We have registered the plugin and now everything works fine.

  Tim

• With vSphere health Analyzer 6 fails - an error occurred while gathering

  If something has changed with vSphere 6 that breaks the health Analyzer?  I use the last 5.0.4.1.  After starting a new project and adding the appropriate in vCenter Server Discovery credentials, he asks for resources to scan.  I have all the boxes and
  Click Next.  He thinks about it for a moment, then returns - an error has occurred at the time of collection.   Of course, this works perfectly under vSphere 5.x.

  Any ideas?

  Thank you

  Steve

  Officially HA5.0.4.x or earlier is not supported with vSphere 6.0. Workaround: Do not enter the information from the SSO server when connecting.

  What will be missing by running HAV without SSO information?

  If VSAN in your vCenter then you will miss the following information:
  Data table for a best practice VSAN-014, table data and the analysis of best practices VSAN-004, 007 VSAN and VSAN-009
  If you have vFRC in your vCenter then data table will be missing for VM - 028.
  As a solution it is manually by using the Web Client vSphere.

  We will address these issues in the 5.0.5 release.

• After copying a machine a host for another vspehere vsphere virtual machine I can not load the VM machine upwards. Can't open the Flash "hard" or one of the disks disk that this depends on

  Here is the error msg I get from vsphere client.

  Cannot open the Flash '/vmfs/volumes/52120f68-3f09e8f0-affd-f01fafcf18af/w2k3SE-base-20101005/Windows w2k3.vmdk' or one of the disks disk that it depends on.

  The system cannot find the specified file

  VMware ESX can not find the virtual disk '/vmfs/volumes/52120f68-3f09e8f0-affd-f01fafcf18af/w2k3SE-base-20101005/Windows w2k3.vmdk '. Check that the path is valid and try again.

  I have ssh client due to vmware ESX.

  ls # vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple

  564d73b4-7443-6b7f-9a70-cd355ad76d3b.vmem Windows XP Professional.vmx.0 Windows w2k3 - s004.vmdk Windows w2k3 - vmware - 16.log s009.vmdk

  Windows XP Professional - 24367b9b.hlog Windows XP Professional.vmxf Windows w2k3 - s005.vmdk Windows w2k3.vmdk vmware - 17.log

  Windows XP Professional.nvram Windows w2k3 - s001.vmdk Windows w2k3 - s006.vmdk hiding vmware - 18.log

  Windows XP Professional.vmsd Windows w2k3 - s002.vmdk Windows w2k3 - 14.log - vmware vmware - 19.log s007.vmdk

  Windows XP Professional.vmx Windows w2k3 - s003.vmdk Windows w2k3 - vmware - 15.log vmware.log s008.vmdk

  It seems that all the files are there. Except that there are some spaces.

  / vmfs/volumes/52120f68-3f09e8f0-AFFD-f01fafcf18af/Apple # cat "Windows w2k3.vmdk".

  # Disk DescriptorFile

  version = 1

  Encoding = "windows-1252".

  CID = 97c834c1

  parentCID = ffffffff

  isNativeSnapshot = 'no '.

  createType = "twoGbMaxExtentSparse.

  # Description of the measure

  RW 4192256 CLAIRSEMES "Windows w2k3 - s001.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s002.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s003.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s004.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s005.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s006.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s007.vmdk.

  RW 4192256 CLAIRSEMES "Windows w2k3 - s008.vmdk.

  RW 16384 SPARSE "Windows w2k3 - s009.vmdk.

  # The database disk

  #DDB

  ddb.virtualHWVersion = "7".

  DDB. UUID = "60 00 C2 91 86 bb a5 - 5 c bc 28 89 75 01 c9 b0 e1"

  DDB. Geometry.Cylinders = "16383.

  DDB. Geometry.Heads = "16".

  DDB. Geometry.sectors = "63".

  ddb.adapterType = 'ide '.

  ddb.toolsVersion = "8228.

  ddb.longContentID = "9d219dcc524591ac1095297d97c834c1".

  and here's a copy of the vmware.log file

  2014-08-14 T 19: 01:56.925Z | VMX | I120: DISKLIB-STRING: "/ vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3.vmdk ': cannot open (the system cannot find the specified file).

  2014-08-14 T 19: 01:56.925Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s001.vmdk ": closed.

  2014-08-14 T 19: 01:56.925Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s002.vmdk ": closed.

  2014-08-14 T 19: 01:56.925Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s003.vmdk ": closed.

  2014-08-14 T 19: 01:56.925Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s004.vmdk ": closed.

  2014-08-14 T 19: 01:56.925Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s005.vmdk ": closed.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s006.vmdk ": closed.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s007.vmdk ": closed.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s008.vmdk ": closed.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: DISKLIB-VMFS: ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3 - s009.vmdk ": closed.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: DISKLIB-LIB: can't open ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3.vmdk' with flags 0xa, the system cannot find the specified file (25).

  2014-08-14 T 19: 01:56.926Z | VMX | I120: Msg_Post: error

  2014-08-14 T 19: 01:56.926Z | VMX | I120: [msg.disk.fileNotFound] VMware ESX can not find the virtual disk "/ vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3.vmdk» Check that the path is valid and try again.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: [msg.disklib.FILENOTFOUND] the system cannot find the specified file

  2014-08-14 T 19: 01:56.926Z | VMX | I120: [msg.disk.noBackEnd] cannot open disk ' / vmfs/volumes/52120f68-3f09e8f0-conf-f01fafcf18af/apple/Windows w2k3.vmdk' or one of the snapshot disks it depends on.

  2014-08-14 T 19: 01:56.926Z | VMX | I120: ----------------------------------------

  2014-08-14 T 19: 01:56.939Z | VMX | I120: DISC: discs of opening had 24 ms.

  2014-08-14 T 19: 01:56.939Z | VMX | I120: Module DiskEarly market failed.

  2014-08-14 T 19: 01:56.939Z | VMX | I120: VMX_PowerOn: ModuleTable_PowerOn = 0

  2014-08-14 T 19: 01:56.942Z | VMX | I120: WORKER: asyncOps = 1 maxActiveOps = 1 maxPending = 0 maxCompleted = 0

  2014-08-14 T 19: 01:56.950Z | VMX | I120: Vix: [12787513 mainDispatch.c:3870]: VMAutomation_ReportPowerOpFinished: VarEtat = 1, newAppState = 1873, success = 1 additionalError = 0

  2014-08-14 T 19: 01:56.951Z | VMX | I120: Vix: [12787513 mainDispatch.c:3870]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1 additionalError = 0

  2014-08-14 T 19: 01:56.951Z | VMX | I120: Past vmx/execState/val of poweredOff

  2014-08-14 T 19: 01:56.951Z | VMX | I120: Vix: [12787513 mainDispatch.c:3870]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 0 additionalError = 0

  2014-08-14 T 19: 01:56.951Z | VMX | I120: Vix: [12787513 mainDispatch.c:3909]: error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): unknown error

  2014-08-14 T 19: 01:56.951Z | VMX | I120: Vix: [12787513 mainDispatch.c:3870]: VMAutomation_ReportPowerOpFinished: VarEtat = 0, newAppState = 1870, success = 1 additionalError = 0

  2014-08-14 T 19: 01:56.951Z | VMX | I120: Past vmx/execState/val of poweredOff

  2014-08-14 T 19: 01:56.952Z | VMX | I120: VMIOP: output

  2014-08-14 T 19: 01:56.956Z | VMX | I120: Vix: [12787513 mainDispatch.c:861]: VMAutomation_LateShutdown()

  2014-08-14 T 19: 01:56.956Z | VMX | I120: Vix: [12787513 mainDispatch.c:811]: VMAutomationCloseListenerSocket. Close the socket of the receiver.

  2014-08-14 T 19: 01:56.957Z | VMX | I120: VMX VMDB Flushing connections

  2014-08-14 T 19: 01:56.957Z | VMX | "I120: VmdbDbRemoveCnx: remove Cnx Db for ' / db/connection / #1 /"

  2014-08-14 T 19: 01:56.957Z | VMX | I120: VmdbCnxDisconnect: Disconnect: pipe closed for pub cnx ' / db/connection / #1 /' (0)

  2014-08-14 T 19: 01:56.961Z | VMX | I120: Exit VMX (0).

  2014-08-14 T 19: 01:56.961Z | VMX | I120: AIOMGR-S: o stat = 1 r = 3 w = 0 I = 0 br = 49152 bw = 0

  2014-08-14 T 19: 01:56.961Z | VMX | I120: OBJLIB-LIB: ObjLib cleaning done.

  2014-08-14 T 19: 01:56.961Z | VMX | W110: VMX has left the building: 0.

  Assuming that you have enough free disk space on the host ESXI 5.1 data store, I suggest you that you load the multiextent module as shown in the link, I posted and then clone the virtual disk using the vmkfstools command line utility.

  vmkfstools 'Windows w2k3.vmdk'-i 'clone.vmdk' slim-d - an ide

  vmkfstools EI 'Windows w2k3.vmdk' 'old.vmdk '.

  vmkfstools EI "clone.vmdk" "Windows w2k3.vmdk".

  The first line of the clones of the virtual disk in a virtual drive put in service end format, and the following two lines renaming virtual disks, so that you can delete the "old*.vmdk" files once the VM works as expected.

  Alternatively, you can also run the commands on the host ESXi 4.1 and then copy the new files hard again to avoid loading the multiextent module in the new host.

  André

• With vSphere test/recovery replication all while keeping the main site online.

  Hi guys. niot sure if I'm missing something really obvious.

  From what I can understand tha base "recovery process" in vSphere Replication5.1 implies the following workflow

  However, our profession demands that we test the ability to recover the VMs selected the site of DR then than DO NOT impact main site.

  Is this possible without SRM / table to database replication / replication of VEEAM?

  Our installation program

  VCenter PROD (dedicated VLAN x)

  VR PROD device (including VLAN, dedicated)

  PROD-HA and DRS Cluster

  Guest PROD networking (VLAN z)

  DR VCenter (dedicated Vlan X)

  VR PROD device (including VLAN, dedicated)

  PROD-HA and DRS Cluster

  PROD comments Networking (VLAN, isolated, cannot drive to the main site)

  No RS and no possibility to use the replication table according to preverred, no Budget for VEEAM replciation.

  MUST BE DONE, while the primary site remains fully alive >

  Basic procedure to test recovery to DR and come back if I understand correctly >

  1 tasks replication setup (fact)

  2 access to the web in VCENTER DR > Pause/Stop replication on the virtual machines, we want to retrieve.

  3 web access in VCENTER DR > retrieve DR virtual machines using 'recover with the latest changes' (Show stop as primary/Source VM needs to go down)

  3 assuming that it is a path last step 3, we intend to move guests picked up at DR VLAN, one port groups and reconfigure the Ips using Powershell process mass

  4 active Directory and DNS will be changed to Dr. TEST Site to make usable salvaged customers.

  test to DR on revovered VMs in DR VLan 5 users, so this should be route back or affect the site of PROD.

  6 not recovered VMs to the main site. This required once more primal VMs being to low or EVEN be removed from the inventory!

  Procedure here

  VMware vSphere 5.1

  Looks like so there is no way to use vSphere replication to TEST the abilty to toggle, unless you can share the secrets with me.

  If you are using vSphere replication without SRM above it, recovery Test is not available. The process, you can follow in case you do not want your main Web site:

  (1) perform a recovery using the second option (retrieve by using the latest available data). In this way you will not have to power off of the VMs source and your main site will be online.

  (2) when the recovery is complete, stop the replications (which will be in a State of recovery)

  (3) power off VMs recovered, unsubscribe them inventory of VC, but keep the files of disk intact.

  (4) manually configure all repetitions using disks that have been left in the form of initial seeds. This will cause the changes to synchronize.

  In step 4 of ease, you can use the multi-vm replication configuration wizard vSphere. Just make sure that the data store target each disk that will be used as initial copy is put in the folder with the name of the virtual computer. Then, you could try to configure all virtual machines at once, performing the search of seeds and confirming to use.

• Migration of VMS of vsphere 5.0 and 5.5. The virtual computer hardware should be upgraded?

  We have a few virtual machines to a roommate with a newer version of vsphere. Are there benefits to upgrading in addition what is listed in the link below? We have really no need for the maximum ram or cpu upgrades. I thought that now version 8 virtual machines should be fine, unless there is a major performance improvement or other reason to upgrade to 10.

  Hardware features available with the Virtual Machine compatibility settings

  You are on point with your comments. There is no need to upgrade to version 10, you if you don't need. This is why VMware is now calling VM Compatibility virtual rather than physical level. This is to remove the pressure of always trying to follow with the virtual hardware.

  By experience, I find the upgrade virtual hardware, one of the scariest parts of any upgrade project. Ive met a lot question after her that is why it is always recommended to create a snapshot prior to an update of the virtual hardware. Its the only way to restore.

• How to accumulate vSphere 5.5 (or 5.1) of the Earth? (If you do not have a stand-alone client)

  This can be a very basic question, but I wonder if these conditions have been met:

  1. you gave with bare metal resources (with complete listing of virtualization server hardware)

  2 client/customer wants a 'all ' virtual environment (so including vcenter, secondary AD/DNS, database servers, etc.)

  3. primary DNS must be on a server (standalone) bare metal as shown.

  Before vSphere 5.5/5.1, (my) would be to

  1. install a single ESXi host,.

  2 install vmware client on a laptop Desk/computer

  3 to connect to the first host

  4 build virtual machines for AD/DNS secondary servers and the database server required (SQL for example) as VMs.

  5 build vCenter server (and other requirements)

  6 build other esxi hosts

  7. Complete/Build of the cluster

  8. Migrate/move the primary VMS (vcenter, AD/DNS) to cluster (with technical details applied)

  How it should be done in vSphere 5.5 (5.1)?

  If you are using an older version (5.0 or 5.1) for 5.5 access is what you will see. Some want to make already installed 5.0 or 5.1 it will appear

  

  This happens if you use your previously installed client. If you do not have any client installed in your environment with the new ESXi a 5.5 vsphere client will be given which can be used to access the server directly.

  It is possible by going to https:// after installing an ESXi 5.5. You will find an option called download vsphere client 5.5 which will connect to the internet and download a client.

  SSO is a module to be installed as part of your installation of vCenter. If you are installing vCenter using a simple installation, it will install SSO service inventory, vSphere client Web (access to vcenter via a web browser) and vCenter server.

  After installing SSO and vcenter you can add your advertisement as a source of authentication to your vCenter.

  This is not to be confused, but if you plan to go with vSphere 5.5 in most functions in vSphere client is disabled and you use Vsphere web customer to make the most of management activities.

  vSphere Web Client Demo - YouTube   If you are new customer Web. This will help you.

• An internal error has occurred in the vSphere Client. Details: Index was outside the bounds of the array.

  Hello world

  I have a number of active hosts VMWare ESXi 5 I manage, but since yesterday I encounter the above error.

  On a new server, I installed ESXi 5 successfully and I can connect to my Client vSphere host. However, as soon as I try to create a new virtual machine, the error message appears. (See attached screenshot)

  Later, I tried to connect to my existing 5 ESXi hosts and has experienced the same error when you try to perform the same operation.

  Any advice on how to fix this? I tried to reinstall the client on my machine without success. However, I can perform the same operations with success since another spare machine I have on the network.

  vSphere Client: Version 5.1.0 Build 786111

  (I'm trying to download the new version as we speak)

  Well, there are two things you could do to further isolate:

  1. on your account, try a clean boot and check http://support.microsoft.com/kb/929135

  2. try to recreate your user profile and check the difficulty of a user profile is corrupted

  Concerning

  one