Force a Domain-Wide Update of Group Policy with PowerShell

re: Force a Domain-Wide Update of Group Policy with PowerShell

jrv — Wed, 13 Mar 2013 21:18:34 GMT

@bimplant

$cn = get-content c:\servers.txt

will not work on any version. It is not possible to do this with a text file.

re: Force a Domain-Wide Update of Group Policy with PowerShell

bimplant — Wed, 13 Mar 2013 20:16:46 GMT

Hi. I'm getting the same error as SdeDot, but according to $host i'm on 3.0.

Any Ideas?

I'm using

$cn = get-content c:\servers.txt

$cred = ...

$session = New-PSSession -cn $cn.name -cred $cred

New-PSSession : Cannot validate argument on parameter 'ComputerName'. The argument is null or empty. Supply an argument that is not null or empty and then try the command again.

At line:1 char:30

+ $session = New-PSSession -cn $cn.name -cred $cred

re: Force a Domain-Wide Update of Group Policy with PowerShell

Ed Wilson — Sat, 17 Nov 2012 10:24:15 GMT

@SEDDot yes, using $cn.name is a PowerShell 3.0 syntax.

re: Force a Domain-Wide Update of Group Policy with PowerShell

SdeDot — Tue, 13 Nov 2012 11:01:46 GMT

I believe my issue is due to running the script on a 2.0 system and $cn.name can only be done on a 3.0 system.

re: Force a Domain-Wide Update of Group Policy with PowerShell

SdeDot — Tue, 13 Nov 2012 10:18:19 GMT

So what am I missing here?

When I run the following:

$cn = Get-ADDomainController -filt *

$cred = Get-Credential acme\Batman

$session = New-PSSession -cn $cn.name -cred $cred

I get the following error:

New-PSSession : Cannot validate argument on parameter 'ComputerName'. The argument is null or empty. Supply an argumen

t that is not null or empty and then try the command again.

At line:3 char:29

+ $session = New-PSSession -cn <<<< $cn.name -cred $cred

+ CategoryInfo : InvalidData: (:) [New-PSSession], ParameterBindingValidationException

+ FullyQualifiedErrorId : ParameterArgumentValidationError,Microsoft.PowerShell.Commands.NewPSSessionCommand

When I list $cn, it contains all my DCs. When I list $cn.name, I do not see anything.

What I did to get this to work is the following:

$cn = Get-ADDomainController -filt * | sort name | select -Expandproperty name

$session = New-PSSession -cn $CN

icm -Session $session -ScriptBlock {gpupdate /force}

icm -Session $session -ScriptBlock {Get-EventLog -LogName system -InstanceId 1502 -Newest 1}

remove-pssession $Session

re: Force a Domain-Wide Update of Group Policy with PowerShell

SdeDot — Tue, 13 Nov 2012 10:08:28 GMT

Good practical use of Powershell I can use on a regular basis. Thanks

re: Force a Domain-Wide Update of Group Policy with PowerShell

IamMred — Mon, 12 Nov 2012 20:41:29 GMT

@PowerShell100 Yes you are correct. The remote servers all have WinRM enabled. Some of the Domain Controllers are Windows Server 2012, Some are Windows Server 2008 R2, and one is Windows Server 2008. The Windows Server 2008 Domain Controller has the Active Directory GateWay service running on it.

re: Force a Domain-Wide Update of Group Policy with PowerShell

Powershell100 — Mon, 12 Nov 2012 17:11:22 GMT

I presume you must have the winrm service running on the server/workstations, and the

Domain controllers are on server 2008 r2, or gateway service installed in 2008?

re: Force a Domain-Wide Update of Group Policy with PowerShell

Ed Wilson — Mon, 12 Nov 2012 13:21:04 GMT

@Incredulous -- nope. not kidding. Been told that on several occasions. Luckily, PowerShell makes it easy to comply.

re: Force a Domain-Wide Update of Group Policy with PowerShell

Incredulous — Mon, 12 Nov 2012 08:21:39 GMT

Refresh group policy five times, five minutes apart? Are you kidding?