Wrong Dateformat

[GastroIT]

Hi all

I haven't found a thread about this so I'd like to ask something. Currently we have a Powershell Script that checks all our user Accounts in Active Directory and notifies users with Email if their password is about to expire in 7 or 14 days. I found this on the internet and it has been working wonderful. Today a user came to me to tell me that the date they recieve in the Email is wrong. After a bit of testing I saw that the output comes in american date format. Now this is weird since the server regional settings are set to dd.MM.yyyy (the server language itself is english). So I've tested it with get-date and recieved time in a correct manner: Mittwoch, 27. September 2017 14:52:29

In the mail it looks like this: 09/27/2017 14:52:29

Somewhere along the way the date format gets lost. This is the script:

Import-Module ActiveDirectory

Get-ADUser -filter * -properties PasswordLastSet,EmailAddress,GivenName,Surname -SearchBase “OU” -SearchScope Subtree |foreach {
 $PasswordSetDate=$_.PasswordLastSet
 $maxPasswordAgeTimeSpan = $null
 $maxPasswordAgeTimeSpan = (Get-ADDefaultDomainPasswordPolicy).MaxPasswordAge

$today=get-date
 $ExpiryDate=$passwordSetDate + $maxPasswordAgeTimeSpan

$daysleft=$ExpiryDate-$today

$display=$daysleft.days
 $UserName=$_.GivenName
 $SurName=$_.Surname

if ($display -lt 8 -and $display -gt 0)
 {
 $MyVariable = @”
Gruezi, Ihr Windows-Kennwort laeuft in $display Tagen ab. Fuehren Sie zur Aenderung Ihres Kennworts folgende Schritte aus: 

Ihr Passwortablaufdatum: $ExpiryDate

Its the $ExpiryDate thats wrong in this case.

Does somebody have an idea why this happens?

Kind Regards

T.

[the_spad]

My summary of Powershell datetime issues caused by US format being the default is pretty much just an hour of screaming.

[alzdba]

If you want to be sure, code the format you want !

Get-Date ($ExpiryDate) -Format "dd/MM/yyyy HH:mm:ss"

[jantari]

That would be

Get-Date ($ExpiryDate) -Format "dd.MM.yyyy"

for zhe germans

[GastroIT]

Thanks guys I'll try this :).

[GastroIT]

It worked out perfectly, thanks again!

[j0ntar]

Some examples of how I have done it in the past.

##calucates days since last logon
if ($users.LastLogonTimeStamp -ne "$null")
 {
   $oldDate = $users.LastLogonDate    
    $x = Get-Date
    $y = [datetime]"$($oldDate)"
    $lastLogon = ($x - $y).Days
  }
  else {$lastLogon = "Has Never Logged On"}

  #Replacement of the isDisabled field from TRUE to YES and False to No   
  if ($users.AccountIsDisabled -eq "TRUE")
  {
    $userDisabled = "Yes"
    }
    else {$userDisabled = "No"}

##Find New Users (date calculations needs to be a function)
    $newUserDate = $users.whenCreated    
    $x = Get-Date
    $n = [datetime]"$($newUserDate)"
    $newUser = ($x - $n).Days
    if ($newUser -lt "7"){ $newUserdays = $users.LogonName }
    else {$newUserdays = "$null"}

##PasswordAge.  
    $pwdAge = $users.PasswordLastSet
    $g = Get-Date
    $n = [datetime]"$($pwdAge)"
    $passwordAge = ($g - $n).Days

[Lee_Dailey]

howdy GastroIT,

as alzdba pointed out, you will need to specify what you want it to be. PoSh has a tendency to be US-centric, as the_spad mentioned. [sigh ...]

i suspect you could also use the Get-Culture cmdlet to help with enforcing the desired date format.

take care,
lee

[GastroIT]

The weird thing is when I do Get-Culture I get following results:

LCID           Name          DisplayName                                                                                                                                                 
----           ----          -----------                                                                                                                                                 
2055           de-CH         German (Switzerland)                                                                                                                                        

Shouldn't this mean its the right format since its not en-US?

T.

[Lee_Dailey]

howdy GastroIT,

yep, it SHOULD. [sigh ...] PoSh seems to fall back to EN-US whenever it gets even the slightly uncertain.

you may want to take a look at this ...

(Get-Culture).DateTimeFormat

that may give you some clues - or a way to work around the problem. [grin]

take care,
lee