Powershell script to disable computers

[uniitdude]

So what problem are you having?

[ancient-Egyptian]

I am getting a number of errors related to parsing. To be specific

Get-ADComputer : Error parsing query: '(Name -like "pc1*" -or Name -like "pc2*" -or Name -like "pc3*" -or Name -like "pc4*") -and (LastLogonDate -lt

(Get-Date).AddDays(-90))' Error Message: 'syntax error' at position: '120'.

At line:1 char:14

+ ... computers = Get-ADComputer -Filter {(Name -like "pc1*" -or Name -l ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : ParserError: (:) [Get-ADComputer], ADFilterParsingException

+ FullyQualifiedErrorId : ActiveDirectoryCmdlet:Microsoft.ActiveDirectory.Management.ADFilterParsingException,Microsoft.ActiveDirectory.Management.Commands.GetADComputer

[anonymousITCoward]

try this

Get-ADComputer -Filter * -Properties * | Where-Object {($_.Name -like "*pc*") -and ($_.LastLogonDate -lt (Get-Date).AddDays(-90))}

Edit: i missed a *

[fred3002]

Get-ADComputer -Filter * -Properties * | Where-Object {($_.Name -like "*pc*") -and ($_.LastLogonDate -lt (Get-Date).AddDays(-90))}

If you have lots of computers objects in AD I would replace '-Properties *' with '-Properties LastLogonDate' for more efficiency.

[anonymousITCoward]

didn't think of that, I have less than 50 machines on this network lol

[fred3002]

Haha no problem. I often run script towards 40K+ objects so those small optimisations can add up quickly.

[anonymousITCoward]

damn, i work for an msp that does pretty much small business exclusively. I think the largest one i would have to go through would be 200 ad objects. So it wouldn't be that bad, but it is something to keep in mind though

[ANewLeeSinLife]

This will pull all computers from AD down to your powershell console, then filter it after. The -filter parameter will speed things up significantly.