windows 7 premium 64 bit downloadwindows vista ultimate service pack 2 free downloadvegas make it big download freethe science of getting rich free download pdf
The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Microsoft Office 2010 isn't able to launch.
Microsoft Outlook 2010 ceases to launch after configuration.
Microsoft Office cannot verify the license due to this application. A repair attempt failed or was canceled with the user. The Application will shut down.
Cannot Start Microsoft Outlook. Cannot open the Outlook window.
These are known difficulty with ThinApp and Office 2010 family products, including Office 2010, Project 2010, and Visio 2010. Unless otherwise noted, all conditions that refer to Office 2010 make reference to all products inside the Office 2010 family.
Note : The workarounds underneath are offered as suggestions only. Individual results are different. These workarounds are specific to capturing Microsoft Office 2010 with ThinApp 4.6.1 to 4.7.3.Р’ If that you are capturing with ThinApp 5.0 or more, see Packaging guide for ThinApp 5.x and Microsoft Office 2010 2062694 and Packaging Guide for ThinApp 5.x and Microsoft Office 2013 2062691.
The using ThinApp 4.6.0 will not be recommended. Use ThinApp 4.6.1 or more instead.
Microsoft Office 2010 could only be virtualized when captured on or deployed to Windows XP SP3, Windows Vista SP1, Windows 7, Windows Server 2003 R2, Windows Server 2008, Windows Server 2008 R2, and patch levels.
Capturing Office 2010 with a 64-bit main system is unsupported. When capturing Office 2010, employ a 32-bit computer.
Any deployment to Windows Vista, Windows 7, or Windows Server 2008 does not launch if the retail license is needed. Virtualizing Office 2010 to prospects operating systems uses a volume license. Volume licensing can utilize a couple of licensing activation technologies: Key Management Server KMS or Multiple Activation Key MAK.
ThinApp deployments can't be used to bypass Microsoft Office 2010 activation behavior expected in the native environment.
ThinApp deployments may do not activate if Microsoft Office 2010 with KMS licensing was activated before the postscan. When capturing Microsoft Office 2010 with KMS licensing, be sure that it isn't activated by disconnecting the network card NIC through the capture machine in the installation process.
Virtualized Office using MAK licensing must be activated by each user once it is launched.
KMS Licensing doesn't require the user to activate manually.
VMware recommends which you stop the Office Software Protection Platform service ahead of the postscan.
A virtualized Office 2010 family product using KMS or MAK licensing activation will terminate having an error if launched on an os where another virtualized Office 2010 family strategy is already running. To address this, install ThinApp 4.7.1 or better.
Office 2010 may terminate using a licensing error if deployed to an main system that either has or had the Microsoft Office 2010 Deployment Kit for App-V installed.
Note : Uninstalling miracle traffic bot may not be sufficient to avoid the licensing error.
Office 2010 may neglect to launch, or terminate by having an error, when deployed to an os that already posseses an Office 2010 component natively installed.Р’ If this is encountered, see Resolving licensing errors when deploying virtual Office into a system with Office installed natively 2107369. When captured on Windows XP or Windows Server 2003, any deployment to Windows Vista, Windows 7, or Windows Server 2008 doesn't launch unless these steps are finished: In the project directory, move the folder OfficeSoftwareProtectionPlatform from:
Common AppData%Microsoft.
From 4.7.3 onwards, perform these steps In the project directory, copy the folder OfficeSoftwareProtectionPlatform from %DriveC%Documents and SettingsAll UsersMicrosoft to %DriveC%ProgramDataMicrosoft
Note: If the destination folder PrgramData won't exist, make sure that the folder is just not hidden by showing hidden files. If the folder still won't exist, you may create a folder ProgramData orР’use theР’existing folder, %Common AppData%Microsoft since the destination folder.
If present, delete creases from file within the project directory:
The Outlook portion of Microsoft Office 2010 ceases to launch after account configuration when deployed to an os that has Windows Search installed. To allow Outlook 2010 to file for, add these entries to your bottom with the file inside project directory:
Users without Administrator rights could possibly be unable to activate Microsoft Office 2010 if it truly is using MAK license activation, unless these entries are added for the bottom from the file inside project directory: When accessing Help in Word 2010 with a Windows 2008 64-bit main system, chances are you'll see the material There are no help topics available that satisfy your request unless these steps are executed: Install ThinApp 4.7.1 or better.
When capturing Office 2010, pick a custom installation and do the installation to C:Office.
After installing Office 2010, launch it and press F1 to activate Help prior to taking the postscan.
THE CONTENT OF THIS ARTICLE IS PROVIDED AS-IS, AND TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, VMWARE DISCLAIMS ALL OTHER REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, REGARDING THIS CONTENT, INCLUDING THEIR FITNESS FOR A PARTICULAR PURPOSE, THEIR MERCHANTABILITY, OR THEIR NONINFRINGEMENT. VMWARE SHALL NOT BE LIABLE FOR ANY DAMAGES ARISING OUT OF OR IN CONNECTION WITH THE USE OF THIS CONTENT, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF VMWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
To automate the Office 2010 activation on user machines, they can do this with the Volume Activation Management Tool VAMT. For more information for the Volume Activation Management Tool, view the Microsoft download page.
Note : The preceding link was correct since October 17, 2013. If you find the hyperlink is broken, please provide feedback plus a VMware employee will update the web link.
Note : These steps are available as suggestions only. Individual results can vary greatly. Copy or extract the Microsoft Office 2010 installation source into a location the location where the files could be edited.
Locate. This is in a very folder called suite WW, where suite is replaced through the suite of Microsoft Office 2010 that you are installing.
Add creases to the bottom from the file, immediately higher than the last line which reads /Configuration :
Note : Replace with all the name of your respective KMS server.
Note : Replace AAAAA-BBBBB-CCCCC-DDDDD-EEEEE along with your MAK information.
Р’ !- Display Levelfull CompletionNoticeyes SuppressModalno AcceptEulano-
Display Levelnone CompletionNoticeno SuppressModalyes AcceptEulayes/.
Take a prescan, then double-click in the modified installation source.
Note : Refer on the rest of this post for other considerations.
To request a fresh product feature or even provide feedback on the VMware product, please go to the Request a Product Feature page.
Did this post help you?
This article resolved my issue.
This article failed to resolve my issue.
This article helped but further information was instructed to resolve my issue.
What are we able to do to improve these records? 4000 or fewer characters
Sharing IT knowledge, One Post At A Time.
After successfully the ability to create afull Microsoft Office 2010 suiteThinApp, I have written a setup help guide detail the steps which had to be drawn in order to obtain all Office applications working also to allow standard windows users non local administrators to activate office when launching the ThinApp for initially. This article may be written using information for VMware sources and my experience. The following ThinApp capture continues to be performed on the fresh installing of Windows XP SP3 with VMware ThinApp 4.6.1.
1. Download and copy Framework3.5 and Microsoft Office 2010installation files towards the ThinAppcapture machine.
2. Ensure you have throttle on the ThinApp capture machine.
3. Install VMware ThinApp on capture machine.
4. Run the Setup Capture wizard, start and take care of the pre-scan process.
5. When the pre-scan is complete, around the Install Application page in the Setup Capture wizard, minimize the wizard and install Framework3.5.
6. The installation generates the procedure that continues on an extended period, we'd like tostop the process together with the tool. Open a whole new command prompt window and type the next command and press return:
7. In order for Office 2010 to activate correctly we want toedit file and specify your Multiple Activation Key MAK. By default, theMicrosoft Office 2010 file is stored inside the core product folder inside the Microsoft Office 2010 installation media.Explore the Office 2010 installation media onthe capture machineand you ought to seea folder named similar folder. For example, if my Microsoft Office 2010 media was Professional Plus, thefolder name would.
8. Open the core product folder and locate the file. Open the with Notepad and add these lines to your towards the file file and save it in your localC:drive:
Note: Do not enter any spaces or hyphens when entering the license key inside the PIDKEY value, this should be all one string including ABCDEFGHIJK.
9. To start the Microsoft Office 2010 setup wizard and apply the settings in, opena newcommand prompt window andtype navigate in your Office 2010installation media by utilizing for example cd d:. When inside installation media directory enterthe following command and press return.
10. When not hard to install starts click to just accept the relation to theagreement and click on next.
11. On the Choose cellular phone dialog box, click on the Customise button.
12. Select Microsoft Officeand then select Run all from My Computer since the installation option.
13. Click Install Now to setup Microsoft Office 2010, this would take some time.
14. When set up . is complete click Finish. Proceed and click on the Start menu, choose the Run option, and after that type and then click ok. Whenthe services snap-in opens scroll along the list of services andlocate the Office Software Protection Platform service, right click a reverse phone lookup and select stop.
15. Maximise the ThinApp Capture wizard we minimised in step5 then click to start out the post scan process.
16. Once the post scan process has completed, customize the Inventory name to something right for your use, one example is Microsoft Office 2010.
17. Before building the ThinAppproject, copy the OfficeSoftwareProtectionPlatform folder from C:Documents and SettingsAll UsersMicrosoft to your folder%Common AppData%Microsoft. To get to your %Common AppData%Microsoft folder open the ThinAppSetup Wizardand select the Open Project Folder button, inside the resulting window it is best to then seea folder named %Common AppData% double click this folder then double select the Microsoft folder inside. Simply copy and paste the OfficeSoftwareProtectionPlatform folder into this location.
18. On the capture machine open the registry editor and navigate to your following key:
In this location, right click inside a white space area an build a new Multi-String Value while using name of, without quotes, isolationwritecopy. Right select the created isolationwritecopy key and select Modify. When the modify window opens, inside value area, enter the subsequent information and then click ok:
19. In the sameregistry editor window navigate for the following key:
In this location, right click inside a white space area an make a new Multi-String Value with all the name of, without quotes, isolationfull. Right select the created isolationfull key and select Modify. When the modify window opens, inside value area, enter these information and then click ok:
20. In exactly the same registry editor window navigate towards the following key:
In this location, right click in the white space area an develop a new Multi-String Value together with the name of, without quotes, isolationwritecopy. Right click on the created isolationwritecopy key and select Modify. When the modify window opens, inside value area, enter the next information and then click ok and after that close the registry editor:
21. Maximise the ThinApp Setup Wizard and click for the Edit button before you start the build process. In the ini file customize the MSIStreaming value to a single if you want this being streamed ThinApp otherwise this could be a local ThinApp.
22. Click the Build button in ThinApp and wait for build process to perform.
23. The ThinApp creation process is complete plus the applications should work and activate correctly on Windows XP systems. If you intend make use of the Office 2010 ThinApp on Windows 7 os, some additional changes need being made to make sure that the product activation works correctly.
24. For Windows 7 machines only, to enable the ThinApps to file for and activate Office 2010correctly you have got to disable the Windows Search Service and completely disable User Account Control UAC. Disabling those two properties might be achieved by utilizing Group Policy Objects as detailed here and here.
That s it, it is best to now have a totally functionaly Microsoft Office 2010 VMwareThinApp that work well on both Windows XP and Windows 7 os's.
Has anyone been able for getting the help file system in Office 2010 to use above or other procedure on XP SP3 using Thinapp client 4.6.1?
I can successfully obtain it to go on W7 32bit and 64bit platforms however XP SP3 it fails anytime. Has anyone got a workaround or can confirm it can be also a concern for them?
Hi Andrew, we've successfully designed a ThinApp of Office 2010 by using this guide together with the help files implementing both Windows 7 and Windows XP.
The only difference i'd made to my ThinApp may be the activation method. I utilize a KMS server to active the Office 2010 ThinApp in opposition to entering this product key in to the setup, this shouldnt make any difference to your help files though.
Thanks for your reply and check in. I am glad you are able for getting it to visit. We are also using KMS so same procedure there.
I view a discrepency with above procedure on Point 17 where it says to COPY the OfficeSoftwareProtectionPlatform folder. I have followed other procedures which thought to MOVE this folder this done W7 32bit and 64Bit.
I will endeavour the copy to find out if that resolves it.
Also of note I develop the App-V deployment kit for Office 2010 installed for getting this application workingactivated correctly. Without it particularly on W7 Office 2010 would to try and configureself heal itself and fail.
Do you 'must' have this dependency installed as well to obtain your version and help going?
I will tell you COPYING the OfficeSoftwareProtectionPlatform produces a similar Help issue:. The only other difference I can imagine was I 3.5 SP1 from the same layer not 3.5.
I will retry using version.
I do not possess the installed to generate this operate. I think the issue your getting with Office 2010 attempting to configureself heal is always to do using the windows search service on Windows 7.
I were built with a similar problem, but following step 24 the appliance loads without problem on Windows 7. Note that the search service needs to get turned off on all Windows 7 client machines while using the ThinApp.
All i'm able to suggest is usually to follow the guide by making use of only what exactly is detailed, ThinApp only. I managed to acquire this working by only with the information the guide suggests.
With comparison to its moving the OfficeSoftwareProtectionPlatform folder, i could truthfully only copy it because the folders were locked. This worked for me.
Hope you will get some success soon.
I ve been struggling for a while now to have this working as well as getting very frustrating carrying it out over and over I can find the MAK license working but have to have it setup for KMS licensing.
What installation media will you be using? Also, when conducting a fresh install of WinXP SP3 will you let windows updates run first before installing ThinApp 4.6.1 then apping Office? I have followed the steps on here and well as around the VMWare blog disabled any office protection service, tried together with no luck
Im by using a clean install of WinXP SP3no updating, ThinApp 4.6.1 and KMS.
If you can consider anything that i would try/do differently please make me aware!
I did update my Windows XP SP3 but I also have tried it without updating and I can still have it working.
Confirm your KMS is using the services of Office 2010 as i needed to install a whole new KMS on Windows 2008 R2 to feature Office 2010 to be a product that could be activated.
How odd I stumbled onto the identical issue using the help files not working looking to press help inside ThinApp launched an installer which failed and no help. According the VMware this is the known issue and in addition they had no solution on how to have it to be effective! So, I m really curious on what you managed this trick
I m having issue w/getting install to begin with. Everytime i run from command line i buy windows xp setup message stating please go to your control panel to set up and configure system components. Any ideas? im using
Is there good reason why you affect the registry following the post scan? The changed keys don t appear from the files within the ThinApp Project Folder.
Do you would imagine is possible to eliminate C:MSOcache before postscan?
within a typical installing Office 2010 it might be safe to eliminate the MSOCache, however I cannot say beyond doubt this would be advisable when building a ThinApp. In theory it needs to be ok to eliminate the MSOCache before post scan, which could reduce the actual size with the ThinApp, however it truly is possible this may be referenced when running the approval for the very first time. My best advice is usually to just try it out and see what goes on.
Thanks to the article; very hopeful I can get this to work.
The question grew up above, but never answered. Shouldn t the Registry changes occur BEFORE the Post-Scan as an alternative to After?
If the intent ended up being to have us edit, then I declare that this is undoubtedly an easier strategy to document it and achieve the result.
There should be NO empty lines on the top with the file, and ONE empty line involving the new entries along with the ones generated by ThinApp.
However I continue to have licensing problems after virtualizing, so YMMV!
Hi there. I just needed to say thanks due to this guide. I d been being affected by ThinApping Office 2010 Pro Plus for a couple of days before I found this. I followed these instructions for the letter and after packaging on XP, I have an Office 2010 package that actually works on both XP and Win7.
My only question for you is, how exactly does making the registry changes steps 18-20 affect anything when they re performed as soon as the post-scan process? I m a newcomer to ThinApp and am teaching myself, so forgive me if that is a stupid question.
Hi, I followed all in the 24 steps, but I still receive the message that Office can t be licensed. I captured on XP SP3 i try to file for on Win7 32bits. I relies on a MAK license code within the Anymore choices for me???
Hello and appreciate your all the comments for this post. For those person asking concerning the registry key changes following your post scan process, these steps were extracted from an offical VMware blog post in order to ThinApp Microsoft Office 2010.
Please see steps 11-15 in addition to being you will see to all cases these changes will always be applied following your post scan. I am glad this informative guide has worked for almost all of you!
I could see some of you happen to be having problems with acquiring a working ThinApp of Office 2010. I have successfully created my Office 2010 ThinApp following this guide, so I have come up with a video tutorial on the way to achieve this.
Please view my article below as I can guarantee this method works as shown around my video.
This worked perfectly to me! Thanks tons!
Its been like to some month of struggle doing learning from your errors on capturing Project 2010 using thinapp 4.7.3 and I did keep to the guide noted with this KB:
Your email address contact info will not be published. Required fields are marked
2015 All rights reserved.
Sharing IT knowledge, One Post At A Time.
After successfully being able to produce a full Microsoft Office 2010 suite ThinApp, I have written a setup secrets and techniques for detail the steps which in fact had to be consumed order to have all Office applications working and also to allow standard windows users non local administrators to activate office when launching the ThinApp for the very first time. This article continues to be written using information for VMware sources and my own, personal experience. The following ThinApp capture has become performed on the fresh installing of Windows XP SP3 with VMware ThinApp 4.6.1.
1. Download and copy Framework3.5 and Microsoft Office 2010installation files on the ThinApp capture machine.
2. Ensure you have online on the ThinApp capture machine.
4. Run the Setup Capture wizard, start and handle the pre-scan process.
5. When the pre-scan is complete, within the Install Application page in the Setup Capture wizard, minimize the wizard and install Framework3.5.
6. The installation generates the method that continues to have an extended period, we want tostop the process using the tool. Open a whole new command prompt window and type these command and press return:
7. In order for Office 2010 to activate correctly we'd like toedit file and specify your Multiple Activation Key MAK. By default, theMicrosoft Office 2010 file is stored within the core product folder within the Microsoft Office 2010 installation media.Explore the Office 2010 installation media onthe capture machineand you ought to seea folder named similar folder. For example, if my Microsoft Office 2010 media was Professional Plus, thefolder name would.
8. Open the core product folder and locate the file. Open the with Notepad and add the next lines to your on the file file and save it for a localC:drive:
Note: Do not enter any spaces or hyphens when entering the license key from the PIDKEY value, this should be all one string for example ABCDEFGHIJK.
9. To start the Microsoft Office 2010 setup wizard and apply the settings in, opena newcommand prompt window andtype navigate in your Office 2010installation media by employing for example cd d:. When inside installation media directory enterthe following command and press return.
10. When not hard to install starts click to receive the comparison to its theagreement and then click next.
11. On the Choose mobile phone dialog box, go through the Customise button.
12. Select Microsoft Officeand then select Run all from My Computer as being the installation option.
13. Click Install Now to set up Microsoft Office 2010, this tends to take some time.
14. When mobile phone is complete click Finish. Proceed and click on the Start menu, simply select the Run option, and type and then click ok. Whenthe services snap-in opens scroll on the list of services andlocate the Office Software Protection Platform service, right click a reverse phone lookup and select stop.
15. Maximise the ThinApp Capture wizard that people minimised in step5 and after that click to get started on the post scan process.
16. Once the post scan process has completed, customize the Inventory name to something ideal for your use, as an example Microsoft Office 2010.
17. Before building the ThinApp project, copy the OfficeSoftwareProtectionPlatform folder from C:Documents and SettingsAll UsersMicrosoft for the folder%Common AppData%Microsoft. To get to your %Common AppData%Microsoft folder open the ThinApp Setup Wizardand select the Open Project Folder button, inside the resulting window it is best to then seea folder named %Common AppData% double click this folder then double select the Microsoft folder inside. Simply copy and paste the OfficeSoftwareProtectionPlatform folder into this location.
18. On the capture machine open the registry editor and navigate towards the following key:
In this location, right click inside a white space area an build a new Multi-String Value using the name of, without quotes, isolationwritecopy. Right select the created isolationwritecopy key and select Modify. When the modify window opens, within the value area, enter the subsequent information and click on ok:
19. In the sameregistry editor window navigate for the following key:
In this location, right click inside a white space area an build a new Multi-String Value using the name of, without quotes, isolation full. Right go through the created isolation full key and select Modify. When the modify window opens, inside the value area, enter this information and then click ok:
20. In exactly the same registry editor window navigate for the following key:
In this location, right click within a white space area an produce a new Multi-String Value while using name of, without quotes, isolationwritecopy. Right go through the created isolationwritecopy key and select Modify. When the modify window opens, from the value area, enter these information and then click ok then close the registry editor:
21. Maximise the ThinApp Setup Wizard and click for the Edit button before commencing the build process. In the ini file customize the MSIStreaming value to just one if you want this for being streamed ThinApp otherwise this could be a local ThinApp.
22. Click the Build button in ThinApp and wait for an build process to try and do.
23. The ThinApp creation process is actually complete as well as the applications should work and activate correctly on Windows XP systems. If you intend make use of the Office 2010 ThinApp on Windows 7 os's, some additional changes need to become made to make sure the product activation works correctly.
24. For Windows 7 machines only, to enable the ThinApps to file for and activate Office 2010correctly you have got to disable the Windows Search Service and completely disable User Account Control UAC. Disabling the two of these properties is usually achieved through the use of Group Policy Objects as detailed here and here.
That s it, you need to now have a totally functionaly Microsoft Office 2010 VMware ThinApp that works well on both Windows XP and Windows 7 os.
Has anyone been able for getting the help file system in Office 2010 to use above or some other procedure on XP SP3 using Thinapp client 4.6.1?
I can successfully understand to go on W7 32bit and 64bit platforms however XP SP3 it fails each and every time. Has anyone got a workaround or can confirm it can be also a problem for them?
Hi Andrew, i've successfully made a ThinApp of Office 2010 applying this guide with all the help files working away at both Windows 7 and Windows XP.
The only difference i did made to my ThinApp could be the activation method. I work with a KMS server to active the Office 2010 ThinApp averse to entering the item key in the setup, this shouldnt make any difference on the help files though.
Thanks to the reply and check in. I am glad you happen to be able to have it to search. We are also using KMS so same procedure there.
I visit a discrepency with above procedure on Point 17 where it says to COPY the OfficeSoftwareProtectionPlatform folder. I have followed other procedures which asked MOVE this folder this handled W7 32bit and 64Bit.
I will endeavor the copy to find out if that resolves it.
Also of note I contain the App-V deployment kit for Office 2010 installed to have this application workingactivated correctly. Without it particularly on W7 Office 2010 would to try and configureself heal itself and fail.
Do you 'must' have this dependency installed as well for getting your version and help going?
I knows COPYING the OfficeSoftwareProtectionPlatform produces the identical Help issue:. The only other difference I can consider was I 3.5 SP1 from the same layer not 3.5.
I will retry by using their version.
I don't have the installed to create this operate. I think the challenge your getting with Office 2010 attempting to configureself heal should be to do while using windows search service on Windows 7.
I were built with a similar problem, but through using step 24 the application form loads without problem on Windows 7. Note that the search service needs to get turned off on all Windows 7 client machines while using ThinApp.
All i am able to suggest is always to follow the guide by utilizing only what on earth is detailed, ThinApp only. I managed to obtain this working by only in what the guide suggests.
With relation to its moving the OfficeSoftwareProtectionPlatform folder, i could truthfully only copy it because folders were locked. This worked for me.
Hope you have some success soon.
I ve been struggling for a while now for getting this working as well as getting very frustrating executing it over and over I can have the MAK license working but require it setup for KMS licensing.
What installation media are you currently using? Also, when you are conducting a fresh install of WinXP SP3 will you let windows updates run first before installing ThinApp 4.6.1 and after that apping Office? I have followed the steps on here and well as for the VMWare blog disabled work protection service, tried together no luck
Im employing a clean install of WinXP SP3no updating, ThinApp 4.6.1 and KMS.
If you can visualize anything that i'd personally try/do differently please inform me!
I did update my Windows XP SP3 but I have tried it without updating and I can still have it working.
Confirm your KMS is dealing with Office 2010 as i needed to install a fresh KMS on Windows 2008 R2 to incorporate Office 2010 as being a product that could be activated.
How odd I stumbled onto precisely the same issue while using help files not working looking to press help from the ThinApp launched an installer which failed after which no help. According the VMware it is a known issue and so they had no solution on how for getting it to operate! So, I m really curious how you managed this trick
I m having issue w/getting install to begin with. Everytime i run from command line i buy windows xp setup message stating please go to your control panel to set up and configure system components. Any ideas? im using
Is there an excuse why you customize the registry as soon as the post scan? The changed keys don t appear inside files inside ThinApp Project Folder.
Do you imagine is possible to get rid of C:MSOcache before postscan?
within a typical installing of Office 2010 it might be safe to eliminate the MSOCache, however I could hardly say for certain this would be advisable when coming up with a ThinApp. In theory it needs to be ok to take out the MSOCache before post scan, which might reduce the actual size in the ThinApp, however it truly is possible this is referenced when running the application form for once. My best advice is usually to just test it out for and see what the results are.
Thanks for that article; very hopeful I can get this to work.
The question spent my youth above, but never answered. Shouldn t the Registry changes occur BEFORE the Post-Scan rather than After?
If the intent would have been to have us edit, then I claim that this is surely an easier strategy to document it and achieve the specified result.
There should be NO empty lines on the top with the file, and ONE empty line relating to the new entries along with the ones generated by ThinApp.
However I still licensing problems after virtualizing, so YMMV!
Hi there. I just wished to say thanks due to this guide. I d been experiencing ThinApping Office 2010 Pro Plus a couple of days before I found this. I followed these instructions on the letter and after packaging on XP, I have an Office 2010 package that work well on both XP and Win7.
My only real question is, so how exactly does making the registry changes steps 18-20 affect anything whenever they re performed following your post-scan process? I m a novice to ThinApp and am teaching myself, so forgive me if this can be a stupid question.
Hi, I followed all with the 24 steps, but I still receive the message that Office can t be licensed. I captured on XP SP3 and that i try to file for on Win7 32bits. I works on the MAK license code inside the Anymore methods of me???
Hello and appreciate your all the comments for this post. For those individuals asking around the registry key changes as soon as the post scan process, these steps were stripped away from an offical VMware blog post regarding how to ThinApp Microsoft Office 2010.
Please see steps 11-15 and since you will see in most cases these changes will almost always be applied following the post scan. I am glad this informative guide has worked for many of you!
I can easily see some of that you are having problems with finding a working ThinApp of Office 2010. I have successfully created my Office 2010 ThinApp through using this guide, so I have assembled a video tutorial in order to achieve this.
Please view my article below as I can guarantee this works as shown within my video.
This worked perfectly to me! Thanks a lot!
Its been like to your month of struggle doing learning from mistakes on capturing Project 2010 using thinapp 4.7.3 and I did continue with the guide noted about this KB:
languageenUS cmddisplayKC externalId1022287 however no luck. Can anyone please help me out? Im using KMS and capturing the build using win7 32bit OS.
Your email will not be published. Required fields are marked
2015 All rights reserved.
Below are instructions to thinapp the VMware Horizon View Client. version 5.4.0 build 1219906
A Thinapp-ed version with the VMware Horizon View client may be very useful in situations the place you do not want to or cannot install software in your Windows PC.
Install latest VMware Thinapp version 4.7.3 build 891762 before writing
Select Full write access.
Change ;MSIStreaming0 to MSIStreaming1 Make sure you take away the ; prior to the line
Enter your current email address to subscribe for this blog and receive notifications of latest posts by email.
Post wasn't sent - look at email addresses!
Email check failed, please try again
Sorry, your blog post cannot share posts by email.
The very first time that you create a forex account in Outlook and connect to a Exchange server, it requires a while for Outlook to have ready to be used and for you to see you calendar items and emails. During the preparation of Outlook, file will be created on your own machine in C:UsersuserAppDataLocalMicrosoftOutlook.
So, why file being created? file has created therefore you will have an area copy of most items being stored upon an Exchange server. Emails, calendar items, reminders etc. This Cached Exchange Mode permits you to keep on doing work in Outlook even though you may dont have an association offline to your Exchange server. A sync with all the server can happen when your device is connected to your Exchange server. By default, this method is fired up but you can make to turn it well. Besides the offline reason, additionally you could say a cached version is improving performance and buyer.Redirecting file to some share is held by Microsoft, though with restrictions. If you want to have in mind the basics files, click here. In this blog, Im only files are certainly popular likewise and it is possible to use the identical solution s as I describe files.
In a VDI world, virtual desktops are residing very close to your Exchange server within the data center. And, inside a VDI concept, there isn't any offline means of working thinking about the Exchange Server. So, in thiscase, there is absolutely no real reason to turn around the Cached Exchange Mode. Especially, when you happen to be working with Linked Clone Floating VMs in VMware Horizon View, the location where the clones gets deleted/refreshed after logoff. One thing you dont want would be to create file whenever a user logs on into a clean virtual desktop. Best practice is always to disable the Cached Mode in Horizon View.
So far so great, right?! That is what I thought also. But, a different phenomenon exists; Office 365.
When clients are using Office 365, and to get more specific, also make use of the email part of it, different rules apply. In that case, the Exchange server isnt sitting within the customers data center, right near the virtual desktops. The Exchange Server might be inside a different country. I have heard several customers now, praoclaiming that without using file, the performance of Exchange in Office 365 isnt as it accustomed to be when Exchange was on premises.
So, dealing with this new situation? Best practice is usually to avoid files in the Horizon View environment but performance requires them whenever using Exchange in Office 365. What to perform? Well, there's two options. Well, 2. Im not sure you want to make use of option 1 but a couple of of exceptions, it may very well be a valid solution Below the two solutions:
Use a Full Clone Dedicated VM for users and encourage the Cached Mode. gets created however the VM wont get deleted and also a user always will end up for the same VM. For a handful users this might be an option.
App Volumes: Use the Writable Disk feature of App Volumes for users to keep file. With a writable volume, user data in a very VM could be redirected for this writable volume. This way, it is possible to files with all the Linked Clone Floating desktops and delete/refresh these desktops after use. Next time a person logs on into a clean VM, you writable volume with gets mounted and an individual can use Outlook with all the same performance as before.
Use the App Volumes Profile template on your writable volumes. This way, a users profile could possibly get redirected for the writable volume. By default, file has written inside of a users profile.
Use the UIA User Installed Apps template for the writable disks. This way you don't possess to redirect a users whole profile but merely file. You can make use of this approachwhen you make use of a profile management/user environment management tool like VMware UEM, where UEM saves settings for users to your central place. Make sure you take file outside a users profile; by way of example, write it to C:Outlookdata. Saving file to your different location is quite possible via a GPO/ADMX setting /en-us/library/c6f4cad9-c918-420e-bab3-8b49e1885034ConfigureDefaultOST
If you arent knowledgeable about App Volumes, App Stacks and/or Writable Volumes, please check this out VMware blog.
In the very last couple of weeks I have been presenting about VMware Professional Services, and much more specific, that they handle a View project from start to finish. VMware PSO follows a standardized framework to produce a successful Horizon View implementation. This framework, within my honest opinion, isnt too difficult but surprisingly, I hardly begin to see the steps with this framework being taken by customers or partners when doing a VDI project.
I would prefer to share the framework with you therefore you will know how we are approaching a greater Horizon View project. And no, this method isnt a secret. In fact, we have a public white paper available around the VMware website which references this framework and just how we used this which has a customer, a vehicle manufacturer, to return up having a 2, 100 seat, twin data center Horizon View design and implementation.
During this phase, one from the steps is usually to investigate your overall environment: you monitor your physical desktop environment and that means you gather info on RAM, CPU, IO and application usage. Tools to complete this in a very detailed matter are, by way of example, Lakeside Systrack and Liquidware Labs Stratusphere. A new as well as simple tool may be the VMware Cloud-Hosted Systrack tool. This will provide you with a good understanding about resource utilization of your employees. These tools will likely come up with reports or a recommendation how many specific ESXi servers you will want when moving towards the virtual world. And yes, I agree, the virtual environment look different than the physical one, and resource usages might be a bit different but at the very least your can have a good understanding on resource usage but not completely be within the dark.
Also on this phase is describing/understanding the organization needs. This is a crucial step because this can be the justification to the project and within the end, the justification for your available budget. You can read the company drivers from the car manufacturer use case.
One on the steps to take on this phase should be to organize workshops. Get employees involved also. Interview them, inquire further what they think regarding the current environment, what is usually done differently, better.
Also, build business use case. Describe which groups are present from the organization; exactly what do these groups needs to have from an IT viewpoint.
Another step should be to build a small-scale Proof of Concept/Proof of Technology.
No real ought to explain this phase but see below the steps to adopt within this phase. And do follow them clockwise. To give you a good example: I have seen customers buying end point devices first and within the end figuring out they didnt purchase the right end points.
Start with Use Case Definitions. Know which groups and users are as part of your organization and exactly what desktop and apps you would like them to have.
With the Use Cases at heart, it is possible to make a Pool Design easily and with that at heart, you are able to design View Blocks and Pods, design vSphere, storage and networking. Last but not least, since you know what customers need for getting and how they will have it, you know whatever they need to access everythingthe end points.
In this phase you'll build the designed environment. An important step we have found load testing. Test the environment and find out if your design is using the services of full load. If it isnt behaving not surprisingly, this would be the time for making adjustments like adding more resources.
And the past phase is always to optimize your newly implemented solution, check it's according tips etc. After which you can carry it into production.
These will be the phases we follow within a project. Again, no brain surgery but an incredibly structured method of handling a project. Hopefully you imagine a lot of these steps are open doors/obvious. I just seen in reality this framework is simply not that common.
Recently, I have done a Proof of Concept with a customer site with App Volumes. What I didnt know was the fact this customer was using RES Workspace Manager. Right after we started the PoC, we found App Volumes and RES didnt like one another.
Both App Volumes and RES use filter drivers, and the drivers are conflicting. Symptons are; startmenu settings, that come form RES, arent coming through. Also, after mounting an App Volumes app stack, no desktop details are flowing back on the RES management console.
To solve this, you should update your app stacks as well as your templates. You have to customize the file as part of your app stack/template and add exclusions for RES.
To improve your app stacks, makes use of the update button from the App Volumes management interface, provision the app stacks, log on to your provisioning machine and study to and edit the file.
To improve your template, stick to the procedure described with this KB article.
Below you might find the exclusions for RES for at the same time 32-bit as 64-bit OSs. After adding these exclusions, App Volumes and RES worked happily together.
I need to admit, precisely the name helped me curious already. But, after looking at about Enzo, seeing the videos and speaking with colleagues, my curiosity have the roof because everything about Enzo is bold!
Just several statements;
From scratch, develop the first desktop installed and operating in an hour,
From 1 or 2, 000 desktops in twenty minutes,
Create 100 desktops within a minute,
No more downtime for app, OS and infrastructure/system updates,
Desktops may be placed on premises, within the Cloud or both, and move rid of it and forth,
It will definitely cost less than a cup of joe.
Enzo is a brand new way of building, delivering and managing virtual workspaces apps and desktops having a unified, single pane of glass management interface. Administrators can manage these workspaces on premises and from the Cloud, and move the apps and desktops between your 2.
Which components make Enzo?
The ground layer is Enzo Ready Infrastructure. The may be EVO:RAIL, EVO:RACK or another Hyper Converged Infrastructure appliance from VMware partners which can be Enzo enabled. The intelligence that's responsible to the set up, orchestration and automation originates from VMware Smart Node technology. This might be a virtual appliance, pre configured, sitting around the appliances.
The second layer may be the desktop layer. Because of latest technologies like instant cloning and I will write a blog about that soon Enzo will likely be capable of getting desktops installed and operating in seconds. Not only cloning may go incredibly fast, and you most likely will save on vms because over provisioning of vms will likely be reduced. Just-in-Time desktop means vms is going to be created when users are demanding them. Nowadays, vms are provisioned in the beginning most on the time. With JIT desktops, other solutions like App Volumes and VMware User Environment Manager come into play to provide apps and personalize the desktop.
layer may be the management layer. It is called the Enzo Control Plane. This web-based portal are going to be delivered to customers to be a cloud based service. It will probably be hosted on VMwares vCloud Air platform. Via this portal you'll be able to set up your Enzo environment, deliver apps and desktops and monitor all components. And because of this hosted portal, you are able to connect your private environment to public cloud environments and move apps and desktops from 1 for the other.
A public beta may come out come early july. Visit /enzo.There you are able to register for Early Access and find more info on Project Enzo, watch a relevant video and webinar about Enzo.
More info ahead about this amazing project. Stay tuned
A several years ago, I had the pleasure for being introduced to Atlantis Computing.Atlantis would help solving the storage IO issues customers were facing when implementing VDI. Basically their solution would cache storage IO in memory making sure that disks wouldnt function as bottleneck anymore. Nowadays, Atlantis does much more than that and they also call it storage optimization.
Atlantis ILIO, the item name, comes as being a virtual appliance and runs for the VMware vSphere hypervisor. You need a home appliance on every ESX host. Traditionally, that appliance sits between virtual machines and storage local storage and/or shared storage. The appliance is applying physical ESX memory because of its operation. The appliance caches storage IO plus does inline deduplication. By doing that, it boosts VDI performance, making you able to run more VMs per storage device plus, its not necessary a high performance storage device. With ILIO Diskless VDI, you dont even need physical storage anymore. VMs are running in memory.
When you have ESX servers attached to shared storage, for VDI, you may lower the specs of the SAN. You need less performance as well as less disk capacity from a array. Pick a more mainstream array as opposed to SSD based arrays. Eventually this comes down to your lower price per virtual desktop. Also, concerns around storage with VDI decreases important. VDI doesnt need to become difficult anymore. This solution is an excellent fit for stateful/dedicated full clone desktops
More and more company is running stateless desktops on local ESX storage so no need for a shared storage array for anyone VMs. For storage sometimes they chose SSDs or FusionIO for performance. To save on capacity, you might use ILIO purely for deduplication but in addition think in regards to the ILIO Diskless VDI option: no storage in any way. All VMs run from ESX memory. The ILIO appliance takes ESX memory and uses it a datastore.
This week I also heard the next: use local storage for stateful/dedicated full clone virtual desktops. Use ILIO to enhance performance and dedup and likewise use VMware Mirage like a backup tool, in the event an ESX host would fail and backup local data and apps. Interesting thought, isnt it?!
Bottom line, there are numerous solutions which could absolutely help together with the VDI storage IO issues. They all have an alternative price, purpose and perhaps even present you with additional advantages. Take a fantastic look at these solution and chose what type suits you best and provide you the lowest price per desktop.
The first book on VMware ThinApp 4.7 is published!! Specialist Systems Engineer ThinApp at VMware Peter Bjork will be the author of VMware ThinApp 4.7 Essentials.
ThinApp 4.7 design and implementation suggestions
Good news became available last night: VMware View has become compatible with vSphere 5.1. A new build of ESXi 5.1 continues to be released. Also, a patch for for ESXi continues to be released. Install either of which and you are going to be capable to run View 5.1 along with vSphere 5.1.
When I received my invitation for VMworld Barcelona 2012 as booth staff, I noticed I was scheduled for that VMware Workstation 9 and Fusion 5 booth. I honestly must say that wasnt my first choice. In VMware I mostly cover VMware View, ThinApp and Horizon. I considered Workstation and Fusion for being more consumer products instead of enterprise. How wrong was I!
I had the pleasure of talking to your Product Manager of VMware Workstation/Fusion, Jason Joel but in addition the pleasure of speaking with many clients during VMworld. Four things I noticed inside my conversations:
I pointed out that still, you'll find people who do not know Workstation/Fusion. Well, permit me to quickly introduce Workstation and Fusion: Both items are, that which you call, a kind 2 hypervisor. So, you install both programs over an Operating System. You install Workstation in addition to a Windows OS one example is Windows 7 and/or 8 so you install Fusion in addition to Mac OSX one example is Mountain Lion. It is called a sort 2 hypervisor since you install the programs over an OS rather than on top of bare metal. Installing a hypervisor over bare metal is called a kind 1 hypervisor. vSphere/ESX is a good example of a sort 1 hypervisor.
After installing Workstation/Fusion buyers ., you may install WS on Windows 8 and Fusion on Mountain Lion, you are going to be capable of create virtual machines on top of one's desktop/laptop. To supply you with an idea:
You can run Windows 8, 7, XP, Ubuntu, Server 2012, Hyper-V and vSphere/ESX inside Workstation. Also, you are able to run Windows 8, 7, XP, Ubuntu, Mountain Lion, Server 2012, Hyper-V, and vSphere/ESX inside Fusion.
The second thing I noticed is the fact that a lot of people are running just one or both products privately. User who will be using Workstation and/or Fusion on their own private laptops, testing software, getting knowledgeable about new Operating Systems, following courses and need to do tests. Although I expected this use case, I still was impress with all the amount of individuals who are with such products this way
The use case by 50 percent also expanded to your enterprise: users using WS/Fusion for their corporate desktops/laptops for testing purposes. I do should admit, I didnt expect this use case using this amount of users. I know many customers giving developers/testers a View desktop besides their normal laptop.
Fourth, I do expect WS/Fusion to become considerably more enterprise, meaning, both products are certainly separate on the rest of VMware EUC now, but I do think it really is coming together. During the EUC keynote with Steve Herrod and Vittorio Viarengo, VMware View and Mirage merged. So, what will be the place for WS/Fusion? BYOD! Today, you could potentially install Fusion with a private BYO Mac, purchase a Windows OS, Mirage agent as well as the company can stream a company image for your Mac. Yep, cool, but nonetheless too manual to my liking. I would like to view a system where, via Mirage, an image has streamed with WS/Fusion wrapped around it. Yes, like WS Ace Edition had with VMware Player from the old days:. Maybe it even can be an idea to produce a Mirage Image available via PXE: switch on Fusion, PXE boot and receive the initial image. Another option would be to manually install WS/Fusion, and IT provides you with a link to some streamlined Windows package using the Mirage agent. Click, download, open and run it. Maybe thinking out with the box, maybe you can find tools like Apple Remote Desktop to push Fusion and after that the VM.
After spending a week using the VMware team and partners/customers I possess the feeling WS/Fusion is usually a bit under estimated, under valued maybe not recognized even though it won many awards. Both products arent only for people in the home. It also is for your enterprise. I agree, both need more features around policies like expiration dates, policies around physical and virtual networks etc. Work being done, yes. Know that WS/Fusion are evolving, are wonderful products and is usually used inside enterprise. Do read concerning the features like restricted VMs. Also, do understand both backpacks are great test environments for View and example would be the video driver. In all products this driver will be the same and may be tested in WS/Fusion first before it will come into View/vSphere.
Lastly, do check out WSX. WSX can help you remotely connect for your hypervisor/VM and show a VMs content to, for instance a tablet. Read more over it here.
I became to comprehend WS/Fusion much more after actually talking to Product Management, customers and partners. It is usually a great and mature products that may integrate with additional products.
The views expressed anywhere within this site are strictly mine instead of the opinion nor take a look at VMware.
The very first time that you create a forex account in Outlook and connect in an Exchange server, it will require a while for Outlook to acquire ready for usage and for you to see you calendar items and emails. During the preparation of Outlook, file is now being created in your machine in C:UsersuserAppDataLocalMicrosoftOutlook.
So, why file being created? file has created therefore you will have a nearby copy coming from all items being stored with an Exchange server. Emails, calendar items, reminders etc. This Cached Exchange Mode means that you can keep on doing work in Outlook even if you dont have vital offline on the Exchange server. A sync with all the server can happen when your device is connected to your Exchange server. By default, this method is switched on but you can pick to turn it well. Besides the offline reason, moreover, you may could say a cached version is improving performance and buyer experience.Redirecting file with a share is backed up by Microsoft, however with restrictions. If you want to understand the basics files, go here. In this blog, Im only files are incredibly popular too and you are able to use exactly the same solution s as I describe files.
In a VDI world, virtual desktops are residing very close for the Exchange server within the data center. And, within a VDI concept, there's no offline strategy for working thinking about the Exchange Server. So, in thiscase, there is absolutely no real reason to turn about the Cached Exchange Mode. Especially, when you happen to be working with Linked Clone Floating VMs in VMware Horizon View, the location where the clones gets deleted/refreshed after logoff. One thing you dont want would be to create file whenever a user logs on with a clean virtual desktop. Best practice is always to disable the Cached Mode in Horizon View.
So far so competent, right?! That is what I thought also. But, a fresh phenomenon exists; Office 365.
When people are using Office 365, and to get more specific, also utilize email part of it, different rules apply. In that case, the Exchange server isnt sitting inside customers data center, right near the virtual desktops. The Exchange Server might be within a different country. I have heard several customers now, proclaiming that without using file, the performance of Exchange in Office 365 isnt as it familiar with be when Exchange was on premises.
So, how to cope with this new situation? Best practice is usually to avoid files in the Horizon View environment but performance requires them when you use Exchange in Office 365. What to complete? Well, the two options. Well, 2. Im not sure you want make use of option 1 but a couple of of exceptions, it may very well be a valid solution Below both the solutions:
Use a Full Clone Dedicated VM for users and give the Cached Mode. gets created however the VM wont get deleted as well as a user always will end up for the same VM. For a handful users this can be an option.
App Volumes: Use the Writable Disk feature of App Volumes for users to save file. With a writable volume, user data in a very VM could be redirected to this particular writable volume. This way, you'll be able to files when using the Linked Clone Floating desktops and delete/refresh these desktops after use. Next time a person logs on with a clean VM, you writable volume with gets mounted and an individual can use Outlook together with the same performance as before.
Use the App Volumes Profile template for the writable volumes. This way, a users profile are certain to get redirected for the writable volume. By default, file is now being written inside of a users profile.
Use the UIA User Installed Apps template for ones writable disks. This way you do not have to redirect a users whole profile however file. You will use this approachwhen you employ a profile management/user environment management tool like VMware UEM, where UEM saves settings for users to some central place. Make sure you take file outside a users profile; for instance, write it to C:Outlookdata. Saving file to some different location can be done via a GPO/ADMX setting /en-us/library/c6f4cad9-c918-420e-bab3-8b49e1885034ConfigureDefaultOST
If you arent accustomed to App Volumes, App Stacks and/or Writable Volumes, please look at this VMware blog.
In the very last couple of weeks I have been presenting about VMware Professional Services, and much more specific, the direction they handle a View project from start to finish. VMware PSO follows a standardized framework to supply a successful Horizon View implementation. This framework, around my honest opinion, isnt nuclear physics but surprisingly, I hardly begin to see the steps in this particular framework being taken by customers or partners when they're doing a VDI project.
I would prefer to share the framework with you which means you will appreciate how we are approaching an increased Horizon View project. And no, this method isnt a secret. In fact, there's a public white paper available around the VMware website which discusses this framework and just how we used this that has a customer, a vehicle manufacturer, to return up that has a 2, 100 seat, twin data center Horizon View design and implementation.
During this phase, one in the steps should be to investigate your environment: you monitor your physical desktop environment and that means you gather info on RAM, CPU, IO and application usage. Tools to perform this in a very detailed matter are, as an example, Lakeside Systrack and Liquidware Labs Stratusphere. A new and tool could be the VMware Cloud-Hosted Systrack tool. This will provide a good understanding about resource using of your employees. These tools will likely come up with reports or even a recommendation regarding how many specific ESXi servers you'll need when moving towards the virtual world. And yes, I agree, the virtual environment will be different than the physical one, and resource usages would have been a bit different but at the very least your should have a good understanding on resource usage instead of completely be from the dark.
Also on this phase is describing/understanding this company needs. This is a essential step because this could be the justification for that project and from the end, the justification with the available budget. You can read the business enterprise drivers inside car manufacturer use case.
One with the steps to take in this particular phase is usually to organize workshops. Get employees involved at the same time. Interview them, inquire further what they think concerning the current environment, what might be done differently, better.
Also, build business use case. Describe which groups are present inside organization; exactly what do these groups needs to acquire from an IT viewpoint.
Another step is usually to build a subtle Proof of Concept/Proof of Technology.
No real must explain this phase but see below the steps to look at within this phase. And do follow them clockwise. To give you one example: I have seen customers buying end point devices first and inside the end discovering they didnt pick the right end points.
Start with Use Case Definitions. Know which groups and users are in your organization and exactly what desktop and apps you would like them to have.
With the Use Cases under consideration, you are able to make a Pool Design easily and with that in your mind, you'll be able to design View Blocks and Pods, design vSphere, storage and networking. Last but not least, simply because you know what clients need for getting and how they will understand it, you know what you need to access everythingthe end points.
In this phase you'll build the designed environment. An important step here's load testing. Test the environment to see if your design is dealing with full load. If it isnt behaving needless to say, this could be the time to create adjustments like adding more resources.
And a final phase would be to optimize your newly implemented solution, check it's according suggestions etc. After which you can carry it into production.
These will be the phases we follow throughout a project. Again, no too difficult but an extremely structured strategy for handling a project. Hopefully you would imagine a lot of these steps are open doors/obvious. I just welcomed in reality until this framework isn't really that common.
Recently, I have done a Proof of Concept with a customer site with App Volumes. What I didnt know was the fact until this customer was using RES Workspace Manager. Right after we started the PoC, we discovered App Volumes and RES didnt like 1 another.
Both App Volumes and RES use filter drivers, that drivers are conflicting. Symptons are; startmenu settings, that can form RES, arent coming through. Also, after mounting an App Volumes app stack, no desktop info is flowing back towards the RES management console.
To solve this, you need to update your app stacks plus your templates. You have to change the file as part of your app stack/template and add exclusions for RES.
To improve your app stacks, utilize the update button inside App Volumes management interface, provision the app stacks, log on towards the provisioning machine and look at to and edit the file.
To remodel your template, stick to the procedure described on this KB article.
Below you might find the exclusions for RES for too 32-bit as 64-bit OSs. After adding these exclusions, App Volumes and RES worked happily together.
I should admit, precisely the name forced me to be curious already. But, after looking at about Enzo, seeing the videos and speaking to colleagues, my curiosity experienced the roof because everything about Enzo is bold!
Just several statements;
From scratch, contain the first desktop operational in an hour,
From one or two, 000 desktops in twenty minutes,
Create 100 desktops within a minute,
No more downtime for app, OS and infrastructure/system updates,
Desktops is usually placed on premises, inside Cloud or both, and move it well and forth,
It costs less than a mug of coffee.
Enzo is a whole new way of building, delivering and managing virtual workspaces apps and desktops having a unified, single pane of glass management interface. Administrators can manage these workspaces on premises and from the Cloud, and move the apps and desktops between 2.
Which components make Enzo?
The ground layer is Enzo Ready Infrastructure. The could be EVO:RAIL, EVO:RACK or some other Hyper Converged Infrastructure appliance from VMware partners that happen to be Enzo enabled. The intelligence that's responsible to the set up, orchestration and automation derives from VMware Smart Node technology. This would have been a virtual appliance, pre configured, sitting within the appliances.
The second layer could be the desktop layer. Because of the latest technologies like instant cloning and I will write a blog about that soon Enzo will probably be capable of getting desktops ready to go in seconds. Not only cloning should go incredibly fast, nevertheless, you most likely will save on vms because over provisioning of vms will probably be reduced. Just-in-Time desktop means vms will probably be created when users are demanding them. Nowadays, vms are provisioned beforehand most in the time. With JIT desktops, other solutions like App Volumes and VMware User Environment Manager come into play to supply apps and personalize the desktop.
layer would be the management layer. It is called the Enzo Control Plane. This web-based portal will probably be delivered to customers to be a cloud based service. It will likely be hosted on VMware s vCloud Air platform. Via this portal you may set up your Enzo environment, deliver apps and desktops and monitor all components. And because of this hosted portal, you are able to connect your private environment to public cloud environments and move apps and desktops from 1 on the other.
A public beta may come out come july 1st. Visit /enzo.There you are able to register for Early Access and obtain more info on Project Enzo, watch videos and webinar about Enzo.
More info in the future about this amazing project. Stay tuned
A few years ago, I had the pleasure to be introduced to Atlantis Computing.Atlantis would help solving the storage IO issues customers were facing when implementing VDI. Basically their solution would cache storage IO in memory making sure that disks wouldnt become the bottleneck anymore. Nowadays, Atlantis does considerably more than that and in addition they call it storage optimization.
Atlantis ILIO, the merchandise name, comes like a virtual appliance and runs around the VMware vSphere hypervisor. You need a home appliance on every ESX host. Traditionally, that appliance sits between virtual machines and storage local storage and/or shared storage. The appliance is utilizing physical ESX memory for the operation. The appliance caches storage IO and as well does inline deduplication. By doing that, it boosts VDI performance, causes you to able to run more VMs per storage device plus, it's not necessary a high performance storage device. With ILIO Diskless VDI, you dont even need physical storage anymore. VMs are running in memory.
When you make use of ESX servers linked to shared storage, for VDI, you may lower the specs of the SAN. You need less performance plus less disk capacity out of your array. Pick a more mainstream array as opposed to SSD based arrays. Eventually this comes down with a lower price per virtual desktop. Also, worries around storage with VDI decreases important. VDI doesnt need for being difficult anymore. This solution is a great fit for stateful/dedicated full clone desktops
More and more clients are running stateless desktops on local ESX storage so no need for a shared storage array for anyone VMs. For storage sometimes they chose SSDs or FusionIO for performance. To save on capacity, you might use ILIO purely for deduplication but additionally think concerning the ILIO Diskless VDI option: no storage whatsoever. All VMs run from ESX memory. The ILIO appliance takes ESX memory and uses it as being a datastore.
This week I also heard this: use local storage for stateful/dedicated full clone virtual desktops. Use ILIO to enhance performance and dedup and likewise use VMware Mirage to be a backup tool, in the event an ESX host would fail also to backup local data and apps. Interesting thought, isnt it?!
Bottom line, there are various solutions that may absolutely help with all the VDI storage IO issues. They all have another price, purpose along with perhaps even offer you additional advantages. Take a great look at these solution and chose what kind suits you best and offers you the lowest price per desktop.
The first book on VMware ThinApp 4.7 has become published!! Specialist Systems Engineer ThinApp at VMware Peter Bjork will be the author of VMware ThinApp 4.7 Essentials.
ThinApp 4.7 design and implementation recommendations
For more details about the great book and also to order it, use the subsequent link: /vmware - thinapp - 4-7 - essentials/book
Good news became available last night: VMware View is compatible with vSphere 5.1. A new build of ESXi 5.1 continues to be released. Also, a patch for for ESXi is released. Install either of these and you'll be capable to run View 5.1 along with vSphere 5.1.
When I received my invitation for VMworld Barcelona 2012 as booth staff, I noticed I was scheduled with the VMware Workstation 9 and Fusion 5 booth. I honestly must say that wasnt my first choice. In VMware I mostly cover VMware View, ThinApp and Horizon. I considered Workstation and Fusion to get more consumer products but not enterprise. How wrong was I!
I had the pleasure of talking for the Product Manager of VMware Workstation/Fusion, Jason Joel but additionally the pleasure of conversing with many customers during VMworld. Four things I noticed in doing my conversations:
I remarked that still, you can find people who have no idea Workstation/Fusion. Well, ok, i'll quickly introduce Workstation and Fusion: Both backpacks are, what we should call, a sort 2 hypervisor. So, you install both programs together with an Operating System. You install Workstation over a Windows OS for instance Windows 7 and/or 8 and also you install Fusion along with Mac OSX one example is Mountain Lion. It is called a sort 2 hypervisor when you install the programs along with an OS instead of on top of bare metal. Installing a hypervisor together with bare metal is called a sort 1 hypervisor. vSphere/ESX is an illustration of a sort 1 hypervisor.
After installing Workstation/Fusion you will find, you are able to install WS on Windows 8 and Fusion on Mountain Lion, you'll be capable of create virtual machines on top of one's desktop/laptop. To supply you with an idea:
You can run Windows 8, 7, XP, Ubuntu, Server 2012, Hyper-V and vSphere/ESX inside Workstation. Also, you are able to run Windows 8, 7, XP, Ubuntu, Mountain Lion, Server 2012, Hyper-V, and vSphere/ESX inside Fusion.
To find out about Workstation, read here:
To uncover more about Fusion, read here:
The second thing I noticed is the fact a lot of people are running both or both products privately. User who will be using Workstation and/or Fusion on his or her private laptops, testing software, getting informed about new Operating Systems, following courses and need to do tests. Although I expected this use case, I still was impress together with the amount of people that are by using these products this way
The use case into two also expanded for the enterprise: users using WS/Fusion on their own corporate desktops/laptops for testing purposes. I do must admit, I didnt expect this use case on this amount of users. I know many customers giving developers/testers a View desktop besides their normal laptop.
Fourth, I do expect WS/Fusion to become much more enterprise, meaning, both products are certainly separate on the rest of VMware EUC now, but I do think it really is coming together. During the EUC keynote with Steve Herrod and Vittorio Viarengo, VMware View and Mirage merged. So, what may be the place for WS/Fusion? BYOD! Today, you could potentially install Fusion using a private BYO Mac, purchase a Windows OS, Mirage agent plus the company can stream a business image on your Mac. Yep, cool, but nevertheless too manual to my liking. I would like to visit a system where, via Mirage, an image has been streamed with WS/Fusion wrapped around it. Yes, like WS Ace Edition had with VMware Player inside old days:. Maybe it even can be an idea to create a Mirage Image available via PXE: activate Fusion, PXE boot and obtain the initial image. Another option should be to manually install WS/Fusion, and IT supplies you with a link to some streamlined Windows package while using Mirage agent. Click, download, open and run it. Maybe thinking out with the box, maybe you will find tools like Apple Remote Desktop to push Fusion and after that the VM.
After spending a week with all the VMware team and partners/customers I develop the feeling WS/Fusion is usually a bit under estimated, under valued maybe not recognized even though it won many awards. Both products arent only for people in the home. It also is with the enterprise. I agree, both need more features around policies like expiration dates, policies around physical and virtual networks etc. Work being done, yes. Know that WS/Fusion are evolving, are excellent products and may be used inside the enterprise. Do read in regards to the features like restricted VMs. Also, do understand both goods are great test environments for View and example could be the video driver. In all products this driver may be the same and continues to be tested in WS/Fusion first before it will come into View/vSphere.
Lastly, do check out WSX. WSX means that we can remotely connect on your hypervisor/VM and show a VMs content to, for instance a tablet. Read more concerning this here.
I became to comprehend WS/Fusion much more after speaking to Product Management, customers and partners. It can be a great and mature products that may integrate with additional products.
The views expressed anywhere with this site are strictly mine instead of the opinion nor take a look at VMware.
Добавлена рабочая версия 14.0.0.323 с Русификатором
Всё распаковывается и прекрасно работает.
Архиватор WinRar v.5.21 x64
NEW: Providing VNC Server and VNC Viewer tend to be version 5.3, connections utilize very latest RFB 5 protocol for enhanced security, with updated cipher suites and support for Perfect Forward Secrecy.
NEW: VNC Server by having an Enterprise or possibly a Personal license can restrict the IP addresses on what it listens for connections, lowering the attack surface. Note the InTransports parameter is removed, which implies VNC Server which has a Free license cannot listen on just IPv4 addresses, or on just IPv6 addresses.
NEW: VNC Viewer can send keep alive messages to VNC Server so that you can maintain perhaps minimized connections that will otherwise be considered idle by routers or gateways, and unexpectedly terminated. Conversely, a similar mechanism can cleanup connections which have terminated, perhaps on account of network failure.
NEW: VNC Server has a whole new screen capture architecture which is both tougher and responsive. Users should see fewer disconnections and reconnections when transiting between desktop and login screens. System administrators should be aware of a brand new vncagent binary and process.
Screen capture on Windows 8 computers using DirectX has become more efficient, giving a better buyer. As part of this work, the UpdateMethod parameter may be renamed CaptureMethod on all platforms, and has now new defaults which will make choosing the optimal capture method easier.
Configuring to protect VNC Server with the command line or using policy is actually simpler using new, separate, more intuitive Authentication and Encryption parameters. On upgrade, SecurityTypes and UserPasswdVerifier values are mapped appropriately unless a VNC password is mandated using policy.
The vncpasswd utility presenting flags that will make specifying a VNC password for VNC Server in most modes easier. In addition, running the utility without having a flag now shows the support rather than defaulting to VNC Server in User Mode.
The Password parameter is actually included in policy template files so VNC Server by having an Enterprise license might be remotely provisioned using a VNC password. To obtain a password inside correct obfuscated format, run vncpasswd - print.
NEW: Support for Windows 10.
NEW: VNC Viewer can send media keys for example Play and Volume Up to VNC Server.
NEW: VNC Server can remap keys received from VNC Viewer, perhaps to inject a non-native character or control key.
a few cloud related bug fixes, mostly for DropBoxV2 and Amazon Cloud Drive.
fixes instability of real-time profiles for those who have several sharing the identical event watching thread concentrating on the same source folders around the same drive. A bug was fixed in 7.30 but unfortunately a whole new bug was added at a similar time.
Те кто думает, что это дрова на видюху.
От NVIDIA надо только драйвер ставить.
Добавлена версия 5.20 Build 515 - списка изменений не встретил
Pinnacle Studio Ultimate 19.0 keygen CORE - файл не распаковывается, с ошибкой. Проверьте, замените.
При распаковке архива Pinnacle Studio Ultimate 19.0.1.245 x64 архиваторами WinRar и 7-Zip тоже 2 две ошибки.
Может надо РІСЃС‘-таки проверить архивы? Рли удалить?
Рли напишите каким архиватором Рё какой версии распаковывать.
Есть ли смысл качать остальные?
антивирь с похожим дизайномКВАДРАТНЫМ, а то этот все равно ругаеться на мои SFX архивы
А что, прослеживается взаимосвязь между квадратно-плиточной мордочкой АВ и его паранойей?
А настройки сайтов зачем удалять?Настройки они на то и настройки, что бы отображало так как тебе надо.
Значит Р’С‹ РЅРµ сталкивались СЃ внедрением вредоносного РєРѕРґР° РЅР° РџРљ через эти самые настройки сайтов. Рспользую массу различных порталов Рё сайтов. РРЅРѕРіРґР°, как правило нахожу РІСЃСЏРєСѓСЋ нечисть РІ РІРёРґРµ ехе или РґСЂСѓРіРёС… исполнительных файлов РІРѕ временных папках. РћРґРёРЅ только этот чего стоит. Блокировщик РІ большинстве случаев РЅРµ даёт загружаться этим временным исполнительным файлам. Другими словами РІ помощь антивирю. Отсюда привычка полной очистки данных папок после каждой сессии для страховки.
Странно-у меня нет ничего, а вот малая мне написала, что именно к ней обнова прилетела Обое сидим в Польше-но в разных городах Я сразу сюда, на и точно, читаю вот, прилетело-только как то не всем сразу, получается.
Чтобы видеть скрытый текст, вам надо зарегистрироваться и набрать 5 комментариев, перейдя в группу Заглянувший, ограничений больше не будет.
with 902/35 signatures, Main GUI changed
Обновилась мощная программа для виртуализации и создания так называемых портативных приложений переносимых, цель программы помочь пользователю перенести уже существующие программы на другие платформы без перекомпиляции последующего тестирования, в полной новости каждый из вас сможет скачать VMware ThinApp.
Данный продукт это отличное решение для виртуализации приложений. Программа умеет легко выполнять совершенно любое приложение и пир этом вам не надо будет его устанавливать в традиционном нашем понимании. Все создаваемые ресурсы будут сохранять на выбранном диске в папке с программой. Если какое-то приложение будет запрашивать любой ресурс, то слой виртуализации VMware ThinApp сразу перехватит исходящий запрос и отправит значение уже из файла который находится на диске. Таким образом программа обманута и она будет считать себя полностью установленной.
VMware ThinApp не требует от пользователя установки ни как программы ни так драйверов, поэтому вы сможете запускать виртуализированные продукты с любого накопителя типа USB, можно также запускать с сетевых дисках не прибегая к правам администратора. Продукт VMware ThinApp умеет много чего делать, например он легко ведет преобразование обычного установочного в файлы, которые уже будут содержать в себе все самое необходимое для запуска приложения. Обратите внимание, что программа сможет создать переносимое приложение основываясь только на данных о изменениях в системных файлах, тоже самое относится и к реестру, однако для этого вам надо будет запустить режим сканирования до и после установки приложения.
Почти все приложения для Windows программа VMware ThinApp может сделать переносимыми, однако конечно же есть исключения. Например продукт не сможет работать с приложениями, которые требуют установки драйверов устройств, также не получится работать с приложением которое поддерживает аппаратную защиту от копирования. В целом программа ясна, пользоваться удобно, все понятно и просто, если у вас возникнут какие-то вопросы, пробуйте спрашивать тут или на форуме, думаю вам помогут, а я заканчиваю обзор, всем приятного дня!
Работает ли в Windows XP?, и как обстоят дела с Windows 10?
Укажите точную версию которую можно использовать для сборок, запускаемых в Windows 10
VMware ThinApp 5.2 props up the Windows 10 computer.
The ThinApp 5.2 release resolves this issues:
Microsoft PowerPoint 2010 crashes at launch on 32-bit Windows 10 machines.
Resolution: This issue is resolved in ThinApp 5.2.
Runtime error is displayed for the launch of 64-bit ThinApped applications on 64-bit Windows 10 machines.
Resolution: This issue is resolved in ThinApp 5.2.
The ThinApped Setup Capture program fails on 64-bit Windows 10 machines.
Resolution: This issue is resolved in ThinApp 5.2.
All 64-bit ThinApped applications do not launch on 64-bit Windows 10 machines.
Resolution: This issue is resolved in ThinApp 5.2.
All 32-bit ThinApped applications neglect to launch on 64-bit Windows 10 machines.
Resolution: This issue is resolved in ThinApp 5.2.
можно по подробнее в какой версии! и какое издание!
Под Windows 10 работают версии до 5 только x86. Запустилась 4.7.3
О дате релиза ничего не известно, просто сказано ожидать анонса.
А порташки в вин 10 будут работать? А то сколько не делал в семёрке всё пашет а в 10-ке нет
Чтобы видеть скрытый текст, вам надо зарегистрироваться и набрать 5 комментариев, перейдя в группу Заглянувший, ограничений больше не будет.
sure, РЅРµ обижайтесь. РЇ сделал перевод для людей Рё обеими руками Р·Р° его распространение. Просто обём работы большой, Рё возможны огрехи. Если замечаю сам, или подсказывают заинтересованные юзеры, вношу поправки. РРЅРѕРіРґР° правки важные.
На двух указанных ресурсах всегда актуальная редакция. Нежелательно, чтобы по другим ресурсам гуляла начальная редакция. Хотя, это не страшно - в предисловии о возможном обновлении я написал и указал, где брать.
pavlaf, хорошо, больше ваши мануалы выкладывать не буду. Делал вам рекламу
Рчем - то не угодил? Бесплатный обменник, файлы порой удаляют, но это и на других файлообменниках делают. В остальном всё устраивает, ждать не надо, цифры/буквы вводить тоже, что ещё нужно. Может, баннерорезок у кого нет, проблемы и наблюдаются, так это заморочка - проблема самих юзеров, без них и в сеть выходить не стоит.
Вообще-то, что выложено в сети, является де-факто достоянием народа, в противном случае нужно свою работу передавать через личку, хотя всё равно шило в мешке не утаить.
Главное, чтобы юзер выкладывающий материал, не присваивал себе авторских прав. С этим здесь всё в порядке.
На том стоит, и стоять будет тырнет :
Русский перевод руководства пользователя ThinApp 5.1.0. В одном документе объединены руководство пользователя и справочник по параметрам в файлах конфигурации проекта. В архиве три варианта английский, русский и совмещённый русско-английский. В конце имени архива указана дата последней правки: день-месяц-год.
Начальная редакция - 14.11.2014
Текущая редакция - 19.11.2014
sure Рё РґСЂСѓРіРёРµ, РЅРµ выкладывайте перевод мануала РЅР° РІСЃСЏРєРёРµ фаллос-обменники. Оригинал СЏ публикую только РЅР° этих ресурсах. РРЅРѕРіРґР° редактирую для устранения замеченных огрехов Рё обновляю архив РЅР° РѕР±РѕРёС… ресурсах. РџСЂРё этом РЅР° Яндекс Диске ссылка постоянная, Р° РЅР° меняется.
Полный перевод мануала от разработчика. В одном документе объединены руководство пользователя и справочник по параметрам в файлах конфигурации. Три варианта мануала английский, русский и совмещённый русско-английский. В конце имени архива указана дата последней правки документа.
Бредятина невнятная какая-то, простая Cameyo сто крат лучше, даже снимок реестра сделать не может.
Все прекрасно работает. Нужно иметь прямые руки.
ThinApp Package Management, allowing to dynamically reconfigure the attributes of deployed ThinApp packages at runtime
Бредятина невнятная какая-то, простая Cameyo сто крат лучше, даже снимок реестра сделать не может.
Errare humanum est sed stultum est in errore perseverare.
Bandwidth Control Managing desktops and PCs across many remote branch sites is tough. With that at heart, Mirage was made to help IT manage devices across distributed environments. And in these distributed environments, bandwidth can be quite a concern. Image management solutions like Mirage require at the very least some bandwidth to deploy systems and applications. In Mirage 5.1, IT can control the level of bandwidth Mirage clients consume directly through the Mirage management console. IT can set bandwidth limitation dependant on categories like per subnet, or per Active Directory site. Setup is easy and allows IT to not should rely on QoS tools on their own network when working together with Mirage client to server communication.
API Extensibility As part of Mirage 5.1, weve started formalizing and publishing APIs. Customers and partners can utilize the data that Mirage collects to integrate his or her systems with Mirage. If you have something that requires plugging into data and services offered by Mirage, now you are able to connect through with your documented API set. This will be the beginning of the journey to create Mirage more extensible.
Reporting Framework Weve enhanced our reporting framework in Mirage 5.1. IT can create and run reports that happen to be output into HTML or CSV format. Scheduling automatic generation and email of reports helps give IT better analytics and visibility in the different Mirage operations which are being performed. Overall support time might be reduced with quicker to consume reports based from this new framework.
Customer Experience Improvement Program Were always in search of feedback from customers using Mirage. With 5.1, Mirage now includes the VMware Customer Experience Improvement Program CEIP. This an optional, encrypted and anonymous solution to send technical data through the Mirage database and log files to VMware. This helps us improve Mirage solution.
Прога отличная. Только работает она немного дольше чем Cameyo, но зато здесь есть возможность редактирования проекта и сжимания виртуального пакета, что очень даже хорошо. Хотел бы ещё подчеркнуть, что прогу лучше всего использовать на виртуальной чистой ОС.
Русификатор ThinApp 5.0.1-1801916 от Meteor
Спасибо за русик, с ним как-то веселей
Русификатор ThinApp 5.0.1-1801916 от Meteor
Ртот пакет локализации предназначен только для оригинального релиза программы VMware ThinApp v5.0.1 Build 1801916 Рё установленного РІ каталог РїРѕ умолчанию. Выполнить установку русификатора РЅР° РґСЂСѓРіСѓСЋ версию РЅРµ удастся.
Посетители, находящиеся в группе Гости, не могут оставлять комментарии к данной публикации.
Copyright 2009-2015 При размещении материалов на других сайтах обязательна ссылка на данный ресурc.
2015 Free Software KeysFree 3G, 4G, GPRS All Network Settings
DAYU Disk Master Professional 2.6 Free Download Full Version With Lifetime License Code DAYU
AOMEI Partition Assistant Professional 5.6 Free Download Full Version With License Code AOMEI
Hard Disk Sentinel Pro 4.2 4.4 Free Download Full Version Registration Key Hard Disk
HD Video Converter Factory Pro 8.5 Free Download Full Version Lifetime Key Updated HD Video
320X Fresh Socks 5 Proxy Servers 2012 What is SOCKS and What is SOCKS Proxy Server? SOCKS
Muneer Hussain And Tanveer Hussain Are The Security Experts And Blogger From Kashmir Valley. Both Are The Founder Of M14HackersWorld And M14MuscleBase Blogs. At M14HackersWorld Both Writes About Ethical Hacking, Hacking Prevention, Technology, Free Software Keys, Free Internet And Many More Security Related Topic s And At M14MuscleBase Both Writes About MuscleBase For BodyBuilding, Motivation, Exercise Tips Tricks, Supplements, Diet Sechdule And Many More GYM Related Topic s.
Keygen. Crack, Serial, Patch For Softwares