TagWindows Server

Stop Exchange 2010 From Changing Resource Calendar Subject Lines

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

Install .NET Framework 3.5 on Windows Server 2012

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:

X:\Sources\SxS

Now the installation should complete without any issues.

Exchange 2010 Move Requests With BadItemLimit Larger Than 49

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

© 2015 Dustin Riley

Theme by Anders NorenUp ↑