Jump to content

Recommended Posts

Posted
I am currently developing our Windows 10 rollout, and I'm working on both LTSB and 1709, to try and find the one that best does what we want. LTSB was in the lead, until it came to settings. For Students it's easy, we can simply block access to Control Panel and Settings entirely, but we need to give staff access to altering the desktop resolution at the very least. In 1709 that's easy - there's a GPO, but that GPO doesn't apply on LTSB. Is there a way I can do what I need on LTSB?
Posted

Which GPO do you mean? Haven't found any that don't work on both sides.

 

But in regards to the way we do it is disable settings and then use the "only show these" in control panel and put bits we want in like bitlocker/display/blahblah

 

Steve

Posted
It's the Computer policy Control Panel\Settings Page Visibility. On LTSB I can see the policy has written into the Registry, but it doesn't apply. On 1709 it works. If you right click on the desktop and go to Display it opens the Settings version of desktop, so if we disallow settings completely in LTSB staff get an error message.
Posted

On the GPO setting did you try it like - showonly:display pretty sure that's what I was playing with before I decided to block all of settings

 

Steve

Posted
Windows 10 has forced me to move away from a fat image - I'm now using the install.wim from the disk, and doing everything I would have done in my image in my SCCM TS. This has made it easy to test both flavours - 1709 and LTSB. As long as I can get my Start Menu working as I would like, it looks like 1709 will now win - for now. I'll get a working system, then test with a small group of machines and users.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...