I woul like to ask you what is the best way to deploy Office 365. I have created the XML file from Microsoft configuration tool, but as far as I understand it can be used for local installation by script. But we want to use ITSM as a deployment also for an office. So it means we have to create a script somwhere?
Thank you for your hints.
Deploying Microsoft Office 365 updates with Patch Management Solution
Just create it as a regular Software Release, install command line:
setup.exe /configure configuration.xml
Detection rule HKLM\Software\Microsoft\Office\ClickToRun\Configuration VersionToReport >= 16.0.....
I know this post was more about initial install, but I just wanted to share my experience with keeping it current. I am a happy Symantec Patch Management customer & use it for many titles, but I find letting Microsoft patch office 2019 (which is same as 365 essentially) is very smooth and I'd encourage people to try both to see what works best for their environment. Office titles only patch when closed, and I think the built in microsoft schedule is better at handling that (patching attempt at login).
Hi there Sally, as far as I know when patching Office 365, the installation would require a reboot in order to complete when the user is active (working), no applications will be closed or anything. Once the device reboots, the installation would complete due to files in use and such.
Hello, as far as I know the SYMC Altiris does not support O365 patches, as it is described here in this KB https://support.symantec.com/in/en/article.info3521.html
do you have already any experiences with it? We have setup the XML with the local server folder for updatePaths, but we do not know exactly how else to proceed...
any idea would be helpful.
is it possible to discuss it with you in more details? We have quite hard times with O365 patchmanagement with Altiris :(
I went with just enabling cloud to patch office and haven't been disappointed. I use altiris to check on the patch level, and so far no regrets.
I am trying to set it up take patches from local source...
You can with PM, but couple of things:
- You need to approve them according the channel installed
- You need to make sure you have the languages as installed on clients
- Proofing Tools are currently not supported as far as I know, only full LAP's (or language ID installed)
Otherwise installation will fail. It will require a reboot to complete, as it doesn't close applications or anything, so file renaming etc. is done after a reboot.
As for installing Office 365, you can either have an XML pulling the sources from the internet or download the sources first using the ODT, then create a package to install accordingly as a software release.
Well, I must ask again for SW package creation details for Office 365.
When installing it manually, I have copied files to C:\INSTALL\O365 and updated CONFIGURATION.XML accordingly:
Installation then completed smoothly.
When creating SW Package in SMP Console, what shall I specify in SourcePath option?
Local CACHE will be under Software Delivery folder, but GUID of package is not known ahead of time.
C:\Program Files\Altiris\Altiris Agent\Agents\SoftwareManagement\Software Delivery\<GUID>
What is recommended process to create SW Product in SW Catalog, that would be deliverable accross all underlying SMP servers and clients?
Thanks for advices.