View: 7933|Replies: 31
楼主| 发表于 2022-5-13 14:37:05 | 只看该作者
This post was last edited by 2012wwzrh on 2022-5-13 15:19
微软办公软件 2010
Microsoft Office 2010 is usually used with older plugins or business line applications. This can be problematic as companies are eager to migrate their users to the latest versions of Office 365 or Office 2016, which cannot run concurrently with Office 2010.
Fortunately, Office 2010 applications can run in a Turbo container, allowing them to be isolated from existing installations. Below are the steps required to create your own Office 2010 image.
Architecture
To create the Office 2010 version, you need to use Turbo Studio to take a snapshot. You will need a clean computer or VM to do this (no other applications installed, Office not previously installed). For maximum compatibility, it is recommended to use a Windows 7 x64 snapshot computer and the Office 2010 x86 installer.
Download Microsoft Office 2010 Deployment Tool for App-V. This includes the licensing service components that allow Office 2010 to run in a container. You want the version of the toolkit (64-bit or 32-bit) to match the system architecture (x64 or x86), rather than matching the installation type of Office itself.
Extract the files from the deployment toolkit to the snapshot computer. Install the Office License Service from the extracted deployment toolkit:
msiexec /i OffVirt.msi PROPLUS=1
Note: The parameters passed to OffVirt.msi depend on the Office 2010 product to be installed. For information on available options please see how to sequence Microsoft Office 2010.
Start shooting with Turbo Studio.
Install Microsoft Office 2010. Note: This must be done using a KMS or VLK installer. Retail licenses will not work properly.
If the build includes any other components or plugins, please install them immediately.
After installation is complete, run the installed Office applications to ensure that the initial configuration and licensing are correct.
Capture completed.
After the snapshot is complete, the Microsoft Office Snapshot Wizard will provide you with some options for isolating the profile. In almost all cases, you will need the first option, which is to isolate from the native system. This will allow you to run alongside the native version of Microsoft Office. In cases where Office 2010 containers run with native components and plugins, you may need to select the second option. However, this option usually does not allow for parallel operation with the native Office installation.
Set the "Project Type" to "Independent/ISV Application (EXE)", save the configuration and generate.
测试若要测试 Office 2010 内部版本，请将输出.exe复制到新计算机。你将必须以与在快照计算机上相同的方式安装适用于 App-V 的 Microsoft Office 2010 部署工具包。
楼主| 发表于 2022-5-13 15:20:08 | 只看该作者
Start File Trigger
Container packages can define multiple startup files. These can be activated at startup or configured to start only when a specified trigger is given. This is very useful for suite applications that share most container packages (such as Microsoft Office).
In Turbo Studio, the startup file trigger is managed in the 'Startup File' dialog.
In this example, the application package is defined using three launch files: Word, Excel, and Access. By default, any launch file without a specific trigger or with 'auto-start' enabled will start. No launch file with a trigger (but not 'auto-start') will start unless a trigger is specified. Multiple launch files can have the same trigger to enable grouped launching.
To start the startup file via the trigger, specify its trigger as the first parameter of container.exe:
to launch word
virtual-app.exe WORD
to launch access
virtual-app.exe ACCESS
to launch excel
virtual-app.exe EXCEL
to launch excel as the default
virtual-app.exe
To create an accessible shortcut for the trigger, right-click the packaged executable file and select "Create Shortcut." Then, right-click the newly created shortcut and append the trigger to the "Target" field. Change the shortcut name and icon to distinguish the application entry point that will be launched when the user runs the shortcut.
Worry-Free Coin +10
Collapse Reason
- 5
'Give a thumbs up!'
- 5
发表于 2022-5-14 14:10:39 | 只看该作者
This post was last edited by kli on 2022-5-14 14:17 Seeing that a friend mentioned entry tools above, I tried using turbo to create an office capture platform win8.1 x64. The test results are as follows: office2010 cannot solve the activation problem, turbo settings have set the automatic startup of OSPPSVC.EXE verification program, after starting the program, I saw this in the process. I also tried adding token.dat in various directories that might be verification (I used this method with thinapp to solve the problem of different appdata directories in win7 and above and xp). office2010 failed, office2007 can run on win7+, xp failed, win11 obviously has difficulty starting, waiting a long time to enter the working interface. Then another problem with the program created by turbo is that after the program runs, almost all related files are copied to the sandbox folder, causing the program body and the sandbox to occupy double space. I searched all options, but there seems to be no relevant ones. If anyone understands, please correct me. The thinapp created, except for dealing with high version systems that cannot use compression parameters, starts smoothly, and the sandbox folder only saves the changed settings and registry, occupying much less space. In my original post of thinapp office2010, someone said that turbo's compatibility is much better, but the test results are the opposite, complicated operation, poor compatibility. Using Total Uninstall to track the system changes after use, I found a more unbearable problem, that is, even if all folders' virtualization in the settings are selected as full, and the sandbox location is written as @appdir@, a considerable number of folders are still created in the same location on the physical machine. Thinapp does not do this, thinapp does not have ##Attributes folders that can be fully accessed, but it also does not create garbage in the physical machine system, and changes to folders with ##Attributes are all in the sandbox folder.
楼主| 发表于 2022-5-14 19:02:51 | 只看该作者
kli posted on 2022-5-14 14:10 I saw a friend mention an entry tool upstairs, so I tried using turbo to create office again
Capture platform win8.1 x64
Sure, using Turbo Studio to create shortcuts for Office 2010 and Access 2010, Excel 2010, PowerPnt 2010, and Word 2010 can all run normally. You can try the Office 2010 four-in-one slim installation version. I only created it in the Sandbox of Windows 11 and ran it in the physical Windows 11. I didn't change the icons of the shortcuts, so I won't share them. As for how to use KMS, I haven't researched it. You can check the doc tutorial. To be honest, WPS is easier to use than Microsoft Office.
发表于 2022-5-14 19:16:50 | 只看该作者
The problem with the streamlined version of Office 2010 Turbo that I am using is that I cannot resolve the activation issue; it prompts a license problem and exits after running. Of course, in a system with the same version installed, the packaged generated files run without issues, but as soon as the physical version is uninstalled, opening the file immediately prompts for activation. Reinstalling allows it to run again, so Turbo requires the physical machine to run the validation service. I checked the option in the Turbo configuration to automatically open the server process, and after running, I can see OSPPSVC.EXE in the physical machine's processes, but it still prompts for activation. Have you run it on Win11, and can you confirm that you ran it after uninstalling the physical machine's Office? --------------------------------------------------- Actually, I don't usually use Office myself, as I don't have work that requires it. For the occasional need to open Word and Excel, I use the SoftMaker Office portable version. The ThinApp Office I created is also rarely used after testing.