This is my script, it works when I run it locally but won't deploy when I roll it out through Intune:Ĭd HKCU:\SOFTWARE\Microsoft\Office\16. styles.xml contains the document styles so this xml file could be pulled out of a document manually updated then write a PS script to loop through a document share etc, and open the file as an archive and inject this updated xml file. but basically the new office format documents are really just zip files containing XML files. Apply the cloud policy to a security group that target users are members of. Set a cloud policy (for Microsoft 365): Create a font policy from Policy Management. I was trying to find the example for this that explained the process of doing this (came out around the same time they introduced the new file format). For more information, see Change the default settings for new documents. If you are wanting to reto-fix existing documents then that becomes a bit more complex. intunewin containing the script and the new filesĤ - upload to MEM as Win32 application and configure detection rules etcĥ - link Win32 Application to a device and test
\NormalEmail.dotm -destination $env:Appdata\Microsoft\Templates -forceģ - using the Microsoft Win32 Content Prep tool make an.
If it's just changing the default settings for word/outlook then the easiest method is to update the Normal.dotx / NormalEmail.dotm file on a device and replace the versions on the rest of the devices with the updated ones.ġ - update Normal.dotx / NormalEmail.dotm and save to a folderĢ - create a PowerShell script to copy the above files to the correct location - you will want to include something in the script to write a file or a reg key that you can use in the detection rules in MEM copy-item -path. Are you able to clarify are you wanting to just change the default settings for new documents? or are you wanting to retro-fix existing documents as well?
0 kommentar(er)
