If you’re using resource mailboxes in Exchange 2010 and have it automatically process meeting invites, then you may notice that the subject lines are getting stripped and replaced with the organizer’s name. Depending on how you are using the resource mailbox, this may be an undesired action. If you wish to leave the original subject in the calendar entry, run the following command in the Exchange Management Shell:
Set-CalendarProcessing -Identity ResourceMailbox -AddOrganizerToSubject $false -DeleteSubject $false
If you try to install .NET Framework 3.5 on Windows Server 2012, using the Server Manager and accepting the defaults, you will get an error stating that the source files could not be found. During the installation process Windows Server 2012 does not copy the required files for installation of .NET Framework 3.5 as it did in Windows Server 2008 R2. On the confirmation screen after selecting the .NET Framework 3.5 Features, you’ll notice a yellow bar telling you that an alternate path to the data files needs to be specified. Near the bottom of the window is an option to Specify an Alternate Source Path. Click this and specify the following path, substituting X with your optical drive with the Windows Server 2012 media:
Now the installation should complete without any issues.
If you’re performing a local move request in Exchange 2010 using the Exchange Console, it will only allow you to set a BadItemLimit up to 49 items. To allow a higher amount you need to do use the Exchange Shell. Use the following syntax, replacing SomeUser, ExchDB, and 75 with the appropriate values:
New-MoveRequest -Identity ‘SomeUser’ -TargetDatabase ExchDB -BadItemLimit 75 -AcceptLargeDataLoss
A fairly straight forward way has been introduced in Exchange 2010 to import PST’s into mailboxes from the Exchange Shell. Mailbox import requests were added into Exchange 2010 in SP2.
Give yourself permission to use Mailbox Import Requests:
New-ManagementRoleAssignment –Role “Mailbox Import Export” –User Administrator
Import PST (Allowing 49 bad items before the transfer fails):
New-MailboxImportRequest -Mailbox Usermailbox -BadItemLimit 49 -FilePath\\SERVER\SHARE\SOMEPST.PST
Import PST into an Online Archive:
New-MailboxImportRequest -Mailbox Usermailbox -BadItemLimit 49 -IsArchive -FilePath\\SERVER\SHARE\SOMEPST.PST
Performing Mailbox moves in Exchange 2010 can be a rather slow process, moving at 3-4GB an hour. If you’re migrating a large store this is a long period of time to wait. Here’s how you can speed up the process significantly. I’ve used these settings on several SBS 2003 to 2011 swing migrations including from a 2003 swing server running in Hyper-V on a SATA drive. If you’re moving from something beefier than that I would suggest bumping up the MaxActiveMoves settings accordingly.
On the server you’re migrating to edit MSExchangeMailboxReplication.exe.config located in your Exchange bin folder (by default: c:\Program Files\Microsoft\Exchange Server\V14\Bin)
Find the following default values:
MaxActiveMovesPerSourceMDB = “5″
MaxActiveMovesPerTargetMDB = “2″
MaxActiveMovesPerSourceServer = “50″
MaxActiveMovesPerTargetServer = “5″
MaxTotalMovesPerMRS = “100″
Change them to:
MaxActiveMovesPerSourceMDB = “7″
MaxActiveMovesPerTargetMDB = “7″
MaxActiveMovesPerSourceServer = “50″
MaxActiveMovesPerTargetServer = “40″
MaxTotalMovesPerMRS = “250″
Restart Microsoft Exchange Replication Service
If you attempt to create multiple sites in IIS6 that use the same SSL port (by default 443), then you will get an error message when you try to start the second one stating “IIS was unable to start the site. Another site may already be using the port you configured for this site. Please select a unused port for this site.” To setup SSL on the second site you need to either use a different port or edit the metabase directly. II6 comes with a script that will allow you to edit the metabase and add the binding for the second SSL site
The script is located in the Inetpub/AdminScripts directory and will need to be run from there in the command prompt. You will need to know the site identifier for the site you want to add the binding to. You can find this in the IIS Manager, drilling down to Web Sites, it will be in one of the columns in the right pane.
cscript.exe adsutil.vbs set /w3svc/<Site Identifier>/SecureBindings “:<Port>:<Host Header>”
cscript.exe adsutil.vbs set /w3svc/1/SecureBindings “:443:server.example.com”
Once you complete this you should be able to start the site in the IIS Manager.