I like this approach because you can be as selective as you like by writing the Current User Keys directly. It is nice to see that there is a specific Show Only and well as a Hide Only option when controlling this.Ī list of applets (can we call them that?) is outlined below displayīecause I like to do everything with WEM where I can, this article will cover the configuration at a WEM level, however GPP and Item Level Targeting can achieve the same thing for other environments. Alternatively you can write the HKCU keys with whichever VUEM tickles your fancy, or via good old GPP with Item level targeting. On computers that do not have Control Panel or File Explorer, this cmdlet gets only control panel items. This cmdlet gets only the control panel items that can be opened on the system. You can use it to find control panel items by name, category, or description, even on systems that do not have a user interface. Microsoft provide an ADMX option to lock this down which Carl has already documented here. The Get-ControlPanelItem cmdlet gets control panel items on the local computer.

The official release details can be found here The Management Options Finally as of the September Cumulative Update for Server 2016, we can selectively lock this down in a similar fashion that we can with the traditional Control Panel.Ĭredit goes out to sklopp at Citrix discussions who brought this to light.

It has been a considerable amount of time that the inability to nicely manage the Immersive Control Panel or “Settings” App provided in place of the traditional Control Panel in Server 2016 has frustrated Citrix and RDS admins.

Windows immersive control panel