First of all – excellent work; I have implemented a deviation of this script in our current messaging environment. The major changes I made was to log to the event log instead of the console, as well rewriting the mailbox retrieval logic:

[DateTime]$LastRun = Get-Date ((Get-ItemProperty -path HKLM:\Software\Sauer-Danfoss\$strScriptName -Name LastRun).LastRun) -Format s
if ($Verbose) { write-eventlog -logname application -source $strScriptName -eventID 5 -entrytype Information -message “Last run time: $LastRun”}

Set-ItemProperty HKLM:\Software\Innervation\$strScriptName -Name “LastRun” -Value (Get-Date -Format s) | Out-Null

Get-Mailbox -ResultSize Unlimited -Filter {(IsResource -eq $false) -and (IsShared -eq $false)} | ? {($_.WhenMailboxCreated -gt $LastRun) -and ($_.ExchangeUserAccountControl -ne “AccountDisabled”)}

You will notice that I’ve changed WhenCreated to WhenMailboxCreated as mailboxes are not necessarily created at the same time as the mailbox. Also, I removed the ElapsedTime logic, as it was redundant (you can compare WhenMailboxCreated directly to a timestamp), and finally, moved adding the new timestamp to the registry to before the mailboxes are enumerated, as there would otherwise be a gap during the time it takes to enumerate all mailboxes.

I’d be happy to send you a copy of my script if you would like to take a look at the changes.

Again, thank you for your inspiration!

Larry can you send me a copy of the script that Pat send you?

Couple of points…

When entering the message body into $strmsgbody, I found it only works with linebreaks rather than carriage returns… (i.e. Shift-Return instead of Return) at the end of each line. If I entered the text with “proper” carriage returns at the end of each line, powershell does not like it!

Also, rather than entering all of the body text in the script, I wanted to give the ability to simply maintain a single text file somewhere on the network, and pull it in with get-content… This works fine to a point, but it does not preserve the formatting in the text file at all… neither linebreaks or carriage returns are honoured, and the content is rendered as a single line.. – any ideas how to improve that?

And lastly, rather than running a scheduled script, I plan to use the extension agent and put this into the scriptingagentconfig.xml file for the new-mailbox and enable-mailbox cmdlets so that the mail is generated automatically for all new mailboxes AS they are created…

just a quick question, does this work for new users that were copied from an existing one?
I mean, I implemented this and it works fine if I create a new user from EMC, but if a copy an user in AD and then create it on EMC doesn’t work, any idea?

Hi, thanks för at great script. In the changelog v1.3 i mentioned, but i cannot find it to download. The link points to v1.2 or am i missing something?

yes… no version 1.3 for download…

This does not work for exchange 2010.

Is there away to make it work for exchange 2010?

I use Send-NewUserWelcome.zip and i modifed it. No errors. I created a new mailbox and new user but still no mail. I checked the registry key and it was created.

if (-not((Get-PSSnapin) -match “Microsoft.Exchange.Management.Powershell.E2010”)){ Add-PSSnapin Microsoft.Exchange.Management.Powershell.E2010 }

$strScriptName = $MyInvocation.MyCommand.Name
if (!(Get-ItemProperty HKLM:\Software\Innervation\$strScriptName -Name LastRun -EA SilentlyContinue)){
# this is the first time the script has run – let’s create the registry key and value for future runs
New-Item -path HKLM:\Software\Innervation -EA SilentlyContinue | Out-Null
New-Item -path HKLM:\Software\Innervation\$strScriptName | Out-Null
New-ItemProperty -path HKLM:\Software\Innervation\$strScriptName -Name “LastRun” -Value (Get-Date -Format G) -propertyType String | Out-Null
write-host “Initial configuration completed.” -ForegroundColor green
}
# get time stamp from registry so we know when it last ran
$LastRun = Get-Date ((Get-ItemProperty -path HKLM:\Software\Innervation\$strScriptName -Name LastRun).LastRun)
$ElapsedTime = ((Get-Date) – $lastrun).TotalSeconds

$strMsgFrom = “Administrator ”
$strMsgTitle = “Welkom bij Company!”

$SMTPClient = New-Object Net.Mail.SmtpClient(“*.*.*.*”)

$MBXArray = @(Get-Mailbox -ResultSize Unlimited | ? {($_.WhenCreated -gt (Get-Date).AddSeconds(-$ElapsedTime)) -and ($_.ExchangeUserAccountControl -ne “AccountDisabled”)})

ForEach ($mailbox in $MBXArray ) {
$strMsgTo = $mailbox.PrimarySMTPAddress

$strMsgBody = “Beste, “+$mailbox.DisplayName+”, welkom bij Company! Deze email is persoonlijk. Het bevat gevoelige informatie.
————————————–
Gebruikersnaam en wachtwoord
————————————–
Jouw netwerk gebruikersnaam is ‘”+$mailbox.SamAccountName+”‘.
De Support Afdeling”

$SMTPClient.Send($strMsgFrom,$strMsgTo,$strMsgTitle,$strMsgBody)
}

# update registry here with a fresh time stamp
Set-ItemProperty HKLM:\Software\Innervation\$strScriptName -Name “LastRun” -Value (Get-Date -Format G) | Out-Null

Is there anyway i can put html in the body?

It is working. I changed your script a little bit. I made the mail more html. But thnx for your nice script.

Your script is running great but it is sending emails to existing users also. Everytime this script runs, it sends email to new user as well as existing user. Would you please help?

Thank You for this great script. However, I need some help in modifying this script.

1. Can we send a PDF attachement along with this Welcome email, if so how?

2. We need to send this PDF attachment to only new mailbox users who have “EX” in the “Description” field in the Active Directory user properties. Is this possible?

Thank You in advance. Kindly help.

would anybody be able to assist in setting this up I am a little confused here. I downloaded the script and saved it to my script folder then ran .\New-WelcomeEmail.ps1 -Install however the only thing it did was ask me for my password and created the scheduled task. It did not however go through the parameters and ask me for things like IP address of email server, or OWA URL etc. Am I missing something, I think this script would be great if I could get it to run and test it. Any guidance is greatly appreciated.

ok thanks for the quick response. SO the only way to test is by creating a new account and seeing if I get the email right?

Ok so I got it to run and send the email great sript by the way, but instead of sending the email to the newly created mailboxit is sending it to my account which is who the scheduled task is to run under. The email contains all the correct information for the newly created account i.e. testuser domain name and email address but it just keep sending it to me and I dont know where its getting my email address from. How can I get this to send it to the new mailbox instead.

please disregard previous comment I figured out where I had put my email address. Sorry

One last question and I think I am all set. For testing purposes I set the scheduled task to run every 5 minutes, the email is created and sent to the correct email address fine but for whatever reason it sends it over and over to the same user every time that tasks run. Shouldn’t it identify it sent it already to this test user?

yes there is but the timestamp is from early this morning and it has ran multiple times since then but seems like the timestamp is not updating. However I also see LastRun under HKLM:\Software\Innervation and the timestamp there is updating, I tested it by running the task again manually and it changed it once it completed.

I fixed it the command at the end Set-ItemProperty HKLM:\Software\Innervation\$strScriptName -Name “LastRun” -Value (Get-Date) | Out-Null was updating HKLM:\Software\Innervation instead. So I changed that line to Set-ItemProperty HKLM:\Software\Innervation\New-WelcomeEmail.ps1 -Name “LastRun” -Value (Get-Date) | Out-Null and I received only one email at it has ran at least twice. I’m not sure why it didnt identify the variable correctly but thanks. Again thanks for all the help and awsome script been looking for something like this for a while.

No worries I didnt even catch that myself. Thanks again

I am seeing an odd issue with the script and I wanted to see if you or anyone else have experienced it as well. Right now the script works perfectly BUT only if I create the user in AD then add the mailbox through the EMC i.e New Mailbox –> Existing user, look for the newly created user and complete the wizard. Once the script runs it finds the newly created mailbox and sends the email fine. However if I create the new user using the EMC from the beginning the email is never sent, the script never sees this newly created account from the EMC. When I run the following in EMS (Get-Mailbox -ResultSize Unlimited | ? {($_.WhenCreated -gt (Get-Date).AddDays(-1)) -and ($_.ExchangeUserAccountControl -ne “AccountDisabled”)}) I do see the all three accounts that I created including the one from within the EMC. Anyone else seen this?

Pat – I just ran across this and it looks like it will be a great solution for us. I have one question, however, before I implement it. We are a construction company, and over the lifespan of a computer it will serve many different users. I am concerned that writing the timestamp in HKLM will only notify the first, new user of a machine. Would the best remedy be to just use HKCU instead of HKLM or I am I misunderstanding how the script runs? Thanks!

Pat – thanks for the quick response. One more question. Will the script work with Office 365? We have a hybrid setup so I can relay mail off of our on-premises Exchange box, but all of our mailboxes are in the cloud.

I know this script not seems updated since v.1.3 But I added the attachments function to it.
Just add tje next line before the command Send-Mailmessage
Get-ChildItem “c:\scripts\files”| Where {-NOT $_.PSIsContainer} | foreach {$_.fullname} |

So add this command will result in
Get-ChildItem “c:\scripts\files”| Where {-NOT $_.PSIsContainer} | foreach {$_.fullname} | Send-MailMessage -To $UserEmail -Subject “Welcome to $company!” -Body $emailbody -From $EmailFrom -SmtpServer $EmailServer -Priority High -BodyAsHTML

Where c:\scripts\files is the directory where all the attached file is stored and you want to send it with the email.
I’ve tested it on Exchange 2013 and it’s works perfectly

Great script, used previously with exchange 2010

I am now trying to implement with O365 hybrid. Mailboxes in cloud. I have tried making a remote connection to exchange online, but no success.

Would appreciate it if you have any more thoughts.

Thanks

Understandable. Thanks for replying.

HI I have exchange two 2013 server on prod.But only installed CAS one of server.
Now I tried send automatically mail to new users but not work.
Please give me any advice.

HI I have exchange two 2013 server on prod.But only installed CAS one of server.
Now I tried send automatically mail to new users but not work.
Please help me.
I use this script

Add-PSSnapIn Microsoft.Exchange.Management.PowerShell.Admin
Get-Mailbox | where {$_.WhenCreated -gt (get-date).adddays(-1)} | foreach{
$alias = $_.Alias
$name = $_.Name
$domain = “domain name”
$Smtp = “hostname”
$from = “username@domain.name”
$Subject = “Welcome to OUR Company”
$Body = “Welcome text”
$enc = New-Object System.Text.utf8encoding
Send-MailMessage -From $from -To $alias@$domain -Subject $Subject -Body $Body -Encoding $enc -SmtpServer $Smtp -BodyAsHtml
}

Hi Pat,

Does it work on exchange server 2016 version?

Best regards.