markdjones82's Accepted Solutions

You can also choose force migrate and it will run the install.  I believe after that it will keep the existing VIBs that are installed, but I have not tested it out. Using the Force Migrate option might cause the upgraded host to not boot properly, to exhibit system instability, or to lose functionality. If you are upgrading a 5.0.x host, supported custom VIBs that are not included in the ESXi installer ISO are migrated. You do not need to to select the Force Migrate option. See Upgrading Hosts That Have Third-Party Custom VIBs. VMware vSphere 5.1 VMware KB: Upgrading to ESXi 5.x reports the warning: Host contains third-party VIB(s)

Here is the modified, i didn't test it connect-viserver vcenter get-datastore | % { $datastore = $_ $_ | Get-VM | Select Name,@{N="Datastore"; E={$datastore.Name}} } | Export-csv -notypeinformation "E:\location\VM_Report.csv" disconnect-viserver vcenter

I've never had any issues there, but I suppose from a security perspective there is more routed traffic if not on that subnet.  I've been doing this a long time and never considered it to be essential.  Either way is ok, but I've never ran it on the management network and personally don't feel the need to put it on there. What happens if you have multiple management subnets? IE in my case we have different management networks for some of our clusters and therefore VCenter could not be on both.  I am surprised they put that in the documentation.

I found it, I had to do the drop down for advanced search and select Drafts.  Looks like the default view is to only view active.  I'll leave this post up in case anyone else misses it like I did.

I would go with option C. VSAN i would agree has some silly requirements, but what they were aiming for is almost enterprise class SAN at a decent price by using SSD's for caching like arrays, but like you said if you are not needing high performance I would continue to go with a NAS NFS solution.

Wajeeh,   That is correct on both cases. YOu can just let SDRS place it for you (which is my suggestion), but i thought you wanted it to go to a specific datastore.  That being said you can re-enable SDRS for a VM under the SDRS edit settings if you ever do disable for a VM

Duncan,   If I am reading correctly you want to build a "fresh/new" install of Vcenter on 2012 while your existing one runs in parallel?  If so, the SSO will be an independant installation and you should select option 1 for a new installation. Then, when you get everything migrated to new VCenter you deocmmission the old one. As far as DR goes, yes it is recommended to have a separate SSO at the secondary site and then you choose option 2 and link it to the primary site.  5.5 U1 will replicate changes between the 2, but if one goes down you will still be able to function independently.  I would also recommend checking out linked mode for one pane of glass.

Try this.  I took the hotadd function from here: http://ict-freak.nl/2009/10/05/powercli-enabledisable-the-vm-hot-add-features/ I tested against 1 VM and it works ok.  it will loop and power all VM's off in parallel, then it will modify them all.  THen power them all on in parallel.  If you don't want parallel you can modify it. I would test in your lab or against 1-2 non prod VM's first. Same CSV colum VMNAME,MEM,CPU Function Enable-MemHotAdd($vm){     $vmview = Get-vm $vm | Get-View     $vmConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec     $extra = New-Object VMware.Vim.optionvalue     $extra.Key="mem.hotadd"     $extra.Value="true"     $vmConfigSpec.extraconfig += $extra     $vmview.ReconfigVM($vmConfigSpec) } Function Enable-vCpuHotAdd($vm){     $vmview = Get-vm $vm | Get-View     $vmConfigSpec = New-Object VMware.Vim.VirtualMachineConfigSpec     $extra = New-Object VMware.Vim.optionvalue     $extra.Key="vcpu.hotadd"     $extra.Value="true"     $vmConfigSpec.extraconfig += $extra     $vmview.ReconfigVM($vmConfigSpec) } $vmlist = Import-CSV C:\csvfile.csv foreach ($item in $vmlist) {     $vmname = $item.vmname     Stop-VM -VM $vmname -RunAsync     } foreach ($item in $vmlist) {     $vmname = $item.vmname     $cpu = $item.cpu     $mem = [int]$item.mem * 1024     Enable-MemHotAdd $vmname     Enable-vCpuHotAdd $vmname     Set-VM -VM $vmname -NumCpu $cpu -MemoryMB $mem -RunAsync -Confirm:$false } foreach ($item in $vmlist) {     $vmname = $item.vmname     Start-VM -VM $vmname -RunAsync     }

I don't believe there is a remove adapter for the vswitch.  What you can do is set the switch for the adapters you want it it to have as opposed to what to remove. IE, the below will set your virtual switch to have only Vmnic1 if you wanted to remove vmnic0. Get-VirtualSwitch -VMhost $VMHost -name "vSwitch0" | Set-VirtualSwitch -Nic "vmnic1" -Confirm:$false If you have multiple and need to keep say 2 but not 3 it would be:   Get-VirtualSwitch -VMHost $VMHost -name "vSwitch0" | Set-VirtualSwitch -Nic "vmnic0","vmnic1" -Confirm:$false

A couple options: 1.  You could setup everything but vcenter, export the DB for vcenter, and import into the new database server.  Shut down original vcenter and install Vcenter and point to imported DB. 2. You could build it up in parallel and get everything functioning.  Setup your clusters and permissions just the same.  Then, unregister and re register your hosts into the fixed Vcenter. If you have your hosts on a DVS you would need to migrate off the DVS to a standard switch before unregistering.  Also, you will not be able to use the existing Vcenter name due to conflicts.  Whatever name you build your Vcenter as is what you will need to keep it as. It is not recommended to rename Vcenter as it can cause issues with ADAM services etc.

I agree with Philly.  We prefer the 2 socket setup and scaling out, preferably blades as well.  If you are still doing rack mount I would highly suggest looking into blades. Some people do swear by the 4 socket, but you usually hit memory limits way before you will hit CPU limits.

Try this: (Get-EsxImageProfile -Name "Profile A").VibList     ---------- Example 1 ----------     C:\PS>Get-EsxImageProfile     Display all image profiles from depots and all image profiles the user created during this PowerCLI session:     ---------- Example 2 ----------     C:\PS>Get-EsxImageProfile -Name "ESX-5.0*"     Display all ESX 5.0 profiles:     ---------- Example 3 ----------     C:\PS>Get-EsxImageProfile | ? {$_.Vendor -ne "VMware"}     Display all image profiles from vendors other than VMware:     ---------- Example 4 ----------     C:\PS>(Get-EsxImageProfile -Name "Profile A").VibList     List all the VIB packages from a particular image profile:

In 5.1 you can export and import the configuration settings listed here, but you will be unable to do that in your case. VDS Export/Import with PowerCLI | VMware PowerCLI Blog - VMware Blogs It appears you are trying to do thsi in a 5.x environment though.  You will have to move all your hosts to a standard switch and then unregister/reregister at new Vcenter. The process is well documented on this blog posting: http://virtualkenneth.com/2012/10/19/migrate-to-new-vcenter-server-while-using-dvswitches/