Wednesday, December 15, 2010

good tool for Bulk Changes

ADModify.NET is a tool primarily utilized by Exchange and Active Directory administrators to facilitate bulk user attribute modifications. See http://blogs.technet.com/exchange/archive/2004/08/04/208045.aspx for launch details

How to cleanup the Exchange Catalog Data after a mbdc move

So for example I have a mailbox that resided at the following: E:\Mailbox\USMBDB03 and after moving the DB to F:\ the Catalog data is still there: E:\Mailbox\USMBDB03\CatalogData-4aa4fde6-634a-4845-b62f-d853c52a7536-0ba86735-c7aa-4fd7-a497-5e36462e842d

Open up Exchange Powershell and run the following CMD:

Set-MailboxDatabase "US MBDB Users D-F" -IndexEnabled $false

Move the catalog file to an alt location until everything is said and done.

then do a Set-MailboxDatabase "US MBDB Users D-F" -IndexEnabled $true

Reference:

Monday, August 16, 2010

Automatic workstation object removal

You can use dsquery command to find inactive computers and then delete them
with dsrm.
dsquery computer domainroot -inactive NumberOfWeeks | dsrm -noprompt



http://technet.microsoft.com/en-us/library/cc755655(WS.10).aspx

Monday, July 12, 2010

Best practices the following have been disabled on each server

· Windows Firewall

· TCP Chimney

· IPV6

· RSS

· Network DMA

- Autotunning

Syntax: netsh interface tcp set global autotuninglevel=disabled

You need to set permissions on each mailbox database for BES when running in an Exchange 2010 env.

Unable to reply to email on BES device

I was getting the following errors in the application logs on the BES server:

"xxx"

So a restart of the server resolved the issues, and I was able to reply to email.

Messages stuck in Exchange 2010 queue for certain email domains

I set the FQDN of the SMTP connector on the HT and disabled autotuning via the folowing syntax:

netsh interface tcp set global autotuninglevel=disabled