Starting from Exchange 2010 SP1 a scheduled task called Database One Copy Alert will be configured automatically on each mailbox server. This script will be executed every hour and will check if multiple copies are available inside the DAG. Besides this the status of the copy will be checked. This because a copy which is not healthy may lead to data lost during a failover.
A while ago Microsoft announced the Exchange ActiveSync Logo program. Using this program Microsoft will test the compatability of devices with ActiveSync.
This week I received a question via e-mail about an Exchange 2010 environment. In this environment some big problems did occur which caused a large amount of messages to be placed in the Unreachable queue. Messages will be placed in the queue when Exchange can’t deliver the messages. This can be both messages which need to be sent to external mailservers or internal Exchange servers.
Both the Exchange Management Console (EMC) and Exchange Management Shell (EMS) are making a connection to Powershell using a remote session. During the session a connection will me made to the virtual directory Powershell which can be found in the IIS Management Console. This virtual directory can only be accessed by using port 80 by default.
Update 1-5-2010: this issue only occurs if opening one of the items which are located in the organizational management folder
After the installation of Exchange 2010 SP1 on a server which only contains the Mailbox Server role you might get a lot of errors in the event log.
The OAB Generator of Exchange is responsible for generating the Offline Address Book (OAB). To generate this the service will use information which is found in the Active Directory. When you have a single forest and domain this will not give a lot of issues. But what happens when Exchange is installed in the forest root domain and the users are placed in a child domain? In this case Exchange will contact the domain controllers in the child domain to gather the information.
It’s time for another update for the prepare_owa_im script, this update is pretty big compared to the earlier update. Starting with this version it’s possible to configure both OWA and Lync using the script. There is one limitation: it’s not possible to enable the new topology.
In Exchange 2010 almost all connections are made via the CAS server, excluded the Public Folder connection. On the CAS server a service is running called the RPC Client Access Service which is used by Outlook to make a connection to the mailbox. When this service isn’t running no MAPI connections can be made to the server.
One of the options which was missing in the first edition of the script was to check if a certificate is self-signed or not. By default a self-signed certificate is installed on an Exchange CAS Server. The problem with this kind of certificates is that other servers won’t trust it.
