• Presentation Name = Discussion on VMware Certification
• Topics:
  • Currently available certifications, tracks, and levels.
  • VCP5-DCV and VCAP5-DCA requirements
  • Exam Expirations
  • Details and advice  VCP5-DCV Delta Exam and Recertification
  • Recommendations on  preparing for the VCP5-DCV and VCAP5-DCA exams.
• Duration: about 45 minutes

Also at the event:

• A fellow vExpert – Kendrick Coleman – presents on vCloud Air API Usage
• Presentation by Nimble Storage
• Lunch, giveaways, and colleagues

Location and Registration:

• Kentucky Science Center – Downtown Louisville
• Registration and Details

The post Discussion on VMware Certification appeared first on New Age Technologies.

For those of you that choose to use the Official VMware VCAP5-DCA Cert Guide from the VMware Press to prepare for the VCAP5-DCA exams, be sure to purchase the Premium Edition, which includes online content that covers the blueprint for the VDCA550 exam.  The online materials include information on using the vSphere Web Client, new features in vSphere 5.5, items that covered in the VDCA550 blueprint (but not covered in the VDCA510 blueprint), and additional practice exams.

The post VCAP Exams on vSphere 5.1 Expiration appeared first on New Age Technologies.

Our main concern is if we deploy two VMs from a template or VM that already has a SID, then an issue may occur if we try to add both new VMs to the domain.  The following error may occur when adding the second VM.

To fix this in the second VM, you can use these steps:

1 – Open RUN and enter sysprep

2 – Right-click on sysprep and choose Run as Administrator

3 – In the System Preparation Tool Window, set the System Cleanup Action dropdown = Enter System Out of Box Experience (OOBE). check the Generalize box, and set the Shutdown Options to Reboot.

4 – SYSPREP will run the necessary action and restart Windows.

5 – As Windows reboots, it will prompt for new Settings.  Apply the appropriate settings for this VM.   Windows will now have a new SID.

6. – After Windows starts, you should be able to successfully add it to the AD domain.

To avoid this issue in the future, deploy a Windows VMs from a template where SYSPREP has been used to strip the SID and where Windows will prompt for new settings on the next boot.  To prepare the template, perform these steps:

• In a new VM, install Windows 2012 R2
• Install VMware Tools
• Install all Windows Updates
• Use Steps 1 to 3 from above, except on step 3, set the Shutdown Options = Shutdown (not restart)
• After Windows shutdown finishes, use the vSphere Client to right-click on the VM and choose Convert to Template

The post Manually Using SYSPREP in Windows 2012 VMs and Templates appeared first on New Age Technologies.

http://www.vladan.fr/how-to-reset-esxi-5-x-root-password-and-under-which-conditions/

But, it may not be supported.  The statement in the following KB article indicates that the only supported way to reset the root account password on an ESXi host is to reinstall ESXi.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1004659

The post Forgot ESXi Password? Here is a fix. appeared first on New Age Technologies.

• Based on IP hash – Use this only for Etherchannel (port channel).  If the uplinks on a standard virtual switch or distributed virtual switch connect to an Etherchannel, then set the NIC Teaming Load Balancing to IP Hash for each virtual port group that uses these uplinks.    This could also be used when implementing new features in vSphere 5.1 and 5.5 that allow LACP to be configured on the physical uplinks of a distributed virtual switch.
• Based on originating virtual port – This is the default.  It has traditionally been the best setting for most virtual port groups, whenever Etherchannel is not involved.  It is still the best setting in most cases when Ethernet is not involved for standard virtual port groups,  Load Based Teaming (LBT) is often preferred in this case for distributed port groups
• Based on source MAC hash – This is seldom used, but is preferred whenever you want to control the placement of VMs based on their MAC address assignments.
• Based on physical NIC load – This is also called Load Based Teaming (LBT).  It is a fairly new feature on dvSwitches and is typically preferred over port-based teaming, because the two perform identically, except that LBT includes intelligence to migrate virtual adapters from a busy uplink to a lesser active uplink.  In many cases, this is preferred over using Etherchannel to provide a scalable NIC Team that does not require special settings on the physical switch, so it is easy to manage.  However, Ethernet is still preferred in cases where the best resiliency, scalability, and performance is needed.
• Explicit Failover – Used in cases where the administrator prefers to manually balance the workload by placing some VMs and vmkernel virtual adapters on specific port groups that utilize a specific set of active ports.  A common example, is where the Management Network and vMotion are the placed on a virtual switch by themselves – often the Management Network is set to use vmnic0 as Active and vmnic1 as Standby and vice versa for the vMotion port.

The post Choosing the Best NIC Teaming Load Balancing Policy in vSphere appeared first on New Age Technologies.