![]() ![]() Low user satisfaction when having to pick the matching package out of a bunch of options.High user impact, if you haven’t kept the source files current and installing a component will perform a downgrade, just to perform an update to the current version soon after.High maintenance costs to keep embedded source files current.High bandwidth consumption, as a client might get the full 2.5 GB package pushed down before install.High number of packages, the four listed components would result in 16 or more packages.At the end, we would not have one package per component, but rather four, covering each possible permutation of SAC/SAC-T and x86/圆4. You might have a mix of update channels (often SAC and SAC-T) and maybe you are currently transitioning from 32 bit to 64 bit, and for quite some time you will have to support both architectures. Especially in larger organizations, you often do not run a single installation of Office 365 ProPlus. ![]() Usually, for each of the above components, an admin would combine the necessary source files (~2.5 gigabyte), a copy of the Office Deployment Tool (ODT) together with a configuration file, into a package. ![]() In traditional managed environments that would require a dedicated installation package in order to allow an automated and controlled way to install: After the initial migration to ProPlus, you might have to provide ways for your users to acquire automated installs of additional features or other components. Today I am going to talk about Office 365 Pro Plus lean installations often referred to as second install. Challenges in traditionally managed environments ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |