What should be in Powershell 101 and Group Policy 101 Sessions at MangoCon 2016?
-
I have 1 -1.5 hours at MangoCon to cover powershell 101 and group policy 101. What do you think should be covered in those?
I was thinking for Group Policy to cover backup, restore, copy, link, apply, inherit, permissions, and then show a couple common uses.
For powershell I was going to give a little background for all the dos scripters out there and then move in the verb-noun construct of commands, how to get help with commands, and then build some commands to work with AD objects.
-
Group Policy Targeting would be an interesting topic. Group Policy itself is fairly easy to understand I think people struggle with targeting using WMI, explaining user vs computer policy and how to target using both, How to target userA, but not userB when they use the same computer and are in the same AD groups, etc.
-
There used to be a separate area for first time applied IE settings, then ignore - damn I can't recall the name now...Not sure it's still there or not.
How about including building a central store for GP policies?
-
@Dashrender said in What should be in Powershell 101 and Group Policy 101 Sessions at MangoCon 2016?:
How about including building a central store for GP policies?
Easy to do. All you need is 5 minutes and google search. We want the juicy stuff.
-
@IRJ in the 30 minutes I'm getting to present Group Policy to people that may not have touched it, I don't think there is going to be lots of juice. However, since this is Mango, I'm sure a quick poll can identify those of us that used group policy to do some cool stuff.
In the WPA2-Enterprise deployment session, I'll hit on how you push the cert and SSID to your domain joined devices to have the connect automatically to your WPA2-Enterprise SSID.
-
@Mike-Davis said in What should be in Powershell 101 and Group Policy 101 Sessions at MangoCon 2016?:
In the WPA2-Enterprise deployment session, I'll hit on how you push the cert and SSID to your domain joined devices to have the connect automatically to your WPA2-Enterprise SSID.
I like this idea.
