New vCenter Server install fails - SSO

Similar Questions

• New vCenter Server Hardware

  Hello

  I go to the construction of a new vCenter server to my upgrade to vSphere 5.  The server vCenter 4.1 existing will be decommisioned and a new vCenter 5 installed.  I will keep the existing SQL database however.

  All settings are since I was on the existing DB?  I don't need to execute one of this batch of data migration tool file I do?

  If you use an existing DB, you all that you need to do is create your ODBC connection, test it and install vCenter ' help and existing DB.  VCenter all the setting is preserved.

  The existing DB is external to the vCenter Server Correct?

• Call 'HostDatastoreSystem.QueryVmfsDatastoreCreateOptions' of object 'datastoreSystem-281"on vCenter Server"example"failed.

  Dear friends;

  I increase my SAN storage, and I get this error:

  Call 'HostDatastoreSystem.QueryVmfsDatastoreCreateOptions' of object 'datastoreSystem-281"on vCenter Server"example"failed.

  Is - everyone gets this error?

  Thank you

  Saman Salehi

  I am not sure the MSA2000, but I do not think that it supports a narrowing of a LUN.

  VMware has its own type of partition (VMFS). If you sign such a LUN on a Windows host, it will be will the LUN and change the type of partition that is not what you want to do. In addition to this Windows cannot read a VMFS partition.

  What you could possibly do (I have never myself) is to create a new logic of at least 1.6 to unit number (best 1.8 to), then mount this LUN as LUN resized a Linux host and use "dd" to copy the contents of the disc (the first to 1.8) for the new LUN. After that, you may need to repair the partition table on the new LUN to make it work. However, as I said it's just a good. Maybe someone else has a better idea.

  André

• VCenter Server installed as a virtual machine within a ESXi servers it manages?

  Hi all.  I'm new in the world of VSphere... still in my evaluation period.

  I have only a single ESXi server running at the moment but plans to add a second later for high availability, vmotion, increase general capacity, etc.  They are / will be ESXi running on the internal storage and the virtual machines running on a shared SAN.

  Today, I installed VCenter Server 4 on a server at bottom of range/Office that I was carrying around running XP Pro x 64.

  As I was installing I read the guide installation and to my surprise, it seems to recommend that I have installed VCenter Server 4 as a virtual machine on my ESXi host.

  Now maybe I just spent too much time setting up my without new Lefthand requiring a 'witness' during the failover of one SAN to another... but I was under the impression that VCenter Server is not designed simply to host configuration, but is also designed to act as a 'witness' or to take account of quorum whenever a failure scenario occurred on one of my ESXi hosts.  I also noticed the VCenter Server features of a port "heartbeat", which I suppose one would use for the ESXi server heartbeat, but perhaps it is used for "connected mode" with other VCenter servers (I was intending to use only one since it is a small scale installation) I also felt that it would be useful enough to restore a damaged or shot ESXi host.

  So my question is, if my ESXi host dies and it is where I have VCenter Server installed, then high availability will be unable to work?  I guess there are going to be other issues with me unable to access VCenter Server while I have an ESXi host shot, too, as a greater difficulty to get the ESXi up?

  Maybe I'm wrong understand the purpose of the VCenter server... maybe it's not something that's necessary for HA, recovery, etc. and acts only as a configuration tool until something is wrong?  Or maybe I misunderstood the installation guide and they recommend only installing VCenter Server on an ESX box... they don't want this ESX box to be part of the group that manages the server?

  Finally, if indeed they recommend I install this on a ESXi host manages... would I ideally be install this for local storage on the server (where I installed ESXi) or on the SAN (where all my other virtual machines are installed)... or is it just personal preference?

  Thank you!!

  When you add hosts an active hemagglutinin vCenter cluster HA agent is installed on it.  This agent is what is actually the HA.  While necessary to add new hosts in a cluster and configure some specific parameters of vCenter vCenter's agents HA are self-sufficient and can handle HA failover so vCenter is offline.

  You must install the vCenter VM on SAN storage, so that he can use the vMotion, sVmotion, DRS, HA, functions etc. that require a SAN.

  -MattG

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

• PowerCLI Script to migrate virtual machines with the same network Source for the new vCenter Server.

  Hi all

  I checked a few posts on the migration to the new vCenter Server virtual machine. But I'm not very good with Powercli and need some help here.

  We have a new vCenter server where we migrate virtual machines from one source vCenter server. Here are two things that I don't know how to connect together to make sure that bwfore we turn on the virtual machine to the virtual machine is connected to its source network.

  Part 1 - this script works well but do not get any network on the vCenter destination.

  cluster = Get-Cluster "clusterA.

  $inventory = get-Cluster $cluster | Get - VM | Add-Member - MemberType ScriptProperty-name "VMXPath" - value {$this.extensiondata.config.files.vmpathname}-Passthru-Force | Select-Object Name ResourcePool, folder, VMXPath |

  $inventory | Export-Csv c:\file.csv

  $inventory = import-csv c:\file.csv

  $cluster = get-group 'b '.

  {foreach ($vm to $inventory)

  $ESXHost = get-Cluster $cluster | Get-VMHost | Select - 1 first

  New-VM - VMFilePath $vm. VMXPath - VMHost $ESXHost - location $vm. Folder - ResourcePool (Get-Cluster $cluster |) Get-ResourcePool $vm. ResourcePool)

  }

  Part 2 - I want to preserve the Portgroup macaddress and the Ip of the virtual computers and connect them to the new vCenter. How can I do this with the script below. Or how can I combine them together?

  $vm_list = get-Cluster-name "clustera | Get - VM test * | Name sort

  $information = {foreach ($vm to $vm_list)

  $network_adapter_information = get-NetworkAdapter - VM $vm

  $vm | Select Name,PowerState,ResourcePool,@{N="Path; E=       {$_. ExtensionData.Summary.Config.VmPathName}},@{N="NetworkAdapter '; E = {[string]: join (":", ($network_adapter_information |))} %{$_. {{(Nom + "," + _.NetworkName $}))}}, @{N = "MacAddress"; E = {[string]: join (",", ($network_adapter_information | % {$_.}))} MacAddress}))}}

  }

  Step 2

  # Unsubscribe virtual machines

  Remove-VM - VM $vm_list-RunAsync Verbose - confirm: $false

  Step 3

  $cluster = get-group 'b '.

  {foreach ($vm to $inventory)

  $ESXHost = get-Cluster $cluster | Get-VMHost | Select - 1 first

  New-VM - VMFilePath $vm. VMXPath - VMHost $ESXHost - location $vm. Folder - ResourcePool (Get-Cluster $cluster |) Get-ResourcePool $vm. ResourcePool)

  }

  # Save virtual machines

  foreach ($info in $information)

  {

  $vmxpath = $info. Path

  $resource_pool = $info. ResourcePool.Name

  New-VM - ResourcePool (ResourcePool-Get-name $resource_pool) VMFilePath - $vmxpath - RunAsync-Verbose | Out-Null

  }

  Step 4

  # Put the network cards

  foreach ($info in $inventory)

  {

  foreach ($network_information in ($info.NetworkAdapter - split ":"))))

  {

  $virtual_machine = $info | %{$_. Name}

  $network_adapter = ($network_information-split ",") [0]

  $network_vlan = ($network_information-split ",") [1]

  Get-VM-name $virtual_machine | Get-NetworkAdapter-name $network_adapter | Together-NetworkAdapter - NetworkName $network_vlan-Verbose-RunAsync-confirm: $false | Out-Null

  }

  }

  # Start the virtual machines

  foreach ($vm to $vm_list)

  {

  Start-VM - VM $vm. Name-RunAsync Verbose - confirm: $false | Out-Null}

  }

  Thanks in advance for any help.

  Hi all

  I made some changes to the script and it worked for me. We have added a host on the destination with all exchanges and storage mapped vCenter.

  $vm_list = get-Cluster-name 'Site B - b | Get - VM | Name sort

  $information = {foreach ($vm to $vm_list)

  $network_adapter_information = get-NetworkAdapter - VM $vm

  $vm | Select Name,PowerState,ResourcePool,@{N="Path; E=       {$_. ExtensionData.Summary.Config.VmPathName}},@{N="NetworkAdapter '; E = {[string]: join (":", ($network_adapter_information |))} %{$_. {{(Nom + "," + _.NetworkName $}))}}, @{N = "MacAddress"; E = {[string]: join (",", ($network_adapter_information | % {$_.}))} MacAddress}))}}

  }

  # Unsubscribe virtual machines

  Remove-VM - VM $vm_list-Verbose - confirm: $false

  $cluster = get-Cluster "Site A - clustera.

  {foreach ($vm to $information)

  $ESXHost = get-Cluster $cluster | Get-VMHost | Select - 1 first

  New-VM - VMFilePath $vm.path - VMHost $ESXHost - location $vm. Folder - ResourcePool (Get-Cluster $cluster |) Get-ResourcePool $vm. ResourcePool)

  }

  # Save virtual machines

  foreach ($info in $information)

  {

  $vmxpath = $info. Path

  $resource_pool = $info. ResourcePool

  New-VM - ResourcePool (ResourcePool-Get-name "test1") VMFilePath - $vmxpath - RunAsync-Verbose | Out-Null

  }

  # Put the network cards

  .

  foreach ($info in $information)

  {

  foreach ($network_information in ($info.NetworkAdapter - split ":"))))

  {

  $virtual_machine = $info | %{$_. Name}

  $network_adapter = ($network_information-split ",") [0]

  $network_vlan = ($network_information-split ",") [1]

  Get-VM-name $virtual_machine | Get-NetworkAdapter-name $network_adapter | Together-NetworkAdapter - NetworkName $network_vlan-Verbose - confirm: $false | Out-Null

  }

  }

  # Start the virtual machines

  foreach ($vm to $vm_list)

  {

  Start-VM - VM $vm. Name-RunAsync Verbose - confirm: $false | Out-Null

  }

  Hope this will help many of you.

• New Vcenter server and host add

  Hello, we are planning to create a new server Vcenter.  Had a bunch of weird issues with Vcenter.  Vcenter 5.1 on Windows running.  have not decided if we will use the VCenter, or create a new virtual machine from Windows to Vcenter again but I don't think that will count for my question.

  My plan is to turn off HA and DRS on the old server Vcenter, then remove a host from the old server Vcenter, and then add this host on the new Vcenter server.  Then just repeat the process for each host.

  My question is, should I turn off any virtual machine running on the hosts before removing the old server vcenter?

  If I remember correctly you have not, the virtual machine must remain in place and running, no connectivity should be lost and users should not not the difference.  We plan to do this off-peak hours, but there are always a couple of vm that are used 24/7.  It would be therefore rather not have to stop first.

  Thank you

  Hi defrogger

  Yes, it's the right way to migrate a new vCenter ESX Server.

  Disable HA/DRS and then disconnect the ESXi, vCenter server and plug them into the new vCenter.

  By disabling the DRS, you will lose the Resource Pools. So its maybe you assign only manual DRS.

  Another thing that many people forget are the options of the virtual machine on the cluster options. they have been set up again on the new cluster.

  BTW. There is a guide of vmware:

  VMware KB: Move a managed ESX ESXi host to a vCenter Server to a different Server vCenter

• New Mirage Management Server install fails

  I try to install on Server 2008 R2 5.3 Mirage and Management Server installation fails with errors below.

  Server tools VMware Mirage has stopped working. A problem caused the blocking of the program works correctly. Please close the program.

  Name of the failing application: Wanova.Server.Tools.exe, version: 5.3.0.31896, time: 0x54e4e316

  Name of the failed module: KERNELBASE.dll, version: 6.1.7601.23002, time stamp: 0x5507b734

  Exception code: 0xe0434f4d

  Offset: 0x000000000000adad

  ID of the process failed: 0 x %9

  Start time of application vulnerabilities: 0 x % 10

  The failing application path: %11

  Path of the failing module: 12%

  Report ID: 13%

  Product: VMware management server Mirage - unable to prepare VMware Mirage Database for updating.

  
  

  Later, MirageDB is removed from SQL 2012 R2. Same on Server R2 2012. Any ideas?
  

  Yes, the user was already part of the admin groups. In any case, using even install Setup, I was able to install Mirage 5.4 with no problems. Don't know which increased with 5.3.

• vCenter Server install Question

  Hello fellow professionals of computer science,

  My question is based on 1 single step in installing vCenter. The part of the installation that I have a question about is the destination directories. In this step, it gives you the option to use the default directory or change the directory where the server vCenter Server is installed. Then just below that is the ability to change the directory data for the vCenter Server server are installed too. My question is when he says data do you mean virtual machines? I ask because I have little space to work with the vCenter Server alone. If the data for the vCenter server means computer virtual vhd then I can change that to a SAN that has at least 5-6 to a value space.

  Hello

  The vCenter Server allocates any virtual machine inside the disks.

  This means installation vCenter only data. You point where the virtual machine is preserved when you create a new virtual machine (normally on storage)

• VCenter Server Appliance fails without VT in nested ESXi 5.1 support

  I am trying to run vCenter Server Appliance in a nested ESXi 5.1 64-bit environment.

  At the start of the vCenter Server Appliance, it fails with:

  This virtual machine is configured for 64-bit operating systems. However, the 64-bit mode is not possible.

  This host does not support VT for more information, see http://VMware.com/info?id=152 .

  My configuration is:

  Hardware Intel Serverboard S1200BTS

  Intel Xeon E3-1230 V2 3.30 GHZ CPU

  (This processor supports VT + EPT)

  BIOS Intel VT is enabled

  Intel VT for directed IO is enabled

  Latest version of the BIOS

  HW-ESXI 5.1 vhv.allow = "TRUE" is defined

  VM-ESXi 5.1 CPU/MMU virtualization - Intel VT + EPT active

  vCenter Server Appliance has been installed with the VMware-vCenter-Server-Appliance-5.1.0.5200-880472_OVF10.ova file.

  What I'm missing here?

  MNGZ wrote:

  Set vhv.enable = 'TRUE' in my nested ESXi 5.1 makes no difference.

  Did you put this in the .vmx file for your ESXi 5.1 VM?

• 5.1 ESXi host rest disconnected when it is connected to the new vCenter Server 6

  Hello

  I created a new version of vCenter Server 6.

  I have e vCenter Server 5.1 connect my 5.1 hosts.

  I want to connect hosts to the new vCenter and then upgrade to ESXi 6 guests.

  I disconnect hosts on the old vCenter.

  The I connect hosts to the new vCenter, and it happens with all the vm´s, etc..

  But it is disconnected.

  And it keeps beeing disconnected even when you try to connect again.

  If anyone has experienced this?

  Thank you

  Thomas

  Have you added these hosts in your new server vCenter along with their licenses?

  Otherwise, if please add host license in your vCenter license inventory and assign to those of your hosts and then try to re - connect.

• I can point my Lab Manager 4.0.2 to point to another new vCenter Server?

  Hi guys,.

  I have a client with a LM4.0.2 production and we are considering moving to one another new/a vCenter server.

  It is important to note that the new vCenter will NOT have the same DB or FULL of the old domain name. It's a completely different vCenter with other ESX hosts.

  Now the questions:

  Can I redirect my Lab Manager (VM) at the new vcenter without any problem?

  What of the ESX (resource) on the old vcenter?

  Is it possible to do this without downtime for laboratories? If this is not the case, how can I minimize downtime? cancel the deployment will be enough?

  Does anyone have this done successfully?

  Any comments would be much appreciated.

  Eyal

  etamir,

  There are some excellent discussions within this forum on the same topic.  I strongly suggest to read first, and I'll see if I can find an example.

  Before going further, data warehouses used in the new vCenter/ESX environment will be exactly the same as the current one?  If you want to keep all of your configurations, I need to know that the UUID of the LUN does not change during this process.

  Can I redirect my Lab Manager (VM) at the new vcenter without any problem?

  You can change the IP/domain FULL name vCenter in the settings section of the Lab Manager site... now on the problems that could result.

  You will need to remove anything from the GUI of Lab Manager that has to do with the current vCenter (unedploy, unprepare host esx, resource pools, configurations etc.).  There will be more on this in the dedicated thread

  What of the ESX (resource) on the old vcenter?

  ESX doesn't really matter, it's the data UUID store that matters.  ESX is just virtual machines.  Note: you'll want to throw all States/suspend points on the VMS where processors are different on the ESX hosts.

  > Is it possible to do this without downtime for laboratories?

  No, there will be a form any downtime.  Either that LM site will be useless (no resources with Betclic, consoles will does not work until the guests are prepared, etc.).

  > If not, how can I reduce downtime? cancel the deployment will be enough?

  Yes, to cancel the deployment of will help... but there will be some lag as you reconfigure Manager of laboratory to use the new vCenter.

  > Has anyone successfully done this?

  Yes.  I saw others to do this.

  Subjects in the sample: http://communities.vmware.com/message/1592762

  Kind regards

  Jon Hemming, b.SC., RHCT, VMware vExpert 2009
  http://Twitter.com/vJonHemming

  If your question or problem has been resolved, please click the "right answer".  If someone helped him, please click "useful answer.

• Displacement of the new vCenter Server (running on vDS) ESX hosts?

  Hi guys... as the title suggests... someone can guide me with how best to move the ESXi hosts on vDS linking a vCenter again vCenter?

  In addition, outside of losing performance stats, what are the other things I need to keep in mind?

  Thanks in advance.

  See you soon,.

  K

  Do you have a chance to see this KB

  VMware KB: Spend an ESX/ESXi host with vDS to a vCenter Server to another

  Thank you

  Avinash

• vCenter Server 5.1, SSO and Service of the inventory on a single server?

  It is said in articles vmware all 3 roles can be installed for small deployments on a server with enough hardware requirements (2 hearts and 10 GB of RAM and hard drive 100 GB recommended).

  Question is what is considered to be low?

  Can I install all 3 roles on a server for lets say 14 guests and about 200 virtual machines?

  If I have 3 vCenter servers I'd better install all 3 roles on each of the 3 servers. or have a SSO or SSO HA for all vCenter servers?

  The problem is that we want to separate the vCenter by area.

  A big thank you!

  Yes, you can install all 3 roles on onse Server. We installed it on a virtual machine with 8 GB of RAM, 100 GB HD and 4 CPU.

  For the decision on wheter to install all 3 roles on 3 vCenter servers, I recommend you to read the next page.

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

  If I should make the decision, I separate completely all 3 areas and thus install 3 with 3 roles vCenter servers. But this does not mean you have to do the same thing.

• The upgrade to vSphere + SQL Express to SQL 2005 + new vCenter Server

  Hello world

  It's the scénarion that I have today:

  A node just two HA/DRS cluster with vCenter 2.5 update 4 and two esx 3.5 update 4.

  The environment has increased enough to move from SQL Express to SQL 2005 standard. In the process, I want to upgrade the environment to vSphere and the vCenter move another box.

  I'm quite familiar with the process of vSphere upgrade but I donít know how to move the vCenter to another machine AND I do not know how to go from Express to the standard version of SQL in the process. (I have a SQL machine ready for use)

  I do not know how to handle all the changes here, I thought it would be nice to all move to the new machine and DB so that I could continue with the upgrade to vSphere, if this has meaning or not, I'm waiting for your ideas.

  I hope someone will give me some guidance on moving from SQL Express to SQL and how to move vCenter to another server (of course with a different server name and IP address)

  Thanks in advance for your support.

  I just did something very similar a few Sundays ago and it was really easy.  Refer to the section of the Upgrade Guide that talks about upgrading to vCenter on another Machine... (starts at p. 49).  We went from SQL 2003 32 bits on 32-bit Windows 2003 to SQL 2005 64-bit on Windows 2008 R2 64-bit.  Both are running as VMs - vCenter 2.5 is still there only as a license server - until I get all my hosts upgraded.

• vCenter Server install issues?

  We plan our migration of VI 3.5 to vSphere 4.  Our current vicenter server is running on Windows 2003 with a SQL 2000 database.

  I want to do the following and know if it is possible.

  1 virtualize our current viserver and wipe the hardware it is running on.

  2. install Windows 2008 R2 Enterprise x 64

  3. install Microsoft SQL Server 2005 x 64

  VCenter will work on Windows 2008 x 64?  I tried searching for this information, but for some reason any cannot arrive at this answer.

  Thank you

  Kris Turner

  Yes vCenter 4.0 is compatible with the 2008 x 64 according to the compatibility guide - http://www.vmware.com/pdf/vsphere4/r40/vsp_compatibility_matrix.pdf

  If you find this or any other answer useful please consider awarding points marking the answer correct or useful