TobyFruthParson's Posts

If your application will allow, install it to the root of C:\ during the capture. For example, if your app typically installs to C:\program files\ , try changing it to c:\myapp (or whatever yo... See more...
If your application will allow, install it to the root of C:\ during the capture. For example, if your app typically installs to C:\program files\ , try changing it to c:\myapp (or whatever you like, but I usually try to keep the location name 8 characters or less.)
By the way, Help opens in Project 2010 ThinApp on same Win2008R2 server where Visio 2010 ThinApp Help does not open.  Also, I have both apps running simultaneously, no activation issues.
Lakshman, I was told Visio 2010 needs to be captured online and activated (opened).  I am using the new hotfix and the reg entries and I have no activation errors. I did have a couple of in... See more...
Lakshman, I was told Visio 2010 needs to be captured online and activated (opened).  I am using the new hotfix and the reg entries and I have no activation errors. I did have a couple of installer issues, but eliminated them using the advice found here:  http://www.vmwareinfo.com/2011/09/surgically-eliminating-windows.html The only big Visio 2010 issues remaining for me are: Help won't open on Windows 2008R2 where no prior Office installation is present (think Citrix server situation here).  I get a Microsoft Office Help Viewer error:  "There is a problem with one or more installed help files.  Please repair your Office installation and try again."  I've tried all of the suggestions in the threads and documents regarding the Help folder placement and isolation settings. I've even tried my own advice, but this is the error I always get on Windows 2008R2 where there are no Office products installed.  On any achine where some form of Office is installed, whether Office 2007 or 2010, whether Windows XP, Windows 7 64-bit, Windows 2008, or Windows 2008R2, the Help opens (although on some it still has issues, but at least it opens.)  I've tried granting Merged to %TEMP% and %Internet Cache%, etc. Can't open native Word 2007 and choose Visio object for embedding - Visio not listed as an embedding option (even though installed from MSI.)  Considering entry point or other package.INI settings for this issue. Can't insert native Excel 2007 chart in to virtual Visio 2010.  Get Access Denied message.  Considering entry point or other package.INI settings for this issue.
Sometimes I get a little excited and post results before all the tests are complete.  I'm doing it again! I have the hotfix build of ThinApp, but I did not have the registry entries.  KMS acti... See more...
Sometimes I get a little excited and post results before all the tests are complete.  I'm doing it again! I have the hotfix build of ThinApp, but I did not have the registry entries.  KMS activations were failing about 50% of the time without the registry entries.  I'm testing virtual Project 2010 and virtual Visio 2010 against native Office 2010. I have many more tests to conduct this week, but so far it looks like the hotfix build of ThinApp 4.7, combined with the registry entries, resolves the KMS activation issues. I will try various combinations of reboots and launch sequences and report the reults back to this thread. Wish me luck!
Questions: Do you mean SQL Server or SQL Server Express? Have you reviewed the following articles and threads:  http://blogs.vmware.com/thinapp/2009/03/how-to-thinapp-msdesql-2005-express.... See more...
Questions: Do you mean SQL Server or SQL Server Express? Have you reviewed the following articles and threads:  http://blogs.vmware.com/thinapp/2009/03/how-to-thinapp-msdesql-2005-express.html , http://communities.vmware.com/thread/187010 , http://kb.vmware.com/kb/1006992 , http://communities.vmware.com/message/1517859 Have you considered virtualizing Visual Studio?  Just curious, because it's on my list of apps to package.
Can you upgrade to ThinApp 4.7?  4.7 solved the issues I was seeing with IE8. Is your proxy transparent?  Sorry if you already answered these questions.
The white spaces I believe that are being discussed here are different.  When first running build.bat on Visio 2010 you will see things mentioned during the virtual registry import, like: "White ... See more...
The white spaces I believe that are being discussed here are different.  When first running build.bat on Visio 2010 you will see things mentioned during the virtual registry import, like: "White space at end of line 15281 in HKEY_LOCAL_MACINE..."  Like I mentioned in my earlier reply, I always have three of these lines with Visio 2010, and they always involve ProxyStubCLSID entries.  Maybe I can get a screenshot up on Tuesday.
I'm not sure if the cause is known.  I see the white spaces in any ThinApp 4.7.x build of either Visio 2010 or Project 2010 (or both) regardless of capture machine OS and configuration.
Open a command prompt at the root of your project. Run build.bat One of the first things that happens in the build process is the import of the virtual registry.  Depending on the speed of ... See more...
Open a command prompt at the root of your project. Run build.bat One of the first things that happens in the build process is the import of the virtual registry.  Depending on the speed of your system you may or may not see the white space errors listed right off the bat.  Hit CTRL+C and kill the build as soon as the registry import is finished.  Scroll up and the error codes will tell you the line number(s) containing white spaces. In Notepad you can go to a line number in the appropriate virtual registry text file by clicking  Edit -> Go To.  Input the line number from the error in the command prompt window.  Remove white space from the end of that line. I usually see these white spaces at the end of ProxyStubCLSID type of entries.  There's usually three lines that have this issue, and they are usually within twenty rows of each other.
You are definitely trying everything, which is much appreciated. As for a shortened installation path on the root of C:\, a more specific recommendation would be to ensure that the root folder... See more...
You are definitely trying everything, which is much appreciated. As for a shortened installation path on the root of C:\, a more specific recommendation would be to ensure that the root folder is no more than 8 characters in length. Rather than C:\ADOBECS55, which is a 9 character path, I would suggest C:\ACS55, or anything that stays within the gold old 8.3 naming convention.  I don't know that it will make any difference in your case. How about this:  can you remove VMware tools and Visual C++ 2008 from your capture machine?  I had a situation recently with a package that was exhibiting strange behavior on one of our servers.  Turns out the server did not have the Visual C++ runtime.  I created a snapshot on the capture VM that I can go to whenever I need to capture the Visual C++ 2005 and 2008 runtimes.  Maybe you could give this a try.  I believe some of the Adobe products are expecting one of those runtimes to be present. I hope they'll let me do a capture of CS 5.5 soon.  Alas, all I have an opportunity to package is CS 5, and it's working for us.  Go figure.
From page 30 of the ThinApp 4.6.1 manual PDF: Extracting and Registering ThinDirect After you build an Internet Explorer 6 package, you must extract and register the ThinDirect plug-in on t... See more...
From page 30 of the ThinApp 4.6.1 manual PDF: Extracting and Registering ThinDirect After you build an Internet Explorer 6 package, you must extract and register the ThinDirect plug-in on the test machine.  With ThinDirect, you can associate Web pages with alternative virtualized browser versions. With ThinDirect, users are automatically redirected to the appropriate virtual or native browser as they navigate through different pages, without interruption to their workflow. ThinDirect installs a browser helper object in the native instance of Internet Explorer that runs the virtualized browsers when they are required to navigate to specific predefined URLs. Because ThinApp runs entirely in user mode and does not install any system drivers, the native Internet Explorer instance is completely unaffected by ThinApp. The ThinDirect plug-in must be installed as part of the virtual package. The plug-in is installed in the native browser during the registration process. Extract and register ThinDirect In the console, run the thinreg /a VirtIE6.exe command to extract the ThinDirect application, and extract and register the ThinDirect library.  The ThinDirect application is installed in the Program Files/VMware/VMware  ThinApp/ThinDirect directory.  You can have multiple ThinDirect text files in the ThinDirect directory, if they all have unique names. The ThinDirect plug-in then reads all files. In addition to individual machine registration, you can register Web page redirects on a individual user basis by omitting the /a switch. To achieve individual-user redirects requires that the ThinDirect plug-in be installed as a separate step from an Administrator account. If you do not install the ThinDirect plug-in as a separate step, Thinreg displays an error.You can push additional Web page redirect to end-user computers by copying files with a specific format to specific individual-machine or individual-user locations.
Did you mean ThinApp 4.6 ?
I'm testing a variety of physical and virtual systems to find ways to improve performance in the ThinApp build process.  Most notably, the portion of the build when the MSI is created is quite sl... See more...
I'm testing a variety of physical and virtual systems to find ways to improve performance in the ThinApp build process.  Most notably, the portion of the build when the MSI is created is quite slow in comparison to the rest of the process.  Alas, pigz is not available for Windows (that I'm aware.)  The MSI compression process appears to make use of a single CPU thread.  This is unfortunate.  I am currently testing out the use of a RAM disk, to see if it will help make the compression process go faster.  The RAM disk driver is free and comes from: http://www.ltr-data.se/opencode.html/ . I don't currently have any specialized hardware available to me, like a Fusion-IO card or other caching peripherals.  I don't have an SSD.  I do have a couple of servers, one physical with 8 HyperThreaded cores and 8GB of RAM, running Windows 2008R2 Standard, and one virtual with 4GB RAM running Windows 2008 32-bit. Does anyone know of a way to get the MSI compression portion of the ThinApp build process to make use of more than one CPU?
I customized my installation utilizing Adobe's "Adobe Application Manager Enterprise Edition", available for free at the Adobe web site: http://www.adobe.com/devnet/creativesuite/enterprisedep... See more...
I customized my installation utilizing Adobe's "Adobe Application Manager Enterprise Edition", available for free at the Adobe web site: http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html I installed to C:\AIDCS5.  You might want a different directory.  Sometimes installing to the root of C:\ during the capture process will resolve issues.  Might be worth a try.  Also, the Adobe Application Manager incorporated updates in to the installation package, saving me the need to download the updates on the capture and build machine. Lastly, I was using an enterprise license key.  Not sure of your situation.
Would you mind uploading an attachment of the Package.INI? I packaged InDesign CS5 and would like to compare with the settings in your project.
Use a VBscript to harvest user information and pass it to the virtual bubble?
Thanks for the shrivastavaa. Your post is technically correct, if most of the ThinApp users out there are in the habit of quoting from page 114 of the "VMware Project North Star (Thinstall) Be... See more...
Thanks for the shrivastavaa. Your post is technically correct, if most of the ThinApp users out there are in the habit of quoting from page 114 of the "VMware Project North Star (Thinstall) Beta 1" PDF, and perhaps other ThinApp manuals prior to 4.6.1. For those viewing the ThinApp 4.6.1 manual, here's what they'll see (page 78 of the PDF): VirtualizeExternalOutOfProcessCOM The VirtualizeExternalOutOfProcessCOM parameter controls whether out-of-process COM objects can run in the virtual environment. COM objects that are external to the virtual environment always run in the physical environment. This parameter addressed out-of-process COM objects that are not part of a ThinApp package and are not registered in the virtual registry. ThinApp sets an initial value of the VirtualizeExternalOutOfProcessCOM parameter to run external out-of-process COM objects in the virtual environment to ensure that COM objects cannot modify the host computer. If a compatibility problem exists with an external COM object running in the virtual environment, you can create and run COM objects on the host system. To run only specific COM objects outside of the virtual environment, you can use the ExternalCOMObjects parameter to list the CLSID of each COM object. Examples You can modify the VirtualizeExternalOutOfProcessCOM parameter to run all external out-of-process COM objects in the physical environment rather than the virtual environment. For example, you might use virtual Microsoft Access 2003 to send email through a native IBM Lotus Notes session. [BuildOptions] VirtualizeExternalOutOfProcessCOM=0 For those using the ThinApp 4.7 documentation, you won't find mention of this switch in the main manual.  Instead, you'll have to go to the "ThinApp Package.INI Parameters Reference Guide - ThinApp 4.7."  Again, in that guide, you will not see the parameter listed with an "=1" in any example.
I wish I could remember now wich app it was that turning off compression took away the error I was seeing.  I didn't take the time to isolate the exact folder.  I'll have to revisit.
Which isolation modes have you tried? Did you turn on compression?  If so, try turning it off and see what happens.
I realize this thread is slightly aged and possibly answered, but I have a question I think is relevant to the context. Since VirtualizeExternalOutOfProcessCOM=0 is commented out by default in... See more...
I realize this thread is slightly aged and possibly answered, but I have a question I think is relevant to the context. Since VirtualizeExternalOutOfProcessCOM=0 is commented out by default in Package.ini, I assume that removing the semicolon puts the parameter in effect at the next build. Is there a VirtualizeExternalOutOfProcessCOM=1 value, or is 0 the only value available?