<?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>tanmic Tracker</title>
    <link>https://communities.vmware.com/wbsdv95928/tracker</link>
    <description>tanmic Tracker</description>
    <pubDate>Sat, 25 Nov 2023 11:02:06 GMT</pubDate>
    <dc:date>2023-11-25T11:02:06Z</dc:date>
    <item>
      <title>Re: New virtual machine, reboot, no network...</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/New-virtual-machine-reboot-no-network/m-p/822336#M58461</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks I'll get somebody to check into that.  Forgot to mention that there is no DHCP and that the IPs are manually setup.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 May 2010 17:14:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/New-virtual-machine-reboot-no-network/m-p/822336#M58461</guid>
      <dc:creator>tanmic</dc:creator>
      <dc:date>2010-05-31T17:14:23Z</dc:date>
    </item>
    <item>
      <title>New virtual machine, reboot, no network...</title>
      <link>https://communities.vmware.com/t5/ESXi-Discussions/New-virtual-machine-reboot-no-network/m-p/822334#M58459</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I've been given the task to figuring out an issue on why a virtual machine, whether it's one brought over from an older ESX server, or even a newly created VM using Win XP SP3, has issues with the network.  (A bit of background - I'm not too familiar with ESX other than having the ability to create VMs, convert to templates and create machines from templates).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The issue is that when the machine is shutdown then powered back up, the virtual machine is not able to ping the network nor can we see the virtual machine if we try and ping it.  If i go to vmware tools and disable nic 1 then re-enable it after a few seconds, then the machine can see the network and I can ping it.  Reboot it, most of the time it works, but if I shut it down and restart it, we lose it again.  I've tried everything from using a different NIC (vmxnet 2, vmxnet 3, flexible), uninstalling/installing vmware tools, etc and can't seem to resolve this.   I've been told by the folks that has setup this environment, the network configuration on the backend is all okay. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The version ov vmware vcenter server is 4.0.0 build 20811. Version of the ESX is 4.0.0 build 236512.  I do have a support case opened with vmware but not making any real progress at this time, so if anybody has suggestions on what to look for, let me know.   &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance...&lt;/P&gt;&lt;P&gt;Mike &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 31 May 2010 15:53:03 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ESXi-Discussions/New-virtual-machine-reboot-no-network/m-p/822334#M58459</guid>
      <dc:creator>tanmic</dc:creator>
      <dc:date>2010-05-31T15:53:03Z</dc:date>
    </item>
    <item>
      <title>Re: 4.0.4 and Win7 64-bit</title>
      <link>https://communities.vmware.com/t5/ThinApp/4-0-4-and-Win7-64-bit/m-p/1599599#M3813</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;It's pretty well any file dialog, 99% of the time it'll crash.  Same thing if I have a virtualized WinZip and go to the Extract To in the file menu, it'll crash and the workaround is to drag and drop the file to the destination.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Nov 2009 18:53:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/4-0-4-and-Win7-64-bit/m-p/1599599#M3813</guid>
      <dc:creator>tanmic</dc:creator>
      <dc:date>2009-11-25T18:53:00Z</dc:date>
    </item>
    <item>
      <title>4.0.4 and Win7 64-bit</title>
      <link>https://communities.vmware.com/t5/ThinApp/4-0-4-and-Win7-64-bit/m-p/1599596#M3810</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Aware that 4.0.4 will not function properly with win7 completely but the option is there so I decided to try out Firefox 3.5.5.  Created a couple packages, one on XP SP2 32-bit and another on Win 7 64-bit and the results have been the same when running the virtualized package on Win 7 64-bit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When trying to attach a file to a message in gmail for example, when it opens the file dialog window, it crashes.  Any pages with Flash content will also crash the browser.  Plus it'll crash from time to time for no reason at all (haven'tdone any logging at this time).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm sure there are more issues but at least it's something we can experiment with until full support comes later next year.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Nov 2009 16:29:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/4-0-4-and-Win7-64-bit/m-p/1599596#M3810</guid>
      <dc:creator>tanmic</dc:creator>
      <dc:date>2009-11-11T16:29:14Z</dc:date>
    </item>
    <item>
      <title>Re: 6.5.3 and bridged networks</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/6-5-3-and-bridged-networks/m-p/824492#M43672</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nobody?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 10 Oct 2009 17:07:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/6-5-3-and-bridged-networks/m-p/824492#M43672</guid>
      <dc:creator>tanmic</dc:creator>
      <dc:date>2009-10-10T17:07:23Z</dc:date>
    </item>
    <item>
      <title>6.5.3 and bridged networks</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/6-5-3-and-bridged-networks/m-p/824491#M43671</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Been using the second latest and greatest version and decided to upgrade to 6.5.3 (running on Vista 64-bit with the latest SP).  Well, I have a couple virtual machines where I use a bridged network vs NAT and none of them work anymore with bridged... occurs with both XP and Win7.    I also had problems where the network adapter was not found and in some cases adding the ethernet0.virtualDev = "e1000" helped with Win7 but not Win XP.  So after messing around with things for hours and hours trying to get it to work, I decided to uninstall and go back to 6.5.2 which did correct the bridged network issue I was wrestling with.  Note though 6.5.3 hung during the uninstall at the point where it was modifying the network configuration.  Trying to kill the task didn't work so I had to reboot and then clean up some things manually before 6.5.2 would install.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; Anybody run into this problem? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 03 Oct 2009 15:21:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/6-5-3-and-bridged-networks/m-p/824491#M43671</guid>
      <dc:creator>tanmic</dc:creator>
      <dc:date>2009-10-03T15:21:40Z</dc:date>
    </item>
    <item>
      <title>Host loses ability to see network drives eventually when VMWorkstation in use</title>
      <link>https://communities.vmware.com/t5/VMware-Workstation-Pro/Host-loses-ability-to-see-network-drives-eventually-when/m-p/2491145#M149279</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So here's an issue that I've never been able to figure out and have to adjust how I do work on this one particular machine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm using VMware Workstation 6.5.2-build 156735 and the problem also existed on the previous build.  I know there's a newer build but suspect that the issue will still be around (yes I know, I could upgrade and then see if the problem is still around or not).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I'm running WinXP within the VM (with a bridged network configuration to the host), if I do a fair bit of data copying back and forth to a network share (in this case, it's to a QNAP TS-406 NAS), eventually the host will lose all ability in accessing any shares.  Whatever process running on the host that is either read/writing to that share will freeze and I can't kill it and the only way to get things 'fixed' is to reboot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now, from within the VM, I can still map to these shares and transfer data to and from the share so I know that it's not the NAS that is at fault.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anybody seen this before?  The host machine is Vista with all of the patches.  I'm suspecting that it's some network binding that has gone awry but I can still ping the NAS just fine from the host. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 25 Sep 2009 18:12:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Workstation-Pro/Host-loses-ability-to-see-network-drives-eventually-when/m-p/2491145#M149279</guid>
      <dc:creator>tanmic</dc:creator>
      <dc:date>2009-09-25T18:12:40Z</dc:date>
    </item>
    <item>
      <title>Question on ChildProcessEnvironmentDefault</title>
      <link>https://communities.vmware.com/t5/ThinApp/Question-on-ChildProcessEnvironmentDefault/m-p/213361#M21</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have a build of Firefox with this option enabled and when I click on a link that goes to a Word doc, it asks me whether I want to open it in Word or not.  When I chose to have Word open it, I can see that the document does get saved to the temp folder (not in the sandbox as I have this folder set to merged) then the MS Installer runs and fails and Word never starts up to open the document.  If I have Word running already, same problem.  I do have Office installed on the worsktation.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anybody suggest what I'm doing wrong?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 08 Jul 2009 15:55:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Question-on-ChildProcessEnvironmentDefault/m-p/213361#M21</guid>
      <dc:creator>tanmic</dc:creator>
      <dc:date>2009-07-08T15:55:40Z</dc:date>
    </item>
    <item>
      <title>Use of xcopy...</title>
      <link>https://communities.vmware.com/t5/ThinApp/Use-of-xcopy/m-p/194734#M12</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My sandbox got corrupted so I'm trying to manually copy files back into the sandbox using the virtualized command prompt.  I noticed that if I try and use xcopy (as the files I want to copy back into the sandbox are in multiple folders), xcopy is unable to create the folder.  Same issue with robocopy.  I even tried to use Windows Explorer (launched from within the virtualized environment) and copy something from C:\TEST (which resides on the actual file system) to %appdata%\TEST on a Vista machine, nothing happens.  Note that the same Explorer is being used to copy and paste.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Anybody know of another workaround? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Jun 2009 14:37:19 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Use-of-xcopy/m-p/194734#M12</guid>
      <dc:creator>tanmic</dc:creator>
      <dc:date>2009-06-25T14:37:19Z</dc:date>
    </item>
    <item>
      <title>Re: New version 4.0.3 of ThinApp released</title>
      <link>https://communities.vmware.com/t5/ThinApp/New-version-4-0-3-of-ThinApp-released/m-p/2122566#M5353</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Still crashes with Win7 - expected as support will come later.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tried the latest 4.03 with the hp ServiceDesk  to see if it resolves a bug that was introduced with 4.0.2 - it's still broken unfortunately.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jun 2009 12:57:39 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/New-version-4-0-3-of-ThinApp-released/m-p/2122566#M5353</guid>
      <dc:creator>tanmic</dc:creator>
      <dc:date>2009-06-24T12:57:39Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent ThinApps being copied</title>
      <link>https://communities.vmware.com/t5/ThinApp/Prevent-ThinApps-being-copied/m-p/258909#M46</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Just tried this... seems that for the next version, any change to c:\program files\thinstallplugins should be ignored and that the original files always be maintained to workaround this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Jun 2009 16:59:25 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Prevent-ThinApps-being-copied/m-p/258909#M46</guid>
      <dc:creator>tanmic</dc:creator>
      <dc:date>2009-06-15T16:59:25Z</dc:date>
    </item>
    <item>
      <title>Re: Prevent ThinApps being copied</title>
      <link>https://communities.vmware.com/t5/ThinApp/Prevent-ThinApps-being-copied/m-p/258907#M44</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can just drop a vbscript in your project folder before compiling.  The vbscript can check for the IP address, or some other file/registry key that would be present on these machines and if these conditions are not met, the script would tell thinapp to quit and not run the program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I use this myself - a script to check to see if the evaluation period has expired and if a specific registry key and/or environment variable is not present.  If both of thes conditions aren't met then the process quits byusing ExitProcess.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Jun 2009 13:21:02 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/ThinApp/Prevent-ThinApps-being-copied/m-p/258907#M44</guid>
      <dc:creator>tanmic</dc:creator>
      <dc:date>2009-06-15T13:21:02Z</dc:date>
    </item>
  </channel>
</rss>

