How to Disable Autodiscover in Outlook 2010/2013

There is an MS KB article to reference and Outlook 2007 and 2010 ADM files http://support.microsoft.com/kb/2612922. The ADM files attached to the article were great because they gave a way to disable the different methods Outlook uses to determine autodiscover in Outlook 2007 and 2010. Outlook (generically) uses 5 methods to determine discoverer.

1. SCP object lookup
2. Root domain query based on your primary SMTP address
3. Query for the AutoDiscover domain
4. HTTP redirect
5. SRV record query in DNS

Unfortunately Outlook 2013 is a little new and MS doesn't have a nice preconfigured ADM. That's ok because the exact same methods for autodiscover are used in 2013 as they were in previous version.

We can create a reg file for 2013 by exporting the key that gets created when the ADM is applied via GPO for 2010 and just changing the registry path. So instead of:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\14.0\Outlook\AutoDiscover

I changed it to:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\15.0\Outlook\AutoDiscover

You can change the various options from the registry file as well. They are:

"ExcludeScpLookup"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000000
"ExcludeHttpsAutoDiscoverDomain"=dword:00000000
"ExcludeHttpRedirect"=dword:00000000
"ExcludeSrvRecord"=dword:00000000

Above the SCP lookup is disabled.

 

How to use the ADModify.NET tool to add an X.500 proxy address to multiple accounts

How to use the ADModify.NET tool to add an X.500 proxy address to a user account

Admodify2.1 nolonger support X500 tab entry, thus we will have to use custom tab.

 

X500 addresses are useful once we migrated volume of mailboxes from another organization and we enabled GAL sync between Exchange organizations before migration. Lack of the lagacyExchangeDN of old organization or x500 address, migrated users may get NDR once they tried to reply to existing emails to certain users.

1. Click the Custom tab.
2. Under Custom Attribute Set, follow these steps:
3. Click to select the Make a customized attribute modification check box.
4. In the Attribute Name box, type proxyAddresses.
5. In the Attribute Value box, type the X.500 address.
   
   For example, if you want an X.500 address of /o=OldOrganization/ou=OldSite/cn=Recipients/cn=mailNickname, type the following in the Attribute Value box:
   X500:/o=OldOrganization/ou=OldSite/cn=Recipients/cn=%'mailNickname'%
   
   
   In this example, we use the %'mailNickname'% variable because we assume that the mailNickname attribute in the new organization matches the mailNickname attribute in the old organization. If these attributes do not match, use another variable.
   
   Note If the migrated user account is from an Active Directory directory service environment, use the Adsiedit tool to locate the old legacyExchangeDN attribute of the user. Then, use the old legacyExchangeDN attribute for the X.500 address.
6. Click Multivalued Append, and then click Go.

 

 

http://support.microsoft.com/kb/909271

 

Use Poolmon to identify Exchange 2010 mailbox server memory leaking issue

We have four hardware identical Cisco UCS servers that installed as Exchange mailbox servers mailbox role and joined DAG replication partners. Two local servers are working fine. However, two remote servers keeping running out of memory and we had to reboot these two servers at regular base (once a month) until we used Poolmon to identify the cause of the memory leaking, a known Cisco NIC teaming bug. Poolmon was able to identify with tag Team caused memory leaking that consumed more than 5 GB nonpaged memory before the server running out of available memory less than 20MB of 96 GB physical RAM and Hard Faults per sec pager constantly reached 100.

 

Once poolmon identify tag Team, then we used the following string to find the driver that caused the memory leaking:

 

findstr /m /l team *.sys either of system32  or \system32\drivers directory.

 

for more info, please read the following links:

 

http://forum.sysinternals.com/nonpaged-pool-memory-leak-caused-by-dire_topic16133_page3.html

 

http://blogs.technet.com/b/askperf/archive/2008/04/11/an-introduction-to-pool-tags.aspx?Redirected=true

How to Disable Attachment Filtering on Exchange 2010 Edge Transport

We had an interesting issue recently where our Exchange 2010 Edge Transport server was erroneously stripping out .docx, .xlxs, and .pdf files. 

 

There is a Microsoft KB to address the issue, however, it doesn't work for us.

 

http://support.microsoft.com/kb/2855809

The attachmentfilteragent has been enabled by default, and I wanted it off, so we needed to add an exception for our receive connector. It's not as straightforward as you would expect though to turn off attachment filtering on an Exchange 2010 Edge Transport server.

 

The first step is to see if there are any connectors on the attachment filter exception list presently.  To do so, run this command:

 

Get-AttachmentFilterListConfig
 

About the fifth line down you should see "ExceptionConnectors" which probably has nothing next to it. 

You can only turn off attachment filtering by referencing the GUID, so now we need to get the GUID of the relevant receive connector. 

 

Get-ReceiveConnector  | Format-List
 

This will give us all the properties of our Receive Connector, including the GUID, which will be listed about 10 lines up from the bottom. Now that we have the GUID, we can run the command to add the receive connector to the list of exceptions for attachment filtering by running this:

 

Set-AttachmentFilterListConfig –ExceptionConnectors [GUID]
 

Replacing [GUID] with the GUID we retrieved in the previous step.

 

Finally, run Get-AttachmentFilterListConfig again and check the Exceptions line, you should now see your receive connector listed there.

 

reference link:

 

http://beccabits.com/2011/05/24/how-to-turn-off-attachment-filtering-on-exchange-2010-edge-transport/

Migrate Public Folders to Exchange 2013 From Previous Versions

 

http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx