Another useful option is Patch My PC's ability to decipher and install 64-bit apps by default on 64-bit systems, and you have the optional ability to choose to install 32-bit apps on 64-bit systems. The installation of outdated software is performed as silently and smoothly as possible, meaning no install-wizards shuffle through. The top of the screen lists a simple overview of apps to install, up-to-date, and even Windows Updates. Patch My PC has a simple, easy-to-use interface with apps broken into 17 different categories on the left, an app update summary on the right, along with the available options, startup, an uninstaller, and even a scheduler. This visual representation keeps everything organized and manageable. Green means the latest version is installed red means it's outdated, and black means it's not currently installed. Once you run Patch My PC, it will only show you a supported software list and then let you know the status. I plan to hopefully at least test this idea soon.Patch My PC is a portable app designed to check your system against the current version of over 300 apps and allow for streamlined updating. This would create drawbacks where some customers have indicated they wanted multiple configurations of the Office app in their environment/tenant one with base M365 apps, another with base apps + Project, another with base apps + Visio, another with base apps + Project + Visio.Īt this time, this is not natively possible via the Publisher's UI until this idea is implemented: - however if you executed a script client side (bundled as pre script via the right click option Add pre/post custom scripts) to determine the conditions as to whether the client should install with an alternate configuration XML, you can rename the XML on the fly to the file name specified Modify command lineĪs for detection, it could be non-version dependent - just detect whether or not M365 apps are on system, regardless of specific versions. The more I think about this, the more I foresee needing to let customers define their own XML for the ODT (to configure their own preferences for things like channel, language, products to be installed, etc) and we'll simply include the ODT as the binary in the catalogue.Ĭustomers would add their XML via the Add additional file(s) (in Add custom pre/post scripts), and then change Modify command line to specify the name of the XML file. Maybe also add a sample base pmpc xml? i'm available for testing purposes ^^
0 kommentar(er)
