- #Proplusww.msi office 2010 in windows 10 how to
- #Proplusww.msi office 2010 in windows 10 install
- #Proplusww.msi office 2010 in windows 10 update
- #Proplusww.msi office 2010 in windows 10 windows 10
- #Proplusww.msi office 2010 in windows 10 series
#Proplusww.msi office 2010 in windows 10 install
Check for and install updates from WSUS once again. Install Adobe Reader DC, Office 2016, VLC Media Player and Google Chrome. Check for and install updates from the WSUS server. These steps will create a Task Sequence that will: If you need to customise the Adobe Reader DC installation to a greater degree then you may want to download the Adobe Customisation Wizard, which will enable you to create a transform file which you can call using the command line: [adobe reader installer name\.exe /msi TRANSFORMS="%DEPLOYROOT%\Applications\Adobe Reader DC\TRANSFORM-FILE.mst" /qn Create the Task Sequence Now we’ll add Google Chrome, the command line will be: msiexec /I googlechromestandaloneenterprise64.msi /qn The command line will be: vlc-2.2.4-win32.exe /S Following the same steps for Adobe Reader DC we’ll add VLC media player. The quiet install command that you’ll need can be found in the command line help for the installer or online. Repeat these steps for other products that you require. Enter the Destination directory: Adobe Reader DC. MDT will copy all files and folders from the specified directory. Enter the Source directory of the Adobe Reader installer file. Give the application the name: Adobe Reader DC. Here we’ll import Adobe Reader DC, VLC media player and Google Chrome. Importing Applications - Adobe Reader DCĪs this is a “real world” demo on creating a reference image, I want to walk through adding common non-Microsoft products. If you wish to customise the installation to a greater degree, the Office Customization Tool can be launched from the Office Products tab and you can also add extra Office applications and language packs via the Add button on the same tab. 
Microsoft Office is now set up to be installed in an automated fashion by a Task Sequence.
Go to the Details tab and the Quiet install command should now read: setup.exe /config proplus.ww\config.xml. Check the Always suppress reboot option. Check the Display level option and select None in the drop down menu. Check the Customer name option and enter the desired information. To activate Office via KMS leave the Product Key option unchecked. Choose the desired Office Product to Install from the drop down menu. Right click on Microsoft Office 2016, go to the Office Products Tab. On the summary page, click Next and after the files are copied click Finish to complete the wizard.Ĭonfigure the Application - Microsoft Office 2016. For the Command line enter anything - we’ll revisit this soon. Enter the Destination directory: Microsoft Office 2016. Enter the Source directory of the installation files. Give the application the name: Microsoft Office 2016. In the New Application Wizard, choose Application with source files. Right click on Applications and select New Application. Go to Deployment Workbench > Deployment Share > Applications. Microsoft Office integrates into MDT very well, let’s take a look: Importing Applications - Microsoft Office 2016 If you’ve followed my previous post, your Microsoft Deployment Toolkit installation should have Windimported as an Operating System, KB3193494 imported as a Package, and a Selection Profile for Wind圆4 packages created. Adobe Reader DC offline/full installation files. For this demo I’ll be using Office 2016, but the method is the same for both 20. Office 2010, 2013 or 2016 installation files. A Hyper-V virtual machine or equivalent - VM01. A WSUS server (my previous post: Installing WSUS from scratch!) running on Windows Server 2016 Standard - WSUS01. 
An installation of Microsoft Deployment Toolkit 8443 configured as per my previous post, running on Windows Server 2016 Standard - WDS01. Active Directory Domain Controller running on Windows Server 2016 Standard - DC01. #Proplusww.msi office 2010 in windows 10 series
In this series of posts, here’s what I’ll be using on my demo network:
#Proplusww.msi office 2010 in windows 10 how to
I’ll also touch on how to silently install common Microsoft and non-Microsoft products and customising installs. In this post I’ll be building a task sequence to create a reference image that would be suitable for a real world deployment on new devices or performing a ‘wipe and load’ on existing devices.
#Proplusww.msi office 2010 in windows 10 update
Update : Please note that this post is also relevant to Wind(Creators Update) with a few minor changes, which I’ve posted about here.
#Proplusww.msi office 2010 in windows 10 windows 10
Following on from my previous post (Getting Started With Microsoft Deployment Toolkit 8443 and Windows 10 1607), I’ll be continuing my series of deploying Windows 10 with Microsoft Deployment Toolkit.
0 kommentar(er)
