Slackbot
02/01/2024, 9:04 PMJames Kindon
02/01/2024, 10:08 PMMatt Sliva
02/01/2024, 10:11 PMJames Kindon
02/01/2024, 10:16 PMMatt Sliva
02/01/2024, 10:17 PMJames Kindon
02/01/2024, 10:20 PMMatt Sliva
02/01/2024, 10:25 PMJames Kindon
02/01/2024, 10:28 PMJames Kindon
02/01/2024, 10:29 PMMatt Sliva
02/01/2024, 10:30 PMJames Kindon
02/01/2024, 10:35 PMc:\progradata\Microsoft\Windows\Start Menu\Programs then use a GPO (machine level) to apply permissions to each shortcut. I've done that on a project with thousands of shortcuts and aligned it to WEM processing groups - also works a treat, and very fastMatt Sliva
02/01/2024, 10:43 PMJames Kindon
02/01/2024, 10:44 PMMatt Sliva
02/01/2024, 10:45 PMJames Kindon
02/01/2024, 10:50 PMMatt Sliva
02/01/2024, 10:50 PMMatt Sliva
02/01/2024, 11:06 PMc:\progradata\Microsoft\Windows\Start Menu\Programs in the start menu layout xml. For your second option to work, I think I would need to unconfigure the "remove common program groups" GPO to show common shortcuts and have a GPO apply NTFS permissions on individual shortcuts.James Kindon
02/02/2024, 12:11 AMRemove common program groups from Start Menu is the devil. It introduces so much non-needed user based configuration..... you are correct on the above process (or use app masking)Sharp Guo
02/02/2024, 8:50 AM