JustyC's Posts

Worked through the problem(s) with some help from VMware Support.  Found documentation on un-registering vCenter\PSC somewhat sparse and\or confusing.  Was following VMware KB 2106736.  Make sure... See more...
Worked through the problem(s) with some help from VMware Support.  Found documentation on un-registering vCenter\PSC somewhat sparse and\or confusing.  Was following VMware KB 2106736.  Make sure to stop the PSC service before doing unregister vCenter.  The vCenter step is on the last page of the KB.... not sure why..  I guess I needed to read between the lines, which I didn't do.  The other item that caused an issue was having to re-point one of the 4 PSCs in Linked mode.  Finally in the end cmsso-util still threw an error....... Had to run the vdcleavefed command to force a rip out of the machine account.  All appears to be working well now. 
Getting an error when unregistering a PSC. Our environment has 4 sites running Linked-Mode.  Each site has 3 guests.... 1 vCenter, 1 PSC and 1 SQL.  Sites 2, 3 and 4 partner back to the PSC at ... See more...
Getting an error when unregistering a PSC. Our environment has 4 sites running Linked-Mode.  Each site has 3 guests.... 1 vCenter, 1 PSC and 1 SQL.  Sites 2, 3 and 4 partner back to the PSC at site 1.  We are shutting down site 2. I'm following VMware KB 210736.  I stopped the PSC service at site 2, then  on that PSC ran cmsso-util to unregister the vCenter, which was successful.  Then I went to the PSC at site 4 and ran cmsso-util to unregister the PSC at site 2, but received an error.  A bit confusing..... displays error 1, but then shows Success. Below is the cmsso-util output.  I believe I need to run vdcleavefed -h -u -w to force a rip-out of the machine account, but need someone to verify if that is correct.  If it is, where do I run vdcleavefed ?  From the PSC at site 4 or on the PSC at site 2 (the one being removed) ?  Thanks in advance for any help. D:\Program Files\VMware\vCenter Server\bin>cmsso-util unregister --node-pnid km- 001-psc01.minoltana.minolta.com --username administrator@vsphere.local --passwd Admin01$ D:\Program Files\VMware\vCenter Server\python-modules\identity\vmkeystore.py:4: RuntimeWarning: to-Python converter for struct client already registered; second conversion method ignored.   import identity.vmafd as vmafd D:\Program Files\VMware\vCenter Server\python-modules\identity\vmkeystore.py:4: RuntimeWarning: to-Python converter for class vmafd_exception already registered ; second conversion method ignored.   import identity.vmafd as vmafd WARNING! This step is irreversible! Are you sure you want to unregister host km-001-psc01.minoltana.minolta.com ? (Y or N) Y 2018-01-31T21:51:05.712Z   Running command: ['D:\\Program Files\\VMware\\vCenter Server\\vmafdd\\dir-cli.exe', 'service', 'list', '--login', 'administrator@vsph ere.local'] 2018-01-31T21:51:06.012Z   Done running command 2018-01-31T21:51:06.848Z   RC = 1 Stdout = vdcleavefd offline for server km-001-psc01.minoltana.minolta.com Leave federation cleanup failed. Error[1] - Operations error Stderr = password: ERROR unregistering computer account. Success
Just started working with SRM version 6.5.  Will be using SRM to move a datacenter to a new facility.  Once the SRM process completes..... all guests are visible at the new site I would like to ... See more...
Just started working with SRM version 6.5.  Will be using SRM to move a datacenter to a new facility.  Once the SRM process completes..... all guests are visible at the new site I would like to test in an isolated network.  The guests are SAP-Hana...... we want he original guests, those on the sending site to remain active...... the ones at the new site need to be up and on a isolated network.  There cannot be any connections between the 2 environments. What is the best way to do isolated testing once guests are at the new site ?  Was looking at creating a standard switch, however all guests will not fit on 1 host. I did create a DvSwitch port with no uplinks, but not sure if that will work.  I do not want to create a new private VLAN if that entails using our Network Group's precious time. What is the best way to accomplish isolated testing ?  Thanks in advance.
Looking for options to move guests from ESX 4.0 hosts managed by vCenter 5.0 to a new vCenter 6.0 environment.  We do not want to upgrade the ESX 4.0 hosts as the hardware is old and will be take... See more...
Looking for options to move guests from ESX 4.0 hosts managed by vCenter 5.0 to a new vCenter 6.0 environment.  We do not want to upgrade the ESX 4.0 hosts as the hardware is old and will be taken out of service.  vCenter 5 doesn't see the same SAN storage as the vCenter 6.   I know we can use the VMware Converter, but guests need to be powered down.  Using vMotion between vCenters is not possible.  CPUs in  the 4.0 hosts are AMD....... CPUs in the vSphere 6 hosts are Intel.  Ideally we don't want any down time for the 140 guests.  Can anyone offer some other options ?  Thanks in advance. 
There has been some discussion on a DR site.  Nothing is in place right now.  It could be 6-12 months before a DR site is available.  If I build vCenter with embedded PSC what factors come into p... See more...
There has been some discussion on a DR site.  Nothing is in place right now.  It could be 6-12 months before a DR site is available.  If I build vCenter with embedded PSC what factors come into play when we start using SRM ? Would the embedded PSC need to be moved to external for SRM and Linked Mode ?    
In the past I liked the idea of vCenter being physical since we have on-going issues with our iSCSI connected SAN storage.  Should there be high latency or lost access to storage then vCenter can... See more...
In the past I liked the idea of vCenter being physical since we have on-going issues with our iSCSI connected SAN storage.  Should there be high latency or lost access to storage then vCenter can be unavailable for a time. On the other hand going the virtual route does add HA & DRS and would use the same backup process as used for all the other VMs.  Our AD and DNS are servers are split between physical and virtual so should vCenter be down we can still function to some extent with .  vCenter appliance has been behind on features compared to the Windows install.  Is that still the case with version 6.0 ?  Should I focus on the appliance version ?
We are building a new vCenter 6 U2.  Been going round and round between embedded versus external PSC.  We have other business entities running VMware, but they manage themselves, at least for no... See more...
We are building a new vCenter 6 U2.  Been going round and round between embedded versus external PSC.  We have other business entities running VMware, but they manage themselves, at least for now.  Here at my location (corporate) we have 45 hosts and around 800 VMs.  Installing as embedded would be easier and should provide headroom to increase the maximum number of hosts.  Installing with the PSC external may be of value should we have to hook into the other business entities, but also  poses concerns about PSC HA, patch updates, backup\recovery, etc. There also appears to be more administration.  Our current 5.0 vCenter runs on physical hardware.  Some recommend sticking with physical while others say go the virtual route.  Can anyone offer some advice on these questions ?  Thanks. .  
We currently run vCenter 5.0.  We were going to do a new fresh install of 6.0 U2, but now see 6.5 is out.  Should we stick with 6.0 U2 for now and then upgrade to 6.5 later or just jump right int... See more...
We currently run vCenter 5.0.  We were going to do a new fresh install of 6.0 U2, but now see 6.5 is out.  Should we stick with 6.0 U2 for now and then upgrade to 6.5 later or just jump right into 6.5 ? Anyone have a recommendation ?  Are there any 6.5 support or stability issues that would affect the decision ?  Thanks.
Hello.  We have 2 ESX 4.0 U2 hosts that are now obsolete, but still powered up.  The license used on them was downgraded from ESXi 5 Enterprise to ESX 4.0 Enterprise.  We need to upgrade that lic... See more...
Hello.  We have 2 ESX 4.0 U2 hosts that are now obsolete, but still powered up.  The license used on them was downgraded from ESXi 5 Enterprise to ESX 4.0 Enterprise.  We need to upgrade that license..... back to 5.0.  We see how to do that through My VMware License Keys.  Do the old hosts need to be powered down first before we do the license upgrade and remove the licenses from them ?  Would removing the hosts from inventory remove the association of the ESX 4.0 key so that we can upgrade it to 5.0 and apply to the newer hosts we just built ?  Thanks in advance.
Just added 2 Emulex LPe12000-E HBAs to a couple of ESXi 5.0 U3 hosts.  In vCenter when I display storage adapters one host displays 1 of it's LPe12000-E adapters as a LP6000. I did a SSH session... See more...
Just added 2 Emulex LPe12000-E HBAs to a couple of ESXi 5.0 U3 hosts.  In vCenter when I display storage adapters one host displays 1 of it's LPe12000-E adapters as a LP6000. I did a SSH session to the host and esxcfg-scsidevs -a shows both HBAs as being LPe12000-E.  I then checked firmware and driver versions and all are at the same level.  Both HBAs appear to be working OK.  Is there any reason for concern ?  Thanks.
We are running W2012 R2 guests on ESXi 5.0 U2 hosts.   Guests fail and reboot often with Windows event 1001 Bugcheck stop 0x00000109.  We created a CPUID mask on these guests as per VMware KB 20... See more...
We are running W2012 R2 guests on ESXi 5.0 U2 hosts.   Guests fail and reboot often with Windows event 1001 Bugcheck stop 0x00000109.  We created a CPUID mask on these guests as per VMware KB 2060019.   That seems to prevent the failures as long as the guest stays on the same host.  If we vmotion or there is a HA or DRS execution the guests end up running on different hosts.  The bugcheck then starts happening again.  All hosts are the same hardware and BIOS settings are consistent.  We don't understand why the CPUID mask made via vcenter to edit the guest settings no longer works.  If we migrate the guests back to where they were - then all works OK again.  Anyone experience this condition ?
I will keep my fingers crossed for success.  Regarding certificates.... ours are expired  - we have just been ignoring the warning messages.   I was going to use the default VMware supplied certs... See more...
I will keep my fingers crossed for success.  Regarding certificates.... ours are expired  - we have just been ignoring the warning messages.   I was going to use the default VMware supplied certs when upgrading to 5.5.  Do you see any possible issues with that ?  Also, if I can ask a question on SSO site name.... we have only 1 vCenter now.  The actual Windows computer name is called vCenter.    What is your recommendation on a SSO site name. Should I use the fully qualified name of the server (example - vcenter.companyx.com or can I create something new and more definitive like vcenter-corp-usa ?  Thanks.
OK, but should the upgrade to 5.5 have issues and I need to fail back to vCenter 5.0 (system state backup) the hosts may already have had their agents updated. Wouldn't that case issues ?
I seem to recall reading that some or all hosts may not be connected in vCenter after the upgrade to 5.5.  Would that be a possible ? 
Planning to upgrade vCenter 5.0 to 5.5 in the near future.  Half of our hosts are  ESX 4.0 and the other half ESXi 5.0.  Will host agents need to be upgraded as part of the vCenter upgrade ?  If ... See more...
Planning to upgrade vCenter 5.0 to 5.5 in the near future.  Half of our hosts are  ESX 4.0 and the other half ESXi 5.0.  Will host agents need to be upgraded as part of the vCenter upgrade ?  If so, is that something we can get back to at a later date or have to do during the same update time window ?  We currently do not use Update Manager.  How easy is it to use Update Mgr. to do the agent updates ?  Or can they be done manually host by host ?  Thanks.
Question on snapshots.... We powered off a group of W2K8 guests and took snapshots.  A few days later our developers asked us to put the guests back to the point in time when the snapshots were ... See more...
Question on snapshots.... We powered off a group of W2K8 guests and took snapshots.  A few days later our developers asked us to put the guests back to the point in time when the snapshots were taken.   In snapshot manager we clicked on Go To, had the developers check to ensure their changes were not present.  All appeared to be good, but later we noticed the original snapshot entries still show in snapshot manager.  We were thinking the Go To option put the guest back to the state the guest was in at snap time and removed the snap file.  Apparently not.  We no longer need the snapshot file(s).  Can we just select Delete All,  which would leave the guests functioning the way they are now and also delete the snap file ?
Andre... 50-50 on the environment.  Half the hosts are ESX 4.0 U2 - the other half ESXi 5.0 U2.  All are managed by one vCenter.  We are planning to upgrade vCenter to 5.5, rebuild the 4.0 hosts... See more...
Andre... 50-50 on the environment.  Half the hosts are ESX 4.0 U2 - the other half ESXi 5.0 U2.  All are managed by one vCenter.  We are planning to upgrade vCenter to 5.5, rebuild the 4.0 hosts to 5.5 and then upgrade the 5.0 hosts to 5.5 in a few months.  It should be possible to build a test 5.0 host with an eval license that sees the NetApp and VNX array, then use vMotion to move the datastores.  Would there be any issues moving vmfs3 block 8 datastores to vmfs5 block 1 ?  You seem to be leaning towards vMotion and not using the data browser way.  vMotion would probably be faster and safer.
Yes, the block size is a problem.  The guest is currently VMFS3 block 8.  I was testing using storage vMotion to another VMFS datastore with block size 4, which was one of the few datstores with... See more...
Yes, the block size is a problem.  The guest is currently VMFS3 block 8.  I was testing using storage vMotion to another VMFS datastore with block size 4, which was one of the few datstores with enough free space.  It wasn't happy.  Ideally, I'd like to get it to a VMFS5 datastore.
We have ESXi 5 Enterprise Plus licensing.  The host we want to move to is ESXi 5.0.  Unfortunately, it does not see the NetApp array where the guest currently runs.
Read some of the other discussions on this topic .... I have a slight twist... can someone offer guidelines\options on the best way to relocate a very large VM from a NetApp array to a EMC VNX a... See more...
Read some of the other discussions on this topic .... I have a slight twist... can someone offer guidelines\options on the best way to relocate a very large VM from a NetApp array to a EMC VNX array.  The VM has 4 disks  -  2 of which are 1+ TB each and currently runs on a ESX 4.0 host.  We want to move the datastores and guest to a new ESXi 5 host.  Can be 2 steps if necessary.  Taking any downtime will be difficult and must be kept to a minimum.  I've used vMotion and Converter.  A vMotion test generated a block size complaint.  Converter is very slow and often times out.  If the guest can be powered off I can use the datastore browser to move the .VMDKs, then unregister\re-register the .vmx.  Slow maybe, but should be better than Converter.  Unfortunately the 4 disks are all separate datastores and therefore do not reside with the dtatastore containing the .vmx.  Can I still do this by modifying the .vmx to point to the new disk locations ?