![]() You will need to look for "Personal templates path for PowerPoint" and "Personal templates path for Word" and enable them. The last thing you would need to do in both situations, is point your users to their template path which can be accomplished by creating an Administrative Templates configuration profile. ![]() This also helps if you choose to remove this "app" later on. ![]() Path: C:\Users\%username%\AppData\Roaming\Microsoft\Templates\Company Templates | File or folder: Letterhead.dotm | Detection method: File or folder exists). ![]() All you have to afterwards is make detection rules to verify those files are there (Ex. This way when it deploys, those folders get created with your custom templates inside. intunewin file I recommend making a Company Templates folder in the default template folder and placing your custom templates in there before you build the MSI with advanced Installer. If you decide to create a WIN32 app with a. I'm pushing out installs based on users so a security group with with your target users will work. Install context with a LOB app in this case would be by user and "No" will suffice for ignore app version. This is optional, but I recommend it because you can't use detection rules on a line of business app. Advanced Installer outputs an MSI file which I run through the IntuneWinApp Utility to create a.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |