Event ID: 112 Source: EXOLEDB Type Error Description: Microsoft Exchange OLEDB was unable to register OnSyncSave event for Schema propagation on MDB s

Event ID: 112 Source: EXOLEDB Type Error Description: Microsoft Exchange OLEDB was unable to register OnSyncSave event for Schema propagation on MDB startup HRESULT = . Concepts to understand What is an HRESULT? The oldest schema-root folder is not necessarily the one at fault. Rename either folder, stop and start the Microsoft Exchange Information Store, and if the errors disappear then you have correctly identified the offending folder. Then you are safe to delete the renamed folder from ESM. If however you receive EventID 1194 from source MSExchangeIS and EventID 111 from source EXOLEDB complaining about MAPIRPC and Schema propagation you have renamed the wrong one. Do not forget that you will have to rename the offending folder before you can rename the one you want to keep.
Reported error codes:- 0x8000ffff = "Catastrophic failure error"From a newsgroup post: "In ESM, check to see if you see two "schemaroot" system folders. To check this, right click "Public Folders" and click "View System Folders". You can safely delete the older one. This should correct the EXOLEDB event."From a newsgroup post: "This error can get logged when the exoledb interface tries to make a call to the store but the databases are dismounted (as will usually happen at startup). You should then see informational events for your stores mounting and no more of the 112s. If this is what you are seeing you can ignore the errors. If you, however, continue to see the events while the dbs are mounted then you have a problem that will require further investigation."
- 0x80040e19 = "Bind failed"From a newsgroup post: "On the exchange CD, support/utils/i386, copy the smtpreinstall.exe to the EXCHSRVR/BIN and run it."

After Global Catalog Server rebooting, the BlackBerry Enterprise Servers (4.X) have lost their connections to the Global Catalog servers

SYMPTOMS: After Global Catalog Server rebooting, the BlackBerry Enterprise Servers (4.X) have lost their connections to the Global Catalog servers.

Per RIM,

The BlackBerry Enterprise Server has lost its connection to the Global Catalog server and did not receive a referral.

Resolution

This issue has been identified by Microsoft and a hotfix has been released. For more information, see article 929439 on the web site.

Note: As part of this resolution, Global Catalog server referrals on the Microsoft Exchange server must be turned on.

---

Workaround

If the BlackBerry Enterprise Server has lost its connection to the Global Catalog server, you can restart the BlackBerry Enterprise Server or the BlackBerry Dispatcher and BlackBerry Controller service to reconnect to the Global Catalog server.

Important: Restarting certain BlackBerry Enterprise Server services will delay email message delivery to BlackBerry smartphones. For more information, see KB04789.

Per Microsoft:

A MAPI program may not obtain a referral server when the global catalog server to which the MAPI program points is shut downA MAPI program may not obtain a referral server when the global catalog server to which the MAPI program points is shut down. Microsoft has released hotfix to address the issue from the following link:

http://support.microsoft.com/kb/929439/en-us

Note:

You must create the EMSAB_UserAuth_Credentials registry entry on the Exchange 2003 server where the hotfix is installed for this hotfix to work. With the EMSAB_UserAuth_Credentials registry entry set to the value 1, the MAPI provider will never enter the user credential state. When the global catalog server is still shutting down, MAPI clients that have this registry entry will continue to obtain the MAPI_E_NETWORK_ERROR error code. However, as soon as the global catalog server has finished shutting down, and the Exchange 2003 server has established a connection with a new global catalog server, the MAPI client will obtain the expected MAPI_E_END_OF_SESSION error code.

Important When this registry key is set on an Exchange 2003 server with the hotfix installed, the user credential state cannot be entered by MAPI clients that are running on the server. This hotfix will prevent the MAPI clients that require user interface from connecting across domain boundaries, where it is expected that users can be prompted for credentials. Make sure that you do not set the registry entry on Exchange 2003 servers when the UI prompt for credentials is desired by MAPI clients that are running on the servers. This hotfix does not alter the behavior of Exchange 2003 as a MAPI server. Also, it does not affect Outlook clients or any other MAPI clients that are running on other computers in which the hotfix and registry key have not been applied.

To set the EMSAB_UserAuth_Credentials registry value, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate the following registry subkey:
   HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Exchange Provider
3. On the Edit menu, point to New, and then click DWORD Value.
4. In the Details pane, type EMSAB_UserAuth_Credentials, and then press Enter.
5. Right-click EMSAB_UserAuth_Credentials, and then click Modify.
6. In the Edit DWORD Value dialog box, click Decimal in the Base area.
7. In the Value data box, type 1, and then click OK.
8. Exit Registry Editor.

Prerequisites

Because of file dependencies, Microsoft Exchange Server 2003 Service Pack 2 (SP2) must be installed on the server before you apply this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

836993 (http://support.microsoft.com/kb/836993/ ) How to obtain the latest service packs for Exchange Server 2003

Restart requirement

You do not have to restart your computer after you apply this hotfix. However, the following services are automatically restarted when you apply the hotfix:

• Microsoft Exchange Information Store service
• Microsoft Exchange MTA Stacks
• Microsoft Exchange System Attendant

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Collapse this tableExpand this table

File name	File version	File size	Date	Time	Platform
Emsabp32.dll	6.5.7652.15	173,568	22-Feb-2007	02:55	x86

How to use the new DNS SRV lookup method to locate the Exchange 2007 Autodiscover service

Note: the feature only works with Outlook 2007 /w SP1

To use the new DNS SRV lookup method in order to locate the Exchange 2007 Autodiscover service, follow these steps.

Note You must create the Autodiscover SRV record in the external DNS zone that matches the right side of your user's SMTP addresses. For example, if a user's primary SMTP address is user@contoso.com, the record must be created in the contoso.com external DNS zone. If you have multiple primary SMTP address domains in your organization, you must create an Autodiscover SRV record in each zone.

1. In your external DNS zone, remove any HOST (A) or CNAME records for the Autodiscover service.
2. Use the following parameters to create a new SRV record:

   Service: _autodiscover Protocol: _tcp Port Number: 443 Host: mail.contoso.com 

   Note For more information about how to create this record, see the "About SRV records" section.
3. to verify the DNS Srv record:

              nslookup -q=srv _autodiscover._tcp.contoso.com and make it returns right host name, IP address and port 443.

 

Note In this example, mail.contoso.com is a name for which your certificate is valid. Usually, this is the same DNS name that you use for Outlook Anywhere and for Outlook Web Access.

In this example, the Autodiscover service does the following when the client tries to contact the Autodiscover service:

1. Autodiscover posts to https://contoso.com/Autodiscover/Autodiscover.xml. This fails.
2. Autodiscover posts to https://autodiscover.contoso.com/Autodiscover/Autodiscover.xml. This fails.
3. Autodiscover performs the following redirect check:
   GET http://autodiscover.contoso.com/Autodiscover/Autodiscover.xml
   This fails.
4. Autodiscover uses DNS SRV lookup for _autodiscover._tcp.contoso.com, and then "mail.contoso.com" is returned.
5. Outlook asks permission from the user to continue with Autodiscover to post to https://mail.contoso.com/autodiscover/autodiscover.xml.
6. Autodiscover's POST request is successfully posted to https://mail.contoso.com/autodiscover/autodiscover.xml

How to add User Principal Name Suffixes

Add User Principal Name Suffixes

You can use Active Directory Domains and Trusts to add user principal name suffixes for the existing user account. The default user principal name suffix for a user account is the DNS domain name of the domain that contains the user account. You can add alternative UPN suffixes to simplify administration and user logon processes by providing a single user principal name suffix for all users. The UPN suffix is only used within the Active Directory forest, and it is not required to be a valid DNS domain name.

Membership in Domain Admins or Enterprise Admins, or equivalent, is the minimum required to complete this procedure. Review details about using the appropriate accounts and group memberships at http://go.microsoft.com/fwlink/?LinkId=83477.

To add user principal name suffixes

1. Open Active Directory Domains and Trusts. To open Active Directory Domains and Trusts, click Start, click Administrative Tools, and then click Active Directory Domains and Trusts.

2. In the console tree, right-click Active Directory Domains and Trusts, and then click Properties.

3. On the UPN Suffixes tab, type an alternative user principal name (UPN) suffix for the forest, and then click Add.

4. Repeat step 3 to add additional alternative UPN suffixes.

Additional considerations

• To perform this procedure, you must be a member of the Domain Admins group or Enterprise Admins group in Active Directory Domain Services (AD DS), or you must have been delegated the appropriate authority. As a security best practice, consider using Run as to perform this procedure. For more information, search for "using run as" in Help and Support.
• UPN suffixes should conform to Domain Name System (DNS) conventions for valid characters and syntax.

How to move susdb.mdf for WSUS 3.0 SP1

By default, WSUS 3.0 on SBS 2003 R2 server uses Windows Internal Database.
If WSUS 3.0 uses other versions of SQL server, the moving steps will be a
little different, but the procedures are almost same. They are:
1. Detach SUSDB from SQL Server.
2. Move SUSDB.mdf and SUSDB_Log.ldf to the new location.
3. Attach SUSDB to SQL Server again.

If WSUS 3.0 is using Windows Internal Database, please follow these steps
to move SUSDB:
1. Open a "CMD" command window, and run these commands to stop the WSUS
service and IIS:
net stop wsusservice
iisreset /stop

2. Detach the SUSDB.
a. Follow the instructions to download and install "Microsoft SQL Server
Management Studio Express" on the WSUS server:
http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=6053
c6f8-82c8-479c-b25b-9aca13141c9e
(Please note: we need to install MSXML6 and .Net Framework 2.0 first. If
this tool already exists, please ignore this step.)

b. Click "Start"->"All Programs"->"Microsoft SQL Server 2005"->"SQL Server
Management Studio" to run this tool.

c. Select the SQL server/instance used by WSUS, and then click Connect. For
WSUS 3.0 with Windows Internal Database, please copy/paste this name:
\\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

(If this name is unreachable, please WSUS may not use Windows Internal
Database, please verify this registry value to confirm the SQL name:
HKEY_LOCAL_MACHINE\Software\Microsoft\Update
Services\Server\Setup\SqlServerName.
%computername%\MICROSOFT##SSEE means Windows Internal Database.)

d. Expand the "Databases" node from the left pane; Right click the "SUSDB",
then click "Tasks"->"Detach" and "OK".

If it fails, please select the "Drop Connections" checkbox and try again.

3. Move the SUSDB.mdf and SUSDB_Log.ldf to a new location by Windows
Explorer. By default, they are in the
"<Driver>:\WSUS\UpdateServicesDbFiles" folder.

4. Attach the SUSDB database from the new location.
a. Switch back to the Management Studio and right click the "Databases"
node, and then click "Attach".

b. Click "Add" button; Navigate to the new location, and then select the
SUSDB.mdf and click "OK".

5. Start the WSUS and IIS services with these commands:
net start wsusservice
iisreset /start

Now the process is finished. Please open the WSUS console and verify if
WSUS is working properly.

How to apply Exchange service packs and hotfixes

How to apply Exchange 2003 service packs and hotfixes on Cluster

 

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

 

How to apply Exchange 2007 service pack 1 on CCR

 

http://technet.microsoft.com/en-us/library/bb676320.aspx

 

 

 

How to Upgrade a Single Copy Cluster to Exchange 2007 SP1

 

http://technet.microsoft.com/en-us/library/bb691226.aspx

 

 

Applying Exchange 2007 Update Rollups to Clustered Mailbox Servers

 

http://technet.microsoft.com/en-us/library/bb885043.aspx

 

 

Cluster.exe group "Cluster Group" /move:<NodeName>

 

 

How to Install Update Rollups in a CCR Environment

 

http://technet.microsoft.com/en-us/library/bb885047.aspx

 

How to Install Update Rollups in a Single Copy Cluster

 

http://technet.microsoft.com/en-us/library/bb885045.aspx

 

 

 

 

How to backup Exchange 2007 on Windows 2008

After all the hassle of getting Exchange 2007 setup, we know that we had no way to backup my Exchange 2007 server running on Server 2008. For whatever reason, Microsoft do not supply NTBackup and there is no in-built way of backing up Exchange 2007 when run on Server 2008 yet.

 

After some research, We found this article on how to install NTNackup on Vista:
http://www.petri.co.il/installing_windows_xp_ntbackup_on_windows_vista.htm

I followed this by copying the following binaries from my old server (C:\Windows\System32\) to my new server (C:\Program Files\NTBackup\):

• ntbackup.exe
• ntmsapi.dll
• vssapi.dll

We installed the removable storage manager from server manager:

• Start Server Manager
• Click Features
• Click Add Features
• Select Removable Storage Manager
• Click Install

When NTBackup starts, you will see an error regarding removable storage, but I just ignored this and clicked "Do not show this again"

Upon running NTBackup, I could see drives and system state, but no Exchange!

I then found this:
http://support.microsoft.com/kb/275876

I copied esebcli2.dll from my old server (C:\Program Files\Exchsrvr\Bin) to my new sever (C:\Program Files\NTBackup)

I ran regedit and changed the esebcli2 key from C:\Program Files\Micrsoft\Exchange Server\Bin\esebcli2.dll to C:\Program Files\NTBackup\esebcli2.dll.

I ran NTBackup and backed up my Exchange store to disk!

The DisplayName property contains leading or trailing whitespace, which must be removed.

Exchange mixed environment (Exchange 2003 & 2007). Move mailbox reported failure with the following message:

Mailbox for user Failed

Error:
The Name property contains leading or trailing whitespace, which must be removed.



For some AD accounts (Mailboxes on 2003), you may notice the following when "Mailbox" is clicked in Exchange Management Console (Exchange 2007).

WARNING: Object DOMAIN.COM/OU/USER, has been corrupted and it is in an inconsistent state. The followingvalidation errors have occurred:WARNING: The DisplayName property contains leading or trailing whitespace, which must be removed.

Solution:

run the following command from Exchange 2007 management Shell:

get-mailbox -identity USER Foreach { Set-Mailbox -Identity $_.Identity -DisplayName $_.DisplayName.Trim() }

substitute the USER with the problematic mailbox user.

How to automatically schedule Windows 2003 ASR Backup without Floppy Disk

Windows 2003 introduces a very useful disaster recovery tool called ASR (Automatical System Recovery Backup). It's very use to schedule ASR backup without a floppy before disaster happens, you can write a script file with correct switches. There is a hidden switch you can use, the "asrbackup". The following is a sample:

ntbackup.exe asrbackup /n "ASR for myServer" /d "ASR for myServer" /v:yes /r:no /rs:no /hc:off /m normal /j "SystemBackup" /l:s /f "D:\ASR\ASR_myServer.bkf"

How ASR Works http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/7b4f0436-cc90-4b52-b6ab-064f9db8d272.mspx
Guidelines for Using ASR http://www.microsoft.com/technet/prodtechnol/windowsserver2003/library/DepKit/ec2605a5-22b0-4f01-83e7-171bc4cbdf04.mspx

How to create Dynamic Exchange 2007 Distribution List Based on Exchange 2007 Database

Exchnage 2007 EMC doesn't offer GUI based wizard to create Exchange 2007 Dynamic Distribution Group by all mailboxes within a Exchange Database. However, it's a usually tool for Exchange admin if you need to notify your users when you are planning a database maintenance at scheduled time. Lukily, you can use EMS to create Exchange 2007 Dynamic Distribution Group by all mailboxes within a Exchange Database. Here's a quick recipe to create a Dynamic Distribution Group to include all mailboxes on a database.

$DB = (Get-MailboxDatabase "SERVER\Storage Group\Mailbox Database").distinguishedName

New-DynamicDistributionGroup MyGroup -RecipientFilter {Database -eq $DB} -RecipientContainer "DC=MySubDomain,DC=MyRootDomain,DC=com" -OrganizationalUnit "OU=MySubOU,OU=Distribution Groups,DC=MySubDomain,DC=MyDomain,DC=com"

Once you have created the Dynamic DL, you can fine tune the DL by using EMC GUI interface to modify it, say, add permission to send, size restriction, enable discover report, etc.

Note:

1. SubDomain and SubOU are optional, depending on your Domain and OU structure.
2. The first step gets the distinguishedName of the mailbox database in a variable called $DB.Parameters:- OrganizationalUnit: Specifies the container/OU where the group will be created- RecipientContainer: Specifies container to pick up recipients from.