Windows 7 GPO

[kennysarmy]

Yay

I have created a new w7 only policy for disabling w7 gadgets

[ZeroHour]

One thing I would do is redirect the w7 app data to a different folder from your xp redirection to ensure you have less issues.

[SYNACK]

Thats in the gotchas thread too Windows 7 Gotchas/Tips/FYI

and here [Solution] Vista Always Loads with Temporary Profile for Specific User Account our google rankings must be slipping.

[kennysarmy]

I would heavily recommend starting from scratch and using WMI filters for sepoate XP and 7 Policies as I have lost count of how many questions I have answered on this forum alone that have been caused by slightly corupted GPOs or settings that have not converted quite right.

My personal solutions to GPOs is to start fresh, read through all of the options and set the ones that need setting. Clean policies mean clean and quick logons without extrenuous registry fragments for XP being pumped into your fresh Windows 7 registry hives.

Just to be clear to do this I would:
1. Make every existing GPO filtered via WMI to just apply to XP computers.
2. Create blank GPO's filtered via WMI to just apply to w7 computers named as existing prefixed perhaps with "7-" eg. 7-default domain policy & 7-student lockdown policy
3. Edit the new w7 GPO's settings to do what the XP ones did AND more
4. test test test

[SYNACK]

Just to be clear to do this I would:
1. Make every existing GPO filtered via WMI to just apply to XP computers.
2. Create blank GPO's filtered via WMI to just apply to w7 computers named as existing prefixed perhaps with "7-" eg. 7-default domain policy & 7-student lockdown policy
3. Edit the new w7 GPO's settings to do what the XP ones did AND more
4. test test test

Yes, that would be my recomendation, it limits the chances of getting some random setting from old policies that cause all sorts of difficult to trace issues and some things you will want to do differently in 7 which can cause issues if overridded from an XP policy. Specificly the start menu styles in my experience.

[kennysarmy]

Great
That's what I will do.

One final quetion

How do I ensure when I am testing that something is behaving differently due to having logged on with the test user before?

I mean how can I make a change to the GPO's, test, logout then ensure when I login again that it's a new clean state?

My w7 pc is a virtual machine so is there a better way than constantly having to undo changes or take snapshots etc etc.

Cheers.

[SYNACK]

Great
That's what I will do.

One final quetion

How do I ensure when I am testing that something is behaving differently due to having logged on with the test user before?

I mean how can I make a change to the GPO's, test, logout then ensure when I login again that it's a new clean state?

My w7 pc is a virtual machine so is there a better way than constantly having to undo changes or take snapshots etc etc.

Cheers.

You could leave the profile path blank in AD for the test user so that it saves locally then restart the workstation after each test, delete the local copy with the admin account and then login as the test user again. Local profiles and snapshotting may be quicker or you could make a startup script that wiped the local profile on boot for testing.

[shoggie]

does anyone have any clean new GPO setup for restricting win 7 stations via 2008 r2 servers. Yes I know not all will be good for evey school but somewhere to start would be great. Is this not what edugeek is all about help and advice, if you have done it why not share to save others time. Believe me it would be much appreciated