PST Capture Tool Setup and Use

Exchange PST Capture Use

There's a few things to do to get this to work properly.  Here's how mine is setup and I have no problems pulling PST files into Exchange 2010.

1. Windows 7 Professional on the domain.

2. Install .NET 4.5 framework.

3. Install Powershell 3.0.  It's part of the Windows Management Framework.  Download HERE.

4. Install Outlook 2010.  Make sure you use the 64-bit version.  Even if the PST file comes from a 32-bit machine.  This is because Exchange 2010 is 64-bit.

5. Run this command using Exchange Powershell  "New-ManagementRoleAssignment -Role "Mailbox Import Export" -User "PSTImportUser"

**If you do not run the Powershell command you will get ERROR OPENING MAILBOX**

6. Install PST Capture.

Once these things are done you are ready to pull the PST files into Exchange using PST Capture.

I highly recommend you go into Settings and remove the check box  beside "Create a subfolder for each PST file".  This will put all mail into the proper folder structure as what is inside the PST.

Also make one more edit under Non-mail items. Check both boxes so it will get their calendar, contacts, etc.

That's pretty much it.  The rest inside PST Import is pretty easy to understand and you're on your way to importing files as needed into a new or existing Exchange server.

Good luck!

Repair Windows 7 ISO Burn

If you have a 3rd party app that breaks your option for Windows 7 to burn an ISO file this is how to fix it.

Create a file named ISO.reg on your desktop.  Copy the text below and paste into it.  From there just right click and select MERGE.  This will repair the Windows 7 registry so the OS can again burn ISO files.

This is all it takes to fix the problem.  Good luck.

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.iso]
@="Windows.IsoFile"

[HKEY_CLASSES_ROOT\Windows.IsoFile]
@="Disc Image File"
"FriendlyTypeName"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,\
  00,6f,00,6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,\
  32,00,5c,00,69,00,73,00,6f,00,62,00,75,00,72,00,6e,00,2e,00,65,00,78,00,65,\
  00,2c,00,2d,00,33,00,35,00,30,00,00,00

[HKEY_CLASSES_ROOT\Windows.IsoFile\DefaultIcon]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,69,00,73,00,\
  6f,00,62,00,75,00,72,00,6e,00,2e,00,65,00,78,00,65,00,2c,00,2d,00,31,00,30,\
  00,31,00,00,00

[HKEY_CLASSES_ROOT\Windows.IsoFile\shell]

[HKEY_CLASSES_ROOT\Windows.IsoFile\shell\burn]
"MUIVerb"=hex(2):40,00,25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,\
  6f,00,74,00,25,00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,\
  00,69,00,73,00,6f,00,62,00,75,00,72,00,6e,00,2e,00,65,00,78,00,65,00,2c,00,\
  2d,00,33,00,35,00,31,00,00,00

[HKEY_CLASSES_ROOT\Windows.IsoFile\shell\burn\command]
@=hex(2):25,00,53,00,79,00,73,00,74,00,65,00,6d,00,52,00,6f,00,6f,00,74,00,25,\
  00,5c,00,53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,69,00,73,00,\
  6f,00,62,00,75,00,72,00,6e,00,2e,00,65,00,78,00,65,00,20,00,22,00,25,00,31,\
  00,22,00,00,00

[-HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\FileExts\.iso\UserChoice]

Export Emails within a Date Range from Exchange 2010

Today I had to do this to assist with an email audit for a government agency.  Below are the steps you need to follow to make this happen.  The TechNet article leaves out a very important step that I have included for you below.


1. Open up the Exchange Management Shell and enter the following command:  New-ManagementRoleAssignment –Role “Mailbox Import Export” –User "DOMAIN\USERACCOUNT"

**NOTE:  Now close the EMS and reopen it.  You have to do this because the roles for the user logged in are loaded when the EMS is started.

2. Use this command to export your email date range and the location where you want to save it: New-MailboxExportRequest -Mailbox "SAMPLE USER" -ContentFilter {(Received -lt '01/01/2012') -and (Received -gt '03/31/2012')}  -FilePath "\\SERVER\EXPORTS\SAMPLE_USER.pst"

Depending on the size of the user's email you may get a file rather quickly or you may get a message from the EMC that the job is queued and will be filled when it is completed the search and export process.

What lead me here was the error "The Term 'New-MailboxExportRequest' is not recognized as the name of a cmdlet, function, script file, or operable program".

The steps above will avoid this error and get you exactly what you need from the email box.

If you just want to dump the entire mailbox use this:  New-MailboxExportRequest -Mailbox "SAMPLE USER" -FilePath "\\SERVER\EXPORTS\SAMPLE_USER.pst"

iOS 7 “Software Update Failed” Message

The iOS 7 rush is causing lots of problems for a lot of people.

iOS 7 downloaded fine for me but then I received a “Software Update Failed” message. 

Follow these steps and your problems will be solved:

1. Restart your device.

2. Disable your Wi-Fi.

3. Turn off your device and keep it off for 5 minutes.

4. Turn your device back on and enable Wi-Fi.

5. Try the download again.

It sounds simple but it has worked 100% of the time for the people I’ve told about it.

Feel free to share this fix on Facebook or tweet about it on Twitter to help others getting this error. 

Removing Exchange 2007 Public Folders from Exchange 2010 Environment

Before beginning any of this work make sure you either no longer need public folders in your environment (Office 2000/2003 has to have them) or that they have fully replicated to your new Exchange server.

1. Try to remove the public folders through the EMC.  If this fails now it's time to get tough.

2. Open Exchange Management Shell and enter the following:

Get-PublicFolder -Server SERVERNAME "\" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server SERVERNAME -Recurse -ErrorAction:SilentlyContinue

3. Next run this command:

Get-PublicFolder -Server SERVERNAME "\Non_Ipm_Subtree" -Recurse -ResultSize:Unlimited | Remove-PublicFolder -Server SERVERNAME -Recurse -ErrorAction:SilentlyContinue

4. Refresh the EMC and the public folders will be gone.  If this does not work and you're fully sure you need them removed then this last step truly removes them from the environment.  All that's left is to manually delete the files if needed.

1. Connect to your DC.
2. Open ADSIEDIT.MSC console and connect to configuration.
3. Go to the following path.

–> CN=Configuration –> CN=Services –> CN=Microsoft Exchange –> CN=YOUR ORGANISATION –> CN=Administrative Groups –> CN=First Administrative Group –> CN=Servers –> CN=SERVER NAME +—> CN=InformationStore

 

This final step ensures that even though the folders/files may still exist they are removed from AD and will not prevent removing Exchange 2007 at that point.

Good luck!