Solved Way to create pst on Exchange 2013
-
@jaredbusch said in Way to create pst on Exchange 2013:
@dbeato said in Way to create pst on Exchange 2013:
@jaredbusch said in Way to create pst on Exchange 2013:
I already have a power shell script to create an export but I was wondering if there was a simple or method to simply export an entire mailbox to a PST prior to deletion
Yes, via the ECP/OWA panel:
http://www.edb.2pst.net/blog/exchange-2013-export-all-mailboxes-to-pst.html
http://www.edbtopstoutlook.com/blog/2013/how-to-export-mailbox-to-pst-in-exchange-2013.htmlWow, not exactly easy. My poweshell script (run form the Exchange Manament Shell) is less work.
I think the thing that kills me here is that need to setup the Import Export rights for all mailboxes.
Maybe that is something that changed. my script was last tested on Exchange 2010.
I'll try that and this method later this afternoon.
The first time is more work because you need to get the rights (Same as powershell) but once that is done is easy. I have Exchange 2010 Scripts and I have been able to use it through Exchange 2016.
-
@dbeato said in Way to create pst on Exchange 2013:
@jaredbusch said in Way to create pst on Exchange 2013:
@dbeato said in Way to create pst on Exchange 2013:
@jaredbusch said in Way to create pst on Exchange 2013:
I already have a power shell script to create an export but I was wondering if there was a simple or method to simply export an entire mailbox to a PST prior to deletion
Yes, via the ECP/OWA panel:
http://www.edb.2pst.net/blog/exchange-2013-export-all-mailboxes-to-pst.html
http://www.edbtopstoutlook.com/blog/2013/how-to-export-mailbox-to-pst-in-exchange-2013.htmlWow, not exactly easy. My poweshell script (run form the Exchange Manament Shell) is less work.
I think the thing that kills me here is that need to setup the Import Export rights for all mailboxes.
Maybe that is something that changed. my script was last tested on Exchange 2010.
I'll try that and this method later this afternoon.
The first time is more work because you need to get the rights (Same as powershell) but once that is done is easy. I have Exchange 2010 Scripts and I have been able to use it through Exchange 2016.
My script has no rights setup on individual mailboxes.
-
@jaredbusch said in Way to create pst on Exchange 2013:
@dbeato said in Way to create pst on Exchange 2013:
@jaredbusch said in Way to create pst on Exchange 2013:
@dbeato said in Way to create pst on Exchange 2013:
@jaredbusch said in Way to create pst on Exchange 2013:
I already have a power shell script to create an export but I was wondering if there was a simple or method to simply export an entire mailbox to a PST prior to deletion
Yes, via the ECP/OWA panel:
http://www.edb.2pst.net/blog/exchange-2013-export-all-mailboxes-to-pst.html
http://www.edbtopstoutlook.com/blog/2013/how-to-export-mailbox-to-pst-in-exchange-2013.htmlWow, not exactly easy. My poweshell script (run form the Exchange Manament Shell) is less work.
I think the thing that kills me here is that need to setup the Import Export rights for all mailboxes.
Maybe that is something that changed. my script was last tested on Exchange 2010.
I'll try that and this method later this afternoon.
The first time is more work because you need to get the rights (Same as powershell) but once that is done is easy. I have Exchange 2010 Scripts and I have been able to use it through Exchange 2016.
My script has no rights setup on individual mailboxes.
You only need the "Mailbox Import Export" permission and have access to any mailbox. NO need to setup individual rights. Probably the first link was misleading if that is the case.
-
It was a quick skim, but both examples look like the import/export right is on the individual mailbox.
-
@dbeato here is the script I currently use. It is used while logged in to the Exhange server with the domain admin account.
# To execute script, you must open an exchange powershell window, elevated permissions not required. # First you must be in the scripts directory. # cd \scripts # Then execute the powershell script with 3 parameters. # ./CreatePST.ps1 >First Name< >Last Name< >email alias< # ./CreatePST.ps1 Bundy Administrator bnaadmin # The export path is not a variable as we need to know that it is writable by the system. param ( [string]$FirstName = $(throw "-FirstName is required."), [string]$LastName = $(throw "-LastName is required."), [string]$alias = $(throw "-alias is required.") ) New-MailboxExportRequest -Mailbox "$alias" -FilePath "\\exch01\c$\PSTExports\$FirstName.$LastName.pst" Write-Host "" Write-Host "To check status, run: Get-MailboxExportRequest | Get-MailboxExportRequestStatistics" -
@jaredbusch said in Way to create pst on Exchange 2013:
@dbeato here is the script I currently use. It is used while logged in to the Exhange server with the domain admin account.
# To execute script, you must open an exchange powershell window, elevated permissions not required. # First you must be in the scripts directory. # cd \scripts # Then execute the powershell script with 3 parameters. # ./CreatePST.ps1 >First Name< >Last Name< >email alias< # ./CreatePST.ps1 Bundy Administrator bnaadmin # The export path is not a variable as we need to know that it is writable by the system. param ( [string]$FirstName = $(throw "-FirstName is required."), [string]$LastName = $(throw "-LastName is required."), [string]$alias = $(throw "-alias is required.") ) New-MailboxExportRequest -Mailbox "$alias" -FilePath "\\exch01\c$\PSTExports\$FirstName.$LastName.pst" Write-Host "" Write-Host "To check status, run: Get-MailboxExportRequest | Get-MailboxExportRequestStatistics"This is good. What you need to do in any Exchange server is the following for the account requesting the export:
New-ManagementRoleAssignment -Role "Mailbox Import Export" -User "<user name or alias>" -
@dbeato said in Way to create pst on Exchange 2013:
This is good. What you need to do in any Exchange server is the following for the account requesting the export:
Never done that before on Exchange 2007 or Exchange 2010.
-
And damnit..
New-MailboxExportRequest : The term 'New-MailboxExportRequest' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again. -
@jaredbusch said in Way to create pst on Exchange 2013:
And damnit..
New-MailboxExportRequest : The term 'New-MailboxExportRequest' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.Once you add the role to the user and open the console again then it will be fine.
-
@dbeato said in Way to create pst on Exchange 2013:
@jaredbusch said in Way to create pst on Exchange 2013:
And damnit..
New-MailboxExportRequest : The term 'New-MailboxExportRequest' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.Once you add the role to the user and open the console again then it will be fine.
And exit the current powershell windows and reopen.
So either all the previous Exchange servers I have done this on already had this role by default, or someone added it.
-
@jaredbusch said in Way to create pst on Exchange 2013:
@dbeato said in Way to create pst on Exchange 2013:
@jaredbusch said in Way to create pst on Exchange 2013:
And damnit..
New-MailboxExportRequest : The term 'New-MailboxExportRequest' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.Once you add the role to the user and open the console again then it will be fine.
And exit the current powershell windows and reopen.
So either all the previous Exchange servers I have done this on already had this role by default, or someone added it.
Yes, you are correct in the assessment.
-
Exchange 2010 I needed to assign the Import/Export role to my user before I could export a mailbox.
-
Were you able to export the mailboxes?
-
@dbeato said in Way to create pst on Exchange 2013:
Were you able to export the mailboxes?
Yes, once I added that role to the domain admin account, it worked perfectly.
-
As a conclusion to this post, I did not find a better method than my current PowerShell script.
-
Out of curiosity, why are you exporting a mailbox before deletion?
Deletion of ex-employee email is something I always struggle with (and have had many discussion here on), so was just wondering...
-
@brrabill said in Way to create pst on Exchange 2013:
Out of curiosity, why are you exporting a mailbox before deletion?
Deletion of ex-employee email is something I always struggle with (and have had many discussion here on), so was just wondering...
Because it makes it no longer an IT issue.
Terminated employees mailboxes are exported and dropped onto a location that the client access or delete. No longer my problem.
-
@jaredbusch said in Way to create pst on Exchange 2013:
@brrabill said in Way to create pst on Exchange 2013:
Out of curiosity, why are you exporting a mailbox before deletion?
Deletion of ex-employee email is something I always struggle with (and have had many discussion here on), so was just wondering...
Because it makes it no longer an IT issue.
Terminated employees mailboxes are exported and dropped onto a location that the client access or delete. No longer my problem.
Depending on where you drop it, still a part of the backup, so....
-
@dashrender said in Way to create pst on Exchange 2013:
@jaredbusch said in Way to create pst on Exchange 2013:
@brrabill said in Way to create pst on Exchange 2013:
Out of curiosity, why are you exporting a mailbox before deletion?
Deletion of ex-employee email is something I always struggle with (and have had many discussion here on), so was just wondering...
Because it makes it no longer an IT issue.
Terminated employees mailboxes are exported and dropped onto a location that the client access or delete. No longer my problem.
Depending on where you drop it, still a part of the backup, so....
but the mailbox is not an issue.
at that point it is just user data. -
I still think is more of an IT issue.
If you work at a smaller company, and the boss doesn't think to ask you what to do. You go to him and say what?
Should we delete it? Should we keep it.
