PowerShell Script to easily copy a file and rename in new destination

Sharing with you a simple Powershell script I wrote and use to generate a .TXT that will list all the file names/location in myfolder A and then easily copy that TXT file from myfolder A in drive A into myfolder B in drive B. It can be used for other file types as well.

For copying between remote servers, you will have to make a few modification to the script – this article from MS can guide you :- https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.management/copy-item?view=powershell-6

$From = “K:\myfolderA\listofusersinthisfolder.txt”
Get-ChildItem K:\myfolderA\*.*| Set-Content K:\myfolderA\listofusersinthisfolder.txt
Copy-Item -Path $From -Destination “J:\myfolderB\newlistofusers.txt” -Recurse -Force

$From = This will be the full path of the file you want to copy

-Destination = This will be the destination drive and folder for your copied file

Mail.Que database too large


Today I will show you how to safely delete and recreate the mail.que – mail queue database file in Exchange server. Upon deletion of the mail.que Exchange will auto create a new mail.que database file, once you restart the Microsoft Exchange transport service.

This is useful, if your mail.que file is getting too large or consuming a lot of space on your drive, but be sure to properly investigate the root cause of the growth, such as safetynetholdtime, pipeline tracing value etc – In my case the safetynetholdtime value Exchange 2016 was set to 7 days which caused the growth of mail.que. MS has a good article to get started on these settings –  https://docs.microsoft.com/en-us/powershell/module/exchange/mail-flow/set-transportconfig?view=exchange-ps

Using Exchange management powershell we can check the existing size of mail.que

Get-ChildItem “D:\Exchange Server\TransportRoles\data\Queue\mail.que” |select name,@{Label=”size”;Expression={“{0:N0}” -F ($_.Length/1GB)}}


By default  your mail.que file location should be at :-  %ExchangeInstallPath%TransportRoles\data\Queue

  1. Put your server in maintenance mode in SCOM etc, or best schedule to perform these actions during out of business hours.
  2. Suspend Microsoft Exchange Transport service (NOT STOP) This will allow the current queue to no longer accept more mails in queue and until the remaining mails are sent out:-
  3.  Suspend-service -name “Microsoft Exchange Transport”
  4. Get-queue  – to check and ensure queues are empty.
  5.  Wait for the queue to drain and ensure no more mails in queue, and message count is 0.   keep checking with Get-Queue. Do not worry about shadow redundancy. Once queues is empty it is now safe to stop the transport service.
  6. Stop-service -name “Microsoft Exchange Transport”
  7. Go over to the mail.que location, select all and move to a different folder or drive with enough space, you can rename it as mail.que.old backup
  8. Start the transport service
  9. Start-service -name “Microsoft Exchange Transport”
  10. You will see a new mail.que is auto created
  11. Get-queue  – check and monitor and ensure mail flow is back to normal

Tip: use a tool such as Treesize free to get a detailed view of files and the size in your drive. It can come in handy when you want to check the size of files in your exchange data path.

Managing MailContacts created in Exchange 2007 in our Exchange 2013


Today, I will show you how to manage MailContacts in an exchange 2007 / exchange 2013 co-existence scenario and also how to easily migrate your bulk mail contacts from Exchange 2007 to Exchange 2013 , this can also be applied to Exchange version 2010 where you plan to move up to 2013/2016 or when you have co-existence and have to toggle managing MailContacts between the higher and lower Exchange version.

Always Note:-

You cannot use a lower version of Exchange server to modify an Exchange object that was created/upgraded in a higher version of Exchange, and likewise, from a higher version of Exchange you will be first asked to upgrade that Exchange object to a higher version before you can modify it.

Common errors you will face:-

Exchange 2007


Or via powershell:-


From Exchange 2013 powershell when modifying a mailcontact originally created in Exchange 2007 you will get this warning:-



TIP:-  Always check the Exchange version of the object that you need to modify or migrate, this will make things easier..

In powershell you can run:-

Get-recipient mytest@contoso.de | fl exchangeversion, name, externalemailaddress

This outputs the Exchange version – Exchange 2013  0.20 {} for the external mailcontact menothappy@contoso.de


You can check the different Exchange versions on Microsoft technet link here  – https://technet.microsoft.com/en-us/library/hh135098(v=exchg.150).aspx

To upgrade/migrate/modify a mailcontact that was created in Exchange 2007, we want to manage this mailcontact in our Exchange 2013 :-

Created in 2007:-


In Exchange 2013:-



We can run the following commands in Exchange Management Shell in Exchange 2013 to upgrade the mailcontact :-

  1. Get-MailContact ‘Happy, Me’ | fl ExchangeVersion,ExternalEmailAddress
  2. Get-mailcontact ‘Happy, Me’| Set-mailcontact -ExternalEmailAddress ‘mytest@contoso.de‘ -Force:$true
  3. Get-recipient ‘Happy, Me’ -ReadFromDomainController:$true| fl ExchangeVersion,ExternalEmailAddress


To do it from ECP Exchange 2013 (read and accept the warning message):-


Once completed you can now easily manage the mailcontact in 2013. Lets try to change the SMTP email address from mytest@contoso.de to menothappy@contoso.de :-


We can do it easily, no more warnings no more errors and in future we can easily change/modify/delete the mailcontact from Exchange 2013.

For Migrating mailcontacts in bulk, you can first use the commands I have provided above to gather information for their ExternalEmailAddress , displayname, put them all in a CSV, name the columns ExternalEmailAddress, DisplayName, then add your mailcontacts external emailaddress and their display names.

You can modify the powershell command above to something like:-

Import-CSV “D:\mycontactsbulk.csv” | foreach {Set-MailContact $_.DisplayName -ExternalEmailAddress $_.ExternalEmailAddress -Force:$true}

First test it with 1 contact and get the results and then you can do it in bulk.

Mount Point Icon shown as Folder instead of default Mount drive Icon – Windows server 2012r2


Mount point Icon shown as a yellow file folder :-


Normal mount drive Icon should look like this :-



Make sure when you are creating a mount point, you need to create the mount point folder from the ‘New Simple Volume Wizard’ in disk management of your windows server, once created, do another quick format again after the first quick format during the wizard creation.


Create a new mount point folder and follow the prompts to complete


Once it is finished. Perform another quick format manually:-


Once it is done, your new mount point will appear with the correct mount drive icon :-


I hope this helps anyone who have encountered this issue :D.

Add domains to Internal Relay on Exchange 2010

Here is a quick step to add new domains to your internal relay on Exchange.

If you are not familiar with what internal relay means and what are its impact, you can head over to Microsoft technet and read more:- https://technet.microsoft.com/en-us/library/bb124423(v=exchg.150).aspx#Anchor_2



  1.  open up the EMC console and under Organization Configuration >> Hub Transport >> Accepted domains, in the actions menu, select New Accepted domain
  2.  Enter the display name, you can use a different name than the actual accepted domain or for me I prefer to keep it the same.
  3.  Select internal relay domain and save.

Via powershell command:-

new-AcceptedDomain -Name ‘contoso.com’ -DomainName ‘testdomain.com’ -DomainType ‘InternalRelay’

4. To verify that the new accepted domain is working, I usually like to test by sending a test message and then see the results, you can do this via powershell as follows:-

Send-MailMessage -From noreply@newcontoso.com -To “administrator@contoso.com” -Subject “Test internal relay ” -Body “Test only. Do not reply” -SmtpServer “name of your hub server”

View the result from message tracking log:-

Get-MessageTrackingLog -ResultSize unlimited -Start “08/06/2018 9:00AM” -Recipients “administrator@contoso.com” -sender noreply@newcontoso.com -Server”name of your hub server”

This will help you to know immediately if something was wrong with your configuration and you can go back and follow the steps again.

Cannot set the security descriptor of mailbox – Exchange PowerShell error when assigning permissions in Exchange 2010/2016 co-existence

You may come across this error especially if you have not fully migrated all user mailboxes to your new exchange 2016 servers, or you have a co-existence 2010/2013 or 2010/2016, and you still have to resolve help desk calls for those users not yet migrated or those who just got migrated.


“Cannot set the security descriptor of mailbox…….. in exchange mailbox database ……..”

Below command was executed to grant full access permission to userB on userA mailbox:-

Add-MailboxPermission -Identity “userA” -User “userB” -AccessRights FullAccess -InheritanceType All

And we got the error described above.


Powershell is throwing this error because the mailbox that you are trying to add the permission is hosted in a higher version of exchange than the server you are running the powershell command from.

That means you should be running the command in Exchange 2016 where the mailbox of userA is now hosted after it was migrated from Exchange 2010.


  1. Check which database the mailbox is currently on, and which version of Exchange server.

Get-Mailbox -Identity UserA | fl database,exchangeversion

2. Use powershell on a higher version of  exchange where the mailbox resides. In my case it is exchange 2016 powershell, it depends on your Exchange version result which you will get by running the command above.

You can always refer to this Microsoft technet link to know your versions of Exchange 🙂 https://technet.microsoft.com/en-us/library/hh135098(v=exchg.150).aspx

The proxy address “smtp:info@contoso.com” is already being used by “contoso.com/Microsoft Exchange System Objects/BI176-Folder”

Today one of my client encountered this error while trying to add a new SMTP address to an existing mailbox account and it failed. He mentioned that the new SMTP address has never been assigned to any other mailbox in the organization.

Error:-  The proxy address “smtp:info@contoso.com” is already being used by “contoso.com/Microsoft Exchange System Objects/BI176-Folder”. Please choose another proxy address.


The user mailbox is hosted on an Exchange 2007 mailbox database.

I suspect one of the public folder child item could be using this SMTP address, either it’s still in use or it’s orphaned.

To troubleshoot, I used ADSIEdit.msc tool to find the Exchange object causing the error, and under the attribute “class”  it is marked “Public Folder”, on the properties dialog, I could see under “proxyAddresses” , the email address in the error was listed there.

Next is to use the tool PFDAVAdmin for exchange 2007,


Using PFDAVAdmin I was able to connect to the public folders in the organization and find one of the subfolders that was using the SMTP address shown in the error.

I requested user to choose another SMTP address, just as the error prompt suggested, and that solved it.

If the Exchange object is already orphaned and no longer in use in your organization you can delete it or rename the proxy-addresses attribute.