![]() ![]() Messages depending on what user logs into the machine (for a hot desking environment for example) this gives a better solution than an MSI deployment where the component is completely removed from the machine which of course would increase network trafficĪnd time to reconfigure the product to add it back based on the user who logs in. This method doesn't actually remove the components it could block access to it, and if you're really clever you could turn this into a "user" focused scenario rather than a device based one, adding the shortcuts back and uninstalling the app help I know this appears a pretty botch job but its the best I can think of, app locker policies could be used but personally I have never been a fan of implementing such restrictions. Will disallow the application to run passing it off as a "compatibility" issue, and that's assuming the user can get to the exe file after the shortcut has gone.Ĭreate a GPP Folder Options – File Type which re-associates the extensions for the blocked app with another application or removes the extension.Īny or all of those steps could form a solution as far as I can tell. The GPP will remove the shortcuts and the start up scripts will install an ACT Database with AppHelp messages. Just in case anyone might find this useful, during my testing phase I implemented the following which seemed to work for me to disallow access to certain O365 components.Ĭreate a GPO which uses User GPP and Computer start up scripts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |