Sunday, December 17, 2006

The RTM download of Exchange 2007 is now available on the licensing
site for those with select or premier accounts.

Test away!

Friday, December 08, 2006

Exchange 2007 has RTM'd! Congrats to the whole Exchange team.

Monday, November 13, 2006

Paul was blogging from Exchange Connections in Vegas and posted
some great info on what features we will see post-beta 2 as well as
the RTM date (December).

Thursday, November 09, 2006

Here's a really nice post on the routing changes coming with Exchange 2007. This
will be a great departure from what currently exists with Exchange 2003 so read up
now so your prepared!

Thursday, October 19, 2006

In conjuction with the last post, here is good discussion of archiving from
the Exchange team. They talk about why (or why not) to install an archving
system and what problems it can solve (and create).
Looks like MS is getting in to the email archiving business with IBM:

With competing products such as EAS and KVS having a big headstart, it will be
interesting to see how well they compete. I'm actually surprised MS didn't build
archiving in to the product with Exchange 2007.

Monday, October 02, 2006

AOL appears to be bouncing some mail with a new error I haven't seen:

It seems some people are getting this NDR even if they don't have a URL
in the message. Haven't heard anything from aol but just an FYI.
Check out this great post over at EHLO about sizing suggestions for Exchange
2007. We are going to start seeing much large base memory configs with Exchange
2007 now that we are 64bit. I know we are already looking at making our base
config for a two proc mailbox server with 1000 mailboxes use 8gb of memory.

Monday, August 14, 2006

After applying the latest hotfixes that MS released, we found one of our
E2k3 OWA servers was getting the dreaded 'Loading...' error in the task pain.
After digging thru the KB I found this article:;en-us;910119&sd=rss&spid=1773

Now in our case, the cause did not match exactly as the FE server was upgraded
to sp1 first then sp2 and the BE server was already running sp2. But... copying
the new folder from the BE to the FE resolved the issue.

Just an FYI if you run in to this issue.

Tuesday, July 25, 2006

Tuesday, June 20, 2006

For those testing/using Direct Push, there is a log file created
on each device that records all the information related to the sync
process between the device and your server. The file name is 'ctrllog'
and is located in the \windows\activesync folder. One useful bit of
information from this file is the current heartbeat interval your
device is using. Values are in seconds with the device starting at 480
and increasing the interval as conditions warrant it. On my device,
the heartbeat tends to hover between 780 and 1080.

This value is critical in the consumption of battery power so if your's is hovering
at 480 most of the day your battery will most likely be consumed quickly.
Just an FYI... they announced at Tech Ed that E2k7 Beta 2 would be
available in July to the general public.

Another intersting note mentioned in one of the sessions.... the log
file size has been changed from 5mb to 1mb to help minimize the chance
of lost data when using LCR or CCR. Looks like we will have a bunch
more log files now.

Monday, June 05, 2006

Here's some interesting info I've found relating to direct push. In the KB
article below it states that the default setting for 'maxheartbeatinterval' is
45 minutes. So if nothing is set in the registry, this is supposed to be the
value used. We have seen a large increase in battery consumption when upgrading
our devices to a rom with direct push.... in the nature of 30-40% reduction in
run time. This didn't make sense to me considering how often the device was
syncing (about 140 messages a day, maybe 10 minutes of voice time) so on a hunch
I manually set the 'maxheartbeatinterval' to 45 minutes. Since making this change,
my battery life has gone from 10-12 hours per charge to 24-26 hours per charge.

I've verified this change on two different devices (a PPC-6700 and a 700W) so
there must be something to this setting. It may be that the setting is forcing
Exchange to use this setting irregardless of the network conditions but I have
seen no adverse effects of changing this. If you have seen similar decreases in
runtime, try this change and let me know your results.

Saturday, June 03, 2006

Here's some good documentation on V2 of the IMF. Much improved over
V1, we are actually using this as an additional layer of antispam filtering
and have seen good results.

Tuesday, May 09, 2006

Microsoft just announced the fix list for this month and Exchange just happens
to have a critical update involving a remote code issue. Test on non-production servers first (as always) and be mindful of the issue with Blackberry/Good servers
this patch brings.

Sunday, April 30, 2006

Here's a heads up on a new product coming out that looks interesting. It's
called MailShadow and is made by Cemaphore ( The product is
geared towards DR scenarios and works at the transaction level so there are no
issues with database level corruption (like you see with other Exchange replication

I haven't seen the product yet in action so I'll reserve my judgement for then
but if it works like they say it could be a great addition for companies looking
to replicate Exchange data to other locations.
MS made this announcement quite a while ago (about breaking permissions in accounts with certain post-sp2 store fixes) but now they have added a script you can run that will identify these accounts before you apply any of those store fixes. I advise everyone run the script now to identify if they do have any account configured in this manner so you can fix them before one of these store fixes sneaks in on a hotfix you desperately need.

Tuesday, April 04, 2006

There is now a way to set a list of smtp addresses that will not be scanned
by the IMF on Exchange 2003/sp1. This is a nice addition to a product that
already works very well. Most likely this functionality will be rolled in to
the GUI but for now, regedit is your friend.

Monday, March 20, 2006

MS just release IE7 Beta 2 preview:

Go take it for a spin!

Saturday, March 18, 2006

As more people are updating their device with AKU2, questions are coming up about
battery consumption on the device. The consensus is Direct Push will consume a larger amount of battery compared with the old method (SMS), where we are seeing about a 15% depletion over 2G protocols and and a 30% depletion for 3G protocols (just for the heartbeat.) If your seeing excessive decline in battery usage after enabling Direct Push you may want to check the time-out value for HTTPS connections on your firewall. MS recommends setting this to 30 minutes as anything less could un-necessarily cause your device to resend additional heartbeats (thus draining the battery quicker.)

This KB talks about the setting in more detail:

Thursday, March 16, 2006

It's arrived! Unofficially (since I haven't seen an official announcment
from Sprint yet) Sprint has released the MSFP (aka AKU2) for the PPC-6700
and we have been testing it over at the great site:

So far the Direct Push feature is working great. Sync times seem to be
about 50% faster and no more SMS messages flying around. The ROM also seems
to have fixed a number of issues with this device making it really shine.

If you have this device, run, don't walk to install this update.

UPDATE: Sprint has now officially rolled this out. Here is a link to the
official rollout download (which is the same as the one posted previously).

Thursday, March 09, 2006

If your in the UK and have a C600 phone from Orange you can now download
MSFP for your device. This is the first carrier in the UK to release the
MSFP for any device.

And where still waiting here in the US...

Wednesday, March 08, 2006

And the waiting continues.... Very few Carriers have released the MSFP
for their devices thus far (None in the US, only one in Korea I believe) and it looks like most are still a few months out. Microsoft needs
to do something about this as the carriers are becoming huge road blocks for
the adoption of Windows Mobile devices in the enterprise. If it takes each
carrier 6-9 months to do a ROM upgrade for a device most devices will only ever
get one upgrade (if their lucky).

There must be a way they could separate the carrier logic from bits MS needs
to update (kind of like how drivers are written now with MS doing the heavy
lifting and developers writing to that core driver)so upgrades are easier to
push out and don't require the carrier's integration efforts.

Are you listening MS?
Brian Desmond ."
had a great article about a potentially bad situation that can
arise from a poorly designed feature in Exchange System Manager. In KB article it talks about how if you choose the delete option by right clicking a server under the system policies section, it doesn't just delete the server from the server policy but also deletes the actual server object from AD. I cannot imagine why MS chose to even allow this but it's there and you should be aware of it.

The KB goes thru the steps to recover the object, needless to say it's alot of
work. BTW, the delete option is only seen if your running Exchange 2003 native

Hopefully MS will correct this in a future sp/hotfix

Wednesday, March 01, 2006

MS just made Beta 1 of E12 available to MSDN subscribers. Download away (remember, no production servers at this time).

Monday, January 30, 2006

According to Cnet, Microsoft is merging the Exchange group with the RTC group to
form an new group for development purposes. Seems logical although the two are
separate products now so the bringing these two teams together may be more for cost
savings rather than interop between the products.
Just an FYI... I'm hearing from one of the largest CDMA vendors that we will see AKU 2.2
next month sometime. I have a feeling Motorola is delaying the Motorola Q rollout until this
is released (which IMO, is a good idea).

Hopefully AKU 2 will bring some improvements since the current WM5 ROM image seems
to have a few issues.