exchange 2010

Convert Exchange 2003 Email Address book Policies to Exchange 2010 Email Address book polices

Posted by robd on May 24, 2017
exchange, exchange 2010 / 2 Comments

If you ever get this annoying message when opening an Email Address book policy:

This means the policies were created with old versions of Exchange, in my case Exchange 2003, you can find them all, looking for the word Legacy:

As you can this will show the ldap query too, the problem is if you run the Set-EmailAddressPolicy against this then you’ll break it, all custom filters (LDAP queries) will be reset to “mailnickname=*” which can result significant email outages.

So how to fix it.

Download this PS script: https://gallery.technet.microsoft.com/office/7c04b866-f83d-4b34-98ec-f944811dd48d

Choose a policy to convert, copy the query from above and run the following:

So now we have this:

Now finially lets run the Set-EmailAddressPolicy:

Done, F5 it in Exchange console and see if you can open it!!

Tags: , ,

Outlook Anywhere Authentication Issue

Posted by robd on December 01, 2016
exchange, exchange 2010 / 1 Comment

Had a  crazy problem recently, a company Contoso.com was using Exchange 2010 (CAS, Hubs and Mailbox servers) with all the latest patches and roll-ups and had users on their domain using Outlook Anywhere perfectly.

The problem was their sub domain SubDomain.Contoso.com is also big company, they have their own Exchange 2010 servers  (CAS, Hubs and Mailbox servers) with all the same patches and roll-ups except they’re “downstream” of Contoso.com.  The problem is all users in SubDomain.Contoso.com couldn’t use Outlook Anyhwere, i.e. RPC proxy redirection wasn’t working:

outlookanywhere

The setup:

rpc-over-https

 

So all in all it was weird, we checked everything, firewall blocks, routing problems etc etc, even https://testconnectivity.microsoft.com/

So finally we logged a call with MS and after some lengthy troubleshooting they found the underlying issue:

https://support.microsoft.com/en-us/kb/2725008,

Although the article relates to Exchange 2010 sp2 RU3 it was still applicable in this scenario (SP3 RU15).

Applying the fix documented in method 2 resolved the issue.

“Disable preferred site enforcement
To resolve this issue, disable preferred site enforcement. To do this, create the following DWORD registry value:

Key:

HKLM\System\CurrentControlSet\Services\MSExchangeRPC\ParametersSystem


Value Name: EnablePreferredSiteEnforcement
Data Type: REG_DWORD
Value: 0”

 

Annoying but at least its fixed.

Tags: , , , ,

Exchange 2010 – Add SendAs permissions from MailboxPermissions

Posted by robd on July 24, 2016
exchange 2010, powershell / No Comments

To add send as permissions from the existing permissions on a mailbox you can use this script:

All you need to do is specify the username twice:

Tags: , ,

Exchange 2010 – Change the language of folder names in Outlook

Posted by robd on July 19, 2016
exchange 2010, powershell / No Comments

So We had a shared mailbox that was originally opened in Finland and as such the inbox was named postilaatikkoon and sent items was named Lähetetyt.

So I thought I’d jump into OWA and change the language there, well it turns out that has nothing to do with Folder names.

So after some research I found I could use:

But the mailbox is shared so doesn’t have a enabled user to logon with so I found this Exchange PowerShell command:

Job done.

Tags: , , ,

Exchange 2010 – PowerShell from another PC

Posted by robd on June 24, 2016
exchange 2010, powershell / No Comments

To connect to Exchange and use powershell use this command:

 

Tags: ,

ActiveSync after Migration to Exchange 2013

Posted by robd on April 10, 2016
exchange 2010, Exchange 2013 / No Comments

A friend came across this issue while migrating from Exchange 2010 to 2013.  Users were unable to receive/send email from their mobile device after migration.  This continues for up to 4 hours or so then starts working out of the blue.

 

It’s actually a bug with certain versions of Exchange 2013.

 

To fix, simply recycle the following App Pools in IIS on the CAS server:

 

  • MSExchangeAutodiscoverAppPool
  • MSExchangeSyncAppPool

 

A fix is in place for CU5, so if you are on that version or higher this fix “shouldn’t” apply…….

Tags: , , ,

Skype presence information not visible in Outlook

Posted by robd on April 09, 2016
exchange 2010, Outlook 2010 / 3 Comments

Hi,

When you install Microsoft Skype on a Windows-based computer that has Microsoft Lync installed, you experience one or more of the following issues:

Microsoft Outlook does not display presence information.
The Microsoft SharePoint client does not display presence information.
Other Microsoft Office applications that support presence features do not display presence information

This behavior may occur if the value of the DefaultIMApp registry entry in the following registry key is incorrect:
HKEY_CURRENT_USER\Software\IM Providers

Note The DefaultIMApp registry entry specifies which IM application provides IM and presence information in Office applications. When you install the Lync 2010 client together with Microsoft Office, the value of the DefaultIMApp registry entry is updated to “Communicator.”  Or, if you install the Lync 2013 client together with Microsoft Office, the value of the DefaultIMApp registry entry is updated to “Lync.”
To work around this issue, follow the steps that are appropriate for the version of Windows that you are running.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs.

Windows XP, Windows Vista, or Windows 7

Exit the Skype client and all Office applications.
Click Start, click Run, type regedit.exe, and then click OK.
Locate the following registry entry:
HKEY_CURRENT_USER\Software\IM Providers\DefaultIMApp registry value
Right-click DefaultIMApp, and then click Modify.
Type Skype in the Value data box, and then click OK.
Exit Registry Editor, and then restart  the Skype client and the Office applications.

Windows 8

On the Start screen, click the Search tile.
Type regedit in the Search window and then double-click regedit.exe.
Locate the following registry entry:
HKEY_CURRENT_USER\Software\IM Providers\DefaultIMApp registry value
Right-click DefaultIMApp, and then click Modify.
Type Skype in the Value data box, and then click OK.
Exit Registry Editor, and then restart  the Skype client and the Office applications

Hope this helps

Tags: , , ,

Exchange 2010 – View Entire Forest

Posted by robd on December 11, 2015
Active Directory, exchange 2010, powershell / No Comments

So today I was trying to running some cross domain PowerShell commands on Exchange but kept getting the following error:

Which basically means the Domain Controller your referencing can only see your sub domain and nothing higher.  So to resolve run this before the command:

Tags: , , ,

Exchange – Start Transcript

Posted by robd on December 07, 2015
exchange, exchange 2010 / No Comments

Want to record exactly what happens when you’re using the Exchange Management Shell? Use the Start-Transcript cmdlet. Anything that you do after you run this cmdlet will be recorded to a text file that you specify. To stop recording your session, use the Stop-Transcript cmdlet.

Notice that the Start-Transcript cmdlet overwrites the destination text file by default. If you want to append your session to an existing file, use the Append parameter:

Tags: , , ,

Exchange store failes due to AD topography changes

So today I was working at a site that has a single Exchange 2010 server that forfills all the Exchange roles (I know….) which happened to fall on its ass.

First thing I did was check the Exchnage services which were in a state of “starting” which is never good and then I went to the registry and found:

MSExchange ADAccess, EventID 2141
Process STORE.EXE (PID=2996). Topology discovery failed, error 0x8007077f

MSExchange ADAccess, EventID 2142

Process MSEXCHANGEADTOPOLOGYSERVICE.EXE (PID=1760). Topology discovery failed, error 0x8007077f

Here’s a few screen shots:

exchange error1exchange error2exchange error3exchange error4

As well as a few more related to AD.

After some investigation I found out that a new DC in a new site had been created for some DFS replication amongst other things.

As the system could start the Microsoft Exchange Active Directory Topology service (until it failed and is restarted by dependent services), Exchange’s other services were also triggered, leading to almost indefinitely restarting services as configured in their corresponding service recovery actions sections.

So next up is to look at Active Directory Sites and Services:

exchange error5

And as you can see from the screen shot the subnets are missing, which is going to cause issues as the new DC is on a different subnet.

When Exchange can’t determine in which site a computer belongs, the function DSGetSiteName, used to retrieve the current site, returns an error 1919 0x77f (ERROR_NO_SITENAME) which in turn kills off Exchange.  You can test this by running nltest /dsgetsite in a command prompt or by having a look at  HKLM\System\CurrentControlSet\Services\Netlogon\Parameters\DynamicSiteName.

To solve the issue you can do any of the following:

  1. Making the site association static using a registry key, which isn’t a best practice. If you must, set registry key HKLM\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\SiteName(REG_SZ) to the desired site name;exchange fix1
  2. Adding proper subnet definitions;exchange fix2
  3. Remove the new site.

 

Finally give Exchange a  bounce and BOOM.

 

Note that the NetLogon service determines site association membership at startup and every 15 minutes. The Microsoft Exchange Discovery Topology service maintains this information by caching the information in the msExchServerSite attribute of the Exchange server object, in order to reduce load on active directory and DNS. Therefore, you might need to wait or restart Microsoft Exchange Discovery Topology if you want to renew site association membership.

 

 

Copy Protected by Chetan's WP-Copyprotect.