This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool.

Problem:
Site folder server deleted
The site-wide public folder database for administrative group ‘Exchange Administrative Group (FYDIBOHF23SPDLT)’ has been deleted. Current public folder store: ‘CN=Public Folder\0ADEL:7b0fc218-05b2-4eae-9660-bbdd01f7e395,CN=Deleted Objects,CN=Configuration,DC=uw,DC=lu,DC=se’.

Solution:
http://technet.microsoft.com/en-us/library/aa996485(EXCHG.80).aspx

The siteFolderServer attribute represents the Distinguished Name (DN) of the Public Folder store that is responsible for hosting the site folders (normally the first server in the site or administrative group).

By default, the Site Folder Server is the first server that is installed in the administrative group. The public folder store on this server is the default location of the free/busy folders and offline address book folders for the administrative group. If you remove or decommission this server without replicating these folders to another server and designating that server as the offline address book server, Microsoft Office Outlook® 2003 users will see problems with the offline address book and with free/busy data.

Aa996485.Caution(en-us,EXCHG.80).gif Caution:
If you incorrectly modify the attributes of Active Directory objects when you use Active Directory Service Interfaces (ADSI) Edit, the LDP (ldp.exe) tool, or another Lightweight Directory Access Protocol (LDAP) version 3 client, you may cause serious problems. These problems may require that you reinstall Microsoft Windows Server™ 2003, Exchange Server 2003, or both. Modify Active Directory object attributes at your own risk.

To correct this error

  1. Open an Active Directory editor, such as ADSI Edit.
  2. Locate the public folder information store that you want to designate as the Site Folder Server. For Exchange Server 2000 through Exchange Server 2007, expand the following nodes in the Configuration container:
    CN=Configuration,DC=<DomainName>,DC=com, CN=Services, CN=Microsoft Exchange, CN=<OrganizationName>, CN=Administrative Groups, CN=<AdministrativeGroupName> CN=Servers, CN=<ServerName>, CN=InformationStore, CN=<StorageGroupName>
    For Exchange Server 2010, expand the following nodes in the Configuration container:
    CN=Configuration,DC=<DomainName>,DC=com, CN=Services, CN=Microsoft Exchange, CN=<OrganizationName>, CN=Administrative Groups, CN=Exchange Administrative Group (FYDIBOHF23SPDLT), CN=Databases
  3. In the right pane, right-click CN=<PublicFolderStoreName>, and then click Properties.
  4. In the Attributes field, scroll down and select the distinguishedName attribute.
  5. Click Edit, and then copy the entire attribute to the Clipboard.
  6. Expand the Configuration container, and then expand CN=Configuration,CN=<DomainName>,CN=com, CN=Services, CN=Microsoft Exchange, CN=<OrganizationName>, CN=Administrative Groups
  7. Right-click the administrative group you want to modify, and then click Properties.
  8. In the Attributes field, scroll down and select the siteFolderServer attribute.
  9. Click Edit, and then paste the value for the distinguishedName attribute into the Value field.
  10. Double-check the contents of the Value field to ensure the paste was performed correctly, and then click OK to save the change.
  11. Click OK to close the Administrative Group properties.
  12. Exit the Active Directory editor and restart the Microsoft Exchange Server Information Store service on all Exchange Server computers in the site for the change to take effect.

For more information about re-creating system folders and resetting the Site
Folder Server, see the following Microsoft Knowledge Base articles:

Tagged with:
 

After migrating your Exchange server (I’ve seen this in transition to exchange 2007 and 2010) the PublicFolderDatabase for your OfflineAddressBook is still pointing to the old servers public folder store.

When you run the get-OfflineAddressBook | fl command in a exchange management shell on your new server, you get a result like this:

At Server you see the new servername and the PublicFolderDatabase is still pointing to your old server. Public folder replica’s and offline address book generation server are already moved to the new server.

Solution: I found if you do the following steps you can change the PublicFolderDatabase.
First start adsiedit and browse to CN=Configuration, CN=Services, CN=Microsoft Exchange, CN=First Organization, CN=Address Lists Container, CN=Offline Address Lists and open the properties of CN=Default Offline Address List

Look for the siteFolderServer attribute, here you will see the old public folder store. Choose clear and close with ok, now you may close adsiedit.

Now go to the exchange management console, Organization Configuration, Mailbox, Offline Address Book open the properties of the Default Offline Address List and go to the tab distribution.

Uncheck “Outlook version 2 and 3″ at client support and uncheck “Enable public folder distribution”. Make sure “Web-based distribution” is enabled. Choose apply and ok, then right click on Default Offline Address List and choose update. After that go back to properties and distribution and check “Outlook client support version 2 and 3″ and “Enable public folder distibution”. Again choose apply and ok and right click and choose update.

When you go back to the exchange management shell and repeat get-OfflineAddressBook | fl you now will see the public folder store on your new server.

Link: http://blog.ronnypot.nl/?p=212

Tagged with:
 

Problem:
In a migration environment with exchange 2007 and exchange 2010 we have client (outlook 2007) that hangs 10 seconds when sending a meeting that books a resource mailbox residing on Exchange 2010 mailbox server.

Microsoft say:
In a support case to microsoft they acknowledge this problem as a feature in exchange 2010 when booking resourcemailboxes. They state that this is a fix (code release) for office 365 (clod exchange) where microsoft is not using public folders. This fix is for Outlook 2003 clients when connection to the clod. Outlook 2003 use public folder for accessing free/busy information and when microsoft closed this door in office 365 they had to get a workaround for outlook 2003 users. This fix is intercepting outlook 2003 calls to public folder on a mailbox server and redirecting them to webservices (EWS) on a CAS on behalf off mailuser.

Outlook 2010 is not affected like outlook 2007.

This is not a correct picture yet. A better one is coming soon.
1. Client try to get free/busy information from it’s mailboxserver holding public folder
2. Mailbox server trying to access https://webmail.org.se/EWS/Exchange.aspx for free/busy information behalf off mailuser insted of accessing public folder.
4. CAS answering mailboxservers request for information.

So this is a fix for exchange in clod only!? – Yes and No…
It is a fix release for both clod and on premise. So it is affection or local environment to and that is bad!

We noticed the following event id’s being generated on the Mailbox server MBX.org.se
Time:     2011-04-01 10:39:52
ID:       4002
Level:    Error
Source: MSExchange Availability
Machine:  MBX.org.se
Message:  Process 2796: ProxyWebRequest CrossSite from S-1-1-0 to https://webmail.org.se/EWS/Exchange.asmx failed. Caller SIDs: NetworkCredentials. The exception returned is Microsoft.Exchange.InfoWorker.Common.Availability.ProxyWebRequestProcessingException: System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException:
No connection could be made because the target machine actively refused it 100.101.102.103:443

Why do we have a problem?
Our Exchange 2010 mailbox servers could not connect to https://webmail.org.se/EWS/Exchange.asmx
Well, we can not access Internal URL for EWS from our mailboxservers.
Is this correct? No!
But our network design is not letting us do this right now.
When we worked around this problem we no longer have a problem with outlook 2007. So thats good!
But this proxy fix for outlook 2003 in the clod is still affecting outlook 2007 even thou we no longer see a problem.

Patch from Microsoft
Microsoft is releasing a option in Exchange 2010 SP1 RU4. You will have a way to disable the Availability intercept by using the following registry value.

KEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeRPC\ParametersSystem
DWORD: DisableAvailabilityServiceCalls
Value: 1 ( Disable)