rcporto's Accepted Solutions

Your processor and vCenter is compatible with the following EVC modes: Haswell, Ivy Bridge, Sandy Brigd, Westmere, Nehalem, Penryn and Merom. The reason why you're not able to enable the EVC m... See more...
Your processor and vCenter is compatible with the following EVC modes: Haswell, Ivy Bridge, Sandy Brigd, Westmere, Nehalem, Penryn and Merom. The reason why you're not able to enable the EVC mode may be due the fact you're with running virtual machine that are using CPU features not present on EVC mode you're selecting. Please, share some screenshots about the error and let us know if your virtual machines are powered on or off.
Robson, qual o SO da estação que você está utilizando para abrir o vSphere Client? E me fala também a versão do seu ESXi. Por último, tenta a solução informada nesse outro thread: Re: vSphere ... See more...
Robson, qual o SO da estação que você está utilizando para abrir o vSphere Client? E me fala também a versão do seu ESXi. Por último, tenta a solução informada nesse outro thread: Re: vSphere Client console only showing part of VM screen
That's because admin account do not have properly permissions, since that the Manage Agents permission is not assigned to any other role, including the Administrator role. So, if you want use the... See more...
That's because admin account do not have properly permissions, since that the Manage Agents permission is not assigned to any other role, including the Administrator role. So, if you want use the "admin" user, assign the Manage Agents permission, or create a new user just for End Point operations and assign the AgentManager role. See the following VMware KB article for additional information: Configuring the End Point Agent for Operating System Monitoring (EPAgent, End Point Operations Management Solution) in V…
Based on the build number, you're running vCenter 6.0.0b, and the full integration of Update Manager and vSphere Web Client is present only on vCenter 6.0 Update 1, see: vSphere Update Manager (V... See more...
Based on the build number, you're running vCenter 6.0.0b, and the full integration of Update Manager and vSphere Web Client is present only on vCenter 6.0 Update 1, see: vSphere Update Manager (VUM) 6.0.1 - Web Client Integration About the flat vSphere Client, when you receive the certificate warning message, just try install the certificate in your management station.
You can ignore that warning, or if you have DRS enabled and on Fully Automated mode, just put the host in Maintenance Mode and the placeholder virtual machines will move out the host.
Like I posted in my previous post in red, you cannot use vmkfstools.
vSphere NIC teaming can work without the need of configure link aggregation on physical switches, but you will need to select the correct load balance algorithm, that should be different than the... See more...
vSphere NIC teaming can work without the need of configure link aggregation on physical switches, but you will need to select the correct load balance algorithm, that should be different than the Route based on IP hash, which you already discovered that work only with link aggregation on physical switch side. And the LACP works only with vDS, even on version 6.5, see: Host requirements for link aggregation for ESXi and ESX (1001938) | VMware KB
There are many ways to run Sysprep when creating a VM from a template, here are some: 1) Run Sysprep on the "master" virtual machine, choose the Sysprep option to shutdown, and then convert th... See more...
There are many ways to run Sysprep when creating a VM from a template, here are some: 1) Run Sysprep on the "master" virtual machine, choose the Sysprep option to shutdown, and then convert the VM to a template, than when you create a virtual machine from that template, Sysprep will run automatically on the first boot; 2) Create a virtual machine from the template, log on Windows and run the Sysprep manually; 3) During the deploy from template Wizard, use the option Guest Customization, that will run Sysprep on virtual machine during the deployment.
1. will Physical Switch have MAC entry of multiple VM's residing on vSwtich mapped to a single physical port? Yes, on physical switch MAC address table you will see a lot of entries pointing to ... See more...
1. will Physical Switch have MAC entry of multiple VM's residing on vSwtich mapped to a single physical port? Yes, on physical switch MAC address table you will see a lot of entries pointing to the physical switch interface where do you have your ESXi host connected. Where each MAC entry can be a MAC address of a virtual machine or ESXi VMkernel interface.
Thiago, pelo jeito a placa foi detectada como VMBHA2, porém aparentemente está sendo utilizada como dispositivo pass-through por alguma VM, veja: 000:005:00.0    Address: 000:005:00.0    Seg... See more...
Thiago, pelo jeito a placa foi detectada como VMBHA2, porém aparentemente está sendo utilizada como dispositivo pass-through por alguma VM, veja: 000:005:00.0    Address: 000:005:00.0    Segment: 0x0000    Bus: 0x05    Slot: 0x00    Function: 0x00   VMkernel Name: vmhba2    Vendor Name: LSI Logic / Symbios Logic   Device Name: Dell 6Gbps SAS HBA Adapter    Configured Owner: VM Passthru    Current Owner: VM Passthru    Vendor ID: 0x1000    Device ID: 0x0072    SubVendor ID: 0x1028    SubDevice ID: 0x1f1c    Device Class: 0x0107    Device Class Name: Serial Attached SCSI controller    Programming Interface: 0x00    Revision ID: 0x03    Interrupt Line: 0x0f    IRQ: 15    Interrupt Vector: 0x32    PCI Pin: 0x09    Spawned Bus: 0x00    Flags: 0x0401    Module ID: 20    Module Name: pciPassthru    Chassis: 0    Physical Slot: 2    Slot Description: PCI2    Passthru Capable: true    Parent Device: PCI 0:0:3:0    Dependent Device: PCI 0:5:0:0    Reset Method: Function reset    FPT Sharable: true
If your old hosts will not be added to the new vCenter, you can let them managed by the old vCenter Essentials without problem.
A lot of reasons can cause the RPO violation error, mainly by the insufficient bandwidth, see: vSphere Replication RPO Violations
Although is recommend your upgrade your PSC and VCSA to Update 3, the vCenter 6 Update 2 supports hosts vSphere ESXi 6.0 Update 3 according with VMware Interop Matrices, see: VMware Product Inter... See more...
Although is recommend your upgrade your PSC and VCSA to Update 3, the vCenter 6 Update 2 supports hosts vSphere ESXi 6.0 Update 3 according with VMware Interop Matrices, see: VMware Product Interoperability Matrices
Upgrade to 6.5 will not make your old CPU be compatible with Broadwell CPU. What you need to do to make possible vMotion between your Broadwell and Sandy Bridge CPU, is configure the cluster EVC ... See more...
Upgrade to 6.5 will not make your old CPU be compatible with Broadwell CPU. What you need to do to make possible vMotion between your Broadwell and Sandy Bridge CPU, is configure the cluster EVC level to L4 Sandy Bridge.
You will need the same major version, see the vSphere Replication FAQ: Storage and Availability Technical Documents To replicate between vCenters, vSphere Replication requires the same major... See more...
You will need the same major version, see the vSphere Replication FAQ: Storage and Availability Technical Documents To replicate between vCenters, vSphere Replication requires the same major version (eg. 5.5.x > 5.5.x) of vCenter and vSphere Replication at both source and target. This is the only officially tested and supported configuration. Check the VMware Product Interoperability Matrix if you have any questions about matching vCenter and vSphere Replication versions.
That problem looks like a permission issue, try with the user local admin instead of the vsphere.local or Active Directory user.
Which version of vCenter you're running? Unless I'm missing something, that feature is available only with vCenter 6.5, see: What’s New in vSphere 6.5: Host & Resource Management and Operations -... See more...
Which version of vCenter you're running? Unless I'm missing something, that feature is available only with vCenter 6.5, see: What’s New in vSphere 6.5: Host & Resource Management and Operations - VMware vSphere Blog Content Library Content Library with vSphere 6.5 includes some very welcome usability improvements.  Administrators can now mount an ISO directly from the Content Library, apply a Guest OS Customization during VM deployment, and update existing templates.
From licensing perspective, the same license utilized by the 6.0 hosts and vCenter can be used in hosts and vCenter at version 6.5, you don't need to upgrade licenses. License upgrade is needed o... See more...
From licensing perspective, the same license utilized by the 6.0 hosts and vCenter can be used in hosts and vCenter at version 6.5, you don't need to upgrade licenses. License upgrade is needed only by major version upgrade, like 5.0 to 6.0. For additional details, see the following VMware KB article: License key requirements for new version of VMware products (2059926) | VMware KB
The XPVM works because it is connected to "VM Network" port group which is present on ESXi1 and ESXi2, and XPVM2 fails because it is connected to "VM Network2" port group which is present only on... See more...
The XPVM works because it is connected to "VM Network" port group which is present on ESXi1 and ESXi2, and XPVM2 fails because it is connected to "VM Network2" port group which is present only on ESXi1 and NOT on ESXi2. So, create the port group "VM Network2" on host ESXi2 and it should fix your problem.
Can you tell us the exact build number of your vCenter Server and the ESXi host that you just installed? If your host are running version 5.5 Update 3b or later, your vCenter must be running vers... See more...
Can you tell us the exact build number of your vCenter Server and the ESXi host that you just installed? If your host are running version 5.5 Update 3b or later, your vCenter must be running version 5.5 Update 3b too, see: ESXi 5.5 Update 3b and later hosts are not manageable after an upgrade (2140304) | VMware KB