Sure, there are loads of MVPs and TAP-Members that have migrated to Exchange 2010 a long time ago, but i’m still proud of this.

At a starting point, i had a Exchange 2007 SP2 machine, with one Mailbox database, no public folders and 35 Mailboxes that used up 25GB of space. Moving this is simple enough, but the issue is that our Exchange isn’t virtualized, and i couldn’t get my hands on new hardware since the current box was only a year old.

Since in-place upgrades are not supported, i needed a temporary server for the migration. I used an HP ML110 from the Lab, which offered enough space to migrate.

Another issue was BackupExec 12.5, which did not support Exchange 2010 yet. Fortunately, Exchange 2010 (and 2007 SP2) can be backed up by using Windows Server Backup. So my goal was to just let WSB backup to a file server, and have BackupExec pickup the files from there. This way, i will get a reliable, clean and supported Exchange backup, and still have it on tape.

To Migration itself was straightforward and easy. There’s already _lots_ of content on the web about Exchange 2010, most of it from the RCs or Beta of course.

I followed the Migration Guide from TechNet, which worked out well enough. Unfortunately, the iPhone does not support Exchange 2010/2007 coexistence, which made it necessary for several people to manually reconfigure their phone.

Removing Exchange 2007 worked without issues, but after moving all the Exchange 2010 data back to the real hardware and removing the temporary server i ran into the issue of moving arbitration mailboxes, which fortunately was already documented widely on the web.

In the end, upgrading from Exchange 2007 to 2010 while keeping the same hardware is not difficult, it just needs a bit more time.

The error message in the IIS Log looks like this:

RdirTo:https%3a%2f%2flegacy.contoso.com%2fMicrosoft-Server-ActiveSync_LdapC2_LdapL15_Error:MisconfiguredDevice_Budget

I’m currently running Windows 7 Build 7100 x64 on my laptop, so i decided to uninstall Office 2007 and install Office 2010, the x64 version.

Unfortunately, the x64 version does not support running any x32 plugins. This is unfortunate, since one of the key features of our ERP package is a tight integration with Microsoft Office, which even i used from time to time. We call it the Office Solution Pack, which has been completely rewritten as a native .NET Office 2007 Plugin. The screenshot to the right is slightly outdated, but it clearly shows the integration we had.

I’m already pushing our developers for a x64 version of the plugin, but i suspect it will take a lot of time until all applications we are using (e.G. System i Access) are running on Office 2010 x64.

Also, its important to know that having 32bit plugins around after installing Office x64 will lead to several nasty error messages. You will need to uninstall the 32bit plugins before installing Office x64. Interestingly, the Primary Interop Assemblies come now shipped with Office by default. This alleviates installing them, streamlining the plugin installation process.

This also means that Office 2010 x64 will be a very niche product, and most people will opt to deploy the 32bit version. This isn’t bad – now that an x64 version is around, plugin developers can start adopting and we may see larger deployments of Office 2010.Next x64.

I’m now running my productive mailbox against Office 2010. Yep, might be risky, but it also gives me a very easy way to learn a new product before we’re actually pushing it to customers. I’ve found that i’ve never learned all that well in a separate environment.

So, whats new in Office 2010? Well, the only application i use daily is Outlook. And we will see how it plays out. Outlook 2010 now also comes with the new ribbon interface, and so far i like it. We will see how this plays out.

But today i experienced the most grave issue with their equipment that critically impacted a customers business.

The customer has two sites – an HQ with an SBS 2008 and a branch office with two Lenovo SFF machines running Windows Vista Business. Both sites are using 20/2 VDSL lines from Swisscom, with ZyXEL P-2802HWL routers.

There is an IPsec VPN configured between these two sites. This has been working fine since January.

Now, about a month ago a telecom service company installed VoIP telephones in the branch office, and enabled QoS on both ZyXEL routers.

Since then, Outlook was unable to synchronize correctly with the SBS server. Unfortunately, the customers personnel isn’t that technically savy, so they weren’t able to tell that they had a problem – because smaller e-mails were able to successfully synchronize, but larger ones failed. This led to very inconsistent states of the OST files, with some mails there and some mails not there.

When i arrived at the branch office i didn’t have a single clue what the issue was or may be. At first i suspected an Outlook problem, so i deleted the OST file. But from there on, nothing happened – Outlook wasn’t able to download anything.

Next, i tried to copy a 50kbyte Excel file from a share to the local computer. This worked. So i tried a 2 megabyte Word file. This failed about halfway through, with Explorer just hanging there and doing nothing. From that point on, i suspected a network issue, but the fact that copying a 50kbyte file worked and a 2 megabyte file didn’t was very odd.

Using Outlook with Outlook Anywhere also worked (when the VPN tunnel was downed).

Whenever i’m confronted with strange network problems, i suspect MTU issues (which was my first “real” network problem i solved back on my first ADSL line – took me weeks for a simple fix). ping -l 5000 CUSTSBS01 worked. ping -l 15000 CUSTSBS01 worked, too. So thought it wasn’t an MTU issue.

Disabling QoS on the ZyXEL router fixed the issue, but made the phones unusuable while Outlook was filling it’s OST files.

So i ran through the usual check points – tcp checksum offloading, chimney, receive window autotuning, reboots, etc. Nothing helped. At the end i was just changing network settings at will. But nothing helped.

Out of any reasonable ideas, i changed the MTU to 1300. That fixed it – with QoS enabled and the NIC MTU of the two machines, everything was working as it should. File transfers worked, Outlook worked, Phones worked.

Don’t buy ZyXEL.

• Intel Xeon 3065 2.33Ghz 4MB L2
• 512MB ECC RAM
• E200 SAS Controller (8 Ports, 128MB BBWC)
• 2x 160GB 7.2kRPM SATA Disks

For less than 400 CHF. As i needed a machine to run SBS2008 at home, and my current one wasn’t 64bit capable, this seemed like a good buy, especially because the E200 with BBWC alone is worth around 300 CHF.

Of course, i needed more RAM and disk space. I also ordered 4x 2GB memory modules (with ECC) from a third party memory manufacturer (Transcend) – priced at around 80 CHF each. I also ordered 4x Western Digital 1TB disks that are optimized for 24 hour use, priced at around 180 CHF.

This brought me to a total price of around 1500 CHF. I had two 160GB disks that i didn’t have any use for (except throwing them at people i don’t like).

1500 CHF is a lot of money for me, but for a company it’s nothing – still, this is ideal for experimentation. The free ESXi supports the E200 SAS controller, making it easy to build a test lab based on VMware – also, Windows Server 2008 x64 and Hyper-V also run flawlessly on the machine.

The machine is also very quiet, making it possible to use it in a normal appartment or in your office.

You get what you pay for still applies – the machine has no remote management features, only a single network port, forcing you to use the same port for management and virtual machine traffic, which can be acceptable in a test environment. HP’s System Insight Manager is not supported on this machine, either.

The case is very small, resembling a normal HP client minitower. The mainboard supports ECC memory, which is becoming more and more important with todays memory sizes. Unfortunately, it only offers four memory slots with a maximum capacity of 2GB per stick, maxing the machine out at only 8GB of RAM.

The integrated E200 SAS RAID Controller has a 128MB BBWC card, that allows it to use it as a write cache, and enables licensing to use RAID5. In my case, i used RAID10. The disk performance is better than anticipated, even though i’m using slow consumer drives, the performance for running VMs is acceptable.

The machine has three x8 PCI-E slots and a single PCI slot. One of the x8 slots is used by the E200 controller.

This offer is still available under HP Part# 470064-639, and there are still some companies that are selling it for the lower promotion price.

I’m currently running SBS2008 directly on the hardware, with not virtualization in-between. The performance is good, but i’d still never use such a setup for a production deployment at a customer – the management options, hardware flexibility, redundancy etc. just aren’t fit for production.

Update: I was asked about Linux compatibility on this machine. See the official HP Linux compatibility list. The E200 SAS RAID Controller is supported by the cciss driver, which is in the vanilla linux kernel. So most distributions will be able to install on this box – support is another matter, though.

There is no easy way to get official support for non-corporate versions of Linux, like Ubuntu. My usual way in those scenarios is to run Linux as a VM under ESXi, but that doesn’t work with the ML110 as ESXi is not supported (but works).

For those of you who do not know SBS: SBS has traditionally been a single server setup with Exchange, SQL Server and ISA Server. It consolidates all “big” Microsoft technologies on a single server. This contradicts most “Best Practices” published by Microsoft, and as such SBS has always been seen as the red-headed stepchild in the Windows Server Family. SBS 2008 aims to improve several of these points (especially with the Premium Edition shipping with TWO server licenses).

After a 6 hour downloaded that trickled in at a few meager 200kbyte/s, i was finally able to get started with it.

SBS 2008 now demands x64 hardware – so for testing i used an IBM x3650 running Windows Server 2008 Enterprise with the Hyper-V RC1. Hyper-V supports 64bit guests. Other hardware requirements have also gotten steeper – you’ll need 4GB RAM minimum (though i launched the VM with only 2GB). The Premium Edition now comes with licenses for two servers – finally making it possible to have redundant domain controllers even in a Small Business setup without paying for full server licenses.

The first half of the setup is similar to what you know from Windows Server 2008 and Windows Vista – you boot, select the disk, have the chance to enter a product key, and finally start the installation. After that, the WIM image is expanded to the harddrive. The machine reboots after installation, and this is where things get different.

After booting, you’ll land in “Install Windows Small Business Server 2008″ Wizard. This can be mostly automated using an Answer file, which is mandatory when migrating from earlier versions. I will check that out later and proceed with a simple installation without using an Answer file.

I get nagged by a “Insufficient Hardware Screen”, reminding me that my (virtual) machine only has 2GB RAM. After acknowledging the warning, i can setup my date and time. I choose the CEST timezone, and move onwards.

Next, a screen confronts me with the fact that i don’t have a NIC – which is true. The machine is running on Hyper-V RC1, and i wasn’t able to install the integration components yet. Luckily, there is a “Browse” Button, where i can launch the Integration Services setup. Installation of the Integration Components worked fine, the machine rebooted. I hope Microsoft packs the Hyper-V RTM bits into SBS RTM. This would make it easier to install it into a VM, but as you can see, it’s not much of a hassle.

I was back at the beginning, at the start of the SBS Wizard. Luckily, i was now able to use the mouse after installing the Hyper-V IC. Next, i get an Update Dialog, asking me if i want to update my server. I choose yes and have to wait.

Next, i was asked to enter my company information. Next, i was able to name my server and the NETBIOS name of the Domain. I was not able to choose a DNS Name for the Domain (This is only possible if using an Answer File). Interestingly, Dashes “-” were not accepted as part of the server name. I wonder why – our production setup uses dashes extensively in server names, and so does Microsoft (judging from their Mail headers).

Then i was asked to create an an administrative account – a good idea. The “Administrator” account shouldn’t be used in a production setup, instead each user with administrative rights should have their own account. SBS enforces this – a very good idea.

After confirming Server name, Domain name and Company name, the installation continued on it’s own. This took a good amount of time, during which the server restarted several times – of course completely unattended. No need to play disc jockey or logon – much better than SBS 2003.

After the installation, i was greeted with a screen that told me that it was unable to install some critical updates. Clicking on that bar revealed an IE7 404. I checked the IP configuration – the server was configured to use 192.168.0.2, and didn’t have a DHCP server installed. There was no default gateway set yet.

Next, i launched the “Connect to the Internet Wizard” which told me that i was already running a DHCP server – which makes sense. After choosing “Postpone”, the Wizard aborted. That wasn’t quite what i was hoping for.

I shut down the VM and reconfigured it to use a private LAN. That way, it wouldn’t have a connection to the internet, but it wouldn’t have to deal with a DHCP Server either. But SBS didn’t like that either – it wanted a router. So i setup a second VM running IPcop (which works flawlessly on Hyper-V using Legacy NICs and a small virtual hard drive).

It was interesting to see using “tcpdump” what SBS did under the covers to detect the router. ARP scanning, IPv6 Discovery, Everything. This seems rather well designed. It was sucessfully able to detect my IPcop VM which didn’t have a DHCP server.

Next, i started the wizard to enable my domain name. It seems that SBS will be able to do some of these things automatically if you live in the US. Here of course we have to do things manually.

So far i don’t like that SBS tells me very very few technical details. But this might be because Microsoft somehow thinks that a Small Business Owner will setup SBS on their own (which just seems a horribly stupid design decision).

Next, it told me that i couldn’t configure my Internet Router properly (my IPcop instance didn’t have UPNP support enabled). It’s interesting to see that it wants to forward port 25 to the server. It looks like the POP3 Connector was finally killed off for good. That’s very good to hear! Unfortunately, it’s still there. Just hidden.

I also had to configure outbound email properly, with the ability to configure a smarthost or use direct sending. There is also a wizard to easily create a properly signed official SSL certificate – nicely done and will surely improve the security of the many SBS setups that are out there.

SBS 2008 also ships with OneCare for Servers already preinstalled. You can just activate it with a few clicks. I don’t see this very positively – I’ve made a few bad experiences with ForeFront Client Security, which OneCare is based on. We’ve been using McAfee for the past. So in the future for SBS setups we will have to either remove OneCare from the SBS, or deal with having multiple virus scanners on the network (a management nightmare).

Another interesting tidbit is that UAC is enabled in approval mode, just like on standard Windows Server 2008 installations when not using the Administrator account. This is annoying, IMHO. I don’t have a problem with UAC on my desktop because i usually use my desktop to work and not change settings – but when i’m logged onto a server, i want to change settings all the time.

That’s it for the first impressions. I will have a closer look at SBS 2008 over the following days and will keep you all updated.

Pictures are here:

Long story shorts: Modify the hosts file, remove the IPv6 localhost (::1) and then add hosts entries for your server. I would recommend against disabling IPv6 on the Exchange server, as this is probably not a recommended or supported configuration.

The root cause is that Outlook 2007 can’t contact a DC/Domain Controller using RPC over HTTP/Outlook Anywhere when used on Windows Server 2008.

Also note that NTLM Authentification for Outlook 2007/Outlook Anywhere is broken on Windows Server 2008.

After playing with it in VMs for a few days, I decided to deploy it internally. Of course, the current deployment is not very integrated – our PBX is years old, and we have no chance to get any decent sort of integration, and we’re not yet on Exchange 2007 (though this is planned). As such, I didn’t expect to much usefulness out of. Boy, was I wrong.

OCS 2007 is several products in one, and it has a few drawbacks in a small business deployment (because it was designed for bigger environments). The price of the product isn’t prohibitive for a small business – 1500 CHF for the server, and 100 CHF per CAL (for Standard versions – the Enterprise versions are more expensive).

So, what features can one expect from OCS2007?

Services

Instant Messaging

One of the OCS2007 functions is an internal Instant Messaging server, with all the standard features you probably already know from ICQ, MSN et al. This part could easily provided by using e.G. an internal Jabber server and a Windows Jabber client like Pidgin. So why use OCS2007 for instant messaging? The reason is easy: Integration. The server software integrates into your Active Directory environment. You extend the AD schema, and all the user information is stored directly in Active Directory, with no need to maintain yet another user database. While that’s an advantage, it not much of a selling point (because the CEO usually doesn’t care if need 3 more minutes to add a user).

So let’s talk about integration on the client. After installing Office Communicator (the IM/VOIP client for OCS) on the client, you will notice full IM integration into Outlook, see the status of all the recipients and senders of the mail. This is a very nice feature, because it offers you information at a glance, without having to open the IM GUI to see whether someone is available for a quick follow up or not. But it gets better: this Integration also works in Sharepoint Services 3.0 and MOSS 2007. Also, the Unified Messaging part of Exchange Server 2007 integrates nicely into OCS 2007. You can check your voicemail using OCS 2007, with a fully graphical interface (similar to how the iPhone handles it’s voicemail)

Besides the ability for instant messaging, there is another very important feature – at least in our company: availability and presence. We have a HQ and a branch office, and our HQ is split over three floors. So usually it’s not easy to tell if someone is at his workplace or not. While Outlooks calender helps to establish the general whereabouts of a person, its not at-a-glance, and it doesn’t help if the person just isn’t at his desk (for whatever reason).

Office Communicator sets your presence to away at the instant you lock your machine, which people do when they walk away from their desk. As such, you can tell whether someone is currently working at his desk or not. This is very cool, and helps to save time on unnecessary phone calls to which no one answers.

There’s also a web client – Office Communicator Web Access. At the first glance, it is indistinguishable from the full desktop client, so the web interface is very nicely done.

Voice over IP (SIP)

OCS 2007 is also a fully blown VoIP solution. I can’t talk about this part too much – i haven’t worked with the mediation server or more enterprise VoIP integration (as said, our PBX doesn’t support that).

The Softphone client, integrated into the Office Communicator works nicely though, the voice quality is normal, and we didn’t have much problems using it over WAN lines.

You can also connect hardware IP phones to OCS2007, which should work with standard SIP phones – not having one, i didn’t test this. There are some very nice looking OCS specific IP phones out there.

Live Meeting

I’ve attended a few Webcasts done using Live Meeting 2005. With OCS 2007, you can now host Live Meetings (using the 2007 client) directly in your company, with no need for any hosted services. This feature might not be terribly useful if you’re working for a single-location Small Business, but it can be a timesaver when spread across the country (or world). Live Meeting also integrates into Outlook (see the above screenshot).

It works flawlessly, and i had few problems using Live Meeting. Didn’t really deploy this into production yet, though.

And more

OCS 2007 can also do a lot more stuff than i mentioned here. Most of this, like CDR and Archival is not necessary (or financially viable) in Small Businesses, so I didn’t invest too much time.

Drawbacks

So, what are the drawbacks of OCS 2007 in a Small Business? The main point i see here is that you need at least three servers – a Standard Server (hosting all the services), a mediation server for connecting to your PBX, and an Edge server offering internet connectivity. These are at least three OS instances that need to be maintained. Add to that the cost of either a proper virtualization server, or a few 1U boxes, and you’ll get into unviable price regions pretty soon.

For basic functionality, you can leave both the Mediation and the Edge server away. This means no integration with your PBX, and no external access to your server – at least in theory.

If you just need external access to IM, you can create appropriate SRV records in your public DNS, and forward port 5061. This will not result in a clean service, but it’s better than nothing. But without a proper edge server, you won’t be able to access other IM networks. Not cool.

Microsoft should really make single-server deployment possible, but probably we’re too small of a market to make this financially viable.

So what’s my conclusion? If you’re an SMB, give OCS2007 a try. It’s a very cool software, and the basic IM functionality isn’t that expensive.

A small business customer was running an Exchange 2003 server behind a ZyXEL ZyWALL 5 with AntiSpam installed and enabled. The ZyWALL forwarded port 25 to the Exchange server. This worked, for the most, flawlessly. But a few hosts (i’ve found no distinct differences between the source hosts – ADSL, Leased Lines, Colocated, Europe, USA) failed to get an SMTP greeting (220 customer.example.com Microsoft ESMTP MAIL Service, Version: 6.0.xx ready at Thu, xx Sep 2007 xx:xx:xx +0200).

When i disabled the Anti-Spam and pressed enter (in a telnet session to port 25), the SMTP greeting appeared. If anti-spam was enabled, it never appeared. But that didn’t help – Postfix still couldn’t send mails:

postfix/smtp[25010]: C65AA88075: conversation with customer.example.com[256.256.256.256] timed out while receiving the initial server greeting

I’ve looked at every setting on both the ZyWALL and the Exchange server, but didn’t find any unusual DNS etc. setting. I even disabled all the DNS lookups done on the Exchange server, but to no avail.

But after upgrading the ZyXEL ZyWALL 5′s firmware to the latest version (V4.02(XD.2)), the problem disappeared. While this wasn’t exactly what i was hoping for, at least the problem was now solved.

Source: MSExchangeSA
Event ID: 9188

Microsoft Exchange System Attendant failed to read the membership of group ‘cn=Exchange Domain Servers,cn=Users,dc=your domain’. Error code ’80072030′.

Please check whether the local computer is a member of the group. If it is not, stop all the Microsoft Exchange services, add the local computer into the group manually and restart all the services.

This error message sounds very serious, but it is entirely possible that the situation is not as grave as it sounds.

If you encountered this error message, you should first read all the hints over at EventID.Net. This shows the most common causes for this problem in bigger environments.

I’ve encountered this error message in smaller environments if specific factors were true: DC and Exchange were on seperate servers, and the Exchange wasn’t a DC (which is correct). However, there is only one DC on the network. In this case, the error message above might appear immediately after you restarted the first DC.

This seems to be a minor problem in Exchange which doesn’t fully recognize that the DC is back up. Restarting the Microsoft Exchange System Attendant service will solve the problem. This is not really a full solution to the problem, as you have to restart the System Attendant service everytime you restart the only domain controller.

The right way to fix this is to install a second domain controller. If you can’t do that, scripting the System Attendant restart makes sense – my approach would be srvany.exe and a plain cmd script. I didn’t write such a script yet, and i don’t really intend to do. Just buy a second DC.

In the end, the choice fell on the HTC TOUCH. It runs Windows Mobile 6 Professional (aka “PDA Phone Edition”), this means it uses the PDA UI, not the SmartPhone UI.

The packaging provided by HTC was very nice, in a sleek black box that comes with everything you need. A USB cable with the usual mini-USB connector (no idea on how this thing is really called), stereo headphones, a 1GB Mini-SD card and a USB charger cable.

Again, setting up the device was a breeze, it automatically configured the necessary GPRS settings. After downloading our self-signed certificate and installing it, the Phone already synced against the Exchange server. No need to plug it into any computer. (Many WM5 modems back in the days required a variety of registry hacks in order to import new trusted certificates – it’s very good to see that this has changed).

I’ve also installed version of Windows Mobile Device Center on the laptop, in order to sync files and notes (You can’t sync Outlook notes over the air, i’d like to see the design decision behind this one). WMDC works fine and integrates completely into the OS. While the ActiveSync desktop software under Windows XP was mostly troublefree when used with Exchange ActiveSync, the WMDC software works even better.

Back to the device itself. The HTC Touch is often touted as an iPhone competitor, but it’s not. They play in whole different areas. The iPhone is a consumer device – it does not offer Enterprise Messaging features like a Blackberry Connectivity Software or Exchange Active Sync. The HTC Touch is meant for professionals which need the ability to synchronize with an enterprise messaging system over-the-air, including contacts, calender, etc.

The HTC Touch has a 2.8″ 320×240 screen. The resolution is acceptable, but i would’ve preferred 640×480 pixels at the same screen size. (I really liked the 2″ 240×320 screen on my HTC MTeoR). The device is much, much smaller than it appears on photos. It’s also much thinner – in fact, it’s the first Windows Mobile device that doesn’t look like a Windows Mobile device (which can usually be described as “bulky”. As such, i think the HTC Touch is very important for the Windows Mobile marketplace.

The Touch has an alternative shell called TouchFLO – it’s a homescreen replacement with support for a few gestures, a program launcher, and a music player. The TouchFLO functionality is nice to use, but it is not a full Windows Mobile touchscreen conversion. As such, the functionality is very, very limited. There’s a standard pen located in the phone’s corner, like with every other PDA. You’ll need this to use much of the functionality. You can place calls with just the touchscreen alone, and the touchscreen seems to implemented very well. It even works beyond the edges of integrated 320×240 screen, which makes using your finger to point at things on the side much, much easier.

There’s an included ZIP-Software and Adobe Reader LE is preinstalled, and there is not much “vendor crap” as i’ve seen on operator branded HTC devices. As such, i see little reason not to recommend this device – the build is very nice, the screen and other hardware components also work as they should. They only points that could be criticized are the screen resolution (which is “normal PDA” resolution instead of “hires PDA”), and the missing UMTS support which only plays a role when surfing the Web or connecting to the Web with a laptop. For EAS purposes, EDGE is enough.

In my opinion, the HTC TOUCH is a very cool Windows Mobile 6 device, thats shows a lot of the progress needed in this sector. Together with the Motorola Q9h (Review from a co-worker), i would vote these two to be the two best available Windows Mobile 6 devices on the market. The TOUCH is better if you want a full fledged PDA with a touchscreen, while the Q9h is a true Smartphone with a full keyboard.

I noticed this on Saturday, and booked a testing appointment for today. I arrived almost late at the testing center, because a customer appointment took longer than i thought (that’ll teach me to book exams in the afternoon). Another bonus was that it is quite hot today (32C according to my car), and the A/C in the testing center has failed or was overloaded – in fact, it was almost cooler outside the building. I was offered to move my testing appointment, but i didn’t want to.

70-237 was easy as pie, and mostly theoretical questions on “how should you do this”. 70-236 required you to learn vast PowerShell commands to be able to pick the right one from the answers given.

70-238 was completely different, and much more technical than 70-237. A very large focus were backup, backup windows, recovery methodologies, migrations from older Exchange versions, migrations from/to clustered mailbox servers, and lots of questions about journalling, mailbox and transport rules, and Send and Receive connectors. Most of the questions focused on where you have to set rules, i.E. Hub or Edge server. This is usually pretty easy, but there were a few cases where the solution wasn’t obvious.

A bit of material was the same as in 70-237 (not word for word, but in the type of questions) – focusing on which rules you need for what. A few other questions centered around Active Directory, and the requirements Exchange has for it.

There were also questions which i found completely irrelevant – at least 3 questions focused on MOM and what you should do to configure it with Exchange. I never used MOM, so i used all my guessing skills.

In the end a passed with around 850 points, i expected much worse than that. I didn’t even have bars that we’re below the (imaginary) 80% margin, even though i don’t think i understood all the Journalling/Transport/Managed folder stuff completely.

So now i should be a MCITP: Microsoft Exchange 2007 Messaging Solutions Administrator, as long as Microsoft doesn’t have the same troubles they had with the MCSA and 70-620.

Update: Updating the transcript wasn’t a problem this time, the credentials were visible a day after i passed this exam.

I didn’t spend too much time preparing for this one, mostly because i wasn’t able to find many referneces on the web related to this exam. This is also why i decided to write this post.

While the 70-236 exam was clearly focused on the technology itself, with many EMS and EMC questions, this exam tested the other half you need to know.

Basically, what Microsoft shuffled into on Exam in the Windows Server 2003 series (70-290, et. al.) is now split into two or more exams – one focused on the handling the technology in detail, and others handling the planning and limitations of the product. This is already explained on the New Generation of Microsoft Certificates page, it’s amazing how this worked out in practice. I really do like this approach, as it makes it easier to prepare for an exam.

I found the 70-237 way easier than the technical exam 70-236, mostly owed to the fact that when knowing all the base rules of Exchange 2007 deployment, you will have a lot of questions in 70-237 covered. But other topics also get their share, like Message Management, Auditing, Archival. None of them to deep. I even got a single question about Unified Messaging, which was not the case in the previous exam.

I honestly didn’t really learn for this exam – i’ve read How to Cheat at Configuring Exchange Server 2007 about a month earlier, but didn’t do anything else.

Now i’ll have to wait till 70-238 is out to complete my Exchange 2007 certification.

Luckily, Microsoft already knows what you have to do:
How to remove and to reinstall IIS on a computer that is running Exchange Server.

As usual, Microsoft KB entries aren’t very reassuring when it comes to “what data will i loose when i do this”. Don’t be concerned, reinstalling Exchange will not hurt your data in any way, if you follow the manual to the letter.

So far i’m through the first three chapters, and i think it’s pretty good so far. I’ve setup a few Exchange 2007 testing environments before, but i never did anything serious with it.

The problem is a bug in Exchange 2003 – there is even a hotfix available in KB930807. However, this Hotfix is not publicly downloadable. You will need to contact Microsoft PSS, in order to get the Hotfix.

And here is where it gets interesting. If you’re running a native language version of your Microsoft Software, Support is only available by phone, for the small sum of 450 US$ – this fee is usually waived though if you just request a hotfix. For original US-English language software, support is also available by E-Mail, for much more reasonable 150 US$.

I’ve tried requesting the Hotfix by E-Mail, and it worked fine (though they referred me to the Phone Support option). It worked fine, and Microsoft provided me with the appropriate Hotfix.

The good thing is, that these problems will be mostly over because both Vista and Longhorn Server are true multilanguage Operating Systems.

However, some users reported that not all deleted items were visible in the “Recover deleted items” dialog. The reason for this was that they didn’t just delete the file, but instead used shift-delete to delete the file immediately, skipping the recycle bin.

In this case, the deleted item is not visible through selecting the recycle bin, and then “Recover deleted items”. Instead, you must select the Inbox, and then the “Recover deleted items” option. This is not as obvious as it should be.

In general, i enjoyed this first part of the event. As always, the Kongresshaus has severe logistical problems, they don’t have enough parking space. Microsoft offered free parking at Albisgüetli, but that is about 15 minutes away.

So instead i choose to go early, and parked right next to the Kongresshaus – arrived at 08:15, and there was still plenty of parking space available. At 27.- CHF for the entire day, it didn’t come cheap, though.

Microsoft seems to have moved back from stickers to lanyards, and there were croissons available in the morning.

The Keynote was very good, held by a guy named Rafal Lukawiecki. A review on security in the past, and in the future. Very interesting, and very well done.

The next on the list was about Windows Sharepoint Services, but aimed at developers (which i didn’t really pay attention too, when choosing). Even though i’m not a developer, it was very interesting to see the architecture behind WSS.

I then attended a talk about Exchange HA & Disaster Recovery – i enjoyed this one too, but i think the title was a bit misleading, it concentrated on backups and reasons for disasters.

It was interesting to hear that he saw incorrectly configured anti virus software as the main reason for exchange full restore – i couldn’t really believe this, because it didn’t look like this guy worked with Small Businesses. He even wrote an Article about this topic on msexchange.org. While listening, i enjoyed that it seems i did everything right in the setups i did in the past, which was very reassuring.

Next was something about Windows Storage Server, or file serving from windows in general. It was very well, with a very competent speaker. It was also interesting to see that Microsoft is entering the Backup Market with DPM – at competitive prices, even though DPM requires a seperate server, which is a bit of a letdown. DFS/DFS-R was also covered very well, though there wasn’t anything there new to me.

What i wondered was that it seems that even though most people attending TechDays aren’t exacly working in SMBs didn’t know much about DFS. I assumed that most bigger companies were already using this.

At that point, i called it a day and went home. Stay tuned for the next part.

However, one user was unable to send mail to the new users. It generated a bounce/NDA, and failed to deliver. I first checked the Exchange Server, and everything seemed to be perfect. I then walked this user through the procedure of selecting the user from the address book, and then sending the mail. This worked.

At first, i was baffled, but then i remembered about the external contacts – the external contacts where defined as X.400 addresses, which coexisted with the new users for a short while. so the external contacts had different X.400 addresses than the new users. (I did handle the SMTP Addresses correctly, but not the X.400 ones).

But the external contacts where deleted, and no longer in the GAL or the OAB. But Outlooks address cache for type-ahead finding of contacts is independent of these two address sources. And that’s what the user used. You can delete entries in this cache by selecting them with the cursor keys, and then pressing the delete key. Seems logical, but i haven’t seen this mentioned anywhere explicitly.

In this case, the user running Outlook 2003 was connected to the exchange server through a WAN link, and has just imported a rather large .pst file, which was being uploaded to the Exchange server.

At that point, i tried to configure Active Sync on the PDA (through a GPRS connection), but it just hung while retrieving the folder list. An Event from Source “Server ActiveSync” and ID 3005 was logged on the Exchange-Server. At first, i thought the device (running PocketPC 3.0) had issues with the Exchange server, but that wasn’t the case. When i quit Outlook (and it stopped uploading from the local store to the server), everything was fine.

I waited until Outlook finished uploading, and from that point on Active Sync didn’t have any issues.

It seems that Active Sync doesn’t work when the Exchange Server is receiving files from a client.