tag:blogger.com,1999:blog-69534180738421571552024-03-05T15:41:14.396-05:00VMTraining BlogVMtraining delivers hundreds of VMware courses annually and our training and certifications are recognized worldwide.VMTraininghttp://www.blogger.com/profile/00394084944990405832noreply@blogger.comBlogger39125tag:blogger.com,1999:blog-6953418073842157155.post-54004477660647773672017-06-02T13:41:00.000-04:002017-06-02T13:42:06.133-04:00"No host data available" error in the Hardware StatusSo having upgraded our environment and several of our customers as well to vSphere 6.5, we realized that the Hardware Status button under the Monitor tab for the ESXi 6.5 hosts are showing "No host data available" for the sensors.<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgEDgAURvpJCA3sqZOa-PQJcpykrKKMnwF-nWETNVcMdpnqy4NrZAHixxhU9UEfT4VJCgPoYLJ9iOrXs0UBdfpdVuARVdGgfr8algyEHkjTY3FLGeGfkl5kN3_r_9iIkmhBRan5R8SwFeAH/s1600/2017-06-02_NoData.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="216" data-original-width="465" height="296" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgEDgAURvpJCA3sqZOa-PQJcpykrKKMnwF-nWETNVcMdpnqy4NrZAHixxhU9UEfT4VJCgPoYLJ9iOrXs0UBdfpdVuARVdGgfr8algyEHkjTY3FLGeGfkl5kN3_r_9iIkmhBRan5R8SwFeAH/s640/2017-06-02_NoData.jpg" width="640" /></a></div>
<br />
<br />
Well apparently this is a known issue as VMware has created KB 2148520 in relation to it.<br />
Apparently, after upgrade, there is a stale Service ID that needs to be removed.<br />
<br />
<h3>
Here are the steps from the KB. Below are my screenshots showing the actual steps:</h3>
<br />
This is a known issue affecting the vCenter Server 6.5. <br />
<div>
Currently, there is no resolution.</div>
<div>
To work around this issue, remove the stale serviceID:</div>
<ol>
<li>From a Web browser, connect to the vCenter Server Managed Object Browser (MOB) at:<br /><br /><span style="font-family: "courier new"; font-size: x-small;"><span style="font-size: small;">https://vcenter_FQDN.com/cm/mob</span></span><br />
<li>Login as the <span style="font-family: "courier new";">administrator@vsphere.local user</span>.
<li>Click <b>Search</b>.
<li>Edit the Value column to only have these lines:<br /><br /><span style="font-family: "courier new";"><searchCriteria></searchCriteria></span><br /><br />
<li>Click <b>Invoke Method</b>.
<li>Press Ctrl+F and search for <span style="font-family: "courier new"; font-size: x-small;">cis.vws.servicename</span>.
<li>Copy the <b>serviceID</b> string directly above <span style="font-family: "courier new"; font-size: x-small;">cis.vws.servicename</span>.<br /><br /><img border="0" height="76" hspace="0" src="https://kb.vmware.com/Platform/Publishing/images/2148520_Hardware_status.PNG" style="margin: 0px;" title="" width="640" /> <br />
<li>Exit this window.
<li>Click <b>UnregisterService</b>.
<li>Under the Value column, enter the string copied in step 7.
<li>Click <b>Invoke Method</b>.</li>
</li>
</li>
</li>
</li>
</li>
</li>
</li>
</li>
</li>
</li>
</ol>
<br />
<h3>
My Steps in pictures:</h3>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg2fbB_bvxzkOF6GmvzefHscHpsXEFuv5VP_6YKVYuCg8gbtEynqek1IrFwyqMdWvFo8FwW_CV46OPRGqNpzShxr0CzozerDaJ98nQ5DfYVWek1STbfQQ4YK6uW2IBZBGzXii9pwkTXs0hO/s1600/2017-06-02_MOBlogin.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="290" data-original-width="484" height="380" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEg2fbB_bvxzkOF6GmvzefHscHpsXEFuv5VP_6YKVYuCg8gbtEynqek1IrFwyqMdWvFo8FwW_CV46OPRGqNpzShxr0CzozerDaJ98nQ5DfYVWek1STbfQQ4YK6uW2IBZBGzXii9pwkTXs0hO/s640/2017-06-02_MOBlogin.jpg" width="640" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgUe_S03pEaDJTDDWYAyxXddhXkdt1-06nN_J-FrQoAu3fj1ZxGoCGN8XbtOiAWry8ktI9nvo8Il7FZd0c3fGJ_FE00cbeP8thYvVZxl2LwMT4JF2lAOfPvj2ZMl7fVrqa3K7fP2kSE6rpx/s1600/2017-06-02_Search.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="532" data-original-width="540" height="393" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgUe_S03pEaDJTDDWYAyxXddhXkdt1-06nN_J-FrQoAu3fj1ZxGoCGN8XbtOiAWry8ktI9nvo8Il7FZd0c3fGJ_FE00cbeP8thYvVZxl2LwMT4JF2lAOfPvj2ZMl7fVrqa3K7fP2kSE6rpx/s400/2017-06-02_Search.jpg" width="400" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjLhLMnl0ZYIUNLah0zxWwU7s0xsABLUNa6-Le4RbmtBrFPuGAQLEI5HlSYN6cmEbPAEtvXOgVTRCcFU7LAMy3-T6XiAdHGnatTRbpXt47_lN5Ct482RSJnY9XXm-EcBwZHeUirDZBH-9uz/s1600/2017-06-02_serviceIDfound.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="291" data-original-width="735" height="252" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjLhLMnl0ZYIUNLah0zxWwU7s0xsABLUNa6-Le4RbmtBrFPuGAQLEI5HlSYN6cmEbPAEtvXOgVTRCcFU7LAMy3-T6XiAdHGnatTRbpXt47_lN5Ct482RSJnY9XXm-EcBwZHeUirDZBH-9uz/s640/2017-06-02_serviceIDfound.jpg" width="640" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiRkFN6upGGizNGW2ROmi0Gtk0TLzgOKfUcBOZtJQmeYBTMnI86ktll9EkR3m-LK9-v6ouvyCwzxFmMEhRgS7K2nIyZH-fyS4AUtbmtvtwJJC_CCaDoUiy4Y7fsqYq1vEGYVVOjLAMo7jHm/s1600/2017-06-02_UnRegister.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="454" data-original-width="450" height="400" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiRkFN6upGGizNGW2ROmi0Gtk0TLzgOKfUcBOZtJQmeYBTMnI86ktll9EkR3m-LK9-v6ouvyCwzxFmMEhRgS7K2nIyZH-fyS4AUtbmtvtwJJC_CCaDoUiy4Y7fsqYq1vEGYVVOjLAMo7jHm/s400/2017-06-02_UnRegister.jpg" width="396" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidz4Uk9ZWmGETbUvn1wtuMuEv6znmxUAF7XDkq5S_bX8omxo9C1rFq_pyriMT28qFY0nD4W1xrH62zXa1NyCaFFND9FKQRYmFJkKBJwuraqtR1FFLd8izcfk3NCzbKd8zTTkO41XXBE4pf/s1600/2017-06-02_UnRegisterInvoke.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="413" data-original-width="591" height="444" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEidz4Uk9ZWmGETbUvn1wtuMuEv6znmxUAF7XDkq5S_bX8omxo9C1rFq_pyriMT28qFY0nD4W1xrH62zXa1NyCaFFND9FKQRYmFJkKBJwuraqtR1FFLd8izcfk3NCzbKd8zTTkO41XXBE4pf/s640/2017-06-02_UnRegisterInvoke.jpg" width="640" /></a></div>
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-REomDc5T277Bgni4P-gqnhXjPKP0OMF6U4IIi9OtKlRXnoevyxn4KPzN5aBpOVG-MxCe2ewHXChAjKFYR03JJF_J_wP99svcY-YBJBrvH5-YES8iTrlYfBQKyJC8dIDMdSpSQaFQoDxJ/s1600/2017-06-02_StatusShowingResults.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" data-original-height="408" data-original-width="655" height="398" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi-REomDc5T277Bgni4P-gqnhXjPKP0OMF6U4IIi9OtKlRXnoevyxn4KPzN5aBpOVG-MxCe2ewHXChAjKFYR03JJF_J_wP99svcY-YBJBrvH5-YES8iTrlYfBQKyJC8dIDMdSpSQaFQoDxJ/s640/2017-06-02_StatusShowingResults.jpg" width="640" /></a></div>
<br />
<h3>
The link for the KB Is here:</h3>
<a href="https://kb.vmware.com/kb/2148520" id="permalink-content" name="&lpos=content : 265" rel="bookmark">"No host data available" error in the Hardware Status tab after upgrading to vCenter Server 6.5</a> <br />
Let us know how this works for you.VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-38813943982739300552017-05-05T22:25:00.000-04:002017-06-02T13:43:11.394-04:00The Vitual SAN host cannot be moved to the destination cluster: destination cluster vim.ClusterComputeResource:domain-### is Virtual SAN disabledSo today while I was teaching class, a student created an interesting problem. We were doing a lab on DRS where they create a single Host Cluster for DRS and all add their hosts.<br />
<br />
Well, one student created his own cluster, apparently checked the box for VSAN cluster in the process, added his host to it, then realized he was supposed to be in the "shared" DRS Host Cluster.<br />
<br />
He deleted the cluster he had created, re-added his host to vCenter and when he tried to move his host into the DRS Cluster, he got the following error:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgITB4csXLIUcv8VLELWbZRdk3njIv_A4QsHvCkmcKxIO7fvJUZygmGVYVy2HudebGruBDz4_2Tz9evTSSBg4YvXUeiIdzYkUxNrovUPA3zNnGQ1VBSum9Hoa-ZYgxQ0eyriIp6FDSio6WE/s1600/VSAN+Cluster+error.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="138" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgITB4csXLIUcv8VLELWbZRdk3njIv_A4QsHvCkmcKxIO7fvJUZygmGVYVy2HudebGruBDz4_2Tz9evTSSBg4YvXUeiIdzYkUxNrovUPA3zNnGQ1VBSum9Hoa-ZYgxQ0eyriIp6FDSio6WE/s640/VSAN+Cluster+error.jpg" width="640" /></a></div>
<br />
It turns out there was a VSAN datastore created with no disks in it and, his host still had an affiliation with the VSAN Cluster that no longer existed.<br />
<br />
<h3>
To resolve the problem we did the following:</h3>
<br />
<h4>
Verification:</h4>
<ol>
<li>From Storage inventory view in vCenter, verify a VSAN datastore still exists.</li>
<li>If it does, Putty into the ESXi host or access it via its ESXi Shell & execute the command:<br /><span style="font-family: "courier new" , "courier" , monospace;">esxcli vsan cluster get</span></li>
<li>If results appear, proceed to the solution ...</li>
</ol>
<h4>
Solution:</h4>
<ol>
<li>From previous command line (SSH or ESXi Shell) to the affected host, execute the following command:<br /><span style="font-family: "courier new" , "courier" , monospace;">esxcli vsan cluster leave</span></li>
<li>Now add the host to the existing Host Cluster...</li>
</ol>
Both Verification and Solution steps together look like this:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj4nSv6OCNM0Vf41PuIfWn7jYqOesY7a7WAJ6wCmyGpIVHYBr7RCsOLNoxjfFIT-hfIksj8VZT2JGGIU0eNdsbrFQylsD9XgNPm_maGbt5_ZMlTwhej-EpkRop00YVlKk4d10zmKSMtkcf8/s1600/Remove+VSAN+from+Host+CLI.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="339" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj4nSv6OCNM0Vf41PuIfWn7jYqOesY7a7WAJ6wCmyGpIVHYBr7RCsOLNoxjfFIT-hfIksj8VZT2JGGIU0eNdsbrFQylsD9XgNPm_maGbt5_ZMlTwhej-EpkRop00YVlKk4d10zmKSMtkcf8/s640/Remove+VSAN+from+Host+CLI.jpg" width="640" /></a></div>
<br />VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-80915112289861952982017-04-26T13:39:00.000-04:002017-04-26T13:45:16.790-04:00vCenter Server Windows & VCSA 6.5.0d is Out!!Well that was fast... 5 days after the release of VCSA 6.5.0c, comes 6.5.0d for both Windows & Photon OS versions of vCenter.<br />
<br />
Primary reason is bug fix support for VSAN 6.6 that was just released.<br />
<br />
<h3>
<a href="https://www.blogger.com/null" name="whatsnew"></a>What's New</h3>
The vCenter Server 6.5.0d release includes new features and bug fixes related to vSAN 6.6. For more information, see the <a href="http://pubs.vmware.com/Release_Notes/en/vsan/66/vmware-virtual-san-66-release-notes.html" target="_blank">vSAN 6.6 Release Notes</a> and the <a href="http://pubs.vmware.com/vsphere-65/index.jsp?topic=%2Fcom.vmware.virtualsan_container.doc%2FGUID-BA963AF2-5D07-488E-939E-7DEAC01BC4A0.html" target="_blank">vSAN 6.6 documentation</a>.<br />
<br />
The new build is:<br />
Name: <span class="fileNameHolder">VMware-VCSA-all-6.5.0-5318154.iso </span> <br />
<span class="releaseDate label">Release Date</span>: 2017-04-18<br />
<span class="build label">Build Number</span>: 5318154<br />
<br />
The new patch is: <br />
<span class="key"><label><a href="http://kb.vmware.com/kb/2149221" target="_blank">VMware-vCenter-Server-Appliance-6.5.0.5500-5318154-patch-FP.iso</a></label></span><br />
<span class="key"><label><span class="key">Download Size:1626.4</span> MB</label></span><br />
<span class="key"><label></label></span><br />
<span class="key"><label>The simplest way to install the patch is to use the Update feature in the VAMI interface of the VCSA GUI.</label></span><br />
<span class="key"><label>Login to <span style="font-family: "courier new" , "courier" , monospace;"><strong>https://<VCSA-IP-or_FQDN>:5480</strong></span></label></span><br />
<span class="key"><label><strong>Click on Update</strong> on the left.</label></span><br />
<span class="key"><label></label></span><br />
<span class="key"><label>You can use the Settings button to setup Automatic Checking for Updates to VCSA.</label></span><br />
<span class="key"><label>You can manually check for updates by clicking the Check Updates button.</label></span><br />
<span class="key"><label>Once an update is displayed as in the following picture, you can install it.</label></span><br />
<span class="key"><label></label></span><br />
<span class="key"><label><br />
<strong>See also</strong>: <a href="http://blog.vmtraining.net/2017/04/vcsa-650c-is-out.html">http://blog.vmtraining.net/2017/04/vcsa-650c-is-out.html</a></label> </span>VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-17332745432764796472017-04-18T00:01:00.001-04:002017-04-18T00:01:16.859-04:00VCSA 6.5.0c is Out!VMware just released a new version and patch for their VCSA 6.5 vCenter Server Appliance.<br />
6.5.0c addresses the Apache BlazeDS security vulnerability.<br />
<br />
<h3>
Resolved Issues</h3>
<a href="https://www.blogger.com/null" id="XXXXXXX" name="XXXXXX"></a> <!--Dev PR:1XXXXXXXX Doc PR:XXXXXXX --> <strong></strong>VMware vCenter Server contains a remote code execution vulnerability due the use of BlazeDS to process AMF3 messages. This issue may be exploited to execute arbitrary code when deserializing an untrusted Java object. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the identifier CVE-2017-5641 to this issue. <br />
<br />
The new build is:<br />
Name: <span class="fileNameHolder">VMware-VCSA-all-6.5.0-5318112.iso </span> <br /><span class="releaseDate label">Release Date</span>: 2017-04-13<br /><span class="build label">Build Number</span>: 5318112 <br />
<br />
The new patch is: <br />
<span class="key"><label>VMware-vCenter-Server-Appliance-6.5.0.5400-5318112-patch-FP.iso</label></span><br />
<span class="key"><label><span class="key">Download Size:</span>1627.4 MB</label></span><br />
<span class="key"><label></label></span><br />
<span class="key"><label>The simplest way to install the patch is to use the Update feature in the VAMI interface of the VCSA GUI.</label></span><br />
<span class="key"><label>Login to <span style="font-family: "Courier New", Courier, monospace;"><strong>https://<VCSA-IP-or_FQDN>:5480</strong></span></label></span><br />
<span class="key"><label><strong>Click on Update</strong> on the left.</label></span><br />
<span class="key"><label></label></span><br />
<span class="key"><label>You can use the Settings button to setup Automatic Checking for Updates to VCSA.</label></span><br />
<span class="key"><label>You can manually check for updates by clicking the Check Updates button.</label></span><br />
<span class="key"><label>Once an update is displayed as in the following picture, you can install it.</label></span><br />
<span class="key"><label></label></span><br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhtE1nh7kLNaFEjZorfZNsv58S6jEWntejAo3PxDeuonYeH3tZzu2ksBjtPZnKWIAkSd7VblFZjqtDGx1uCe10TpodyFCgnK1XCeJHFHOj2931-gKc1RLvebi437T8bOhiwW32ZVi1ZKe6j/s1600/VCSA+Updates1.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="249" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhtE1nh7kLNaFEjZorfZNsv58S6jEWntejAo3PxDeuonYeH3tZzu2ksBjtPZnKWIAkSd7VblFZjqtDGx1uCe10TpodyFCgnK1XCeJHFHOj2931-gKc1RLvebi437T8bOhiwW32ZVi1ZKe6j/s640/VCSA+Updates1.jpg" width="640" /></a></div>
<span class="key"><label></label></span><br />
<span class="key"><label>The installation has a thermometer for completion status.</label></span><br />
<span class="key"><label>This particular update requires a reboot when done, which can also be done from inside the VAMI.</label></span><br />
<span class="key"><label></label></span><br />
<span class="key"><label>More information on the update is here in the <a href="http://pubs.vmware.com/Release_Notes/en/vsphere/65/vsphere-vcenter-server-650c-release-notes.html" target="_blank">Release Notes</a>.</label></span><br />
<br />
<span class="key"><label>If you prefer the command line method for installing VCSA patches, checkout <strong>KB 2149656:</strong></label></span><br />
<span class="key"><label><a href="https://kb.vmware.com/kb/2149656">https://kb.vmware.com/kb/2149656</a></label></span>VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-54302498323147525032017-04-07T15:34:00.001-04:002017-04-11T14:04:13.908-04:00Stop logging me out of the vSphere Web Client!!I know VMware has increase the default timeout value in vSphere 5.5 & higher to 120 minutes, but for me, slowly prying my cold dead fingers off the old .NET, C# Windows vSphere Client, it's not long enough ... so here's how to increase it.<br />
<br />
I'm pulling the basic information from KB 2040626. Click <a href="https://kb.vmware.com/kb/2040626" target="_blank">here</a>.<br />
<br />
<span style="background-color: white; color: #333333; font-family: "proxima_novaregular" , "helvetica neue" , "helvetica" , "arial" , sans-serif;"><span style="font-size: large;"><b>Increasing the VMware vSphere Web Client session timeout period</b></span></span><br />
<div>
<span itemprop="name" style="box-sizing: border-box;"><br /></span></div>
<div>
Changes need to be performed on the server/VM hosting vCenter Server.</div>
<div>
<br /></div>
<div>
File locations depending on version:</div>
<div>
<br /></div>
<div>
<span style="background-color: white; box-sizing: border-box; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px; font-weight: 700;"> vCenter Server 5.x</span><br />
<span style="background-color: white; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;"> Windows 2003 – </span><span style="background-color: white; box-sizing: border-box; color: #333333; font-family: "courier new"; font-size: 10pt;"><span style="box-sizing: border-box; font-size: 10pt;">%ALLUSERSPROFILE%\Application Data\VMware\vSphere Web Client</span></span><br />
<span style="background-color: white; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;"> Windows 2008/2012 – </span><span style="background-color: white; box-sizing: border-box; color: #333333; font-family: "courier new"; font-size: 10pt;"><span style="box-sizing: border-box; font-size: 10pt;">%ALLUSERSPROFILE%\VMware\vSphere Web Client</span><span style="box-sizing: border-box; font-size: 13px;"><br style="box-sizing: border-box;" /></span></span><span style="background-color: white; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;"> VMware vCenter Server Appliance </span><span style="background-color: white; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;">(VCSA) </span><span style="background-color: white; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;">– </span><span style="background-color: white; box-sizing: border-box; color: #333333; font-family: "courier new"; font-size: 10pt;"><span style="box-sizing: border-box; font-size: 10pt;">/var/lib/vmware/vsphere-client</span></span></div>
<div>
<span style="background-color: white; box-sizing: border-box; color: #333333; font-family: "courier new"; font-size: 10pt;"><span style="box-sizing: border-box; font-size: 13px;"><br style="box-sizing: border-box;" /></span></span><span style="background-color: white; box-sizing: border-box; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px; font-weight: 700;"> vCenter Server 6.x</span><br />
<span style="background-color: white; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;"> Windows 2008/2012 – </span><span style="background-color: white; box-sizing: border-box; color: #333333; font-family: "courier new"; font-size: 10pt;">C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client</span><span style="background-color: white; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;"><br /> VMware vCenter Server Appliance (VCSA) – </span><span style="background-color: white; box-sizing: border-box; color: #333333; font-family: "courier new"; font-size: 10pt;"><span style="box-sizing: border-box; font-size: 13px;">/etc/vmware/vsphere-client/</span></span></div>
<div>
<span style="background-color: white; box-sizing: border-box; color: #333333; font-family: "courier new"; font-size: 10pt;"><span style="box-sizing: border-box; font-size: 13px;"><br /></span></span></div>
<div>
<span style="background-color: white; box-sizing: border-box; color: #333333; font-family: inherit;"><span style="box-sizing: border-box;">Add this line to the file:</span></span></div>
<div>
<span style="background-color: white; box-sizing: border-box; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px; font-weight: 700;"> Note</span><span style="background-color: white; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;">:</span><span style="background-color: white; box-sizing: border-box; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px; font-weight: 700;"> </span><span style="background-color: white; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;">If the line already exists, verify that the line does not contain a hash (</span><span style="background-color: white; box-sizing: border-box; color: #333333; font-family: "courier new"; font-size: 10pt;">#</span><span style="background-color: white; color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;">).</span></div>
<div>
<span style="background-color: white; box-sizing: border-box; color: #333333; font-family: inherit;"><span style="box-sizing: border-box;"><br style="box-sizing: border-box; font-family: Arial, Helvetica, sans-serif, "Bitstream Vera Sans"; font-size: 12px;" /><span style="box-sizing: border-box; font-family: "courier new"; font-size: 10pt;"><span style="box-sizing: border-box; font-size: 10pt;"> session.timeout = </span></span><em style="box-sizing: border-box; font-family: Arial, Helvetica, sans-serif, "Bitstream Vera Sans"; font-size: 12px;"><span style="box-sizing: border-box; font-family: "courier new"; font-size: 10pt;"><span style="box-sizing: border-box; font-size: 10pt;">value</span><span style="box-sizing: border-box; font-size: 13px;"><br style="box-sizing: border-box;" /></span></span></em><span style="font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;"> where </span><em style="box-sizing: border-box; font-family: Arial, Helvetica, sans-serif, "Bitstream Vera Sans"; font-size: 12px;"><span style="box-sizing: border-box; font-family: "courier new"; font-size: 10pt;">value</span></em><span style="font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;"> is the timeout value in minutes.</span><br style="box-sizing: border-box; font-family: Arial, Helvetica, sans-serif, "Bitstream Vera Sans"; font-size: 12px;" /><br style="box-sizing: border-box; font-family: Arial, Helvetica, sans-serif, "Bitstream Vera Sans"; font-size: 12px;" /><span style="font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;"> For example, to set the timeout value to 300 minutes, add the line:</span><br style="box-sizing: border-box; font-family: Arial, Helvetica, sans-serif, "Bitstream Vera Sans"; font-size: 12px;" /><br style="box-sizing: border-box; font-family: Arial, Helvetica, sans-serif, "Bitstream Vera Sans"; font-size: 12px;" /><span style="box-sizing: border-box; font-family: "courier new"; font-size: 10pt;"><span style="box-sizing: border-box; font-size: 10pt;"> session.timeout = 300</span><span style="box-sizing: border-box; font-size: 13px;"><br style="box-sizing: border-box;" /></span></span><span style="box-sizing: border-box; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px; font-weight: 700;"> Note</span><span style="font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;">: To set the client to never time out, specify a negative value or 0.</span></span></span></div>
<div>
<span style="background-color: white; box-sizing: border-box; color: #333333; font-family: inherit;"><span style="box-sizing: border-box;"><br /></span></span></div>
<div>
<span style="background-color: white; box-sizing: border-box; color: #333333; font-family: inherit;"><span style="box-sizing: border-box;">Restart the vSphere Web Client Services: </span></span></div>
<div>
<span style="background-color: white; box-sizing: border-box;"><span style="box-sizing: border-box;"></span></span><br />
<ul style="box-sizing: border-box; font-stretch: normal; line-height: normal; margin-bottom: 0px; margin-top: 0px;"><span style="background-color: white; box-sizing: border-box;"><span style="box-sizing: border-box;">
<li style="color: #333333; font-family: Arial, Helvetica, sans-serif, "Bitstream Vera Sans";"><span style="font-size: x-small;">In</span> <b style="font-size: 12px;">Windows </b><span style="font-size: 12px;">operating systems, restart the VMware vSphere Web Client service.</span></li>
<li style="color: #333333; font-family: Arial, Helvetica, sans-serif, "Bitstream Vera Sans";"><span style="font-size: x-small;">In the</span> <b style="font-size: 12px;">VCSA </b><span style="font-size: 12px;">(vCenter Server Appliance), restart the </span><span style="box-sizing: border-box; font-family: "courier new"; font-size: 10pt;">vsphere-client</span><span style="font-size: 12px;"> service.</span></li>
</span></span></ul>
<span style="background-color: white; box-sizing: border-box;"><span style="box-sizing: border-box;">
<span style="color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans";"><span style="font-size: 12px;"><br /></span></span></span></span><br />
<blockquote class="tr_bq">
<span style="background-color: white; box-sizing: border-box;"><span style="box-sizing: border-box;"><b>Note</b><span style="color: #333333; font-family: "arial" , "helvetica" , sans-serif , "bitstream vera sans"; font-size: 12px;">: To restart the vSphere Web Client Service, run these commands:</span></span></span></blockquote>
<blockquote class="tr_bq">
<span style="font-size: small;"><span style="font-family: "arial" , "helvetica" , sans-serif; font-size: small;"><b>In the vCenter Server Appliance 5.x:</b></span><br /><span style="font-family: "courier new" , "courier" , monospace;">/etc/init.d/vsphere-client restart</span></span></blockquote>
</div>
<div>
<blockquote class="tr_bq">
<span style="font-family: "arial" , "helvetica" , sans-serif; font-size: small;"><b>In vCenter Server Appliance 6.x:</b></span><br />
<span style="font-family: "courier new" , "courier" , monospace; font-size: small;">service-control --stop vsphere-client<br />service-control --start vsphere-client</span></blockquote>
</div>
<div>
<br /></div>
<div>
<span style="background-color: white; box-sizing: border-box; color: #333333; font-family: inherit;"><span style="box-sizing: border-box;"><br /></span></span></div>
<div>
<span style="background-color: white; box-sizing: border-box; color: #333333; font-family: inherit;"><span style="box-sizing: border-box;"><a href="https://kb.vmware.com/kb/2040626" id="permalink-content" name="&lpos=content : 268" rel="bookmark" style="box-sizing: border-box; color: #3366cc; font-family: proxima_novaregular, "Helvetica Neue", Helvetica, Arial, sans-serif; font-size: 14px; text-decoration-line: none;">Increasing the VMware vSphere Web Client session timeout period</a></span></span></div>
VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-10415747939809126202017-04-05T20:50:00.002-04:002017-04-05T20:50:48.302-04:00vSphere Data Protection End-of-Life (VDP EOL) & Goodbye 3rd Party SwitchesWell, needing massive changes, VMware's vSphere Data Protection Appliance, even with the addition of the features from VDP Advanced, has proven no match for the plethora of backup Solutions currently on the market.<br />
<br />
As a result they have announced the following:<br />
<br />
<h3>
<span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;">vSphere Data Protection:
End of Life</span></h3>
<span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"><strong></strong></span><span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"><br />
VMware is discontinuing VMware vSphere Data Protection (VDP), a general purpose
backup product included with vSphere. VMware vSphere 6.5 is the last release
which includes the VDP product. </span><br />
<span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"></span><br />
<span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;">All existing VDP installations with active
Support and Subscription (SnS) will continue to be supported until their End of
General Support (EOGS) date. <a href="http://app.learn.vmware.com/e/er?mid=9030&eid=CVMW2000028297745&s=279193683&lid=10474&elqTrackId=061451f4cd5049678a048260a79b9d5a&elq=592ef675c4f240a19f661c3f2e9db7e2&elqaid=9030&elqat=1" target="_blank"><span style="color: #0095d3;">Learn more</span></a>. </span><br />
<span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"></span><br />
<span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"><span style="font-family: inherit;">Additionally, they have made this announcement about 3rd Party vSwitches:</span></span><br />
<span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"><span style="font-family: Times New Roman;"></span></span><br />
<h3>
<span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"><span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;">Notify Customers: Update on
vSphere 3rd Party vSwitch Support</span></span></h3>
<span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"><span style="font-family: Times New Roman;"><span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"></span></span></span><span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"><span style="font-family: Times New Roman;"><span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"><br />
VMware is discontinuing the third party virtual switch (vSwitch) program.
</span></span></span><br />
<span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"><span style="font-family: Times New Roman;"><span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;">VMware will continue to support the 3rd party virtual switch APIs, and the
enablement of a partner's use of these APIs up to the vSphere 6.5 Update 1 and
prior vSphere versions, as long as an active support and subscription services
contract exists. </span></span></span><br />
<span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"><span style="font-family: Times New Roman;"><span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"></span></span></span><br />
<span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;"><span style="font-family: Times New Roman;"><span style="color: #555555; font-family: "Arial",sans-serif; mso-ansi-language: EN-US; mso-bidi-language: AR-SA; mso-fareast-font-family: "Times New Roman"; mso-fareast-language: EN-US;">All vSphere releases and vSphere 6.5 Update 1 will no longer
have third party vSwitch APIs and third party vSwitches will no longer work. <a href="http://app.learn.vmware.com/e/er?mid=9030&eid=CVMW2000028297745&s=279193683&lid=10476&elqTrackId=0cad9c27b0aa41d1b13c7066e274bec7&elq=592ef675c4f240a19f661c3f2e9db7e2&elqaid=9030&elqat=1" target="_blank"><span style="color: #0095d3;">View these FAQs</span></a> to learn
more and encourage your customers to migrate to vSphere Distributed Switch
using our <a href="http://app.learn.vmware.com/e/er?mid=9030&eid=CVMW2000028297745&s=279193683&lid=10475&elqTrackId=3f9fecd8283842928993397e06882656&elq=592ef675c4f240a19f661c3f2e9db7e2&elqaid=9030&elqat=1" target="_blank"><span style="color: #0095d3;">free tool</span></a>.</span></span></span>VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-68913623946960120032017-03-26T14:37:00.003-04:002017-04-05T20:51:04.056-04:00New vSphere 6.0 Version Release this week!<h3>
VMware Releases vCenter Server 6.0 Update 3a </h3>
<br />
Here's What's New in this release:<br />
<br />
<h2>
<a href="https://www.blogger.com/null" name="whatsnew"></a>What's New</h2>
The <strong>vCenter Server 6.0 Update 3a</strong> release addresses an Apache Struts security vulnerability documented in the <a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-vcenter-server-60u3a-release-notes.html#resolvedissues">Resolved Issues</a> section listed here:<br />
<br />
<h2>
<a href="https://www.blogger.com/null" id="resolvedissues" name="resolvedissues"></a>Resolved Issues</h2>
<ul><!--Dev PR:1751103 Doc PR:1776712-->
<li><strong>Update to Apache Struts</strong><br /> Apache Struts is updated to version 2.3.32 to resolve CVE-2017-5638.</li>
</ul>
<br />
The rest of the detail can be found in the Release Notes: <a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-vcenter-server-60u3a-release-notes.html" target="_blank">Here</a><br />
<br />
===============================================================<br />
<br />
If you missed what <strong>vSphere 6.0 Update 3</strong> included here's the What's New from it:<br />
<br />
<h2>
<a href="https://www.blogger.com/null" name="whatsnew"></a>What's New</h2>
<ul>
<li><b>Support for Transport Layer Security (TLS) protocol</b>: Support for TLSv 1.0, TLSv 1.1, and TLSv 1.2 are enabled by default and configurable for vCenter Server 6.0 Update 3. <ul>
<li>VMware Syslog Collector on vCenter Server Appliance supports TLSv1.0 only.</li>
<li> To configure TLSv 1.0, TLSv 1.1and TLSv 1.2, see <a href="http://kb.vmware.com/kb/2148819">KB 2148819</a>. </li>
<li>For VMware products supported for TLSv1.0 disablement and the use of TLSv1.1, TLSv1.2, see <a href="http://kb.vmware.com/kb/2145796">KB 2145796</a>. </li>
<li>Download the TLS configuration script from the <a href="https://my.vmware.com/web/vmware/details?downloadGroup=VC60U3&productId=491&rPId=14487">Product Download</a> page </li>
<li>For known issues related to the TLS protocol, see <a href="http://kb.vmware.com/kb/2148819">KB 2148819</a>. </li>
</ul>
</li>
</ul>
<ul><!--Dev PR:1738996 Doc PR:1794973-->
<li><strong>External database support</strong>: vCenter Server now supports the Microsoft SQL Server 2012 Service Pack 3.</li>
<br /><!--Dev PR:1477940 Doc PR:1790632-->
<li><strong>Changes in command-line templates and strings</strong>: Updates to command-line interface templates and strings. For information about the changes in the CLI installer, see <a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vcsa-cmdline-installer-60u2-to-60u3-changelog.html">VMware vCenter Server Appliance 6.0 Update 3 CLI Installer Changelog</a>. For information about deploying and upgrading the vCenter Server Appliance, read the <a href="http://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/techpaper/vsphere-603-vcenter-server-appliance-cmdline-deploy-and-upgrade.pdf">Command-Line Deployment and Upgrade of the VMware vCenter Server Appliance</a>. </li>
<br />
<li><strong>Windows to Linux migration support</strong>: With installation and upgrade, migration from vCenter Server Windows 5.5.x to vCenter Server Appliance 6.0 Update 3 is supported. Read the <a href="http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.migration.doc%2FGUID-6B02B2DC-F0DB-4CA3-9944-6BED0CF4B78F.html" title="http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.migration.doc%2FGUID-6B02B2DC-F0DB-4CA3-9944-6BED0CF4B78F.html"><em>vSphere Migration</em></a> documentation for more information on migrating VMware vCenter Server to vCenter Server Appliance.</li>
<br /><!--Dev PR:1585029 Doc PR:1795557-->
<li><strong>Updates to time zones in the Linux guest operating system customization</strong>: vCenter Server Linux guest operating system customization supports latest time zones. For more information on time zone changes and daylight saving time (DST) changes in Linux guest operating systems, see the <a href="https://www.iana.org/time-zones">Time Zone Database</a> by Internet Assigned Numbers Authority (IANA).</li>
<br /><!--Dev PR:1585027 Doc PR:1795556-->
<li><strong>Updates to time zones in the Windows guest operating system customization</strong>: vCenter Server Windows guest operating systems customization supports the latest time zones. For more information on time zone changes and daylight saving time (DST) changes in Windows guest operating systems, see the <a href="https://support.microsoft.com/en-us/kb/3162835">Microsoft Knowledge Base article 3162835</a>.</li>
<br />
<li><strong>Platform Services Controller</strong>: Platform Services Controller of vCenter Server Appliance is installed with 4 GB of memory by default, for fresh install and while upgrading from 5.5.x to 6.0 Update 3.</li>
<br />
<li><strong>Transmission Control Protocol (TCP) over User Datagram Protocol (UDP) for Kerberos operations</strong>: For improved performance, use Transmission Control Protocol (TCP) over User Datagram Protocol (UDP) for Kerberos operations when it is a part of the Active Directory<strong>.</strong> To enable this feature, leave and join a domain for a minor update: <ol>
<li>Update your setup to 6.0 Update 3 </li>
<li>Leave and join a domain so that <tt>udp_preference_limit</tt> entry appears in<strong> <tt>/etc/krb5.conf</tt></strong></li>
</ol>
Note: It is applicable for vCenter Server Appliance only. The current setting may remain functional if no operation is performed.</li>
<li><strong>Resolved Issues</strong>: This release of vCenter Server 6.0 Update 3 addresses issues that are documented in the <a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-vcenter-server-60u3-release-notes.html#resolvedissues">Resolved Issues</a> section. </li>
</ul>
The rest of the detail can be found in the Release Notes: <a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-vcenter-server-60u3-release-notes.html" target="_blank">Here</a> <br />
<br />
Please comment on adoption of these updates...VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-28178085341498578952017-03-17T00:34:00.001-04:002017-03-26T14:38:47.936-04:00NEW VC, vSphere Client & VDP Version Releases this week from VMware!!Well, not only has this week seen the belated by one month Patch Tuesday by Microsoft, VMware followed suit with two releases themselves...<br />
<br />
<h3>
VMware vCenter Server Release 6.5b</h3>
<strong>Updated on: 14 March 2017</strong><br />
vCenter Server 6.5.0b | 14 MARCH 2017 | ISO Build 5178943<br />
vCenter Server Appliance 6.5.0b | 14 MARCH 2017 | ISO Build 5178943<br />
vCenter Server 6.5.0b on Windows | 14 MARCH 2017 | ISO Build 5178943<br />
<br />
<a href="http://pubs.vmware.com/Release_Notes/en/vsphere/65/vsphere-vcenter-server-650b-release-notes.html">http://pubs.vmware.com/Release_Notes/en/vsphere/65/vsphere-vcenter-server-650b-release-notes.html</a><br />
<br />
You can use the link to see everything, but here's What's New:<br />
This release of vCenter Server 6.5.0b delivers a number of bug fixes that have been documented in the <a href="http://pubs.vmware.com/Release_Notes/en/vsphere/65/vsphere-vcenter-server-650b-release-notes.html#resolvedissues">Resolved Issues</a> section.<br />
<ul><!--Dev PR:1784936 Doc PR:1820323-->
<li><strong>Updates to time zones in the Linux Guest Operating System customization</strong>. vCenter Server Linux guest operating system customization supports latest time zones. For more information on time zone changes and daylight saving time (DST) changes in Linux guest operating systems, see the <a href="https://www.iana.org/time-zones">Time Zone Database</a> by Internet Assigned Numbers Authority (IANA).</li>
<!--Dev PR:1784939 Doc PR:1820324-->
<li><strong>Updates to time zones in the Windows Guest Operating System customization</strong>. vCenter Server Windows guest operating systems customization supports the latest time zones. For more information on time zone changes and daylight saving time (DST) changes in Windows guest operating systems, see the <a href="https://support.microsoft.com/en-us/kb/3162835">Microsoft Knowledge Base article 3162835</a>.</li>
<!--Dev PR:1794055 Doc PR:None, post-release addition-->
<li><strong>Updates to JRE package.</strong> The Oracle (Sun) JRE package is updated to version 1.8.0_121 to support Turkish timezone.</li>
<li><strong>Additional functionality to the vSphere Client</strong>. This release delivers additional functionality to the HTML5-based vSphere Client. For more information, see <a href="http://pubs.vmware.com/Release_Notes/en/vsphere/65/vsphere-client-65-html5-functionality-support.html" target="_blank"> Functionality Updates for the vSphere Client</a>.</li>
</ul>
Here's more detail on the Updates to the vSphere Sphere Client in VC 6.5b:<br />
<br />
<h4>
First vSphere Client (HTML5) update debuts in VC 6.5b</h4>
<br />
<a href="https://blogs.vmware.com/vsphere/2017/03/first-vsphere-client-html5-update-vsphere-6-5-b.html">https://blogs.vmware.com/vsphere/2017/03/first-vsphere-client-html5-update-vsphere-6-5-b.html</a><br />
<br />
<h2>
New Features – Huge Jump</h2>
The online documentation for vSphere 6.5.0b is the best source for detailed documentation on what functionality is now available (<a href="http://pubs.vmware.com/Release_Notes/en/vsphere/65/vsphere-client-65-html5-functionality-support.html" name="&lpos=apps_scodevmw : 21">http://pubs.vmware.com/Release_Notes/en/vsphere/65/vsphere-client-65-html5-functionality-support.html</a>), but for comparison sake, the bits are just after Fling v3.2, plus a few minor things. The only notable addition beyond v3.2 is the “Accept License” page on OVF deploy, which we specifically pushed into this patch to enable OVF deploy.<br />
This is the list of some of the additional functionality included. Note, some of these features are presented in a partially complete manner. For example, OVF deploy in 6.5.0b will only support URL deployment (no local file). The plan is to fill out all of these features, but the more feedback we get from you regarding what is most important will help us deliver faster.<br />
<ul>
<li>OVF Deploy</li>
<li>Deploy VM from Content Library</li>
<li>Drag and Drop</li>
<li>VM conversion to/from templates</li>
<li>Actions on multiple VMs</li>
<li>Register VMs</li>
<li>SDRS management</li>
<li>Dashboard</li>
<li>Advanced network operations – Distribute switch, Port group creation</li>
<li>Datastore create, mount and unmount</li>
<li>Storage overview</li>
<li>Host configuration (PCI Passthrough)</li>
<li>Host profiles compliance monitoring</li>
<li>Roles and permissions</li>
<li>Create Tags and categories</li>
</ul>
Some of these flows may have had minor tweaks to make them easier to use and learn. If you have feedback about any of the new behavior, or missing portions of features, of course let us know using the integrated feedback tool by clicking on the smiley face in the upper righthand corner.<br />
<br />
<h3>
vSphere Data Protection Release 6.1.4 (VDP)</h3>
<br />
<a href="http://pubs.vmware.com/Release_Notes/en/vdp/61/data-protection-614-release-notes.html#fixedproblems">http://pubs.vmware.com/Release_Notes/en/vdp/61/data-protection-614-release-notes.html#fixedproblems</a><br />
<br />
List of fixed problems:<br />
<h2>
Fixed Problems</h2>
The following table lists the problems that have been fixed in this release of vSphere Data Protection:<br />
<table border="1" style="width: 80%px;"><tbody>
<tr><th align="left" height="50" width="120">Defect Number</th><th align="left" height="50">Description</th></tr>
<tr><td>265470</td><td>When you perform an FLR, and you browse for a virtual machine, the vSphere Data Protection GUI displays a misleading error.</td></tr>
<tr><td>268134</td><td>A replication recovery job that runs on a target vSphere Data Protection appliance publishes the task by specifying the source server as unknown.</td></tr>
<tr><td rowspan="6">274652</td><td height="26">Tivoli Java Collections Library is vulnerable that enables exploitation of port 7778 by running a command on a remote client.</td></tr>
<tr><td>Fix common vulnerabilities and exposures (CVEs) that are found in third-party libraries by updating vSphere Data Protection appliance with Avamar OS rollup version Q4 2016.</td></tr>
<tr><td>On vSphere Data Protection appliance, update the Java runtime binaries version to 8u121.</td></tr>
<tr><td>Provide support for vCenter Server 6.0 U3.</td></tr>
<tr><td>On vSphere Data Protection appliance, enable TLS 1.2.</td></tr>
<tr><td>Fix the error, System accounting is not in use: System accounting not found in /etc/cron.d/sysstat.</td></tr>
</tbody></table>
VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-18209556393445289362017-03-10T00:15:00.004-05:002017-04-11T00:03:23.605-04:00Failed to Deploy OVF package<h3>
Failed to deploy package: File ds:///vmfs/volumes/UUID/_deviceImage-0.iso was not found</h3>
<br />
While working on setup for a Custom version of our Exchange 2013/2016 Ultimate Bootcamp today, I came across a problem which is not new, but was new to me.<br />
<br />
A colleague had saved some VMs to OVA format for deployment in a Master vApp. As I went to deploy them, I received the following error message:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBMr38zgSCLzzHXUbk2_Vom0Bc7QIS5TXnl46os-JeRP98L5VQUWJLSXQLNL_SITCoIdL1QLdKCzdJhvi8LiA3ipzhNXKWO18-xl5fKrxWo6OHp5bD5mJESfX8F1OcQSvVBxqhtcNSbZJ0/s1600/BadOVA.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="161" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgBMr38zgSCLzzHXUbk2_Vom0Bc7QIS5TXnl46os-JeRP98L5VQUWJLSXQLNL_SITCoIdL1QLdKCzdJhvi8LiA3ipzhNXKWO18-xl5fKrxWo6OHp5bD5mJESfX8F1OcQSvVBxqhtcNSbZJ0/s640/BadOVA.jpg" width="640" /></a></div>
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
After doing some research, I came across a couple of articles. Neither gave me what I needed, but through combining bits and experimenting, I found a solution.<br />
<br />
<h4>
PROBLEM: </h4>
The VMs had ISOs attached to their CD-ROMs when the were exported to OVA format.<br />
The OVF file inside the OVA package has information about the attached ISO.<br />
<h4>
</h4>
<h4>
SOLUTION:</h4>
<ol>
<li>Uncompressed the OVA file using either TAR on Linux/ESXi or <em>7-Zip on Windows</em>.</li>
<li>Located the OVF file which contains the configuration of the VM to deploy. <blockquote dir="ltr" style="margin-right: 0px;">
<div class="separator" style="clear: both; text-align: center;">
<br /></div>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhb6eLm77pam-Ehqgt_vaH6Nf57trWndY4ITOkLPep2hVIKojakyQggO5lbXvYfF7ODAJzGteYMMtD8jwW1TDpxHNYhv9PtgFzppN-JifspElkqYWij47SjiBpCT_RS6cJWkfMKzkyY_ms0/s1600/OVA+packaged+files.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhb6eLm77pam-Ehqgt_vaH6Nf57trWndY4ITOkLPep2hVIKojakyQggO5lbXvYfF7ODAJzGteYMMtD8jwW1TDpxHNYhv9PtgFzppN-JifspElkqYWij47SjiBpCT_RS6cJWkfMKzkyY_ms0/s1600/OVA+packaged+files.jpg" /></a><br />
<div>
</div>
</blockquote>
</li>
<li>In the <span style="font-family: "courier new" , "courier" , monospace;">VMname.OVF</span> file, I searched for “<strong>vmware.cdrom.iso</strong>”</li>
<li>I replaced <strong>vmware.cdrom.iso </strong>with <strong>vmware.cdrom.remotepassthrough</strong> and saved the file. <br /><br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgIJvaDZyyRqaOTMideM-znMIcgLojz5DpiJLFrwXnMcIEhsDOq4mNEmSMeYAP-Xz_PECDEn8EqnmcZGXI3sAUZVbCQ5b1j8mfdK03DfAvZlmvsDJGLkXqqelKoTCkNF494ZTyvXq1cYn_6/s1600/CDROM+ISO+in+OVF+orig.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="112" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgIJvaDZyyRqaOTMideM-znMIcgLojz5DpiJLFrwXnMcIEhsDOq4mNEmSMeYAP-Xz_PECDEn8EqnmcZGXI3sAUZVbCQ5b1j8mfdK03DfAvZlmvsDJGLkXqqelKoTCkNF494ZTyvXq1cYn_6/s640/CDROM+ISO+in+OVF+orig.jpg" width="640" /></a><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiteQtWCa9795VTOb6z_6sxWaUAV89RH7x0uXpwBiESGs3UhZqatzo497Ole_aqRgI9i7NppDlVJTBylxDOvZPVIOaLA1klydwttQKOFPjkYq_ndtzNgdTCrHvQinv2KLJNVfHflqmvU01R/s1600/CDROM+ISO+in+OVF+replaced.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="57" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiteQtWCa9795VTOb6z_6sxWaUAV89RH7x0uXpwBiESGs3UhZqatzo497Ole_aqRgI9i7NppDlVJTBylxDOvZPVIOaLA1klydwttQKOFPjkYq_ndtzNgdTCrHvQinv2KLJNVfHflqmvU01R/s640/CDROM+ISO+in+OVF+replaced.jpg" width="640" /></a><div>
</div>
</li>
<li>Calculated a new SHA1 hash for the updated <span style="font-family: "courier new";">VMname.OVF</span> file using HashMyFiles (Download here: <a href="http://www.nirsoft.net/utils/hash_my_files.html">http://www.nirsoft.net/utils/hash_my_files.html</a>)<br /><br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh5wSlVQqff0KtXS5gQG9ZyH9V2Y3zbFhqsx-yYy1i6Euc6jh0SpmcTcLQdIeptl8wK7kg1NiiwEhuYD3TQujSL3PIu6AEw1FDaqciM49Jh5SOiaytY7qH6873uF9ugAlDlMmyhmNz1sTGa/s1600/OVF+file+hash.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="172" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh5wSlVQqff0KtXS5gQG9ZyH9V2Y3zbFhqsx-yYy1i6Euc6jh0SpmcTcLQdIeptl8wK7kg1NiiwEhuYD3TQujSL3PIu6AEw1FDaqciM49Jh5SOiaytY7qH6873uF9ugAlDlMmyhmNz1sTGa/s640/OVF+file+hash.jpg" width="640" /></a></li>
<li>Edited the <span style="font-family: "courier new" , "courier" , monospace;">VMname.mf</span> file and replaced the SHA1 hash for the <span style="font-family: "courier new" , "courier" , monospace;">VMname.ovf</span> with the new one & saved the file.<br /><br /> <img border="0" height="50" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjavfBC7eFllOflTPrOcKQcQBcX6gzQnF9HBAkR4ZtI56oDZHqruyEy146rc2QDpVj-7f0hKefj9KA2_o27XGUEiU5mckC5UBIGFpOhpMCk_9I-nvhBnsw-OqvXRWsr_0_J_7jW91ZLbi84/s640/MF+old+hash.jpg" width="640" /><br /><a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi6-6x9hevSGddoII-fIKdZl7pwEEco-7YW4d0_0TahSv_T1le6Zu8E5mTIryKjoXBMTUOs_7rSed4iYFKAkzHRQJLrOL9QCR3K_sNsVDY-MjQE9fMq_fhJHHa7OsyjlplF74HSiCDtYyhz/s1600/MF+replaced+hash.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="48" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEi6-6x9hevSGddoII-fIKdZl7pwEEco-7YW4d0_0TahSv_T1le6Zu8E5mTIryKjoXBMTUOs_7rSed4iYFKAkzHRQJLrOL9QCR3K_sNsVDY-MjQE9fMq_fhJHHa7OsyjlplF74HSiCDtYyhz/s640/MF+replaced+hash.jpg" width="640" /></a> <div>
</div>
</li>
<li>Deployed a new VM using the OVF file.</li>
<li>Optionally you could repackage the OVF to an OVA using either OVFTool or TAR in a host.<br /><span style="font-family: "courier new" , "courier" , monospace;"><span class="crayon-e">tar </span><span class="crayon-e">cvf </span><span class="crayon-v">VMname</span><span class="crayon-e">.ova</span><span class="crayon-h"> </span><span class="crayon-v">VMname</span><span class="crayon-e">.ovf</span></span><span style="font-family: "courier new" , "courier" , monospace;"><br /><span class="crayon-e">tar </span><span class="crayon-e">uvf </span><span class="crayon-v">VMname</span><span class="crayon-e">.ova</span><span class="crayon-h"> </span><span class="crayon-o">*</span><span class="crayon-e">.mf</span><span class="crayon-h"> </span><span class="crayon-o">*</span><span class="crayon-e">.vmdk</span></span>
</li>
</ol>
<br />
Another option would be to simply delete the MF file. vSphere deployment of the OVF then wouldn't do a hash check at all and the install will complete as expected. Your choice!VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-24225888229978006332017-03-01T00:00:00.000-05:002017-03-01T00:00:35.973-05:00Restart VCSA 6.5 Install at Stage 2<h4>
Problem: For whatever reason, your install of, migration to or upgrade to VCSA 6.5 stops after completing Stage 1</h4>
<br />
While teaching class today, I had a student ask if they could restart their VCSA 6.5 installation after Stage 1. I wasn't sure, so I did some research.<br />
<br />
It turns out you can restart at Stage 2. <br />
<br />
All you need to do is access the new VCSA VM created in Stage 1 with:<br />
<span style="font-family: "Courier New", Courier, monospace;"> https://<VCSA_IP_or_FQDN>:5480</span> <br />
which will redirect to:<br />
<span style="font-family: "Courier New", Courier, monospace;"> https://<VCSA_IP_or_FQDN:5480/#/installer?locale=en</span><br />
<br />
You will then be presented with the following screen. Simply click on the appropriate choice to continue...<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKHP9-p4m2GfVMTSuq6qo7SE6aBBpAC3XSgz9BJ4fBu_9ljzWYaebZBljFjKp2Df5TKy6q_8M3diUVRS1C3_dSGydgZfK8j-88hJmhPuSdXveOE3sUHll-atQiMAEQted11fJG7nWi2cNx/s1600/VCSA+Stage+2.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="593" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjKHP9-p4m2GfVMTSuq6qo7SE6aBBpAC3XSgz9BJ4fBu_9ljzWYaebZBljFjKp2Df5TKy6q_8M3diUVRS1C3_dSGydgZfK8j-88hJmhPuSdXveOE3sUHll-atQiMAEQted11fJG7nWi2cNx/s640/VCSA+Stage+2.jpg" width="640" /></a></div>
<br />
One reason a Stage 2 pre-upgrade check error may occur is if your source vCenter manages the cluster where you're deploying the new vCenter Server Appliance 6.5, you should specify an ESXi host on the following screen: <br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEij6M3zP7A4yfaJh3dQcthUKXHfil-TeRNZ2l6dM0dc3xzjHlu1v7UJdclkYh05RLMwcgq9xpoQtDnAn9SZ_N8-C5wBpos5uqmENX9H-mp9-gg8ydlESYnSNFRk5ja1RWTbV0rIXMJavp03/s1600/Stage+2+pre-upgrade+check.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="522" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEij6M3zP7A4yfaJh3dQcthUKXHfil-TeRNZ2l6dM0dc3xzjHlu1v7UJdclkYh05RLMwcgq9xpoQtDnAn9SZ_N8-C5wBpos5uqmENX9H-mp9-gg8ydlESYnSNFRk5ja1RWTbV0rIXMJavp03/s640/Stage+2+pre-upgrade+check.jpg" width="640" /></a></div>
VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-32507564418393423582017-02-25T16:49:00.002-05:002017-02-25T17:38:14.523-05:00VMware ESXi 6.0 Update 3 Released 2/24/2017!<a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u3-release-notes.html" target="_blank">vSphere 6.0 Update 3 Release Note here...</a><br />
<br />
The major items are the Build number, What's New and Resolved Items.<br />
<br />
<strong>ESXi 6.0 Update 3 | 24 FEB 2017 | ISO Build 5050593</strong><br />
<strong></strong><br />
<h2>
<a href="https://www.blogger.com/null" name="whatsnew"></a>What's New</h2>
<ul>
<li><strong>Updated ESXi Host Client</strong>: VMware ESXi 6.0 Update 3 includes an updated version of the ESXi Host Client, version 1.14.0. The updated Host Client includes bug fixes and brings it much closer to the functionality provided by the vSphere Client. If you updated the Host Client through ESXi 6.0 patch releases, then install version 1.14.0 provided with ESXi 6.0 U3. In addition, new versions of the Host Client continue to be released through the <a href="https://labs.vmware.com/flings/esxi-embedded-host-client" target="_blank">VMware Labs Flings website</a>. However, these Fling releases are not officially supported and not recommended for production environments.</li>
<li><strong>Support for TLS</strong>: Support for TLSv1.0, TLSv1.1 and TLSv1.2 are enabled by default and configurable for ESXi 6.0 Update 3. Learn how to configure TLSv1.0,TLSv1.1 and TLSv1.2 from <a href="http://kb.vmware.com/kb/2148819" target="_blank">VMware Knowledge Base article 2148819</a>. For a list of VMware products supported for TLSv1.0 disablement and the use of TLSv1.1/1.2, consult <a href="http://kb.vmware.com/kb/2145796" target="_blank">VMware Knowledge Base article 2145796</a>.</li>
<li><strong>vSAN Performance</strong>: Multiple fixes are introduced in this VMware ESXi 6.0 Update 3 release to optimize I/O path for improved vSAN perfoamance in All Flash and Hybrid configurations:<br />
<ul>
<li>Log management and storage improvements were made that enable more logs to be stored per byte of storage. This should significantly improve performance for write-intensive workloads. Because vSAN is a log based file system, efficient management of log entries is key to preventing unwarranted build up of logs. </li>
<li>In addition to increasing the packing density of the log entries, for scenarios involving large file being deleted while data services is turned on, vSAN preemptively de-stages data to the capacity tier which efficiently manages the log growth.</li>
<li>The checksum code path is now more efficient. </li>
</ul>
</li>
</ul>
<h2>
<a href="https://www.blogger.com/null" id="resolvedissues" name="resolvedissues"></a>Resolved Issues</h2>
The resolved issues are grouped as follows. <br />
<ul><!--
<li><a href="#radib_issues">Auto Deploy and Image Builder Issues</a></li>
<li><a href="#rbackupissues">Backup Issues</a></li>
-->
<li><a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u3-release-notes.html#rcmiapiissues">CIM and API Issues</a></li>
<!--
<li><a href="#rgosissues">Guest Operating System Issues</a></li>
<li><a href="#ri18nissues">Internationalization Issues</a></li>
<li><a href="#rlicensingissues">Licensing Issues</a></li>
-->
<li><a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u3-release-notes.html#rmiscissues">Miscellaneous Issues</a></li>
<li><a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u3-release-notes.html#rnetworkingissues">Networking Issues</a></li>
<li><a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u3-release-notes.html#rsecurityissues">Security Issues</a></li>
<li><a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u3-release-notes.html#rserverissues">Server Configuration Issues</a></li>
<li><a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u3-release-notes.html#rstorageissues">Storage Issues</a></li>
<!--
<li><a href="#rhardwareissues">Supported Hardware Issues</a></li>
-->
<li><a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u3-release-notes.html#rupgradeinstallissues">Upgrade and Installation Issues</a></li>
<!--
<li><a href="#rupgradeissues">Upgrade Issues</a></li>
--> <!--
<li><a href="#rclientissues">vCenter Server, vSphere Web Client, and vSphere Client Issues</a></li>
--> <!--
<li><a href="#rvcenterssocmissues">vCenter Single Sign-On and Certificate Management Issues</a></li>
-->
<li><a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u3-release-notes.html#rvmissues">Virtual Machine Management Issues</a></li>
<li><a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u3-release-notes.html#rvsanissues">Virtual SAN Issues</a></li>
<!--
<li><a href="#rvmotionstorage">vMotion and Storage vMotion Issues</a></li>
-->
<li><a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u3-release-notes.html#rvmwarehaissues">VMware HA and Fault Tolerance Issues</a></li>
<!--
<li><a href="#rvmtoolsissues">VMware Tools Issues</a></li>
--> <!--
<li><a href="#rvicli_issues">vSphere Command-Line Interface Issues</a></li>
--> </ul>
<!--<b><a name="radib_issues"></a>Auto Deploy and Image Builder Issues</b>--> <!--<b><a name="rbackupissues"></a>Backup Issues</b>--> <b><a href="https://www.blogger.com/null" name="#rcimapiissues"></a>CIM and API Issues</b> <br />
<ul>
<li><a href="https://www.blogger.com/null" id="1731046" name="1731046"></a> <!--Dev PR:1731046 Doc PR:1778836 --> <strong>The Mware provider method used to validate user permissions does not work for username and password after you exit lockdown mode</strong><br /> After the server is removed from lockdown mode, the VMware provider method returns a different value that is not compatible with the value before getting into the lockdown mode. The issue results in the VMware provider method to validate user permissions not to work with the same username and password as it did before the lockdown mode. This issue is resolved in this release.</li>
</ul>
<!--<b><a name="#rgosissues"></a>Guest Operating System Issues</b>--> <!--<b><a name="#ri18nissues"></a>Internationalization Issues</b>--> <!--<b><a name="rlicensingissues"></a>Licensing Issues</b>--> <b><a href="https://www.blogger.com/null" name="rmiscissues"></a>Miscellaneous Issues</b> <br />
<ul>
<li><a href="https://www.blogger.com/null" id="1667992" name="1667992"></a> <!--Dev PR:1667992 Doc PR: 1794936 --> <strong>Upgrading VMware Tools on multiple VMs might fail</strong><br /> Attempts to upgrade VMware Tools on multiple VMs simultaneously through Update Manager might fail. Not all VMs complete the upgrade process. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1763536" name="1763536"></a> <!--Dev PR:1763536 Doc PR:1796337 --> <strong>High read load of VMware Tools ISO images might cause corruption of flash media </strong><br /> In VDI environment, the high read load of the VMware Tools images can result in corruption of the flash media. This issue is resolved in this release.<br />
You can copy all the VMware Tools data into its own ramdisk. As a result, the data can be read from the flash media only once per boot. All other reads will go to the ramdisk. vCenter Server Agent (vpxa) accesses this data through the <tt>/vmimages</tt> directory which has symlinks that point to <tt>productLocker</tt>.<br />
To activate this feature, follow the steps: <br />
<ol>
<li>Use the command to set the advanced <tt>ToolsRamdisk</tt> option to 1:</li>
<tt>esxcli system settings advanced set -o /UserVars/ToolsRamdisk -i 1</tt><br />
<li>Reboot the host. </li>
</ol>
</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1747992" name="1747992"></a> <!--Dev PR:1747992 Doc PR:1796236 --> <strong>The <tt>syslog.log</tt> file might get flooded with <tt>Unknown</tt> error messages</strong><br /> In ESXi 6.0 update 2, hosts with Dell CIM provider can have their <tt>syslog.log</tt> file flooded with <tt>Unknown</tt> error messages if the Dell CIM provider is disabled or in an idle state. Also, when the ESXi 6.0 update 2 host reboots, the <tt>syslog.log</tt> file might log error messages intermittently with <tt>Unknown</tt> entries. This issue is resolved in this release. </li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1645959" name="1645959"></a> <!--Dev PR:1645959 Doc PR:1794932 --> <strong>Userworld core dump failure</strong><br /> A userworld dump might fail when a user process runs out of memory. The error message, <tt>Unable to allocate memory</tt>, is displayed. This issue is resolved in this release. The fix provides a global memory for heap allocation of userworld core dump, which is used when any process runs out of memory.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1739979" name="1739979"></a> <!--Dev PR:1739979 Doc PR:1778070 --> <strong>Attempts to run failover for a VM fail with an error when synchronizing storage</strong><br /> Attempts to run failover for a VM might fail with an error message similar to the following during the synchonize storage operation:<br /><br /><tt>An error occurred while communicating with the remote host.</tt><br /><br /> The following messages are logged in the <tt>HBRsrv.log</tt> file:<br /><br /><tt>YYYY-MM-DDT13:48:46.305Z info hbrsrv[nnnnnnnnnnnn] [Originator@6876 sub=Host] Heartbeat handler detected dead connection for host: host-9<br /> YYYY-MM-DDT13:48:46.305Z warning hbrsrv[nnnnnnnnnnnn] [Originator@6876 sub=PropertyCollector] Got WaitForUpdatesEx exception: Server closed connection after 0 response bytes read; 171:53410'>, >)></tt><br /><br /> Also on the ESXi host, the hostd service might stop responding with messages similar to the following:<br /><br /><tt>YYYY-MM-DDT13:48:38.388Z panic hostd[468C2B70] [Originator@6876 sub=Default]<br /> --><br /> --> Panic: Assert Failed: "progress >= 0 && progress <= 100" @ bora/vim/hostd/vimsvc/HaTaskImpl.cpp:557<br /> --> Backtrace:<br /> --></tt> This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1621742" name="1621742"></a> <!--Dev PR:1621742 Doc PR:1778360 --> <strong>Log messages persistently reported in the <tt>hostd.log</tt> file every 90 seconds</strong><br /> Log messages related to Virtual SAN similar to the following are logged in the <tt>hostd.log</tt> file every 90 seconds even when the Virtual SAN is not enabled:<br /><br /><tt>{ YYYY-MM-DDT06:50:01.923Z info hostd[nnnnnnnn] [Originator@6876 sub=Hostsvc opID=21fd2fe8] VsanSystemVmkProvider : GetRuntimeInfo: Complete, runtime info: (vim.vsan.host.VsanRuntimeInfo) {<br /> YYYY-MM-DDT06:51:33.449Z info hostd[nnnnnnnn] [Originator@6876 sub=Hostsvc opID=21fd3009] VsanSystemVmkProvider : GetRuntimeInfo: Complete, runtime info: (vim.vsan.host.VsanRuntimeInfo) {<br /> YYYY-MM-DDT06:53:04.978Z info hostd[nnnnnnnn] [Originator@6876 sub=Hostsvc opID=21fd3030] VsanSystemVmkProvider : GetRuntimeInfo: Complete, runtime info: (vim.vsan.host.VsanRuntimeInfo) {</tt> This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="bug 1667992" name="bug 1667992"></a> <!--Dev PR:bug 1667992 Doc PR:1794936 --> <strong>Upgrading VMware Tools on multiple VMs might fail</strong><br /> Attempts to upgrade VMware Tools on multiple VMs simultaneously through Update Manager might fail. If this issue occurs, VMware Tools for some VMs might not be upgraded. This issue is resolved in this release.</li>
</ul>
<b><a href="https://www.blogger.com/null" name="rnetworkingissues"></a>Networking Issues</b> <br />
<ul>
<li><a href="https://www.blogger.com/null" id=" 1753438" name="1753438"></a> <!--Dev PR: 1753438 Doc PR:1796333 --><strong>ARP request packets might drop</strong><br /> ARP request packets between two VMs might be dropped if one VM is configured with guest VLAN tagging and the other VM is configured with virtual switch VLAN tagging, and VLAN offload is turned off on the VMs.</li>
</ul>
<ul>
<li><strong>ESXi firewall configuration might get disabled due to scripted upgrade</strong><br /> The ESXi firewall configuration might be disabled after scripted upgrade of ESXi 6.0 Update 1 or later using kick start file over NFS or FTP. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id=" 1768693" name=" 1768693"></a> <!--Dev PR: 1768693 Doc PR:1778312 --><strong>The virtual MAC address of 00:00:00:00:00:00 is used during communication for a newly added physical NIC even after a host reboot</strong><br /> A newly added physical NIC might not have the entry in the <tt>esx.conf</tt> file after a host reboot, resulting in a virtual MAC address of <tt>00:00:00:00:00:00</tt> listed for physical NIC during communication. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1600197" name="1600197"></a> <!--Dev PR:1600197 Doc PR:1775285 --> <strong>Error message displayed during the boot stage</strong><br /> Under certain conditions while the ESXi installer reads the installation script during the boot stage, an error message similar to the following is displayed:<br /><br /><tt>VmkNicImpl::DisableInternal:: Deleting vmk0 Management Interface, so setting advlface to NULL</tt> This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1718878" name="1718878"></a> <!--Dev PR:1718878 Doc PR:1778914 --> <strong>Physical switch flooded with RARP packets when using Citrix VDI PXE boot</strong><br /> When you boot a virtual machine for Citrix VDI, the physical switch is flooded with RARP packets (over 1000) which might cause network connections to drop and a momentary outage. This release provides an advanced option <tt>/Net/NetSendRARPOnPortEnablement</tt>. You need to set the value for <tt>/Net/NetSendRARPOnPortEnablement</tt> to 0 to resolve this issue.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1727390" name="1727390"></a> <!--Dev PR:1727390 Doc PR:1777039 --> <strong>An ESXi host might fail with purple diagnostic screen</strong><br /> An ESXi host might fail with purple diagnostic screen. This happens when <tt>DVFilter_TxCompletionCB()</tt> is called to complete a dvfilter share memory packet, it frees the IO complete data stored inside the packet, but sometimes, this data member becomes 0 which causes a NULL pointer exception. An error message similar to the following is displayed:<br /><br /><tt>YYYY-MM-DDT04:11:05.134Z cpu24:33420)@BlueScreen: #PF Exception 14 in world 33420:vmnic4-pollW IP 0x41800147d76d addr 0x28<br /> PTEs:0x587e436023;0x587e437023;0x587e438023;0x0;<br /> YYYY-MM-DDT04:11:05.134Z cpu24:33420)Code start: 0x418000800000 VMK uptime: 23:18:59:55.570<br /> YYYY-MM-DDT04:11:05.135Z cpu24:33420)0x43915461bdd0:[0x41800147d76d]DVFilterShmPacket_TxCompletionCB@com.vmware.vmkapi#v2_3_0_0+0x3d sta<br /> YYYY-MM-DDT04:11:05.135Z cpu24:33420)0x43915461be00:[0x41800146eaa2]DVFilterTxCompletionCB@com.vmware.vmkapi#v2_3_0_0+0xbe stack: 0x0<br /> YYYY-MM-DDT04:11:05.136Z cpu24:33420)0x43915461be70:[0x418000931688]Port_IOCompleteList@vmkernel#nover+0x40 stack: 0x0<br /> YYYY-MM-DDT04:11:05.136Z cpu24:33420)0x43915461bef0:[0x4180009228ac]PktListIOCompleteInt@vmkernel#nover+0x158 stack: 0x0<br /> YYYY-MM-DDT04:11:05.136Z cpu24:33420)0x43915461bf60:[0x4180009d9cf5]NetPollWorldCallback@vmkernel#nover+0xbd stack: 0x14<br /> YYYY-MM-DDT04:11:05.137Z cpu24:33420)0x43915461bfd0:[0x418000a149ee]CpuSched_StartWorld@vmkernel#nover+0xa2 stack: 0x0</tt> This issue is resolved in this release.</li>
</ul>
<b><a href="https://www.blogger.com/null" name="rsecurityissues"></a>Security Issues</b> <br />
<ul>
<li><a href="https://www.blogger.com/null" id="1582528" name="1582528"></a> <!--Dev PR:1582528 Doc PR:1796627--> <strong>Update to the Likewise Kerberos</strong><br /> The Likewise Kerberos is updated to version 1.14.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1615922" name="1615922"></a> <!--Dev PR:1615922 Doc PR:1796661--> <strong>Update to OpenSSL</strong><br /> The OpenSSL is updated to version openssl-1.0.2j.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1658843" name="1658843"></a> <!--Dev PR:1658843 Doc PR:1796665--> <strong>Update to PAM</strong><br /> The PAM is updated to version 1.3.0.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1756116" name="1756116"></a> <!--Dev PR:1756116 Doc PR:1796680--> <strong>Update to the libPNG library</strong><br /> The libPNG library is updated to libpng-1.6.26.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1769519" name="1769519"></a> <!--Dev PR:1769519 Doc PR:1796699--> <strong>Update to the NTP package</strong><br /> The ESXi NTP package is updated to version 4.2.8p9.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1781383" name="1781383"></a> <!--Dev PR:1781383 Doc PR:1796775--> <strong>Update to the libcurl library</strong><br /> The ESXi userworld libcurl library is updated to libcurl- 7.51.0.</li>
</ul>
<b><a href="https://www.blogger.com/null" name="rserverissues"></a>Server Configuration Issues</b><br />
<br />
<ul>
<li><a href="https://www.blogger.com/null" id="1770561" name="1770561"></a> <!--Dev PR:1770561 Doc PR:1796340--> <strong>Connectivity to ESXi host is lost from vCenter Server when host profile is reapplied to a stateless ESXi host</strong><br /> When a host profile with vmknic adapters in both vSphere Standard Switch and vSphere Distributed Switch is applied to an ESXi host, it might remove the vmknic adapter vmk0 (management interface) from vSphere Standard Switch which could result in the host being disconnected from vCenter Server. This issue is resolved in this release. </li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1744682" name="1744682"></a> <!--Dev PR:1744682 Doc PR:1776646--> <strong>The hostd service might fail when taking quiesced snapshot</strong><br /> The hostd service might fail when performing a quiesced snapshot operation during replication process. An error message similar to the following appears in the hostd.log file: <tt>2016-06-10T22:00:08.582Z [37181B70 info 'Hbrsvc'] ReplicationGroup will retry failed quiesce attempt for VM (vmID=37) 2016-06-10T22:00:08.583Z [37181B70 panic 'Default'] --> -->Panic: Assert Failed: "0" @ bora/vim/hostd/hbrsvc/ReplicationGroup.cpp:2779</tt> This issue is resolved in this release. </li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1611644" name="1611644"></a> <!--Dev PR:1611644 Doc PR:1793296--> <strong>ESXi 6.0 Update 1 hosts might fail with a purple diagnostic screen when collecting statistics</strong><br /> ESXi hosts with a large number of physical CPUs might stop responding during statistics collection. This issue occurs when the collection process attempts to access pages that lie beyond the range initially assigned to it. This issue is resolved in this release. </li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1601293" name="1601293"></a> <!--Dev PR:1601293 Doc PR:1793293--><strong>ESXi patch update might fail with a warning message if the image profile size is larger than set limit</strong> <br /> An ESXi patch update installation might fail if the size of the target profile file is larger than 239 MB. This might happen when you upgrade the system using ISO causing image profile size larger than 239MB without getting any warning message. This will prevent any additional VIBs from being installed on the system. This issue is resolved in this release. </li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1687609" name="1687609"></a> <!--Dev PR:1687609 Doc PR:1776610--> <strong>The <tt>vmkernel.log</tt> file is spammed with multiple USB suspend and resume events </strong><br /> The <tt>vmkernel.log</tt> file is spammed with multiple USB resumed and suspended events similar to the following:<br /><br /><tt>YYYY-MM-DDT<time> cpu28:33398)<6>hub 2-1.7:1.0: resumed<br /> YYYY-MM-DDT<time> cpu28:33398)<6>hub 2-1.7:1.0: suspended<br /> YYYY-MM-DDT<time> cpu28:33398)<6>hub 2-1.7:1.0: resumed<br /> YYYY-MM-DDT<time> cpu28:33398)<6>hub 2-1.7:1.0: suspended<br /> YYYY-MM-DDT<time> cpu28:33398)<6>hub 2-1.7:1.0: resumed<br /> YYYY-MM-DDT<time> cpu28:33398)<6>hub 2-1.7:1.0: suspended<br /> YYYY-MM-DDT<time> cpu28:33398)<6>hub 2-1.7:1.0: resumed<br /> YYYY-MM-DDT<time> cpu28:33398)<6>hub 2-1.7:1.0: suspended</time></time></time></time></time></time></time></time></tt><br />
This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1716844" name="1716844"></a> <!--Dev PR:1716844 Doc PR:1778450--> <strong>Unable to see the user or group list for assigning permissions in the Permission tab </strong><br /> Unable to see the users or groups list for assigning permissions in the <strong>Permission</strong> tab and authentication might fail for the trusted domain's user. The issue occurs when the DNS domain name of a machine is different from the DNS name of the AD domain. This issue is resolved in this release. However, after you upgrade the ESXi host to ESXi 6.0 Update 3, you must remove it from the AD domain and re-add it to the same domain.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1759826" name="1759826"></a> <!--Dev PR:1759826 Doc PR:1778827--> <strong>ESXi host might stop responding and display a purple diagnostic screen </strong><br /> When the Dump file set is called using the <tt>esxcfg-dumppart</tt> or other commands multiple times in parallel, an ESXi host might stop responding and display a purple diagnostic screen with entries similar to the following as a result of a race condition while dump block map is freed up:<br /><br /><tt>@BlueScreen: PANIC bora/vmkernel/main/dlmalloc.c:4907 - Corruption in dlmalloc<br /> Code start: 0xnnnnnnnnnnnn VMK uptime: 234:01:32:49.087<br /> 0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]PanicvPanicInt@vmkernel#nover+0x37e stack: 0xnnnnnnnnnnnn<br /> 0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]Panic_NoSave@vmkernel#nover+0x4d stack: 0xnnnnnnnnnnnn<br /> 0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]DLM_free@vmkernel#nover+0x6c7 stack: 0x8<br /> 0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]Heap_Free@vmkernel#nover+0xb9 stack: 0xbad000e<br /> 0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]Dump_SetFile@vmkernel#nover+0x155 stack: 0xnnnnnnnnnnnn<br /> 0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]SystemVsi_DumpFileSet@vmkernel#nover+0x4b stack: 0x0<br /> 0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]VSI_SetInfo@vmkernel#nover+0x41f stack: 0x4fc<br /> 0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]UWVMKSyscallUnpackVSI_Set@<none>#<none>+0x394 stack: 0x0<br /> 0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]User_UWVMKSyscallHandler@<none>#<none>+0xb4 stack: 0xffb0b9c8<br /> 0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]User_UWVMKSyscallHandler@vmkernel#nover+0x1d stack: 0x0<br /> 0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]gate_entry_@vmkernel#nover+0x0 stack: 0x0</none></none></none></none></tt><br />
This issue is resolved in this release.</li>
</ul>
<b><a href="https://www.blogger.com/null" name="rstorageissues"></a>Storage Issues</b> <br />
<ul>
<li><a href="https://www.blogger.com/null" id="1454324" name="1454324"></a> <!--Dev PR:1454324 Doc PR:1778131--> <strong>Unable to remove stale Virtual Volume volumes and VMDK files using <tt>esxcli vvol abandonedvvol</tt> command</strong><br /> Attempts use the <tt>esxcli storage vvol storagecontainer abandonedvvol</tt> command to clean the stale Virtual Volume volume and the VMDK files that remain on the Virtual Volume volume are unsuccessful. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1764752" name="1764752"></a> <!--Dev PR:1764752 Doc PR:1778203--> <strong>Snapshot creation task cancellation for Virtual Volumes might result in data loss</strong><br /> Attempts to cancel snapshot creation for a VM whose VMDKs are on Virtual Volumes datastores might result in virtual disks not getting rolled back properly and consequent data loss. This situation occurs when a VM has multiple VMDKs with the same name and these come from different Virtual Volumes datastores.<br />
This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1598185" name="1598185"></a> <!--Dev PR:1598185 Doc PR:1778472--> <strong>VMDK does not roll back properly when snapshot creation fails for Virtual Volumes VMs</strong><br /> When snapshot creation attempts for a Virtual Volumes VM fail, the VMDK is tied to an incorrect data Virtual Volume. The issue occurs only when the VMDK for the Virtual Volumes VM comes from multiple Virtual Volumes datastores. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1706150" name="1706150"></a> <!--Dev PR:1706150 Doc PR:1796227--> <strong>VM I/O operations stall or cancel when the underlying storage erroneously returns a miscompare error during periodic VMFS heartbeating. </strong><br /> VMFS uses the SCSI compare-and-write command, also called ATS, for periodic heartbeating. Any miscompare error during ATS command execution is treated as a lost heartbeat and the datastore initiates a recovery action. To prevent corruption, all I/O operations on the device are canceled. When the underlying storage erroneously reports miscompare errors during VMFS heartbeating, the datastore initiates an unnecessary recovery action.<br />
This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1760450" name="1760450"></a> <!--Dev PR:1760450 Doc PR:1809831--> <strong>ESXi 6.x hosts stop responding after running for 85 days</strong><br /> When this problem occurs, the <tt>/var/log/vmkernel</tt> log file displays entries similar to the following: <br /><br /><tt>YYYY-MM-DDTHH:MM:SS.833Z cpu58:34255)qlnativefc: vmhba2(5:0.0): Recieved a PUREX IOCB woh oo <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:34255)qlnativefc: vmhba2(5:0.0): Recieved the PUREX IOCB. <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)qlnativefc: vmhba2(5:0.0): sizeof(struct rdp_rsp_payload) = 0x88 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674qlnativefc: vmhba2(5:0.0): transceiver_codes[0] = 0x3 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)qlnativefc: vmhba2(5:0.0): transceiver_codes[0,1] = 0x3, 0x40 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)qlnativefc: vmhba2(5:0.0): Stats Mailbox successful. <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)qlnativefc: vmhba2(5:0.0): Sending the Response to the RDP packet <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674 0 1 2 3 4 5 6 7 8 9 Ah Bh Ch Dh Eh Fh <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)-------------------------------------------------------------- <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 53 01 00 00 00 00 00 00 00 00 04 00 01 00 00 10 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) c0 1d 13 00 00 00 18 00 01 fc ff 00 00 00 00 20 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 00 00 00 00 88 00 00 00 b0 d6 97 3c 01 00 00 00 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 0 1 2 3 4 5 6 7 8 9 Ah Bh Ch Dh Eh Fh <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)-------------------------------------------------------------- <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 02 00 00 00 00 00 00 80 00 00 00 01 00 00 00 04 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 18 00 00 00 00 01 00 00 00 00 00 0c 1e 94 86 08 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 0e 81 13 ec 0e 81 00 51 00 01 00 01 00 00 00 04 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 2c 00 04 00 00 01 00 02 00 00 00 1c 00 00 00 01 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 00 00 00 00 40 00 00 00 00 01 00 03 00 00 00 10 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 50 01 43 80 23 18 a8 89 50 01 43 80 23 18 a8 88 <br /> YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674) 00 01 00 03 00 00 00 10 10 00 50 eb 1a da a1 8f</tt> This issue is caused by a qlnativefc driver bug sending a Read Diagnostic Parameters (RDP) response to the HBA adapter with an incorrect transfer length. As a result, the HBA adapter firmware does not free the buffer pool space. Once the buffer pool is exhausted, the HBA adapter is not able to further process any requests causing the HBA adapter to become unavailable. By default, the RDP routine is initiated by the FC Switch and occurs once every hour, resulting in the buffer pool being exhausted in approximately 80 to 85 days under normal circumstances.<br />
This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id=" 1729643" name=" 1729643"></a> <!--Dev PR: 1729643 Doc PR:1777862 --> <strong>In vSphere 6.0, the <tt>HostMultipathStateInfoPath</tt> object of the Storage Policy API provides path value as <tt>Run Time Name vmhbaX:CX:TX:LX</tt></strong><br /> In ESXi 5.5, <tt>HostMultipathStateInfoPath</tt> provided path information in this format: HostWWN-ArrayWWN-LUN_ID, For example, <tt>sas.500605b0072b6550-sas.500c0ff1b10ea000-naa.600c0ff0001a20bd1887345701000000</tt>. However, in ESXi 6.0, the path value appears as <tt>vmhbaX:CX:TX:LX</tt>, which might impact users who rely on the <tt>HostMultipathStateInfoPath</tt> object to retrieve information such as HostWWN and ArrayWWN. This issue is resolved in this release. The <tt>HostMultipathStateInfoPath</tt> object now displays the path information as Run Time Name and <tt>HostWWN-ArrayWWN-LUN_ID</tt>.<br />
You can also use the <tt>esxcli storage core path list</tt> command to retrieve the path related information. This command provides the HostWWN and ArrayWWN details. For more information, see the <a href="http://pubs.vmware.com/Release_Notes/en/vsphere/60/%3Chttp://kb.vmware.com/kb/1003973" target="_blank">Knowledge Base article 1003973</a>.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id=" 1729643" name=" 1729643"></a> <!--Dev PR: 1729643 Doc PR:1777862 --> <strong>An ESXi host might fail with a purple diagnostic screen</strong><br /> An ESXi host with vFlash configured might fail with a purple diagnostic screen and an error message similar to <tt>PSOD: @BlueScreen: #PF Exception 14 in world 500252:vmx-vcpu-0:V</tt>. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1739958" name="1739958"></a> <!--Dev PR:1739958 Doc PR:1809704 --> <strong>ESXi host fails with a purple diagnostic screen due to path claiming conflicts</strong><br /> An ESXi host displays a purple diagnostic screen when it encounters a device that is registered, but whose paths are claimed by a two multipath plugins, for example EMC PowerPath and the Native Multipathing Plugin (NMP). This type of conflict occurs when a plugin claim rule fails to claim the path and NMP claims the path by default. NMP tries to register the device but because the device is already registered by the other plugin, a race condition occurs and triggers an ESXi host failure. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1723002" name="1723002"></a> <!--Dev PR:1723002 Doc PR:1777633 --> <strong>File operations on large files fails as the host runs out of memory</strong><br /> When you perform file operations such as mounting large files present on a datastore, these operations might fail on an ESXi host. This situation can occur when a memory leak in the buffer cache causes the ESXi host to run out of a memory, for example, when a non-zero copy of data results in buffers not getting freed. An error message similar to the following is displayed on the virtual machine.<br /><br /> The operation on file <tt>/vmfs/volumes/5f64675f-169dc0cb/CloudSetup_20160608.iso</tt> failed. If the file resides on a remote file system, make sure that the network connection and the server where this disk resides are functioning properly. If the file resides on removable media, reattach the media. Select Retry to attempt the operation again. Select Cancel to end this session. Select Continue to forward the error to the guest operating system. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1671787" name="1671787"></a> <!--Dev PR:1671787 Doc PR:1794943--> <strong>Horizon View recompose operation might fail for desktop VMs residing in NFS datastore</strong><br /> Horizon View recompose operation might fail for a few desktop VMs residing in NFS datastore with <tt>Stale NFS file handle</tt> error. This issue is resolved in this release.</li>
</ul>
<!--<b><a name="rhardwareissues"></a>Supported Hardware Issues</b>--> <b><a href="https://www.blogger.com/null" name="rupgradeinstallissues"></a>Upgrade and Installation Issues</b> <br />
<ul>
<li><a href="https://www.blogger.com/null" id="1708288" name="1708288"></a> <!--Dev PR:1708288 Doc PR:1796231--> <strong>Upgrading ESXi with vSphere Update Manager fails if ESXi was deployed using dd image on USB and <tt>/altbootbank</tt> contains <tt>BOOT.CFG</tt> in upper case</strong><br /> An ESXi dd image generated on certain versions of RHEL by using the <tt>esxiso2dd</tt> utility can contain <tt>BOOT.CFG</tt> in upper case in <tt>/altbootbank</tt>. If <tt>BOOT.CFG</tt> is in upper case, vSphere Update Manager fails to upgrade the host because the upgrade pre-checker accepts <tt>boot.cfg</tt> in lowercase only. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1796649" name="1796649"></a> <!--Dev PR:1796649 Doc PR:1809837 --> <strong>Hostd fails when you upgrade ESXi 5.5.x hosts to ESXi 6.0.x with the ESXi 6.0 patch ESXi600-201611011 or higher</strong><br /> You can observe this issue when you have installed an asynchronous HPSA driver that supports HBA mode. Although ESXi supports getting HPSA disk location information in HBA mode, problems might occur when one of the following conditions is met:<br /><br /><ul>
<li>You installed an old hpssacli utility, version 2.10.14.0 or older.</li>
<li>You used an external array to connect the HPSA controller.</li>
</ul>
These problems lead to hostd failures and the host becoming unreachable by vSphere Client and vCenter Server.<br />
This issue is resolved in this release. When you now use the esxcli command to get the disk location information, hostd does not fail. The esxcli command returns an error message similar to the following:<br />
<tt># esxcli storage core device physical get -d naa.500003963c888808 Plugin lsu-hpsa-plugin cannot get information for device with name naa.500003963c888808. Error was: Invalid output for physicaldrive.</tt></li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1708288" name="1708288"></a> <!--Dev PR:1708288 Doc PR:1796231 --> <strong>vSphere Update Manager upgrade of ESXi booted with dd image on USB might fail when <tt>/altbootbank</tt> contains <tt>BOOT.CFG</tt> (uppercase) instead of <tt>boot.cfg</tt> (lowercase)</strong><br /> ESXi dd image generated on certain versions of RHEL using <tt>esxiso2dd</tt> utility contains <tt>BOOT.CFG</tt> (in uppercase) in <tt>/altbootbank</tt>, presence of <tt>BOOT.CFG</tt> causes vSPhere Update Manager upgrade of ESXi to fail because the upgrade pre-check looks for <tt>boot.cfg</tt> in lowercase only.</li>
This issue is resolved in this release.</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1677237" name="1677237"></a> <!--Dev PR:1677237 Doc PR:1776037 --> <strong>After upgrade to 6.0, the Image Profile name in the summary tab of the host is not updated properly</strong><br /> When you use the <tt>esxcli software profile update</tt> command to apply a new Image Profile, the image profile name does not change to the new image profile name. Also when you use the ISO to perform the upgrade, the new image profile name is not marked as <strong>Updated</strong>. This issue is resolved in this release.</li>
</ul>
<!--<b><a name="rclientissues"></a>vCenter Server, vSphere Web Client, and vSphere Client Issues</b>--> <!--<b><a name="rvcenterssocmissues"></a>vCenter Single Sign-On and Certificate Management Issues</b>--> <b><a href="https://www.blogger.com/null" name="#rvmissues"></a>Virtual Machine Management Issues</b> <br />
<ul>
<li><a href="https://www.blogger.com/null" id="1753809" name="1753809"></a> <!--Dev PR:1753809 Doc PR: 1796335 --> <strong>vSphere Update Manager sends reboot reminders for VMware Tools when reboot already occurred after installation</strong><br /> The VMware Tools installation error code displays that a reboot is required even after the reboot occurred after VMware Tools was installed. The <tt>guestInfo.toolsInstallErrCode</tt> variable on the virtual machine executable (VMX) side is not cleared when VMware Tools is successfully installed and reboot occurs. This causes vSphere Update Manager to send incorrect reminders to reboot VMware Tools. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1705594" name="1705594"></a> <!--Dev PR:1705594 Doc PR: 1795683 --> <strong>Hostd fails when ListProcesses run on guest operating system</strong><br /> When a large number of processes are present in a guest operating system, the ListProcesses process is invoked more than once and the data from VMware Tools arrives in multiple chunks. When multiple ListProcesses calls to the guest OS (one for every chunk) are assembled together, the implementation creates a conflict. Multiple ListProcesses identify when all the data arrived and calls an internal callback handler. Calling the handler twice results in the failure of hostd. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1777279" name="1777279"></a> <!--Dev PR:1777279 Doc PR: 1796343 --> <strong>Possible data corruption or loss when a guest OS issues SCSI unmap commands and an IO filter prevents the unmap operation</strong><br /> When a VM virtual disk is configured with IO filters and the guest OS issues SCSI unmap commands, the SCSI unmap commands might succeed even when one of the configured IO filters failed the operation. As a result, the state reflected in the VMDK diverges from that of the IO filter and data corruption or loss might be visible to the guest OS. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1727390" name="1727390"></a> <!--Dev PR:1727390 Doc PR:1777039 --><strong>An ESXi host might fail with purple diagnostic screen</strong><br /> When a <tt>DVFilter_TxCompletionCB()</tt> operation attempts to complete a dvfilter share memory packet, it frees the IO complete data member stored inside the packet. In some cases, this data member becomes 0, causing a NULL pointer exception. An error message similar to the following is displayed:<br /><br /><tt>YYYY-MM-DDT04:11:05.134Z cpu24:33420)@BlueScreen: #PF Exception 14 in world 33420:vmnic4-pollW IP 0x41800147d76d addr 0x28 PTEs:0x587e436023;0x587e437023;0x587e438023;0x0; YYYY-MM-DDT04:11:05.134Z cpu24:33420)Code start: 0x418000800000 VMK uptime: 23:18:59:55.570 YYYY-MM-DDT04:11:05.135Z cpu24:33420)0x43915461bdd0:[0x41800147d76d]DVFilterShmPacket_TxCompletionCB@com.vmware.vmkapi#v2_3_0_0+0x3d sta YYYY-MM-DDT04:11:05.135Z cpu24:33420)0x43915461be00:[0x41800146eaa2]DVFilterTxCompletionCB@com.vmware.vmkapi#v2_3_0_0+0xbe stack: 0x0 YYYY-MM-DDT04:11:05.136Z cpu24:33420)0x43915461be70:[0x418000931688]Port_IOCompleteList@vmkernel#nover+0x40 stack: 0x0 YYYY-MM-DDT04:11:05.136Z cpu24:33420)0x43915461bef0:[0x4180009228ac]PktListIOCompleteInt@vmkernel#nover+0x158 stack: 0x0 YYYY-MM-DDT04:11:05.136Z cpu24:33420)0x43915461bf60:[0x4180009d9cf5]NetPollWorldCallback@vmkernel#nover+0xbd stack: 0x14 YYYY-MM-DDT04:11:05.137Z cpu24:33420)0x43915461bfd0:[0x418000a149ee]CpuSched_StartWorld@vmkernel#nover+0xa2 stack: 0x0</tt> This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1715318" name="1715318"></a> <!--Dev PR:1715318 Doc PR:1776677 --> <strong>ESXi host with PCI passthru might stop responding and display a purple diagnostic screen</strong><br /> When you reboot a VM with PCI Passthru multiple times, the ESXi host might stop responding and display a purple diagnostic screen with messages similar to the following in the <tt>vmware.log</tt> file:<br /><br /><tt>XXXXXXXXXXXXXXX| vcpu-0| W110: A core file is available in "<path_to_vm>/vmx-debug-zdump.000"<br /> XXXXXXXXXXXXXXX| vcpu-0| I120: Msg_Post: Error<br /> XXXXXXXXXXXXXXX| vcpu-0| I120: [msg.log.error.unrecoverable] VMware ESX<br /> XXXXXXXXXXXXXXX| vcpu-0| unrecoverable error: (vcpu-0)<br /> XXXXXXXXXXXXXXX| vcpu-0| I120+ vcpu-7:ASSERT vmcore/vmm/intr/intr.c:459</path_to_vm></tt> This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1718503" name="1718503"></a> <!--Dev PR:1718503 Doc PR:1776646 --> <strong>The hostd service might fail during replication process</strong><br /> The hostd service might fail when a quiesced snapshot operation fails during replication process. An error message similar to the following might be written to the <tt>hostd.log</tt> file:<br /><br /><tt>YYYY-MM-DDT22:00:08.582Z [37181B70 info 'Hbrsvc'] ReplicationGroup will retry failed quiesce attempt for VM (vmID=37)<br /> YYYY-MM-DDT22:00:08.583Z [37181B70 panic 'Default']<br /> --><br /> --> Panic: Assert Failed: "0" @ bora/vim/hostd/hbrsvc/ReplicationGroup.cpp:2779</tt> This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1754060" name="1754060"></a> <!--Dev PR:1754060 Doc PR:1776638 --> <strong>The hostd service might stop responding if it encounters I/O failures for a VM provisioned with an LSI virtual SCSI controller</strong><br /> An ESXi host might stop responding if it encounters storage I/O failures for a VM provisioned with an LSI virtual controller and memory is overcommitted on the ESXi host. This issue is resolved in this release.</li>
</ul>
<b><a href="https://www.blogger.com/null" name="rvsanissues"></a>Virtual SAN Issues</b> <br />
<ul>
<li><a href="https://www.blogger.com/null" id="1722542" name="1722542"></a> <!--Dev PR:1722542 Doc PR:1814907 --> <strong>Intermittent failures in Virtual SAN cluster operations related to provisioning or resulting in new object creation</strong><br /> A memory leak in the Cluster Level Object Manager Daemon (CLOMD) results in memory exhaustion over a long runtime causing the daemon to become temporarily unavailable. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1777244" name="1777244"></a> <!--Dev PR:1777244 Doc PR: 1796342 --> <strong>DOM module fails to initialize</strong><br /> Description: The Cluster Level Object Manager Daemon (CLOMD) might not use Virtual SAN on an ESXi host with large number of physical CPUs. This issue can occur if the Virtual SAN DOM module fails to initialize when joining a cluster. An error message similar to the following is displayed in the clomd.log file:<br />
<tt>2016-12-01T22:34:49.446Z 2567759 Failed to run VSI SigCheck: Failure 2016-12-01T22:34:49.446Z 2567759 main: Clomd is starting 2016-12-01T22:34:49.446Z 2567759 main: Is in stretched cluster mode? No 2016-12-01T22:34:49.446Z 2567759 CLOMSetOptions: Setting forground to TRUE 2016-12-01T22:34:49.446Z 2567759 CLOMSetOptions: No default configuration specified. 2016-12-01T22:34:49.447Z 2567759 main: Starting CLOM trace 2016-12-01T22:34:49.475Z 2567759 Cannot open DOM device /dev/dom: No such file or directory 2016-12-01T22:34:49.475Z 2567759 Cannot connect to DOM: Failure 2016-12-01T22:34:49.475Z 2567759 CLOM_CleanupRebalanceContext: Cleaning up rebalancing state 2016-12-01T22:34:49.481Z 2567759 Failed to dump data 2016-12-01T22:34:49.481Z 2567759 2016-12-01T22:34:49.481Z 2567759 main: clomd exit</tt><br />
This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1678706" name="1678706"></a> <!--Dev PR:1678706 Doc PR: 1776637 --> <strong>ESXi host fails to rejoin VMware Virtual SAN cluster after a reboot</strong><br /> Attempts to rejoin the VMware Virtual SAN cluster manually after a reboot might fail with the following error:<br /><br /><tt>Failed to join the host in VSAN cluster (Failed to start vsantraced (return code 2)</tt> This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1650174" name="1650174"></a> <!--Dev PR:1650174 Doc PR:1775994 --> <strong>Constant calling of VSAN API might result in display of a misleading task message</strong><br /> In an environment with vCenter Server 6.0 Update 2 and Virtual SAN 6.2, calling the VSAN API constantly results in creation of tasks for registering a ticket to Virtual SAN VASA provider and a message similar to the following is displayed:<br /><br /><tt>Retrieve a ticket to register the Virtual SAN VASA Provider</tt> This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1678706" name="1678706"></a> <!--Dev PR:1678706 Doc PR: 1776637 --> <strong>Virtual SAN Disk Rebalance task halts at 5% for more than 24 hours</strong><br /> The Virtual SAN Health Service reports Virtual SAN Disk Balance warnings in the vSphere Web Client. When you click <strong>Rebalance disks</strong>, the task appears to halt at 5% for more than 24 hours. This issue is resolved in this release and the <strong>Rebalance disks</strong> task is shown as completed after 24 hours.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1727027" name="1727027"></a> <!--Dev PR:1727027 Doc PR: 1776729 --> <strong>ESXi host might stop responding and display a purple diagnostic screen</strong><br /> An ESXi host might stop responding and display a purple diagnostic screen with messages similar to the following:<br /><br /><tt> YYYY-MM-DDT22:59:29.686Z cpu40:84493)@BlueScreen: #PF Exception 14 in world 84493:python IP 0xnnnnnnnnnnnn addr 0xfffffffffffffff0 PTEs:0x0;<br /> YYYY-MM-DDT22:59:29.686Z cpu40:84493)Code start: 0xnnnnnnnnnnnn VMK uptime: 7:15:08:48.373<br /> YYYY-MM-DDT22:59:29.686Z cpu40:84493)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]DOMClient_IsTopObject@com.vmware.vsan#0.0.0.1+0x18 stack: 0xnnnnnnnn<br /> YYYY-MM-DDT22:59:29.687Z cpu40:84493)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]DOMListUuidTopHierarchyCbk@com.vmware.vsan#0.0.0.1+0x69 stack: 0x900<br /> YYYY-MM-DDT22:59:29.687Z cpu40:84493)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]VSANUUIDTable_Iterate@com.vmware.vsanutil#0.0.0.1+0x4b stack: 0x139d<br /> YYYY-MM-DDT22:59:29.687Z cpu40:84493)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]DOMVsi_ListTopClients@com.vmware.vsan#0.0.0.1+0x5a stack: 0x66<br /> YYYY-MM-DDT22:59:29.688Z cpu40:84493)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]VSI_GetListInfo@vmkernel#nover+0x354 stack: 0xnnnnnnnnnnnn<br /> YYYY-MM-DDT22:59:29.688Z cpu40:84493)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]UWVMKSyscallUnpackVSI_GetList@#+0x216 stack: 0xnnnnnnnnn<br /> YYYY-MM-DDT22:59:29.688Z cpu40:84493)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]User_UWVMKSyscallHandler@#+0xb4 stack: 0xnnnnnnn<br /> YYYY-MM-DDT22:59:29.689Z cpu40:84493)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]User_UWVMKSyscallHandler@vmkernel#nover+0x1d stack: 0x0<br /> YYYY-MM-DDT22:59:29.689Z cpu40:84493)0xnnnnnnnnnnnn:[0xnnnnnnnnnnnn]gate_entry_@vmkernel#nover+0x0 stack: 0x0</tt> This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id=" 1740931" name=" 1740931"></a> <!--Dev PR: 1740931 Doc PR:1778352 --> <strong> ESXi hosts might fail with a purple diagnostic screen</strong><br /> ESXi hosts in a Virtual SAN Cluster might fail with a purple diagnostic screen when a Virtual SAN resync operation is paused. This issue is resolved in this release.</li>
</ul>
<!--<b><a name="rvmotionstorage"></a>vMotion and Storage vMotion Issues</b>
<ul>
<li><a name="xxxxxxx" id="xxxxxxx" ></a>
<!--Dev PR:xxxxxxx Doc PR:xxxxxxx --> <!-- <strong>____________________</strong><br>
__________<br><br>
This issue is resolved in this release.<br><br>
</li>
</ul>
--> <b><a href="https://www.blogger.com/null" name="rvmwarehaissues"></a>VMware HA and Fault Tolerance Configuration Issues</b> <br />
<ul>
<li><a href="https://www.blogger.com/null" id="1765418" name="1765418"></a> <!--Dev PR:1765418 Doc PR:1796338--> <strong>ESXi host might fail when enabling fault tolerance on a VM</strong><br /> An ESXi host might fail with a purple diagnostic screen when a Fault Tolerance Secondary VM fails to power on. This issue is resolved in this release.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1776031" name="1662466"><!--Dev PR:1662466 Doc PR:1775254 --></a><strong>vSphere Guest Application Monitoring SDK fails for VMs with vSphere Fault Tolerance enabled</strong><br /> When vSphere FT is enabled on an vSphere HA-protected VM where the vSphere Guest Application Monitor is installed, the vSphere Guest Application Monitoring SDK might fail. This release significantly reduces the increase in the VM network latency when Fault Tolerance is enabled.</li>
</ul>
<ul>
<li><a href="https://www.blogger.com/null" id="1467698" name="1467698"></a> <!--Dev PR:1467698 Doc PR:1775254 --> <strong>Increased latency when SMP Fault Tolerance is enabled on a VM</strong><br /> When symmetric multiprocessor (SMP) Fault Tolerance is enabled on a VM, the VM network latency might go up significantly in both average and variations. The increased latency might result in significant performance degradation or instability for VM workloads that are sensitive to such latency increases. This release significantly reduces the increase in the VM network latency when Fault Tolerance is enabled.</li>
</ul>
VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-19977355925384941312017-02-24T00:00:00.000-05:002017-09-24T11:36:13.612-04:00Fix that Damn Enhanced Authentication Plugin in Any Browser!<h2>
Enhanced Authentication Plugin Driving you Nuts?</h2>
<br />
<span style="color: red;">Update May 2017: To use with Chrome & Firefox, add a step.</span><br />
<div>
<span style="color: #005500;"><br /></span></div>
<div>
Navigate to <a href="https://vmware-plugin:8094/">https://vmware-plugin:8094</a> and <b>Advanced</b> and then <b>Proceed</b>.</div>
<div>
<br /></div>
<div>
<i>Note: For this who are interested, the reason your machine is able to resolve https://vmware-plugin is because during the installation of the plugin your hosts file is manipulated to point vmware-plugin to 127.0.0.1</i></div>
<div>
<i><br /></i></div>
<div>
Once you’ve done this, you’ll be able to check the Use Windows session authentication box and carry on as you had previously.</div>
<div>
<br /></div>
<div>
Courtesy of: <a href="http://www.jonkensy.com/vcenter-6-5-enhanced-authentication-plugin-not-working/" target="_blank">http://www.jonkensy.com/vcenter-6-5-enhanced-authentication-plugin-not-working/</a></div>
<div>
<br /></div>
<div>
------------ <span style="color: red;">End of May update</span></div>
<span style="color: red;"></span><br />
Well I have the answer for you here. 🙂<br />
<br />
Now that you've finished installing or upgrading to vSphere 6.5, no matter what browser you use, IE, Firefox, Chrome, Edge, the damn checkbox for the Enhanced Authentication Plugin won't show up and the link to download it is still there.<br />
<br />
The simple answer is that you need to TRUST the root CA certificates from YOUR vCenter server.<br />
<br />
Uninstall the plugins from your workstation. Some people claim to uninstall all old ones from previous versions, including the old Client Integration plugins, etc.. I'm not convinced that's necessary. I just uninstalled the pair of programs related to the Enhanced Authentication plugin:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjYFfQYM4suPuV7sy289kW_lWvVEr_4js5ivlDj8ExGPbgiEGQlqHB04lQCYVlJYZCCICzQBCwYFChyygjekW756PtbllzIHvQLQGlxLPKj5TFog1j75upyKMH0AC3l_Z_Q1d2AzwQ7W-RL/s1600/Enhanced+Authentication+pair.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="68" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjYFfQYM4suPuV7sy289kW_lWvVEr_4js5ivlDj8ExGPbgiEGQlqHB04lQCYVlJYZCCICzQBCwYFChyygjekW756PtbllzIHvQLQGlxLPKj5TFog1j75upyKMH0AC3l_Z_Q1d2AzwQ7W-RL/s640/Enhanced+Authentication+pair.png" width="640" /></a></div>
<ul>
<li>Open up your browser and point it to your vCenter server <a href="https://%3cvc%20or%20vcfqdn%3e/">https://<VC or VCFQDN>/</a> </li>
<li><strong>Click on</strong> "Download trusted root CA certificates". They are actually downloaded from YOUR VMCA (VMware Certificate Authority).</li>
</ul>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjwErqorFzPgrokeqwhyphenhyphenowgc8hASiaX16WYoJEud4omJpMJaGpcB6lWk5eHycv8soPb67mDvTYN1cyBV2QQaDOl64DPaYHQkkoA_nJdrz2Q3-Qqn-lyHdfuA3jN8LQwUJGqyyCGMU_Q3dPA/s1600/Certs.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="296" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjwErqorFzPgrokeqwhyphenhyphenowgc8hASiaX16WYoJEud4omJpMJaGpcB6lWk5eHycv8soPb67mDvTYN1cyBV2QQaDOl64DPaYHQkkoA_nJdrz2Q3-Qqn-lyHdfuA3jN8LQwUJGqyyCGMU_Q3dPA/s640/Certs.png" width="640" /></a> </div>
<ul>
<li><strong>Download and Extract</strong> the ZIP file.</li>
<li>The certificates in the<span style="font-family: "courier new" , "courier" , monospace;"> .\certs</span> folder need to be installed as "Trusted Root Authorities".</li>
<li>If you extracted the <span style="font-family: "courier new" , "courier" , monospace;">download.zip</span> file to the download folder, you will have a directory structure for Windows workstations like <span style="font-family: "courier new" , "courier" , monospace;">".\download\certs\win</span>".</li>
</ul>
In that folder you will see a series of files like these:<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8sc12AJ2upGbZvcuyzrtxPBzQIK98cqW27WH8H_ENSk-JZGD9nEctLuA1i675qpUlAa0e0PRFxeOs-yhWirPoYJiPk28U1b-wVajjkS1yso1nKsVRmQu3fTwS99gTFFOw1if47pxq1Uv9/s1600/Certs+to+Install.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="126" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEh8sc12AJ2upGbZvcuyzrtxPBzQIK98cqW27WH8H_ENSk-JZGD9nEctLuA1i675qpUlAa0e0PRFxeOs-yhWirPoYJiPk28U1b-wVajjkS1yso1nKsVRmQu3fTwS99gTFFOw1if47pxq1Uv9/s640/Certs+to+Install.png" width="640" /></a></div>
<ul>
<li>For each file that ends in <span style="font-family: "courier new" , "courier" , monospace;">.crt,</span> <strong>Right click</strong> on it and <strong>Choose Install Certificate</strong></li>
<li><strong>Click Open</strong> if you receive a Security Warning</li>
<li><strong>Choose</strong> "Local Machine" as the "Store Location"</li>
<li><strong>Select</strong> "Place all certificates in the following store", <strong>Click Browse</strong></li>
<li><strong>Click</strong> "Trusted Root Certificate Authorities", <strong>Click OK, Click Next</strong></li>
<li><strong>Click Finish, Click OK</strong> on the "Import was Successful" popup</li>
<li><strong><em><span style="background-color: white;">Repeat for each <span style="font-family: "courier new" , "courier" , monospace;">.crt </span>file.</span></em></strong></li>
<li><strong>Reopen your browser</strong> pointing to the <a href="https://vc/vsphere-client">https://VC/vsphere-client</a>, <strong>Download and install</strong> the "Enhanced Authentication Plugin"</li>
<li><strong>Restart your workstation.</strong></li>
</ul>
The plugin should now work in your browser of choice...<br />
<br />
Happy Administering!<br />
<br />
<br />
<br />
<br />
<br />VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-46085602260776589902017-02-17T00:30:00.000-05:002017-02-24T10:14:02.439-05:00Deleting an orphaned virtual machine when the Remove option is not available So, I was testing out our new lab environment this week for the VMware Authorized class; vSphere Install, Configure & Manage 6.5, when I realized the current version has the student inadvertently create an orphaned VM.<br />
<br />
The interesting thing is how it happened and what the resolution is.<br />
<br />
So, we have a VCSA 6.5 vCenter and 2 ESXi 6.5 hosts joined to it. The lab manual has us build a nested VCSA VM to run through the installation of VCSA. AS soon as you get the VM setup, they have you delete it. BUT, they have you use the new embedded Host Client which debuted in ESXi 6.0 with Update 2. <br />
<br />
Since you do this from the host & NOT from the Web Client or new vSphere Client (HTML5) through vCenter, the VM is gone, but the object in vCenter inventory that represents the VM still exists and shows up as orphaned:<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPkt9QjecRcDH11nW1YH0NFwXmK2DNQjpuor7HadrqgmN6YDJqDkYMH0tnQIMtY9-OO7GYHb1G11rHIh-erK_ORwfex6YdGAAMV_zrGjg4wuIL8WQutIx-BdsunUSQXDfGeUMn6tWZG3Lr/s1600/DelOrphVM1.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="295" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhPkt9QjecRcDH11nW1YH0NFwXmK2DNQjpuor7HadrqgmN6YDJqDkYMH0tnQIMtY9-OO7GYHb1G11rHIh-erK_ORwfex6YdGAAMV_zrGjg4wuIL8WQutIx-BdsunUSQXDfGeUMn6tWZG3Lr/s320/DelOrphVM1.jpg" width="320" /></a> </div>
No problem you say, just right click on it and choose Remove or choose Remove from the Actions menu... <strong><em>not so fast, it doesn't exist there</em></strong>:<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhkOdCv-QGw3TFU9wBrpLy4B3v0aDmvRcjp4HA1dMThokho72CHBWG-6EgPfMJgw1BOAOxrKwjsuusYvE6dqZhburiAtUBJuZK_K3VOLM4yncWZvEhyphenhyphent7JXwsP64wAMVWld5kosptGOUzi6/s1600/DelOrphVM2.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="187" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhkOdCv-QGw3TFU9wBrpLy4B3v0aDmvRcjp4HA1dMThokho72CHBWG-6EgPfMJgw1BOAOxrKwjsuusYvE6dqZhburiAtUBJuZK_K3VOLM4yncWZvEhyphenhyphent7JXwsP64wAMVWld5kosptGOUzi6/s400/DelOrphVM2.jpg" width="400" /></a> </div>
Ok you say, well, surely it must be available in the new vSphere Client (HTML5), right? <strong><em>NOPE</em></strong>:<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEij_60Z4N3vT-TKXfnpItEfEiSj1pReDa5D0FuBJLeweuQobAX9QGCDvHWUMUbdiOHcuuoyEVK7r-jqtwd2u4iog8X2KL0SvCGUyVv8bULAqCEKKWKFM3knM7p1aHKcT8SnVmCQN5OIg81R/s1600/DelOrphVM3.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="276" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEij_60Z4N3vT-TKXfnpItEfEiSj1pReDa5D0FuBJLeweuQobAX9QGCDvHWUMUbdiOHcuuoyEVK7r-jqtwd2u4iog8X2KL0SvCGUyVv8bULAqCEKKWKFM3knM7p1aHKcT8SnVmCQN5OIg81R/s400/DelOrphVM3.jpg" width="400" /></a> </div>
OK, so how do you remove it from inventory when there are no options to do so. Well, thanks to <strong>KB 1011468</strong> <a href="https://kb.vmware.com/kb/1011468">https://kb.vmware.com/kb/1011468</a>, we have a workaround. <br />
Here are the steps:<br />
<ol>
<li>Open VMware Infrastructure or vSphere Client and connect to vCenter Server with a user with Administrative rights. </li>
<li>Change the view to the VMs and Templates inventory view. </li>
<li>On the left pane, right-click vCenter Server, click <strong>New Folder</strong> and provide an alpha-numeric name to the folder. </li>
<li>Click the virtual machine and while holding the left mouse button, drag the virtual machine to the folder created in step 3. </li>
<li>Right-click the folder, and click <strong>Remove</strong>. The folder and its contents are deleted. </li>
</ol>
<strong><span style="font-size: large;">Simple right? Wrong...</span></strong><br />
This KB is OLD, so in Step 1 in vSphere 6.5, you might see a problem ... There is no Windows based vSphere Client available. But hold it, the KB shows support for vCenter 6.5, how can that be?<br />
<br />
Well, here's a little known fact. IF you have the 6.0 Update 2 version of the OLD Windows based vSphere Client installed, you can actually use it to connect to vSphere 6.5! Well, kind of, you CAN connect to an ESXi 6.5 host but NOT a vCenter 6.5 server. So again we are stuck.<br />
<br />
<span style="color: red; font-size: x-large;"><strong>OK, so the real answer is to use the command line.</strong></span> <br />
You need to remove the VM information from the vCenter database. <br />
One easy way is with <a href="https://my.vmware.com/web/vmware/details?downloadGroup=PCLI650R1&productId=614" target="_blank">PowerCLI 6.5 Release 1,</a> you need to:<br />
<ol>
<li>Connect to vCenter with a <strong>connect-viserver <VC FQDN></strong></li>
<li>Issue the command <strong>get-vm | select name</strong> so you can see the VM in question</li>
<li>Issue a <strong>remove-vm <VM name></strong> to remove the orphaned VM </li>
<li>Re-run the original command to verify it's gone and view the inventory!</li>
</ol>
<br />
We start with this VM:<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhy7RI6VYMJf-T2PS_dCx13kbBmFtoRSxB3rtKPFyMoAtTq4J-jMt-h-oRORJFDl7N6RVKdS3Pq-uYz8Q2OAWR3FDhRKH59q1mFq_Tn8l6-9oKYsQmCyJyZ_JqYqQsz0o2QIt_3u7bQYgU3/s1600/DelOrphVM5.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhy7RI6VYMJf-T2PS_dCx13kbBmFtoRSxB3rtKPFyMoAtTq4J-jMt-h-oRORJFDl7N6RVKdS3Pq-uYz8Q2OAWR3FDhRKH59q1mFq_Tn8l6-9oKYsQmCyJyZ_JqYqQsz0o2QIt_3u7bQYgU3/s1600/DelOrphVM5.jpg" /></a> </div>
We list VMs in VC inventory & Delete the selected VM & Re-list:<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj5mPkXMtwqYXLNmISt-e6u_NIOgvSHYfSewbdYuWrb8OXqLf1SmZIUvX9c9Lwmy9laCug92MQuBLpsUR-sr6Dgk1W94eMekbXJOz2r_Y6f2veR7IlK-dJPzjUIDXD9O8XIYS0SdXvZOq87/s1600/DelOrphVM6.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="243" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj5mPkXMtwqYXLNmISt-e6u_NIOgvSHYfSewbdYuWrb8OXqLf1SmZIUvX9c9Lwmy9laCug92MQuBLpsUR-sr6Dgk1W94eMekbXJOz2r_Y6f2veR7IlK-dJPzjUIDXD9O8XIYS0SdXvZOq87/s320/DelOrphVM6.jpg" width="320" /></a> </div>
And you can see the VM is now gone from inventory!<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEibwmOR49lam86uhLHYITfoUutetaQDUY_el_RcGJP-kb1_hMB3eRg1MrPTzUd5nIx07AB0EdnlGKpK2iutbwZZDxFgIKE5c0stCG_VdG9BPOFmJTXkhD_QDSpzQjqntGLp5fYiEsJor7UI/s1600/DelOrphVM7.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="320" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEibwmOR49lam86uhLHYITfoUutetaQDUY_el_RcGJP-kb1_hMB3eRg1MrPTzUd5nIx07AB0EdnlGKpK2iutbwZZDxFgIKE5c0stCG_VdG9BPOFmJTXkhD_QDSpzQjqntGLp5fYiEsJor7UI/s320/DelOrphVM7.jpg" width="274" /></a> </div>
So, I've mentioned to my students before, although you can do the vast majority of what you need using a GUI, you may need some command line skills to do certain things when the GUI is lacking.<br />
<br />
Never too late to learn PowerShell with PowerCLI for vSphere 6.5! <br />
<br />
<br />VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-75170471706143398542017-02-10T20:45:00.002-05:002017-04-06T11:46:57.118-04:00How to disable DRS for a single host in the clusterI saw a question today which was interesting, how do I disable DRS for a single host in the cluster? I thought about it, and you cannot do this within the UI, at least… there is no “disable DRS” option on a host level. You can enable/disable it on a cluster level but that is it. But there are of course ways to ensure a host is not considered by DRS:<br />
<ol>
<li>Place the host in maintenance mode<br /> This will result in the host not being used by DRS. However it also means the host won’t be used by HA and you cannot run any workloads on it.</li>
<li>Create “VM/Host” affinity rules and exclude the host that needs to be DRS disabled. That way all current workloads will not run, or be considered to run, on that particular host. If you create “must” rules this is guaranteed, if you create “should” rules then at least HA can still use the host for restarts but unless there is severe memory pressure or you hit 100 CPU utilization it will not be used by DRS either.</li>
<li><a href="https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006989" target="_blank">Disable</a> the vMotion VMkernel interface<br /> This will result in not being able to vMotion any VMs to the host (and not from the host either). However, HA will still consider it for restarts and you can run workloads on the host, and the host will be considered for “initial placement” during a power-on of a VM.</li>
</ol>
I will file a feature request for a “disable drs” on a particular host option in the UI, I guess it could be useful for some in certain scenarios.<br />
<br />
Original post by Duncan Epping from yellow-bricks.com<br />
<a href="http://www.yellow-bricks.com/2017/01/17/disable-drs-single-host-cluster/">http://www.yellow-bricks.com/2017/01/17/disable-drs-single-host-cluster/</a>VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-30876198049442186672017-02-03T16:42:00.001-05:002017-04-06T11:45:56.439-04:00VMware VCSA 6.5 Backup and Restore How-to<h2>
VMware VCSA 6.5 Backup and Restore How-to. </h2>
Note that it is an “out-of-the-box” feature which does a file level backup. It’s “built-in” within the appliance itself, and it allows users to backup not only the vCenter Server but also Platform Services Controller (PSC) appliances directly. VCSA with embedded or external Platform Services Controller (PSC) is supported.<br />
<br />
As you might imagine, the restore has to be launched from somewhere. When you’re in a situation when your VCSA is broken, you’ll have to first deploy clean VCSA via the Installation/deployment ISO, but you do that within the restore operation.<br />
<h3>
</h3>
<h3>
What is backed up? </h3>
The minimum set of data needed is backed up by default. Those are for example the OS, vCenter services and Inventory. You can additionally backup also Inventory, configuration, and historical data (Statistics, events, and tasks) in vCenter server database<br />
<br />
So during the restore operation, you deploy a clean VCSA (phase 1) and you restore from backup (phase 2). The vCenter Server UUID and all configuration settings are restored. The backup file is stored elsewhere, not on the VCSA itself. VCSA backup can be backed and sent up to different location via different protocols:<br />
<ul>
<li>FTP</li>
<li>FTPS</li>
<li>HTTP</li>
<li>HTTPS</li>
<li>SCP</li>
</ul>
<h3>
VMware VCSA 6.5 Backup and Restore How-To</h3>
Browse to <a href="https://vcsa:5480/" rel="nofollow">https://VCSA:5480</a> > <br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjRVpX0flrFEiYNI_jPnPEwmoRDON-JVNFULZ6RVa5-nylvirMIs9vKabmkzvzQu2feLXWmaG5gyGzqqpJJcl2XPQdlvLFGgwTMrj6hyxVM6sCF_DwWMc89m9YR_VkYl44QKgf2-Ldj70n2/s1600/VCSA65login.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="152" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjRVpX0flrFEiYNI_jPnPEwmoRDON-JVNFULZ6RVa5-nylvirMIs9vKabmkzvzQu2feLXWmaG5gyGzqqpJJcl2XPQdlvLFGgwTMrj6hyxVM6sCF_DwWMc89m9YR_VkYl44QKgf2-Ldj70n2/s320/VCSA65login.png" width="320" /></a></div>
<br />
Log in with the password you entered when you have deployed the solution. You’ll see this nice new UI….<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnOFvWfjsPm_6ujPMn7KHD1kkLpSlRHPOvO0RcC6M17NqKbwo2buRmMnmsHUd5E_hwQW-vlYHDJCw5iYw-khvgAMWAKM8qIOghHgNWpZfH-UMa38TtmvEwyo3D_6dYP7iSh5qG4uQ_LhwA/s1600/VCSA65main.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="304" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEgnOFvWfjsPm_6ujPMn7KHD1kkLpSlRHPOvO0RcC6M17NqKbwo2buRmMnmsHUd5E_hwQW-vlYHDJCw5iYw-khvgAMWAKM8qIOghHgNWpZfH-UMa38TtmvEwyo3D_6dYP7iSh5qG4uQ_LhwA/s640/VCSA65main.png" width="640" /></a></div>
<br />
After you log in, then you can hit the big <strong>Backup</strong> button. A wizard will start…. <br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiUn-eLoao2w057f0_RBy-88U3XJSd2bTVXKDneB0rNuViQ_seEcRW-uejfzeqLArl9RPprka6Aw0cktI2BJwFtUvRtaOUMgJX-YK22Dy8knbSmCd81gK1lqZNu9os5g9qtQRy4yskeTDoT/s1600/VCSA65backup1.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="304" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEiUn-eLoao2w057f0_RBy-88U3XJSd2bTVXKDneB0rNuViQ_seEcRW-uejfzeqLArl9RPprka6Aw0cktI2BJwFtUvRtaOUMgJX-YK22Dy8knbSmCd81gK1lqZNu9os5g9qtQRy4yskeTDoT/s640/VCSA65backup1.png" width="640" /></a></div>
<br />
<br />
There you’ll be presented with a nice wizard which will allow you to specify where you want to send this backup. The location must be an empty folder. Note the option to encrypt your backup data, a simple check box.<br />
<br />
Note the option to encrypt your backup data, a simple check box……<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjujno08YRz9vuS78UuSN7Ir-am3k1vXfiD4uRKwsis6B1RZLRyihcim0yAfwU62-GLUAO2448UJRCFmWpGy22o1_8WpPhCd6VXOCIZFSdu09GDwNqE9XKJvndrFNjYD82pXvSll-rbc7oA/s1600/VCSA65backup2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="304" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjujno08YRz9vuS78UuSN7Ir-am3k1vXfiD4uRKwsis6B1RZLRyihcim0yAfwU62-GLUAO2448UJRCFmWpGy22o1_8WpPhCd6VXOCIZFSdu09GDwNqE9XKJvndrFNjYD82pXvSll-rbc7oA/s640/VCSA65backup2.png" width="640" /></a></div>
<em></em><br />
<br />
<strong>NOTE:</strong> If you use HTTP or HTTPS, you must enable WebDAV on the backup Web server.<br />
<br />
The <strong>Encrypt Backup Data checkbox</strong>, when checked, a new section appears inviting you to put login/password combination. The password form is intelligently checking if you enter twice the same password. If not, you have a small notification telling you that your passwords do not match.<br />
And then I entered the backup setting, such as protocol, login/password combination (make sure to give read/write rights on the folder where you’re backing up) > and finish the wizard.<br />
<br />
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGfjm7iVGy8INYMVcwBTLJbO8z81v1AQ7B0HZHogGRWEWTuO0iqEPGn60_XHDf47NV4jqlCgZzrxD-h7J1ms5yN8XfUiWoTfBuKCt3PSmeo-DZPbJBYD1YABT68aK6wY6ihEgaVebmyvBP/s1600/VCSA65backup6.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="200" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjGfjm7iVGy8INYMVcwBTLJbO8z81v1AQ7B0HZHogGRWEWTuO0iqEPGn60_XHDf47NV4jqlCgZzrxD-h7J1ms5yN8XfUiWoTfBuKCt3PSmeo-DZPbJBYD1YABT68aK6wY6ihEgaVebmyvBP/s400/VCSA65backup6.png" width="400" /></a></div>
<br />
<strong>Note</strong>: To check which services are not running you go SSH to the VCSA 6.5 appliance and run<br />
<br />
<span style="font-family: "courier new" , "courier" , monospace;"> service-control — status</span><br />
<span style="font-family: "courier new";"></span><br />
which gives you services which run on one line, and also services which are not running. The “vmware-stsd” service should be normally running.<br />
<br />
To start the service:<br />
<br />
<span style="font-family: "courier new" , "courier" , monospace;"> service-control — start vmware-stsd</span><br />
<br />
<h3>
Restore operation</h3>
Well, from then it is very straightforward. Just quickly…<br />
<br />
<strong>Launch the setup application of the VCSA 6.5 (from the ISO)</strong><br />
<ol>
<li>Click the <strong>Restore</strong> button</li>
<li>Deploy a new appliance using the wizard.</li>
<li>Accept EULA</li>
<li>Enter Backup details</li>
<li>Review backup information</li>
<li>Enter appliance deployment target (ESXi host) ….. from them it is pretty similar to a clean deployment…</li>
</ol>
<div class="separator" style="clear: both; text-align: center;">
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhhIObgqBwS0P7Z_bV9ILv9Ratpv2xmx1EOKnu3mEc4a6Gxo8C1mg0R0_ysdGCt9-w9zrCGOTmrCfKb3L_VbShqKQ7gQeambRhrSreijiDmOfTWgNVnR2GiPZ8rNVOArWx0mF-o1IIqguDx/s1600/VCSA65restore2.png" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="304" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhhIObgqBwS0P7Z_bV9ILv9Ratpv2xmx1EOKnu3mEc4a6Gxo8C1mg0R0_ysdGCt9-w9zrCGOTmrCfKb3L_VbShqKQ7gQeambRhrSreijiDmOfTWgNVnR2GiPZ8rNVOArWx0mF-o1IIqguDx/s640/VCSA65restore2.png" width="640" /></a></div>
<br />VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-18730556169819371402017-01-25T13:35:00.002-05:002017-01-26T23:34:04.023-05:00vSphere 6.5, Important items 2 months after Official Release<h2>
What you should know now that vSphere 6.5 has been out a couple of months...</h2>
<br />
<span style="color: red;"><strong>UPDATE</strong></span>: <em>It figures, as soon as I click Publish on this article, I found out that Veeam released Update 1 for all their 9.5 products on 1/24/2017 making them all compatible with vSphere 6.5!</em><br />
<br />
Well, vSphere 6.5 has brought hundreds of major and minors updates to the venerable virtualization platform from VMware. Many of the changes are significant.<br />
<br />
Realistically, for the small to medium vSphere organization, many of these changes will go unnoticed or unused. But, there are goodies that need to be considered by all.<br />
<br />
The most significant change has to be the re-energized focus on moving to the VCSA or vCenter Server Appliance. In vSphere 6.5, this appliance now runs on VMware's own Photon OS, a Linux distro that they own & maintain in-house. The first major advantage this appliance has over the previous ones is speed. Having eschewed SUSE Linux provides VMware the opportunity to tune & tweak their Linux to provide the best performance possible for their specific needs.<br />
<br />
The VCSA 6.5 gains significant speed advantages over its predecessor as well as the current Windows based vCenter Server 6.5, just because of this change to the underlying appliance OS.<br />
<br />
As with the previous appliance in 6.0, VMware has parity with sizing and maximums between the VCSA 6.5 & the Windows vCenter Server 6.5. A monumental change comes in the fact that the current VCSA 6.5 <strong><em>ONLY</em></strong> supports the embedded PostgreSQL database from VMware. They no longer support an external Oracle database for vCenter! <br />
<br />
A major focus for VCSA 6.5, following the initial introduction of vSphere 6.0 Update 2M, is the ability to migrate from previous versions of Windows vCenter Server and VCSA to the current version, pulling in the database information from any of those previous platforms. This current design obviates the need for an external database from previous designs.<br />
<br />
This practice of embedding the database is followed up with the brand new inclusion of Update Manager 6.5 as part of the appliance as well. In other words, the new VCSA 6.5 is a complete solution for vCenter and Update Manager and their databases in a single VM. That design allows for the other major feature introduced in 6.5 of High Availability for the VCSA (VCHA) without the need to use a host based HA cluster solution. No more worries about losing your vCenter. There is a 2nd VCSA copy that is passive and up to date with a 3rd witness VM, all of which are cloned from the original.<br />
<br />
The final VCSA 6.5 addition that benefits all organizations, is the ability to backup the appliance from within the appliance, no dependency on 3rd party or VDP backup solutions... more on that in another post.<br />
<br />
<h3>
So what do we need to be wary of before upgrading to the latest and greatest vSphere?</h3>
Compatibility of 3rd party products is the most important for many organizations. Many are using Veeam Backup & Replication, which in its current (1/25/2017) version of 9.5 has not released support for vSphere 6.5 yet. It is rumored on their site to be forthcoming in an Update 1 release for 9.5. For many, that's the deal breaker for now, but all your linked or dependent 3rd party apps need to be checked.<br />
<br />
Currently, NSX is not supported on vSphere 6.5 either. If you are currently running a 6.x version of Horizon View, that needs to be updated to at least 7.0. So make sure you carefully plan your upgrades to all 3rd party products designed to support vSphere 6.5 before you jump to upgrade your base virtualization platform...VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-7058904907759154062016-10-11T14:08:00.000-04:002016-10-11T14:10:15.882-04:00Exchange 2016 and Windows Server 2016I am currently updating our Exchange 2013/2016 Ultimate Bootcamp and while searching the web have come up with a few neat things to add to the course. One of the things I have been looking at is of course the release of Windows Server 2016 and compatibility features of Exchange 2016. <br />
<br />
As of right now Exchange 2016 is not supported to run on Windows Server 2016. That is no surprise, but here is what I found interesting. Exchange 2016 is not supported if you have Windows Server 2016 Domain Controllers.<br />
<br />
Here is a list of supported OS's and Supported Domain environments at the time of this posting.<br />
<br />
<a href="https://msdnshared.blob.core.windows.net/media/2016/05/image587.png"><img alt="Exchange Support For Windows Server 2016 - Currently Supported OS" border="0" height="295" src="https://msdnshared.blob.core.windows.net/media/2016/05/image_thumb521.png" style="border-width: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="Exchange Support For Windows Server 2016 - Currently Supported OS" width="806" /></a><br />
<br />
<a href="https://msdnshared.blob.core.windows.net/media/2016/05/image588.png"><img alt="image" border="0" height="303" src="https://msdnshared.blob.core.windows.net/media/2016/05/image_thumb522.png" style="border-width: 0px; padding-left: 0px; padding-right: 0px; padding-top: 0px;" title="image" width="806" /></a><br />
<br />
Will there be support added in the future. Probably, but not sure when. VMware Dudehttp://www.blogger.com/profile/10984544298643970297noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-83119511139170232422015-07-08T10:25:00.001-04:002015-07-08T10:26:49.866-04:00Moving the VMware vCenter Server 4.x/5.x/6.0.x SQL database <!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><br />
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:AllowPNG/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:View>Normal</w:View>
<w:Zoom>0</w:Zoom>
<w:TrackMoves>false</w:TrackMoves>
<w:TrackFormatting/>
<w:PunctuationKerning/>
<w:ValidateAgainstSchemas/>
<w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
<w:IgnoreMixedContent>false</w:IgnoreMixedContent>
<w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
<w:DoNotPromoteQF/>
<w:LidThemeOther>EN-US</w:LidThemeOther>
<w:LidThemeAsian>X-NONE</w:LidThemeAsian>
<w:LidThemeComplexScript>X-NONE</w:LidThemeComplexScript>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:DontGrowAutofit/>
<w:SplitPgBreakAndParaMark/>
<w:EnableOpenTypeKerning/>
<w:DontFlipMirrorIndents/>
<w:OverrideTableStyleHps/>
</w:Compatibility>
<m:mathPr>
<m:mathFont m:val="Cambria Math"/>
<m:brkBin m:val="before"/>
<m:brkBinSub m:val="--"/>
<m:smallFrac m:val="off"/>
<m:dispDef/>
<m:lMargin m:val="0"/>
<m:rMargin m:val="0"/>
<m:defJc m:val="centerGroup"/>
<m:wrapIndent m:val="1440"/>
<m:intLim m:val="subSup"/>
<m:naryLim m:val="undOvr"/>
</m:mathPr></w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:LatentStyles DefLockedState="false" DefUnhideWhenUsed="false"
DefSemiHidden="false" DefQFormat="false" DefPriority="99"
LatentStyleCount="371">
<w:LsdException Locked="false" Priority="0" QFormat="true" Name="Normal"/>
<w:LsdException Locked="false" Priority="9" QFormat="true" Name="heading 1"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 2"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 3"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 4"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 5"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 6"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 7"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 8"/>
<w:LsdException Locked="false" Priority="9" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="heading 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index 9"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 1"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 2"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 3"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 4"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 5"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 6"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 7"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 8"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" Name="toc 9"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="header"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footer"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="index heading"/>
<w:LsdException Locked="false" Priority="35" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="caption"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="table of figures"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="envelope address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="envelope return"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="footnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="line number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="page number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="endnote reference"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="endnote text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="table of authorities"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="macro"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="toa heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Bullet 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Number 5"/>
<w:LsdException Locked="false" Priority="10" QFormat="true" Name="Title"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Closing"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Signature"/>
<w:LsdException Locked="false" Priority="1" SemiHidden="true"
UnhideWhenUsed="true" Name="Default Paragraph Font"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="List Continue 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Message Header"/>
<w:LsdException Locked="false" Priority="11" QFormat="true" Name="Subtitle"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Salutation"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Date"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text First Indent"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text First Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Note Heading"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Body Text Indent 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Block Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Hyperlink"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="FollowedHyperlink"/>
<w:LsdException Locked="false" Priority="22" QFormat="true" Name="Strong"/>
<w:LsdException Locked="false" Priority="20" QFormat="true" Name="Emphasis"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Document Map"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Plain Text"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="E-mail Signature"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Top of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Bottom of Form"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal (Web)"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Acronym"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Address"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Cite"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Code"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Definition"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Keyboard"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Preformatted"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Sample"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Typewriter"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="HTML Variable"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Normal Table"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="annotation subject"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="No List"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Outline List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Simple 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Classic 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Colorful 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Columns 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Grid 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 4"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 5"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 6"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 7"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table List 8"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table 3D effects 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Contemporary"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Elegant"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Professional"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Subtle 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Subtle 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 1"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 2"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Web 3"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Balloon Text"/>
<w:LsdException Locked="false" Priority="39" Name="Table Grid"/>
<w:LsdException Locked="false" SemiHidden="true" UnhideWhenUsed="true"
Name="Table Theme"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Placeholder Text"/>
<w:LsdException Locked="false" Priority="1" QFormat="true" Name="No Spacing"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading"/>
<w:LsdException Locked="false" Priority="61" Name="Light List"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 1"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 1"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 1"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 1"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 1"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 1"/>
<w:LsdException Locked="false" SemiHidden="true" Name="Revision"/>
<w:LsdException Locked="false" Priority="34" QFormat="true"
Name="List Paragraph"/>
<w:LsdException Locked="false" Priority="29" QFormat="true" Name="Quote"/>
<w:LsdException Locked="false" Priority="30" QFormat="true"
Name="Intense Quote"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 1"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 1"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 1"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 1"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 1"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 1"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 1"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 1"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 2"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 2"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 2"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 2"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 2"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 2"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 2"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 2"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 2"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 2"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 2"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 2"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 2"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 2"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 3"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 3"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 3"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 3"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 3"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 3"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 3"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 3"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 3"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 3"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 3"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 3"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 3"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 3"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 4"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 4"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 4"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 4"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 4"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 4"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 4"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 4"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 4"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 4"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 4"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 4"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 4"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 4"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 5"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 5"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 5"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 5"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 5"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 5"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 5"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 5"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 5"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 5"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 5"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 5"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 5"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 5"/>
<w:LsdException Locked="false" Priority="60" Name="Light Shading Accent 6"/>
<w:LsdException Locked="false" Priority="61" Name="Light List Accent 6"/>
<w:LsdException Locked="false" Priority="62" Name="Light Grid Accent 6"/>
<w:LsdException Locked="false" Priority="63" Name="Medium Shading 1 Accent 6"/>
<w:LsdException Locked="false" Priority="64" Name="Medium Shading 2 Accent 6"/>
<w:LsdException Locked="false" Priority="65" Name="Medium List 1 Accent 6"/>
<w:LsdException Locked="false" Priority="66" Name="Medium List 2 Accent 6"/>
<w:LsdException Locked="false" Priority="67" Name="Medium Grid 1 Accent 6"/>
<w:LsdException Locked="false" Priority="68" Name="Medium Grid 2 Accent 6"/>
<w:LsdException Locked="false" Priority="69" Name="Medium Grid 3 Accent 6"/>
<w:LsdException Locked="false" Priority="70" Name="Dark List Accent 6"/>
<w:LsdException Locked="false" Priority="71" Name="Colorful Shading Accent 6"/>
<w:LsdException Locked="false" Priority="72" Name="Colorful List Accent 6"/>
<w:LsdException Locked="false" Priority="73" Name="Colorful Grid Accent 6"/>
<w:LsdException Locked="false" Priority="19" QFormat="true"
Name="Subtle Emphasis"/>
<w:LsdException Locked="false" Priority="21" QFormat="true"
Name="Intense Emphasis"/>
<w:LsdException Locked="false" Priority="31" QFormat="true"
Name="Subtle Reference"/>
<w:LsdException Locked="false" Priority="32" QFormat="true"
Name="Intense Reference"/>
<w:LsdException Locked="false" Priority="33" QFormat="true" Name="Book Title"/>
<w:LsdException Locked="false" Priority="37" SemiHidden="true"
UnhideWhenUsed="true" Name="Bibliography"/>
<w:LsdException Locked="false" Priority="39" SemiHidden="true"
UnhideWhenUsed="true" QFormat="true" Name="TOC Heading"/>
<w:LsdException Locked="false" Priority="41" Name="Plain Table 1"/>
<w:LsdException Locked="false" Priority="42" Name="Plain Table 2"/>
<w:LsdException Locked="false" Priority="43" Name="Plain Table 3"/>
<w:LsdException Locked="false" Priority="44" Name="Plain Table 4"/>
<w:LsdException Locked="false" Priority="45" Name="Plain Table 5"/>
<w:LsdException Locked="false" Priority="40" Name="Grid Table Light"/>
<w:LsdException Locked="false" Priority="46" Name="Grid Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="Grid Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="Grid Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46"
Name="Grid Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="Grid Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="Grid Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="Grid Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="Grid Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51"
Name="Grid Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52"
Name="Grid Table 7 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="46" Name="List Table 1 Light"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark"/>
<w:LsdException Locked="false" Priority="51" Name="List Table 6 Colorful"/>
<w:LsdException Locked="false" Priority="52" Name="List Table 7 Colorful"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 1"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 1"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 1"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 1"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 1"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 1"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 2"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 2"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 2"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 2"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 2"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 2"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 3"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 3"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 3"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 3"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 3"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 3"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 4"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 4"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 4"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 4"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 4"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 4"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 5"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 5"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 5"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 5"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 5"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 5"/>
<w:LsdException Locked="false" Priority="46"
Name="List Table 1 Light Accent 6"/>
<w:LsdException Locked="false" Priority="47" Name="List Table 2 Accent 6"/>
<w:LsdException Locked="false" Priority="48" Name="List Table 3 Accent 6"/>
<w:LsdException Locked="false" Priority="49" Name="List Table 4 Accent 6"/>
<w:LsdException Locked="false" Priority="50" Name="List Table 5 Dark Accent 6"/>
<w:LsdException Locked="false" Priority="51"
Name="List Table 6 Colorful Accent 6"/>
<w:LsdException Locked="false" Priority="52"
Name="List Table 7 Colorful Accent 6"/>
</w:LatentStyles>
</xml><![endif]--><!--[if gte mso 10]>
<style>
/* Style Definitions */
table.MsoNormalTable
{mso-style-name:"Table Normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-priority:99;
mso-style-parent:"";
mso-padding-alt:0in 5.4pt 0in 5.4pt;
mso-para-margin-top:0in;
mso-para-margin-right:0in;
mso-para-margin-bottom:8.0pt;
mso-para-margin-left:0in;
line-height:107%;
mso-pagination:widow-orphan;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-ascii-font-family:Calibri;
mso-ascii-theme-font:minor-latin;
mso-hansi-font-family:Calibri;
mso-hansi-theme-font:minor-latin;}
</style>
<![endif]-->
<br />
<div class="MsoNormal">
A simple necessary task that isn’t so simple.<span style="mso-spacerun: yes;"> </span>So the scenario plays out like this.<span style="mso-spacerun: yes;"> </span>Customer is running vCenter, Update Manager
and SRM databases on a SQL server that is running Windows 2003 with SQL 2005 –
not extremely uncommon.<span style="mso-spacerun: yes;"> </span>With the
impending end of Windows 2003 looming we decide to migrate to Windows 2008 R2
and SQL 2008 R2.<span style="mso-spacerun: yes;"> </span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
For the most part we followed KB 7960893 from VMware.</div>
<div class="MsoNormal">
<a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=7960893">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=7960893</a></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Now this KB will get you close, which is nice.<span style="mso-spacerun: yes;"> </span>And what does close mean.<span style="mso-spacerun: yes;"> </span>It means that we had databases up and running
on the SQL server.<span style="mso-spacerun: yes;"> </span>It means that we had
ODBC connections that were connected and tested OK.<span style="mso-spacerun: yes;"> </span>And then….It means that we couldn’t get the
service to start – WTF.</div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
So let’s look at the process and the final resolution.<span style="mso-spacerun: yes;"> </span>First off it’s a pretty common task and I was
doing this for a customer in their DR site, but it is something that everyone
will run into at some time.<span style="mso-spacerun: yes;"> </span></div>
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
Several steps in the process.</div>
<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">1.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>Backup the databases on the old SQL server.<span style="mso-spacerun: yes;"> </span>Simple enough go into SQL management studio
right click the database and back it up.<span style="mso-spacerun: yes;">
</span>Stop all of the VMware services on vCenter and SRM first.<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">2.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>Copy the databases over to the new server –
Really easy.<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">3.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>Restore the databases to the new SQL server.<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">4.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>Yeah this next step is a little harder.<span style="mso-spacerun: yes;"> </span>Permissions.<span style="mso-spacerun: yes;">
</span>We had to set the proper permissions.<span style="mso-spacerun: yes;">
</span>The customer wanted to use a different service account and instead of
having separate accounts for vCenter, UM, and SRM they wanted to use one
account for all of them.<span style="mso-spacerun: yes;"> </span>Not a huge
deal, so whatever, let’s make it happen.<span style="mso-spacerun: yes;">
</span>We used a local account in SQL with SQL server authentication.<span style="mso-spacerun: yes;"> </span>We then granted <i style="mso-bidi-font-style: normal;">dbo</i> permissions to the vCenter, UM, and SRM databases.<span style="mso-spacerun: yes;"> </span>You also have to give it <i style="mso-bidi-font-style: normal;">dbo</i> for the <i style="mso-bidi-font-style: normal;">msdb</i>
database.<span style="mso-spacerun: yes;"> </span>OK, all of this sounds pretty
straightforward so far.<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">5.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>Edit the <i style="mso-bidi-font-style: normal;">vcdb.properties</i>
file to change the server name – Really easy.<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">6.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>I didn’t update the SQL server agents just yet,
because I didn’t care about performance statistics.<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">7.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>Go to ODBC and ODBC32 on the vCenter server and
change them to point to the new server and the correct database using the
proper username and password.<span style="mso-spacerun: yes;"> </span>Then test
it.<span style="mso-spacerun: yes;"> </span>BOOM, everything worked.<span style="mso-spacerun: yes;"> </span>Start the vCenter and UM services up.<span style="mso-spacerun: yes;"> </span>And…It failed.<span style="mso-spacerun: yes;"> </span>WTF.<br />
<br />
<b style="mso-bidi-font-weight: normal;">Troubleshooting Time</b><br />
<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">8.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>So to do a little troubleshooting I looked in
event viewer, got a whole bunch of nothing.<span style="mso-spacerun: yes;">
</span><br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">9.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>So what next?<span style="mso-spacerun: yes;">
</span>I decided to start the vCenter service using the executable in
standalone mode.<span style="mso-spacerun: yes;"> </span>Open an administrative
command prompt and the run <i style="mso-bidi-font-style: normal;">vcdb –s</i>.<span style="mso-spacerun: yes;"> </span>Hmmm.<span style="mso-spacerun: yes;">
</span>Interesting error.<span style="mso-spacerun: yes;"> </span>Login failure
and it was related to a DSN, which is telling me SQL login failure.<span style="mso-spacerun: yes;"> </span>But the ODBC connections all tested positive.<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">10.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>So I did a registry search and each of the 3
databases all have a section with a DB entry in it.<span style="mso-spacerun: yes;"> </span>In that section I looked in there, and it
still had the old entry for the name in there.<span style="mso-spacerun: yes;">
</span>In the picture it is entry 2.<span style="mso-spacerun: yes;"> </span>So
I changed it.<span style="mso-spacerun: yes;"> </span>DANG IT, the service still
wouldn’t start. <br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">11.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>Well the line right below the username in the
registry is the password hash for the old username, in the picture it is entry
3.<span style="mso-spacerun: yes;"> </span>To change that password hash you have
to go back to that administrative command prompt and run the <i style="mso-bidi-font-style: normal;">vcdb –p</i> command and then enter the new
password twice.<span style="mso-spacerun: yes;"> </span>And now.<span style="mso-spacerun: yes;"> </span>BOOM the service starts.<span style="mso-spacerun: yes;"> </span>WOO HOO.<br />
<ol>
<li>
</li>
</ol>
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_0uMJGJsD-3qqttRlqN1YYppW5vcmqJU8AWOFh4iN0S-zHntdkR5n9Wu5Tp20kL5c5p_bKhiruOJYdGwYJF2PQKjpR9kgj8hNSWClQ331GLqQuQvsd2hCVUCVCdLtcsMSN_G3KsoTRPU/s1600/Reg+1+-+2015-07-08_10-15-06.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="441" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj_0uMJGJsD-3qqttRlqN1YYppW5vcmqJU8AWOFh4iN0S-zHntdkR5n9Wu5Tp20kL5c5p_bKhiruOJYdGwYJF2PQKjpR9kgj8hNSWClQ331GLqQuQvsd2hCVUCVCdLtcsMSN_G3KsoTRPU/s640/Reg+1+-+2015-07-08_10-15-06.jpg" width="640" /></a><br />
<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">12.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>So now let’s start the Update Manager
service.<span style="mso-spacerun: yes;"> </span>It fails.<span style="mso-spacerun: yes;"> </span>WTF.<br />
<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">13.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>This was pretty easy.<span style="mso-spacerun: yes;"> </span>I ran the Update Manager Utility and change
the database in there and it started up fine after that.<span style="mso-spacerun: yes;"> </span>Update Manager Utility is mentioned in KB
2011327, and it is located under Program Files (x86), because it is still a
32bit program, also have to update the ODBC32 as well.<span style="mso-spacerun: yes;"> </span>So start the service and it worked.<br />
<br />
<a href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2011327">http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2011327</a><br />
<br />
<a href="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhnMWekPsZVoYMcZ_9pZVZXeIgIxCagB9YITAQ3wPDOJQtCFfiSKTsJqy4ZAPo2EVddJpELmAuPFlj1AIhenan2OXIEY6bfJOb3oUQ2DunyzaLsMscC1yBkl3P8gk5e18S1XD9R5zj3LkE/s1600/Database+Update+Mgr+Util+-+2015-07-08_10-16-26.jpg" imageanchor="1" style="margin-left: 1em; margin-right: 1em;"><img border="0" height="518" src="https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhnMWekPsZVoYMcZ_9pZVZXeIgIxCagB9YITAQ3wPDOJQtCFfiSKTsJqy4ZAPo2EVddJpELmAuPFlj1AIhenan2OXIEY6bfJOb3oUQ2DunyzaLsMscC1yBkl3P8gk5e18S1XD9R5zj3LkE/s640/Database+Update+Mgr+Util+-+2015-07-08_10-16-26.jpg" width="640" /></a><br />
<span style="mso-no-proof: yes;"><br /></span>
<br />
<br />
<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">14.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>OK so now 2 of the 3 databases are connected and
running.<span style="mso-spacerun: yes;"> </span>Go to the SRM server and start
that service up.<span style="mso-spacerun: yes;"> </span>DANG IT, no go.<span style="mso-spacerun: yes;"> </span>On to troubleshoot that.<br />
<br />
<span style="mso-bidi-font-family: Calibri; mso-bidi-theme-font: minor-latin;"><span style="mso-list: Ignore;">15.<span style="font: 7.0pt "Times New Roman";">
</span></span></span>Went through several troubleshooting steps, and
actually worked with VMware technical support, but since nothing was really set
up in SRM we just did a full uninstall/reinstall.<span style="mso-spacerun: yes;"> </span>It wasn’t pretty and if there had been any
data on there I would have definitely taken the time to get it working, but…I
didn’t so this was the easy way out.
<br />
<div class="MsoNormal">
<br /></div>
<div class="MsoNormal">
So in a nutshell, it wasn’t as easy as I thought it would
be.<span style="mso-spacerun: yes;"> </span>But it is done, consulting is never
quite as easy as it seems, but I still enjoy it.</div>
VMTraininghttp://www.blogger.com/profile/00394084944990405832noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-17727037516956787292015-06-27T02:28:00.000-04:002015-06-27T02:28:10.084-04:00<h2>
ESXi 6.0 false positive warning: Deprecated VMFS volume(s)</h2>
<span style="font-family: Verdana, sans-serif;">I found and interesting problem on my newly upgraded host today. I received the warning:</span><br />
<br />
<span style="font-family: Verdana, sans-serif;"><span style="font-family: Courier New;">Deprecated VMFS volume(s) found on the host. Please consider upgrading volume(s) to the latest version</span> </span><br />
<br />
<span style="font-family: Verdana, sans-serif;">Which looks like this:</span><br />
<br />
<span style="font-family: Verdana, sans-serif;"><img alt="" src="data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAi4AAABuCAIAAACP7w/NAAATcklEQVR4nO2dMWsrPRaG/VP2N6T7XN0y7demvWBYtnW1F1x+pHThMiEL2S0uFwIJrKuASRo3YQmkCMSNixC4hED+gbaYGelI5xyNZuyxxs57eIpkPKM5ko7OK2kmzuATBoPBYLCsNrA//QsGg8FgsBzmSdHfYTAYDAbbuYVS9Mef/wAAAAB2CaQIAABAZiBFAAAAMgMpAgAAkBlIEQAAgMxAigAAAGQGUgQAACAzyVI0vn01xrzdfq+OfL/+bSpbzoqDl0vj7PX6NKWcP/78x+mDvejplBVuHi79QpS7zJ6YP8rBuD/qJcV9f/8ce26/Pjy9+p5Uzpd16ZbCf2Klz6QWxpjX68ufb7QxyzZczqozw0aO9Y4j3ry1ja/1pu+818thf3mXBzcqPferFh5MchIA0C0pUkRGu00BLn+d/nyzCfpyWY5wejBaTpUavCxAkmOZ7j1Vk+7iMlTdwbg/0Ut8V6sTZsUlv1/LQi6Xb79fxcTdBZK0K+ripLQQS3mu4CP0jnBrqXlrGj/am+7T4mDhgBg/xUGpqa3G0HYIDqY6CQDoluRVUTGGqxRAM1SR14JspaYwv5xYJn27/a4Uzu9Cc6v9WTwY96fmEprirefVDz8fykXG6/VtlR99nbZJ05bjrWmqPFi69LR88xqhsLAKUgPGK0vck3qkrnDxLvyOSY2v9KYaLcIRRYrGt6/GLB98SWYHWzgJAOiCllJUJkc2nkvKDCvNMYNUEmzFlMfLubCcfKW77EiKSseeTqlG2nw9ezIPl6cPv3+OXX50hTBvhd2/wg3aJkWxlRunD6xVww06InVSA9rdtnAPU9QbuXdKtixFQszQJZHmrb9BRxdYD5f+6lA4CCkCoCe0lKJALbwxbJNjJLvFU3+Z3J+W1S2EVZF/l11JkVURp0lk6WDlhEzVi08fLr9f/zYPtz/fzHJW6EE5kSdPYnwp8heg1LzWUBcueo5OlqJNxKZZlhdjRnRM9dbp1vfr3+Hq88/IQUgRAPlpLUUOb6ru5tHKkxJxVVQkyupnb6NGfOzB7rIzKSqSZrnHFT5vsKfRXaPTn2+lrL5en54+mEKQ2JMwtiqS9kIFontoYQWbbtBJvWM/3ZoUyTEjLYmi3lZ3uQwmScZ40xpy8PYUUgRAP9hYivjjk/jcVtxgebv9zh78hPNWe6F4l/TXFuL+JDzHrpYp1Uc1UuSfX6VdsuFGnslLUhSTCvnuQgc5tSPbhp7GkIdeYUX83pHOl5q3pkd8/3kV4vFGGqcSD6m/IvMYvLYAQJ9o+Aad8VNnYf5j4WDi+d3lDuW9W3KVnZN6u1Jixgzu8iedXEdf5q71p/bt3vo3Ly6FZQfdrwtkTKyI8n553bMiuwHo7PX61C4yqhYu6+5p/OxJqDLvHbbMUppX/VTYYAwbgbxrHo9D/2mWvISKSFFKdwMAugd/4gpKTh+iq6s9uQUAYB+BFIGCy2Xny4Id3AIAsJdAigAAAGQGUgQAACAzkCIAAACZgRQBAADIDKQIAABAZiBFAAAAMgMpAgAAkBlIEQAAgMxAigAAAGQGUgQAACAzMSn69u2b6bF9+/YtUrGzf/8XfJ0mitQ0u2+7r/IB13q/GqSHLvW2dnssRcaYwWAQaYgff52Br9NEWk0PrJopVT7sWu9Xg/TQpX7Wbr+lyOhqdADd3HW4HF4TiTU9vGrWVvnga71fDdJDl3pYu72XIqOo0a67+fzx/eNx1s/SOs7Rs+WnMcaY9a9dNnhyTbceCb2qr1jlLdd629HY9wbpoL69yFG9bfCikJZStBgPrI0XuxCcqKUloKv7j8/7c3fk14t5X179uFkbHnlNw5Gff/74bsz78orc3Qg3SixNdHKzcJFj5fzx3bVrSrZdPPcmKYs11YZEpSjGGC8qGtR3405RO71hycnxHw4cEp9pjiVgG1Yo3Iuu5OHQ3KVGM5LZ8tOLgW6kN8mlxqNPp1EI7Ta9iFmxlRStz46d/izGx2frdgKyVUtJQLPlJ2mFxXMkB21Fij4+37209Zla5k4Ggxor1a1ny0/zssji6hZrqkWCG3vnj88pGbnr+m5WcqIAt7lRo/PPH8uYtz900XoJ5SQ3yNX9x+fzC8kMnXVxvUtNR1+fSE4vclZsK0WB/Lgj1U/rs+Pj8fi4XDaVi6jinMhHdLlViJ07+fjYCaAnhqIa1eZZNxGwB88f3z/Wzx/GmM93O398WZCr3Lrq1ws5QQzf88f3j8dfpfhd3X983t+4c8LLC38K+3icOU9Y+fyjv8hkyvnJymfhUt9E9Ka0fKmhypHspnVVtLmT179858tG0NpErCltJaHiQk2laiqzkJjzhQ+uYd+XV36nL55tIAZxZcOGNkVYX7/Lgl6o8Sq5c3kXC6HIgseef7M2xjzfxALMrRrPH995JmXDhCbcXy9F4ZF4k9pqk2i3LolhH4vJeDC3danZ6Iv64IVfchenxptcwcT0ImbFdht067NjohZGkaJSXhbj8sSEj5wtxoPgZGMWY6JP8lIsmoBCLXFx77q8ylByaIZbfC6pKVI0K0ZmMSyF2ZbNiX5ydJ6QgR06aXeKru4/yqApK3WzdhHz0ihHi/MyVr7WUKQWLsUEJzvnbVLTmzSsaSAhzDGppjUDXugL0XnWEWy0C+HEpUiQQCmE3M9pXiV2bkr1efDYZE0ns3qAlbns43EW7kOEG3Tvyyu/c5V4jvfCJtHuPCRxGBmnicHc2qUWo0/zgU4gAme0Lk6PN72CaelFyIobvbZQKtJ4oayK/CMpHxm6LApOdvqkK5FTo7rII2NYyB0JUmSn5zVSVEys2DnB5cFerTyhjiQ4f3iTXCA2QqyJaGkuEFn5NQ1V26q2JVOalIzwoJXCvCbUNFWKapxnHVFbx/i18RBqWnJi54rV524EwVO2M9G8SIC5XGOeb9gUQWr5cP4UizelF1pHO2lAp5qRcZoYzK1daj/6JB/ooop3qJhw0iNZr2BNelGy4uZv0C3Gg/FiW1LkNt74yfboIqpExlRqFBuHTtVbSZGbISpZJiiWb7IFl28oRVpSqAuX+jxVe2RbUhRr0tpWijEYDNhBaYNux1IUD6ENpCjWuWJNAzd48JyXmyphLEkBRrSn2LH03RO77GZdbC6Fy8qU4bB5tNPEETRvYh+J86p2LrUffboUac6wLm4cb3oF69MLy4qtpIi+qVBIhZUQu5/WWorsAWFVVC3EEt7Z00fj1f3H5/sHmaylSJF7EstnHHVSJHZDcDnfoEuXIrc2P/tx/nh/c/bjZq2O6haDgZevNZS2um88iVOkKJQQ5phe0+CI9NpC3Pl4MiKO8UQmBkk8hKSSY16l54JIuqkW6NpOY/nG6V+xAPMetrtnS5HoKvvReFGkxZvUCxtEu79/qI+1mj5iwdzapfajTx9Q3Bm9i1PjLaGCTbW23aqIvspdCkX19sF4vNkGnV6O06LEt8e10Thbfoa7DVyK7HO5l8UP+/TyY/0cvLZgjzSczvAC2WsL6VLkTe6q3WTyqzISkgeDVL4sRfRMtv8ZHzmxJpU28VyOSK1pcMQ9kaauqs7HpYju5LAXMZQgYTFAQi6cCdV5lZ4LWJcJTgZN6t2uck9t9uCB9uLZSO/XsIbSHik9i1IUtFXLaA9br1SmyDhNl4F2LrUffXUbdEGHql2cPAoSKpiUXjaTonwWf0zErGanAtRu5hwQ0k5dB9C939x8nc7d3wbpoUtZardnUlS9V9fADrundxwu+053aiSssfrB1+nc/W2QHrq0+9rtmRS1s8Pu6V2GywGwo7VRn/g6nbu/DdJDl3Zcuy8hRQZqtKVwOQygRqCHDdJDl3ZZu68iRaZSowEsamiiAzZ0bmA9bJAeurRFi9UukKLcegGDwWCwL2eQIhgMBoNlNkgRDAaDwTIbpAgGg8FgmQ1SBIPBYLDMBimCwWAwWGaDFMFgMBgss0GKYDAYDJbZUqXo5T9/AwAAALqggRQZswYAAAC2DqQIAABAZiBFAAAAMgMpAgAAkBlIEQAAgMxAigAAAGQGUgQAACAzkCIAAACZgRQBAADIDKQIAABAZvolRavpUfFvzofTu+xNAwAAYDdsXYouRgNio4sm3lyMBoPBcLKqNKkDQSrcO5mbtdnsLnNaz+FklbsjAQBgf9muFBWJ/mi6auXNajJsrF5N8aRoU+YnzeUWAABAyDalSFtk2G0392mRxIdHQ7eqoMupo+nUZXlv/TEYjOaeBhSfjuaVkg0nq/nJYHAyL3717+sXdTIn5aQ56VfZlyJaOL/dcHonu23L8e/CSwMAgENlm1LkpVeLmH/LLD9ZiVpCr4pcLktRoRx03XM3HQ6qtZq/Kkq5S+CkUjUuw4Iw625T8RtO7zrbnwQAgD7SuRQJ038t9UtSRC9PkiIiQnShE5eiBk7SKkcXVeoyyy/Qd3JQnCBcCwAAh0vnG3S7lqJqg4s6Mx91LkXu10pOhCO6FAl6w0sDAIADpfvXFhrvsHlSxBQlbX+vOj6c3m26QZcuRQX85Qt7RHS7lBzlTYpdvMoBAACZ2cXL3IlbVfKzolJISJHztXzQlyLiydHQSRF1Ju21BUWKgpe553SfjbyPTo8odbFbi+7u0rUAAHCw9OtPXKMUeXxL72EDAADoDf2XIv8l73Z/sQQAAKDH9F+KAAAAHDiQIgAAAJmBFAEAAMgMpAgAAEBmIEUAAAAyAykCAACQGUgRAACAzHxVKVpNhj35FoOteXI3HbKvCJqfqH+MVX3HXfhtRrn8b1TObrqvP0GyR3526kyuwdKdk73qu6x0I0X+N9lsmuwakdi1wWner3fT4dF0Hn7523w0GAwnK79q5bc/kIONv0h7S7G4mh7JX1U3P5G+OuhitK2/F97Qf3v5DgZw/CqvZ6tu7WGa4F71ys/CmY5cyjJYmqaUbUVyXknbeVB1JkW2GqvJcJdq1E6KCvlZkY9Wk+HwZOQdPFLGGE3rF6OmX126nS6PSMvddMjafzUZbusrlA5JiuynRUrqVYrvrgv2yJlcg+ULStHO6V6Kgk6iX+FTpnuyeFpNhsPJdMRXGyTXk8UW+drQ4gT3faPD6Z1wOZ35+j23mh7Zb0Etrx1O5tXB+WgwmmrTvYtR7Hu17UfVac4HMvUOxNtpYVHTsl7s61OrepHZnGsTcsRfq5HvUvLWeWwpQHybVtcIX+HKJ+mswPDyEtJfo5PoXfzcUeNS2eZ+U/ixURO0F6PiHwGLcWt44LFm1zxnMZzSXF7hglfKTYPRxKvJIk3tX78oXn3x/GaR09PBoqWUYMhvFMkroUlrUll9bNe0pxAhdWFWO5z7L0VlQ5CUbQOIxkf1X8Cr6rHzxTmLqS4vliPu1vzyixGNjCCBViXMR04UVzQlOZ+pncztt3RL66GyNFe+86HcJYiMrqJx7BZ2OYR4vcj4IfE3H5H/hcH/k4VrJcmf0BNSi5qWlAoML5c8ke8S1pQMM9Ulcl+/KZJXRavpERmNuhu2bcN7RS4JYjihuYLC1WAWx1d0jq8NQ164WJQU1V48N4ucPRwsW4lkJRHFUllabEvtqUdIXZglDecN2KEU8SQezkOPpvNwZ08/n50TrI7jlws9V/TT3XToda33Pyzimzbivy9yCuemIaSCvs4FUcJrpGghmcr5/5BJqywvPPBH9CRyRLyXVmCKJ0pN5btwl6p8ql4lBq0YS6Ib4cn+vRI9T20uVriajuvGS23TicOQh31Qfa3MRpGzj4Nli5HcKJUlxjZvz1iEJIRZfRZtzw436CJ9HBkD8WIH/gMeLSC0Qei7PR8dTeeTYTAlsTFXK0VlLfjK/WRuLkbx1N9odDEHlC24hIlez6VIa+okKWJNUStFom/icR549F6JnjdrLr/wlOZqLUVTMtuVm5c/WE2Tojkrea8Hy7YiuWkqS41tvT3VLoiG2Z5LkV3ikbU5P014UMzODzY3yMnljooXIvxy97jSnU+ZnwwiO3iRAW9jVwn90eiETsTkPQf6hCMyuoR6kZXyajIqb+RexGBjj/oZ29cKPfF80FoyYccv8ER7RiXWlJfDTrb3DZuCpo9IKgmPxOLWNpF/L93zlA06lsi8wudaF0THF29wsX/dhlKd2Jjg1r4z6lWs5L0YLCylyBt0rSO5aSqLx3ZCe4rjSAmzhOGs3L0RO3iZmzymW03CdX2waOVzRr5orQ6M5u5fqRaPCosL3b8S55dXf0xDzydEnwqoExz6v1mlN3OCfnJeeVW2zwxL3yKTI14vN8LdI/GhC6y6BwbUn4gn9MJISyoV1LJP2V+0nFhNJf/Dk90A9psiiI0mOzO+Gyzw2L00z1kMJzSXX3ikC/j4kiatQv/aq+jiQC9KGHeBMxEBC0ru/2CRU4qQeTeJ5IapLBrbSe3Ju1UJs5Th3F8pSmSr67svTsO/KwKgIj4M+YbVtuiu5DowWHoIpOhg6PIPyMEBoy9Vten/JnRXchMwWHrHV/3iHwAAAL0BUgQAACAzkCIAAACZgRQBAADIDKQIAABAZiBFAAAAMgMpAgAAkBlIEQAAgMw0kCIAAACgC1KlCAaDwWCwjgxSBIPBYLDMBimCwWAwWGZrLEX/hMFgMMWQLmDtrI0UtVQ9GAx20MaTA9IFLNHaSNH/Hh8BACBAlKLsXoG94P8gSpiQMJQAsgAAAABJRU5ErkJggg==" /> </span><br />
<br />
<span style="font-family: Verdana, sans-serif;">Turns out simply restarting the management agents on the host will solve this issue. </span>For more information, see <a href="http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1003490" id="referLink_1003490" target="_blank">Restarting the Management agents on an ESXi or ESX host (1003490)</a>.<br />
<br />
This infomration comes from VMware KB Article 2109735.<br />
Click here to access it: <a href="http://kb.vmware.com/kb/2109735">http://kb.vmware.com/kb/2109735</a><br />
VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-56975679248948045292015-06-25T17:32:00.003-04:002015-06-25T17:34:52.299-04:00Unlocking and resetting the VMware vCenter Single Sign-On administrator password (vCenter 5.1, 5.5, 6.0)<span style="font-size: small;"><span style="font-family: Arial,Helvetica,sans-serif;">I ran across this KB article from VMware to resolve this issue caused by a locked SSO password. I am going to describe the solution specifically for vCenter 6.0 SSO. For vCenter 5.1 or 5.1, you can go to the KB article link at the bottom of this page to review the other options.</span></span><br />
<br />
<hr color="#293970" size="4" width="100%" />
<h2>
Symptoms</h2>
<ul>
<li><span style="font-family: Arial; font-size: 10pt;">You are unable to log in to the VMware vSphere Web Client using your single sign-on (SSO) administrator credentials.</span></li>
<span style="font-size: small;">
</span>
<li><span style="font-family: Arial; font-size: 10pt;">Logging in to the vSphere Web Client using your SSO administrator credentials fails.</span></li>
<span style="font-size: small;">
</span>
<li><span style="font-family: Arial; font-size: small;">The password is incorrectly entered three times (by default).</span></li>
<span style="font-size: small;">
</span>
<li><span style="font-family: Arial; font-size: 10pt;"><span style="font-size: small;">You see the error:</span><br /><br /><span style="font-family: Courier New;">User account is locked. Please contact your administrator.</span></span> </li>
</ul>
<hr color="#293970" size="4" width="100%" />
<h2>
Cause</h2>
<span style="font-size: 10pt;"><span style="font-family: Arial,Helvetica,sans-serif;">The SSO Administrator account is automatically locked after too many failed attempts, default is three.</span></span><br />
<br />
<hr color="#293970" size="4" width="100%" />
<h2>
Resolution</h2>
<span style="font-family: Arial;"><a href="https://www.blogger.com/null" name="6.0"></a><b><span style="font-size: small;">For VMware Platform Services Controller 6.0</span></b></span><br />
<ul>
<li><span style="font-family: Arial;"><span style="font-size: 10pt;">Wait for 5 minutes. By default, the account lockout policy is set to unlock after 15 minutes. For more information on account lockout policies for the Platform Services Controller (PSC), see<i> </i></span><span style="font-size: 13.33px;"><i>vCenter Server Password Requirements and Lockout Behavior</i> in the <a href="http://pubs.vmware.com/vsphere-60/topic/com.vmware.vsphere.security.doc/GUID-4BDBF79A-6C16-43B0-B0B1-637BF5516112.html" target="_blank">vSphere Security Guide</a></span><span style="font-family: Times New Roman;">.</span></span></li>
<li><span style="font-family: Arial; font-size: 10pt;">Unlock the account using another session that is still logged into the PSC server or using another user account with SSO administrator privileges.</span> <span style="font-family: Arial; font-size: 10pt;"><br /><br />To unlock an account using another session or using another user account with SSO administrator privileges:</span><ol>
<li><span style="font-family: Arial; font-size: 10pt;">Click <b>Home</b>.</span></li>
<li><span style="font-family: Arial; font-size: 10pt;">Click <b>Administration</b>.</span></li>
<li><span style="font-family: Arial; font-size: 10pt;">Click <b>Single Sign-On</b> > <b>Users and Groups</b>.</span></li>
<li><span style="font-family: Arial; font-size: 10pt;">Click the <b>Users </b>tab.</span></li>
<li><span style="font-family: Arial; font-size: 10pt;">Right-click the affected user account, such as</span><span style="font-family: Courier New;"> administrator@vsphere.local</span><span style="font-family: Arial; font-size: 10pt;">, and click <b>Unlock</b>.</span></li>
</ol>
</li>
<li><span style="font-family: Arial; font-size: 13px;">In emergency situations or if the default policies are changed, you can also reset the password to unlock the account. </span><br style="font-size: 13px;" /><br style="font-size: 13px;" /><span style="font-family: Arial; font-size: small;">To reset the </span><span style="font-family: Courier New; font-size: small;">administrator@vsphere.local</span><span style="font-family: Arial; font-size: small;"> password on a Windows Platform Services Controller or vCenter Server with Embedded Platform Services Controller:</span><ol><span style="font-size: small;">
</span>
<li style="font-family: Arial;"><span style="font-size: small;">Log in to the vCenter Server with a domain administrator account. If the Platform Services Controller is installed separate from the vCenter Server, log in to the Platform Services Controller server.</span></li>
<li style="font-family: Arial; font-size: medium;"><span style="font-size: 10pt;">Open an elevated command prompt. For more information, see </span><a href="http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1003892" id="referLink_1003892" target="_blank"><span style="font-size: 10pt;">Opening a command or shell prompt (1003892)</span></a><span style="font-size: 10pt;">.</span></li>
<li><span style="font-size: 10pt;"><span style="font-family: Arial;">Open the </span><span style="font-family: Courier New;">vdcadmintool</span><span style="font-family: Arial;"> service tool with this command:</span></span><span style="font-family: Courier New;">c:\> "%VMWARE_CIS_HOME%\vmdird\vdcadmintool.exe"</span><br /><span style="font-family: Arial;"><span style="font-size: 10pt;">This console loads:</span></span><br /><br /><span style="font-family: Courier New;">===============================<br />Please select:<br />0. exit<br />1. Test LDAP connectivity<br />2. Force start replication cycle<br />3. Reset account password<br />4. Set log level and mask<br />5. Set vmdir state<br />===============================</span></li>
<li style="font-family: Arial; font-size: medium;"><span style="font-size: 10pt;">Press 3 to enter the <b>Reset account password</b> option. </span></li>
<li><span style="font-family: Arial; font-size: 10pt;">When prompted for the <b>Account UPN</b>, enter:</span><br /><span style="font-family: Courier New;">Administrator@<i>vSphere_Domain_Name.local</i></span><br /><span style="font-family: Arial; font-size: 10pt;"><br />By default, this is:<br /><br /><span style="font-family: "Courier New"; font-size: small;">Administrator@vSphere.local</span><br /><br />A new password is generated.<br /><b>Note</b>: if you customized your vSphere Domain name, provide the customized domain name.</span></li>
<li><span style="font-family: Arial; font-size: 10pt;">Use the generated password to log in to the </span><span style="font-family: Courier New;">administrator@vSphere.local</span><span style="font-family: Arial; font-size: 10pt;"> account.</span></li>
<li style="font-family: Arial;"><span style="font-size: 10pt;">After the password is regenerated, log in to the vSphere Web Client and change the password.</span></li>
</ol>
</li>
</ul>
<blockquote dir="ltr" style="margin-right: 0px;">
<div align="left">
<span style="font-family: Arial;">To reset the </span><span style="font-family: Courier New;">administrator@vsphere.local</span><span style="font-family: Arial;"> password on the Platform Services Controller or vCenter Server with Embedded Platform Services Controller Appliance:</span></div>
</blockquote>
<ul><ol>
<li>Log in to the vCenter Server Appliance via SSH.</li>
<li>Run this command to enable access the Bash shell:<br /><br /><span style="font-family: Courier New;">shell.set --enabled true</span></li>
<li>Type <span style="font-family: Courier New;">shell</span> and press Enter.</li>
<li><span style="font-family: Arial; font-size: 10pt;">Open the <span style="font-family: "Times New Roman";"></span><span style="font-family: "Courier New";">vdcadmintool</span> service tool with this command:</span><br /><span style="font-family: Courier New;">/usr/lib/vmware-vmdir/bin/vdcadmintool</span><span style="font-family: Arial; font-size: 10pt;">This console loads:</span><br /><span style="font-family: Courier New;">================================<br />Please select:<br />0. exit<br />1. Test LDAP connectivity<br />2. Force start replication cycle<br />3. Reset account password<br />4. Set log level and mask<br />5. Set vmdir state<br />================================</span></li>
<li style="font-family: Arial;"><span style="font-size: 10pt;">Press 3 to enter the <b>Reset account password</b> option.</span></li>
<li><span style="font-family: Arial; font-size: 10pt;">When prompted for the <b>Account UPN</b>, enter:</span><br /><span style="font-family: Courier New;">Administrator@<i>vSphere_Domain_Name.local</i></span><br /><span style="font-family: Arial; font-size: 10pt;"><br />By default, this is:<br /><span style="font-size: small;"><br /><span style="font-family: "Courier New";">Administrator@vSphere.local</span></span><br /><br />A new password is generated.<br /><b><br />Note</b>: if you customized your vSphere Domain name, provide the customized domain name.</span></li>
<li><span style="font-family: Arial; font-size: 10pt;">Use the generated password to log in to the </span><span style="font-family: Courier New;">administrator@vSphere.local</span><span style="font-family: Arial; font-size: 10pt;"> account.</span></li>
<li style="font-family: Arial;"><span style="font-size: 10pt;">After the password is regenerated, log in to the vSphere Web Client and change the password.</span></li>
</ol>
</ul>
<br />
<hr color="#293970" size="4" width="100%" />
<b>KB 2034608</b>: <a href="http://kb.vmware.com/kb/2034608">http://kb.vmware.com/kb/2034608</a> VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com2tag:blogger.com,1999:blog-6953418073842157155.post-89761173701554158252015-05-29T11:26:00.002-04:002015-05-29T11:28:15.549-04:00Free alternative for backing up VM's for ESXi<strong>William Lam</strong> of <a href="http://virtuallyghetto.com/">VirtuallyGhetto.com</a> long ago created a free alternative backup solution for ESXi. It is distributed as a simple script. It was developed over 8 years ago for ESX 3.x and continues to be added to and modified today.<br />
<br />
Just yesterday William added a post on his site that it is now available in a self installable VIB format. One of the great things about the VIB is that the program persists now through reboots of ESXi.<br />
<br />
The original page for the script <strong>GhettoVCB</strong> is here: <a href="https://communities.vmware.com/docs/DOC-8760">https://communities.vmware.com/docs/DOC-8760</a><br />
<br />
To read more about the latest updates from William and to get to his links for downloading the VIB & offline bundle, click here: <a href="http://www.virtuallyghetto.com/2015/05/ghettovcb-vib-offline-bundle-for-esxi.html">http://www.virtuallyghetto.com/2015/05/ghettovcb-vib-offline-bundle-for-esxi.html</a>VMGuru1http://www.blogger.com/profile/15123186747483299279noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-16964572799621385662015-03-03T00:42:00.000-05:002017-04-06T11:47:34.772-04:00Active Directory - Fine-Grained Password PolicySo I have been doing quite a bit of consulting lately and thought I would document some of the more interesting tasks that I run across. In the last couple of weeks I have dealt with software deployments through GPO and KACE boxes. Exchange Troubleshooting, VMware Performance troubleshooting, and several other things. <br />
<br />
Got the opportunity to finally implement Fine-Grained password policies. For those of you that don't know what that is, by default using an AD domain you set one password policy at the domain level and everyone inherits that. So what if you want to set different policies on different OUs? No big deal create a couple of GPOs with the policies that you want and apply them to the correct OUs - WRONG!!! That doesn't work. You can't set password policies on an OU. You have to set up what they call Fine-Grained Password Policies. <br />
<br />
I found a pretty good TechNet article that pointed me in the right direction. The problem with a lot of Microsoft's direction is that they point you in the right direction and you are in Los Angeles and want to go to NYC and they say go East. Now it is on you to figure out how to get there. This article was exactly that way. It left out lots of switches and several other things to make sure it was working correctly.<br />
<br />
<a href="https://technet.microsoft.com/en-us/library/cc754461(v=ws.10).aspx">https://technet.microsoft.com/en-us/library/cc754461(v=ws.10).aspx</a><br />
<br />
As I have started to delve more and more back into the Microsoft world I have really come to empower PowerShell quite a bit more than ever. It started with Exchange where I did a complete migration from Exchange 2010 to Exchange 2013 via PowerShell from Setup to migration to tear down. Maybe I was bored, maybe I was trying to be cool (As much as computer dorks can be cool).<br />
<br />
So I accomplished a lot of this task using PowerShell. The concept is pretty Easy. You have to create what is called a PSO (Password Setting Object). You create this by using the <strong>New-ADFineGrainedPasswordPolicy </strong>cmdlet. You then have to specify things like MaxPasswordAge, MinPasswordAge, and a few other parameters. Not all that hard. <br />
<br />
Once you create the PSO you can view it using ADSI Edit under the Password Settings Container. You can also modify settings from here if needed. Once you have gotten this far, it still doesn't work. Now, you have to assign who is going to have this policy applied to them. <br />
<br />
You would think that you can apply this to an OU, but you would be wrong. You have to create a Domain Security Group and then grant that group permissions to the PSO. Now you would think just go to properties and the security tab add it in and you are done. You are wrong. You have to go to ADSI Edit, go to that Password Settings Container and locate the PSO you just created. Click Properties and then click the Attribute Editor tab. Look for the <strong>msDS-PsoAppliesTo</strong> attribute. You then enter the full DN (Distinguished Name) of the Global Security Group.<br />
<br />
After that add users to the Group and you are good. <br />
<br />
So how do you test. Well I picked a user (the wrong user) and added him to the group, we then did a bunch of restarts and nothing. So I found out after some prodding that he changed his password last week but didn't think that would count. So I checked his expiration date. It showed a really long number. Now I had no clue what that number meant. It showed a regular date in the viewing box but when you tried to modify it (which you couldn't) it showed this long number. <br />
<br />
So what does that long number mean out of curiosity I looked it up. This attribute is Integer8, a large 64-bit number that represents a date as the number of 100-nanosecond intervals since 12:00 AM January 1, 1601. 1601??? Wow, not quite sure why that number but OK.<br />
<br />
Anyway I found a user whose password expired about 2 months ago (He had the password never expires on him, which I had to deselect to see this value). I added him to the group and did a restart and he had to change his password. It worked like it should. So for those of you that want to accomplish this, it isn't really difficult, just play around in a test network like your customers production machines and play around.VMware Dudehttp://www.blogger.com/profile/10984544298643970297noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-10988735463051041832014-03-24T16:56:00.002-04:002014-03-24T16:56:56.464-04:00Exchange 2013 Ultimate Bootcamp<span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">We are excited to announce the
arrival of a new class from VMTraining. Although this now means more work
for me. The class has taken many months in the design and implementation
to get the class ready. We did our first delivery last week and it
was a success. We only did a limited run to 10 students while the course
was in beta.</span></span>
<br />
<br />
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><br /></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">The premise for the course is the
following. How to properly run Exchange 2013 while running in a VMware
environment.</span></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><br /></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">For those that don't know me I don't
teach much any more, I primarily do consulting. I have been an
Exchange consultant and Trainer for almost 18 years now. I have done
Exchange migrations and/or implementations for some of the largest companies in
the world to include SanDisk, PepsiCo Bottling Ventures, Yahoo, Smith &
Nephew, American Kennel Club, BB&T Bank, Capital Broadcasting Company, and
many more.</span></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><br /></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">The idea for this class came when I
was talking with one of my Exchange trainer friends. We were talking
about how most of the implementations are being rolled out on VMware and we
were talking about some of the configurations that must be done to make it work
correctly. Needless to say he was unaware of any of these changes.
So here is a guy who has trained hundreds if not thousands of Exchange students
and 85% of them are running on VMware however they have no clue how to truly
configure it. </span></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><br /></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">It made me wonder. Why are
people taking classes using Microsoft Official Curriculum (MOC) and it is built
on top of Hyper V when their environments are running on VMware? The
answer. There are no other options out there. When you are taking a
MOC class it is the same whether you take it from Global Knowledge, or New
Horizons or any other school. Your sole basis of buying the class is
based upon price. Schools will argue how much experience and how great
their trainers are, but ask them what they have done. As someone told me
before trainers train, they don't consult. </span></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><br /></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">So here were numerous issues that we
have addressed with our class.</span></span></div>
<ol>
<li><span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">We built our Exchange 2013
class on VMware vSphere 5.5. We talk about how to configure storage,
SANs, virtual and physical networking, backups, deployments, antivirus, and
much more in a VMWare environment.</span></span></li>
<li><span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Our class is being taught
with real world consultants. So we are actually doing this not just
talking about it. I finished the first class on Friday and Monday I have
a meeting with a customer to actually upgrade their Exchange 2010 servers to
Exchange 2013.</span></span></li>
<li><span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Labs. I believe
that a student learns by doing, so we currently have 38 labs in our class,
compared to 11 in the MS 20341 Core Solutions of Exchange class. By the
next class we will have at least 45 and my goal is over 50 high quality labs on
live real equipment not on some desktop. </span></span></li>
<li><span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Lab Access. Our labs are
available to you 24 x 7 during class. However, we have tons of labs and
you might want to go through them more than once to reinforce learning new
concepts. We make our lab environment available to you after class so
that you can continue to work on labs. Also when new labs become
available we let you have access to these. Your learning doesn't stop on
the last day of class.</span></span></li>
<li><span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Third party tools
integration. We also talk about integration with products like Symantec
Enterprise Vault (ask some of those trainers if they even know what that is
without googling it). We talk about complex backups using various
scenarios and backup software like Commvault, Netbackup, Veeam, and many
others. How do you want to handle things if you are running a SAN
like Netapp. How are you going to manager SNAP drive, SNAP Mirror,
Flexclones, and much more. Is that darn BES thing still
around? How do you implement that with Exchange? How about if I
want to implement Mimecast?</span></span></li>
</ol>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Someone asked me a question.
"I am not running Exchange on VMware, so I guess this class isn't for
me" Absolutely not!!! yes, we built this class with an
emphasis of running it on VMware but we also talk about Hyper V and Physical.
So if you want the best Exchange class in the world we believe we have
that. If you want the ONLY class running and teaching on VMware we are
that.</span></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><br /></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">Another question I got was "I
found an Exchange class from new Horizons for $2200 and that is cheaper than
yours." My response. "Shop around I guarantee you that
you could get it for under $2000." We aren't competing against them
on price, because we don't have an equivalent product. The same way a
Ferrari doesn't compete with a Ford Pinto. </span></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><br /></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">So you have to ask yourself if you
are in the market for a class, do you want to settle for a mediocre class from
a MS training center or pay a tad bit extra to get all of these benefits.</span></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><br /></span></div>
<div class="MsoNormal" style="line-height: normal; mso-margin-bottom-alt: auto; mso-margin-top-alt: auto;">
<span style="font-family: Arial,Helvetica,sans-serif;"><span style="font-size: 12.0pt; mso-fareast-font-family: "Times New Roman";">I hope to see you in a future class.</span></span></div>
VMTraininghttp://www.blogger.com/profile/00394084944990405832noreply@blogger.com0tag:blogger.com,1999:blog-6953418073842157155.post-15567227760239853912013-09-13T10:41:00.000-04:002013-09-13T10:41:01.381-04:00Top 10 vSphere 5.5 ImprovementsAttending VMworld this year was very exciting, the release of their NSX product for true virtualization of the network was amongst its biggest announcements. I am looking forward to see this product in action, I believe we will see some very sold security mitigation techniques stem from this deployment, not to mention the ease of network implementation! We will discuss this in more detail in a future blog. Today we are going to look at the top 10 improvements in the upcoming release of vSphere 5.5, here they are:<br />
<br /><b>1. vSphere Web Client Improvements</b><br />Why did I choose this for our #1? With the push to the web Client from VMware many of us were dealing with a slow interface that decreased our ability to get work done! I do not know about you but I really do not want to spend even an extra 15 minutes a day at work just because I am waiting! This new interface is fast in comparison and I do not feel like I am waiting, which was not the case in previous versions. This new web client has some additional filtering and navigation features and had the ability to manage the new 64TB VMDK (Yes it is really only 62TB). <br /><b>2. Single Sign On (SSO) Improvements</b><br />The new release of SSO is easier to understand and use, I think you will actually like it now! It still provides a great resource for multiple authentication sources! Surprisingly it provides upgrading from 5.0 to 5.5!<br /><b>3. vApp HA Additions</b><br /> vSphere 5.5 can now monitor applications you have running inside the VM! No need for a 3rd party tool now. I like the idea and in testing it works well, I am not 100% convinced yet but I will try this with clients on non-critical systems until I am confident in the results. <br /><b>4. vSAN is now available</b><br />Software Defined Storage is one of the new hot topics and VMware is attempting to lead the pack, however there are other hardware vendors that have a similar implementation that has worked well. However I like where they are headed, I will need a lot more testing before I am ready to use this in any production environment but there are some details. This feature is enabled on the host and will provide redundant, supported storage across a maximum of 8 hosts. VMware states the primary use cases will be VDI, test/dev, big data, and a disaster recovery target. vSAN functionality will be sold as a standalone offering. The vSAN beta is in public beta and available at vSANbeta.com.<br /><b>5. Flash Read Cache Solution Added</b><br />As expected server-side, host-based caching was a hot topic this year and VMware how their own solution. It requires local SSD on every host that has this feature enabled and support vMotion, HA, DRS and other features of vSphere. The virtual machines and applications are not aware of the Flash Read Cache similar to other implementations of features in vSphere like Transparent Page Sharing. This solution will provide a nice performance boost with read intensive solutions like VDI. <br /><b>6. vCenter Multi-Hypervisor Manager (MHM)</b><br />Surprise, Surprise, vSphere now supports managing a Windows 2012 Hyper-V host! I did not see this one coming, however it does makes sense. With the improvement of the latest version of Hyper-V there are many companies wondering what they should do for the future. With this latest release VMware is at least making it possible for the users to continue working in their well known and loved vCenter. You can even perform a cold migration from Hyper-V to vSphere! <br /><b>7. vCSA improvements</b><br />VMware has stated on many occasions that they are likely to dump the windows version of vCenter, personally I think this will be a huge mistake, but before that can even happen they must prove to the world that the vCenter Server Appliance is going to be a viable option. One that is easy and error free! The latest release allows us to manage 500 hosts and 5000 virtual machines with the embedded database! Yes you read that correctly, the embedded database can handle 500 hosts and 5000 virtual machines! Ready to give it a whirl? No need for a costly sql or oracle server, just download the applicane, run through the basic setup and you are ready. Another key item of note with the vCSA is that there is a new vSphere Update Manager plugin for the vSphere Web Client!<br /><b>8. vSphere replication improvements</b><br />
VMware continues to improve its replication solution, the current improvements to the per-VM replication include compatibility with Storage vMotion and Storage DRS along with the ability to have multiple point in time recovery options. You can now have up to 10 appliances per vCenter server which allows for more freedom in your design and lowers the overall cost of vCenter purchases. Site Recovery Manager is updated to support these features as well. <br /><b>9. vCenter Orchestrator Additions</b><br />
VMware views Orchestrator as a key component moving forward in the migration to the cloud and they have improved its scalability and availability to allow for that planned migration. It also added features which include a workflow debugger, health check, and auto-alerts<br /><b>10. vCloud Director New Features</b><br />VMware has already announced that vCloud Director 5.5 will be the last release, choosing to migrate to vCloud Automation Center (vCAC) instead. But that did not stop them from improving upon the functionality of this release. It is now sold as part of the vCloud Suite. So what have they done? Added many features related to the vApp lifecycle management such as Open Virtualization Format (OVF) import and export, the option to add or modify virtual hardware that was created from a template, and the ability to clone a VM while preserving its memory state. There are many more but that will have to come in a later blog. <br />Unknownnoreply@blogger.com1tag:blogger.com,1999:blog-6953418073842157155.post-7069965065097971172013-08-26T17:21:00.001-04:002013-08-26T17:23:47.200-04:00VMworld 2013<b><a href="http://www.vmworld.com/" target="_blank">VMworld2013</a> - what an amazing start! </b><br />
<br />
Over 20,000 attendees all in one place teaming about the latest innovations in virtualization. They have announced the release of version 5.5! We were initially disappointed that they only released vSphere version 5.5 instead of version 6 as we were hoping for another great jump with this next release. THEN they announced VMware NSX which is network virtualization similiar to ESX for servers; we now have a proper hypervisor for the network! This is going to simplify the setup and management of datacenter networks, which will make things much easier! Check back, there will be additional updates coming.VMTraininghttp://www.blogger.com/profile/00394084944990405832noreply@blogger.com0