Skip to main content

Set up your Environment to utilize Invoke-GPUpdate

By
I’m sitting in O’Hare enjoying my 3 hour layover as I get ready to teach a Windows 10 class in Fort Wayne.  I’m actually prepping for my class in Fort Wayne in a few weeks, 10982 Supporting and Troubleshooting Windows 10.  This class is very much like the Windows 7 version that I used to teach so I decided to up the detail quite a bit.  In the GPO troubleshootin chapter, I’m including a demonstration on how to use PowerShell’s Invoke-GPUpdate.  I needed to make sure the environment is set up for me to be able to utilize this cmdlet.  If you read the Notes section on Invoke-GPUpdate’s help file, you will see there are three firwall rules that need to be in place:

  •         Remote Scheduled Tasks Management (RPC)
  •         Remote Scheduled Tasks Management (RPC-ERMAP)
  •         Windows Management Instrumentation (WMI-IN)


I decided to create a little PowerShell script to create this GPO and link it up to the domain.
Here are the steps to create this GPO and link it to your domain.  My test domain is PowerIT.Com so you will need to adjust the code for your domain.

New-GPO -Name "AllowPowerShellGPUpdate" `
        -Comment "Sets the firewall rules to allow Invoke-GPUpdate to work" `
        -Verbose

# Create A GPO Session to reduce the load on the DC.
$GPO = Open-NetGPO -PolicyStore PowerIT.com\AllowPowerShellGPUpdate


# Set the new firewall rules.
New-NetFirewallRule -DisplayName “Remote Scheduled Tasks Management (RPC)” `
                    -Direction Inbound `
                    –Protocol TCP `
                    -Action Allow `
                    -GPOSession $GPO `
                    -Profile Domain

New-NetFirewallRule -DisplayName “Remote Scheduled Tasks Management (RPC-ERMAP)” `
                    -Direction Inbound `
                    –Protocol TCP `
                    -Action Allow `
                    -GPOSession $GPO `
                    -Profile Domain

New-NetFirewallRule -DisplayName “Windows Management Instrumentation (WMI-IN)” `
                    -Direction Inbound `
                    –Protocol TCP `
                    -Action Allow `
                    -GPOSession $GPO `
                    -Profile Domain

# Commit the GPO settings
Save-NetGPO -GPOSession $GPO


Labels:

Comments

Post a Comment

Popular posts from this blog

Sticky Key problem between Windows Server 2012 and LogMeIn

By
This week I instructed my first class using Windows Server 2012 accessed via LogMeIn and discovered a Sticky Key problem every time you press the Shift key. Here is my solution to resolve this.  First off, in the Preferences of LogMeIn for the connection to the Windows Server, click General . Change the Keyboard and mouse priority to Host side user and click Apply at the bottom. On the Windows 2012 server, open the Control Panel – Ease of Access – Change how your keyboard works . Uncheck Turn on Sticky Keys . Click Set up Sticky Keys . Uncheck Turn on Sticky Keys when SHIFT is pressed five times . Click OK twice. If you are using Windows Server 2012 as a Hyper-V host, you will need to redo the Easy of Use settings on each guest operating system in order to avoid the Sticky Key Problem. Updated Information: March 20, 2013 If you continue to have problems, Uncheck Turn on Filter Keys .
6 comments
Read more

With the AD Recycle Bin Turned on, What Happens when you Create a User Account with a Password that does not meet the Password Policy?

By
This was an interesting observation from one of my Windows Server 2012 classes.  While working with the AD Recycle bin in a lab, one of my students discovered some interesting accounts that were created. When he created user accounts that did not meet password complexity requirements, an account is temporarily made and then deleted.  When a new password is provided that meets the password requirements, then a new account is made. We discovered this in two places.  First off in the Active Directory Administrative Center.  This is what caused the initial confusion.  Take a look.  This is in the Deleted Objects OU. You can see multiple deleted accounts for Test2 and one for Test3.  Test3 is a valid, functioning user account.  Using the PowerShell command Get-ADObject –IncludeDeletedObjects –Filter * –Properties ObjectSID we can see that indeed, two accounts were created, with one of them deleted. Notice the RID portion of the SID is different. ...
Post a Comment
Read more

Where did a User’s Account Get Locked Out?

By
Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction.  The code below is correct.   My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...
18 comments
Read more