Some times out of the blue. Mostly in haste to see if an account has been changed or locked.
I usually use a couple of things.
$User = Read-Host 'User'
Get-ADUser -Identity $User -Properties * |ft Name,PasswordLastSet,PasswordNeverExpires,PasswordExpired,PasswordNotRequired
Easy 2 lines of code in Powershell.
title User password state check tool - Max
Set /p name=Hello! Please input a username:
echo This is what i managed to find...
net user %name% /domain | FIND /I "Full Name"
net user %name% /domain | FIND /I "Password last set"
net user %name% /domain | FIND /I "Password expires"
net user %name% /domain | FIND /I "Account expires"
echo - Press ENTER to try another username -
15 Lines in VB script.
So I have been humbled yet again.
I always have RDP or Remote Desktop using various applications. I have always been asked to put credentials in. <-duh!
So there is all these interesting and I am sure noted somewhere on a technet or msdn page how to use parameters to log in.
Domain login is simple. AD pushes your permissions to the domain servers and gives you rights to mess a good server up.
Pushing Local to your machine. Usually means your gonna do a “\”and account that adds your localhost not the machine that your going to remote name.
Then there is tell remote desktop to use the Name or IP of the other machine provided it can be found in a dns structure. or “.\”
However what happens when those dont work? And you need to login but RDP client is misbehaving? try: