<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Change a complete install to a typical install in ESXi Discussions</title>
    <link>https://communities.vmware.com/t5/ESXi-Discussions/Change-a-complete-install-to-a-typical-install/m-p/929722#M79382</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm running esxi 5.5. I have templates set up for various OS's and those have vmware tools on them as a typical install. One of my colleagues decided to do complete installs of vmware tools, which installs the vsepflt filter which then hangs and blue screens the guest machine. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2077302" title="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2077302"&gt;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2077302&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We went in and disabled it on all the affected vms, and everything is functioning now, but I have vmware tools set up to auto-update on reboot in an attempt to keep them semi up to date anyway. When this update happens it detects the complete install, re-installs the vsepflt filter and enables it again. Server then proceeds to bluescreen and hang. The KB article claims this was fixed in 5.5 U2, but that's just not true.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, my questions is, can I fool the installer into thinking a typical install was done rather than a complete install by maybe a registry key change or something like that, rather than having to reinstall vmware tools using the typical install? It's about 80 machines, and rebooting them is a pain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any suggestions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 13 Nov 2014 13:05:20 GMT</pubDate>
    <dc:creator>mdonovan</dc:creator>
    <dc:date>2014-11-13T13:05:20Z</dc:date>
    <item>
      <title>Change a complete install to a typical install</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/Change-a-complete-install-to-a-typical-install/m-p/929722#M79382</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi all&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm running esxi 5.5. I have templates set up for various OS's and those have vmware tools on them as a typical install. One of my colleagues decided to do complete installs of vmware tools, which installs the vsepflt filter which then hangs and blue screens the guest machine. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2077302" title="http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2077302"&gt;http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&amp;amp;cmd=displayKC&amp;amp;externalId=2077302&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We went in and disabled it on all the affected vms, and everything is functioning now, but I have vmware tools set up to auto-update on reboot in an attempt to keep them semi up to date anyway. When this update happens it detects the complete install, re-installs the vsepflt filter and enables it again. Server then proceeds to bluescreen and hang. The KB article claims this was fixed in 5.5 U2, but that's just not true.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, my questions is, can I fool the installer into thinking a typical install was done rather than a complete install by maybe a registry key change or something like that, rather than having to reinstall vmware tools using the typical install? It's about 80 machines, and rebooting them is a pain.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any suggestions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Matt&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Nov 2014 13:05:20 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/Change-a-complete-install-to-a-typical-install/m-p/929722#M79382</guid>
      <dc:creator>mdonovan</dc:creator>
      <dc:date>2014-11-13T13:05:20Z</dc:date>
    </item>
  </channel>
</rss>

