Win 8 & 10 Environment

[Homer]

Morning all

 

Question - is anybody running W10 on a set of computers, and W8 on another set (or the rest of the school?)

 

I've got a room I'd like to image with W10... I can set some WMI filters on GPO's so only the relevant GPO's apply where a user logs in but seems messy to me.

 

Just wondering if anybody else is doing this, and if so, how?

 

Cheers ^_^

[Blue_Cookeh]

We do exactly that, WMI filters on our GPOs for computer OUs. This is for our mixed environment of 7, 8.1, and 10.

 

Then, once I get rid of the last PC with a certain OS I'll disable both User and Computer settings on the GPO, rename it to D- and unlink it from the OU.

 

User OUs we just have 1 GPO per user group (staff/pupil mostly, with some others for office staff etc), rather than looking at the OS.

Edited August 25, 2016 by Blue_Cookeh

[Homer]

Nice one mate does the WMI filtering show any serious slowdowns in logon times or is it OK?

[FN-GM]

Nice one mate does the WMI filtering show any serious slowdowns in logon times or is it OK?

 

We use WMI for a mixed Windows 7 & Windows 10 setup. No slowdown that is noticeable.

[Sagima]

We use WMI filters to filter between the OS versions. It makes no difference to the login times that we can tell

[Homer]

EXCELLENT! Full steam ahead

 

Cheers all

[Norphy]

The only other way I can think to do it is to use security filtering, i.e. create a group containing Windows 8 computers and one containing Windows 10 and then denying access to the appropriate group in the GP. This is far messier imo and you'd have the annoyance of having to keep groups up to date. WMI filters are definitely the way to go.

[FreelanceX]

Don't forget about Item Level Targeting. If its GPPs you are using, you can keep one policy and just target them out.

 

Will need to use a PC running Win 10 with RSAT though to be able target Win 10 (unless your running Server 2016 in a production environment like a B0$$)

[FN-GM]

Will need to use a PC running Win 10 with RSAT though to be able target Win 10 (unless your running Server 2016 in a production environment like a B0$$)

 

Or you import the ADMX files to the central store.

[FreelanceX]

You know that doesn't work for gpp item level targeting right? You can only see as high as your DC, or whatever pc your on. Whichever is greater.

[MatthewL]

You would need to update your AD schema if you are on an older server version (well you used to have to get full functionality of the extra features!).

[FreelanceX]

Even if your functional level is at 2012 R2, the highest it can go currently on released OS's, you still wont see win 10 as an option for ILT unless you RSAT from Win 10. Major reason I always run a Win 10 VM on all my Hyper-V boxes.

 

Edit: Unless you meant something else...

Edited August 26, 2016 by FreelanceX

[Homer]

WMI is working a treat, added the latest ADMX files to the central store and have made it all work! Got a room for testing now