Along with Office , Microsoft has released office deployment tool. The Office Deployment Tool allows the administrator to customize and manage Office Click-to-Run deployments. This tool will help administrators to manage installations sources, product or language combinations, and deployment configuration options for Office Click-to-Run. If you are confused between between Office and Office here is some info about it. There is a Mac version and a Windows version of Office Office is the name Microsoft gives to a subscription service.
Within this service various options are available depending on what you need and want to pay for. Microsoft Office for Mac and Windows are both available within an Office subscription. Talking about the deployment of office , I have got the Microsoft Office Professional Plus 32bit volume license copy with me, we shall see how to deploy it.
On the Configuration Manager server run the command prompt as administrator, change the path where office setup files are located. Run the command setup. You will now see Microsoft Office Customization Tool , Choose Create a new setup customization file for following product, verify that correct product is selected.
Click on OK. Click on Licensing and user interface , choose the option Use KMS client key if you have KMS server in your organization for activating office , else choose Enter another product key and enter the office key.
Click on I accept the terms in the license agreement. Select the Display level as Basic , check the box for Suppress modal and No cancel.
Now click on Modify Setup properties. Click OK. Double click the setting Disable Opt-in Wizard on first run and set the status as Enabled. Close the OCT tool. Choose Automatically detect information and provide the path to file proplusww. Click Next. You can specify a little information about this application.
We will change the Installation program command later. Choose the Install behavior as Install for system. Right click the Office application, click on Properties. Click on Deployment Types tab, click on the msi file and click Edit. Click on Content tab, set the Content location to Office folder or a folder where Office installation files are present, remove proplus.
Click on Apply. Click on Programs tab, change the Installation Program command to setup. Click on Apply and OK. The next step is to make the application available to DP. Right click the Office application, click on Distribute Content , choose you DP and wait until the application is available with DP. You can verify this by checking the Content Status of the Office application under Distribution Status. Deploy the Office application to the desired collection. Right click on the Office application and click on Deploy.
After few minutes, on the client computer we see that the application is available. Select the software and click on Install Selected. Open Appenforce. You could also monitor the installation process. The application is first downloaded to the client computer and then installed. We now see that the application is installed successfully.
If I edit the CustomOffice. Hello Prajwal, Great job. Thanks a lot for this post. It was very helpful. I need to carry this out in my environment. Your help would be much appreciated. Can you tell? I fixed this issue. I understand that SSCM does not use directly this file, but rather thru a file inside the deployment directories. Said folder is found in the root directory of the installation files. Application deployment error 0x87D I have one quick question how did you all get the proplusww.
It just hangs. Deployment becomes unresponsive and eventually my screen just goes black. Tried on virtual machine and laptop. Logs are not very helpful as they just stop. If I restart the computer, the logs pick back up, but still no helpful information. I never get my process to terminate with an exit code. But it passes that error and continues on for a bit before stalling. Any suggestions from anyone? Hi Prajwal, Great Post. This caused confusion with me. I thought others might be too.
Once again keep up the good work. Having issues with this distribution. Checking to see if anyone else has tried this way. I also have a number of patches in the updates folder that I want to get applied right after the install.
Great post. Be useful if you could update it with the uninstall method for Office Your posts are very informative. What do you recommend in the settings of the customization tool if I want to have it display the progress window of uninstalling Office and then the progress window of installing This caused some botched installations that our service desk had to fix. Basically I want something to display on the screen so that the user does not touch any Office applications until the whole process is completed.
Thank you for your help. Actually it works very well, but: After installing i couldnt get Word to open. I wonder that you not set this step.
It worked well. However it is prompting to accept the license agreement and then prompts to click on upgrade.. Request you inputs.. In our environment Skype for business basic installed and we want to deploy ProPlus but not success due to we are unable to uninstall SFB I followed the steps, but the application is not installing quietly. Okay, maybe I am missing something. I noticed that you used the customization tool to create the MSP file, but I do not see any reference of that file in the Application setup for Office I would expect that you would have to the use the adminfile switch for the Installation Program portion where you have setup.
I like the way you use the msi to get the info, and only after that do you change the installation. I need to uninstall previous office versions either prof plus or prof plus during this deployment. Is it possible to deploy with silent uninstall of at same time? So what about the uninstall command? Would be nice to know how others do that and if it works well.
All of our users do not have local admin access to their computers. Is there a way to set these applications to install without admin credentials once approval has been granted?
So the users will be just clicking Install in software center. Let me know if you have further questions. I followed your steps but the deployment did not work. I see the following errors in the AppEnforce and AppDiscovery logs:. Mine was failing that it could not detect the app. I followed your steps and but the deployment did not work.
We had this issue too.. I tried Running the command setup. Like in i dont have admin folder also. Am i missing something. Is my software not volume license copy? I have enough free space on my dis. Hi prajwal hope you doing well i am new in sccm i got error when i delpoy O through sccm Please help thanks in advance. It's failed previously, expect it to fail again. However, this time, you're ready to capture log files that will be detailed enough to help you diagnose the failure point.
After your install attempt, you'll find that you have somewhere between 1 and 20 logs from the installation in your temp directory. When you look through the MSI logs, we will typically want to look for a value 3 entry in the logs. Windows installer returns codes during the installation that indicate if a particular function is successful or not. Therefore, there are many logs to verify. We recommend that you start with the setup.
This log usually has a value 3 entry in it when there is a failure. However, this log isn't clear enough to diagnose the issue. If it doesn't have a value 3 entry, look for the first instance of Rolling back package. Rolling back package indicates that the Office installation has failed and Office is trying to "roll back" the installation. You should be able to identify the failure immediately at that point. As soon as you find value 3 or Rolling back package in the setup.
There's frequently more than one value 3 or rolling back package entry. You should focus on the first entry that you find. Here are some examples of Office installation failures and how we can identify the failure point.
In this example, you don't find a value 3 entry in the setup. The error doesn't tell you why the installation failed. But it does tell you that the failure occurred during the installation of the ProPlusWW. For example, from the bottom of the MSIb0bc7. LOG, you see the information that resembles the following:.
So this is the verbose MSI log for the Office Outlook MUI component, and the component is from the rollback the installation failure occurred earlier than this rollback. When you find the ProPlus log it's the biggest one , you see the following information that indicates it's the ProPlus log:. When you search the log for a value 3 entry, you may not find one, but you may see the following error at the bottom of the log:.
Installer terminated prematurely. Out of memory. Shut down other applications before retrying. This is a known issue about Windows Installer. To fix this issue, install the hotfix. After you install the hotfix and restart, the installation is successful. You may find the following error:. The error doesn't tell you why the installation failed, but it does tell you that the failure occurred during the installation of the AccessRWW.
Looking through the log files, you may find a log for AccessRWW. HResult: 0x Return value 3. To fix this issue, make sure that the network service is running, and then make sure that the following registry keys are present. In this next example, you find a value 3 entry in the setup. Verify that you have access to that directory. Not showing message because suppress modal has been set.
Title: 'Setup', Message: 'Error When you see a value 3 entry in the setup. In this case, the verbose MSI log just repeated what we found in the setup. In this case, you should consider updating. Follow the steps in this section carefully. Serious problems might occur if you change the registry incorrectly.
Before you change it, back up the registry for restoration in case problems occur. Error An error occurred during the installation of assembly component.
0コメント