Whenever a new version of the current branch is downloaded to the Updates folder, it will “update Office to the newest version. The SourcePath is our Deferred that goes as the core install for all our machines, and the Updates path (towards the bottom) is another folder that we run our download process again on a monthly basis for the Current branch. In an enterprise environment, it’s typical that you will have a Deferred and a Current branch (to borrow from Microsoft terminology). You can read more about the syntax, formatting, etc at: The next part to performing the deployment as part of an administrative install is to create the configure XML file. In this case, this folder sits on a file share (which we’ll get to in a moment) that will serve as our “SourcePath” As you can see here, the build is primarily 32-bit but provides 64-bit support as part of the installation. This will sit here for a bit while it downloads the current build to the subfolder under \Office\Data with the build number. Open a command prompt and browse to the extract folder, and run setup.exe /download Run the EXE and extract to a folder – It will only produce setup.exe (Note: you can reuse this tool to download Current branch versions each month, however Microsoft does update this to support new deployment features and resolve deployment bugs so check back often for new versions!) So how do you create an offline installation of Office 365 Pro Plus for distribution on machines when you don’t want them all chewing up the internet connection at once?įirst, download the Office 2016 Deployment Tool from:
0 kommentar(er)
