Saturday, October 11, 2008
They can block it by selecting calendar's permission to "None" for the default setting.
It gets set back to "free+busy" after about 24 to 48 hours later. it is done by BES (4.1.5 or later).
Disable the free+busy look up capability to prevent the problem.
Here is an instruction:
* if you do it, users with handheld software version 4.5 or later can not perform free+busy lookup
Wednesday, October 08, 2008
There are a few possible installation issues that we would like you to be aware of:
1. Exchange 2007 managed services might time out during certificate revocation checks
2. When installing a Rollup, we recommend you use the same account that you used to install Exchange Server. If you are using a different account, that account needs to have Local Administrator rights as well as rights to read Active Directory on Exchange object as well as server level (as the update needs to determine which roles are installed on the server). Not having required permissions can lead to OWA not being updated correctly and displaying a blank page after update has completed.
3. If you have modified the logon.aspx file, it will not be patched by the Update Rollup installer. As a result Outlook Web Access may not be updated correctly and it may display a blank page after the update has finished. In order to avoid this problem, rename the logon.aspx file before applying the update rollup. After you apply an update rollup package, you must re-create Outlook Web Access customization in logon.aspx.
If you have Cisco Unity and exchange server 2007, you might experience IP phone's LED (Voicemail indicator lamp) won't syncronize when a user receives or deletes a message. This update, kb952580, will fix the issue.
This update rollup 4 for exchange 2007 sp1 includes 951251 (http://support.microsoft.com/kb/951251/): A MAPI application does not work correctly if Exchange 2007 is installed on a Windows Server 2008 server.
More information on what was really broken, take a lok at http://blogs.msdn.com/stephen_griffin/archive/2008/07/03/mapi-download-and-the-enumprotocols-bug.aspx
Also If you are using Blackberry enterprise server 4.1.3 or later with exchange server 2007, you might want to update CDO&MAPI on BES, this is optional, here is an instruction
On this instruction remove ESM 2003, and follow the instruction in full.
Saturday, May 03, 2008
Migrating exchange 2003 clustered server environment to exchange 2007 sp1 using windows 2008 servers
Before I post detailed steps, here is a migration plan.
The 2x E2K3 OWA (NLB) and 2x E2K3 clustered backend servers will be replaced/migrated to
- 2x E2K7 SP1 CAS&HT (NLB)
- 1x E2k7 sp1 public folder server (LCR)
- 2x E2k7 sp1 (CCR) mailbox servers (CCR: 1 active and 1 passive)
0. Prep 2x windows 2008 server STD for CAS and HT, install IIS, NBL and etc.
1. Export IIS cert from the exchange 2003 OWA server, and import that to the windows 2008 STD servers.
2. Install exchange 2007 sp1 on windows 2008 server.
3. Create/modify E2k7 connectors, create routing connector to connect EVS1 and E2k7 CAS&HT server.
4. Remove e2k3 OWA servers.
5. Setup e2k7 sp1 STD public folder server (single mailbox server withot mailbox DB)
6. set OAB on e2k7 public folder server for old outlook users. replicate Public Folders.
7. Prep CAS&HT for witness server.
8. install e2k7 ENT CCR mailbox server.
9. migrate mailboxes
10. remove e2k3 server clusters.
11.Clean up AD using ADSI edit tool.
Tuesday, April 29, 2008
Tuesday, March 04, 2008
1. On one of the front end server, request and install SSL.
2. Open the IIS manager, find a "exchange" virtual directory and set Require SSL and Require 128 bit encription.
3. On Exhange Systems Manager, open the front end server.
4. Go to the protocol--> http, right click the http and open the properties for the Exchange Virtual Server.
5. Click settings tab, and check the "Enable Forms Based Authentication"
6. On the front end server, reset the iis or restart the server.
7. Try connect the owa using https://
8. On the front end server, start the IIS manager and export the cert.
9. on the second front end server, import the cert.
10. repeat #2 to #6 on the second front end server.