Use PowerShell to get Service Auto-Start Status Along with Human Readable Service Name

Jon — Wed, 19 Jun 2013 02:30:55 +0000

This falls into the “Come on Microsoft” category.

I have been writing a script that will gather a bunch of information from servers, and returns an object with the information. Part of what I’m gathering is the servers that are set to auto start, and have their corresponding service stopped.

While you can get a list of services that meet part of this criteria like this:

Get-Service -ComputerName "computername" |
Where-Object { $_.status -eq "Stopped" } |
select-object DisplayName

The obvious problem here is that this will not return services that are set to. You can run the following command to find the service name (not the human friendly name above) as well as the startup type using the command below

Get-WmiObject win32_service |
where {$_.state -eq "stopped" -and $_.startmode -eq "auto"}

Now, if only Microsoft allowed us get all 3 (Service Descriptive Name, Service Status, Autostart Status) in one command, that would be great! Until they get around to it, you can use this command:

Get-WmiObject win32_service |
where {$_.state -eq "stopped" -and $_.startmode -eq "auto"} |
Get-Service |
select displayname

The post Use PowerShell to get Service Auto-Start Status Along with Human Readable Service Name appeared first on VirtJunkie.

Use PowerShell to Update Specific AD User’s Description Field with Last Login Time

Jon — Fri, 19 Apr 2013 16:00:31 +0000

I encountered a challenge today that was fun to fix. There’s an Organizational Unit in my AD setup that has historically been used to store disabled AD objects instead of deleting them.

When an employee leaves the organization, our standard procedure is as followed:

Disable User Object
Move to separate OU (IE AD://internal.msd/disabled/users)
Update Description field with something like: Disabled by [username] on [date]
Retain user object for x amount of days, then tombstone it.

Best laid plans of mice and men… yada yada…

I was able to go through all of these user objects that didn’t get their description updated with the one liner below. I’ll explain this beginning with script line 3 below:

(Line 3) Find all users in the OU: ‘OU=Users,OU=Disabled,DC=internal,DC=msd’ – customize this to your environment
(Line 4) Exclude objects where the description does not contain the word “disabled”.
(Lines 5-7) Loop through each object that remains and update the description with the same object’s last login date.

FYI – this script requires the Quest ActiveRoles Powershell Toolkit (http://www.quest.com/powershell/activeroles-server.aspx)

#This script requires Quest AD Tools
add-pssnapin Quest.ActiveRoles.ADManagement

#Everything below this is on one line
get-QADUser -searchroot 'OU=Users,OU=Disabled,DC=internal,DC=msd'
| Where-Object { $_.Description -notlike "*disabled*" }
| ForEach-Object { set-qaduser -identity
(get-qaduser $_.samaccountname) -description
("Last Login: " + (get-qaduser $_.samaccountname).lastlogon})

I’m sure there’s a more elegant way to handle this, but in 30 minutes I created this one liner, and updated a lot of user objects.

Cheers!

The post Use PowerShell to Update Specific AD User’s Description Field with Last Login Time appeared first on VirtJunkie.

Windows Stuff Archives - VirtJunkie

Use PowerShell to get Service Auto-Start Status Along with Human Readable Service Name

Use PowerShell to Update Specific AD User’s Description Field with Last Login Time