November 26, 2008
When installing Exchange Server 2007 as a regular old standalone product, opening the Exchange Management console for the first time presents you with this gem of a task list…

There’s quite a bit of stuff on that Finalize Deployment list, some of which is required to actually get your deployment to a point where it can be considered complete AKA functional. Obviously, some of that depends upon the features you want to use. Here’s a TechNet article that talks about these critical post-installation tasks.
You see the same list in Essential Business Server when you open Exchange Management Console. But nearly every item on that list is already handled for you, thanks to the magical world created by Essential Business Server’s Integrated Installation wizards.
In particular, you don’t have to fret about that first item. So don’t waste any of your valuable time looking for an Exchange Server license key to enter. Just like the Prego spaghetti sauce ads say…it’s in there!
|| posted by chris under essential business server, it pro || comments (1) ||
||
November 25, 2008
If you’re trying to book either the EBS 2008 or SBS 2008 exam and get a bit confused when looking at the Prometric registration site, don’t feel bad. Here’s what you’ll see right now:

Word of advice: I always go by exam number, rather than titles, when I’m booking my exams.
Notice how 70–653 and 70–654 both show with the title TS: Windows Essential Business Server 2008, Configuring. Oh yeah…that’s not confusing AT ALL.
Here’s Microsoft Learning’s officially official listing for 70–653:

Note the correct title of TS: Windows Small Business Server 2008, Configuring for 70–653 here.
And here’s Microsoft Learning’s officially official listing for 70–654:

So yes, Virginia…there is a real exam for EBS 2008. And one for SBS 2008 as well.
I’m sure the PTBs will get this fixed ASAP. But if you want to book an exam now, then just remember this…
And good luck on your test!
|| posted by chris under essential business server, it pro || comments (2) ||
||
November 23, 2008
As every good admin knows, a healthy DNS infrastructure is the second most-important aspect of a reliable network. Based on my own experience in the field, DNS has to be the least understood, and most commonly misconfigured service, on any given network.
And if DNS is wrong, then that network will have problems. No argument about that.

Since the configuration of EBS is based on the best practices recommended by Microsoft, it stands to reason then that the way EBS configures DNS is a good model, right?
Here are the DNS settings for the internal network adapter of each of the core EBS servers…
- Management Server (DNS server, domain controller, PDC emulator)
- DNS1 = 127.0.0.1 (localhost)
- Messaging Server (DNS server, domain controller)
- DNS1 = IP address of Management Server
- DNS2 = IP address of Messaging Server
- DNS3 = 127.0.0.1 (localhost)
- Security Server (Edge security)
- DNS1 = IP address of Management Server
- DNS2 = IP address of Messaging Server
Yes, the Security Server also has an external adapter. But there shouldn’t be any DNS servers defined on that adapter, since that would kinda defeat the whole purpose of even having a Security Server.
The Management and Messaging servers should be the only ones handling DNS queries in an EBS network. If something isn’t located in their databases, then they should also be the only machines going out and getting the info from the big bad world, using either root hints or forwarders.
Speaking of forwarders, OpenDNS pretty much rocks.
In a semi-related story, anyone able to tell me the most important aspect of a reliable network?
|| posted by chris under essential business server, it pro, rx || comments (4) ||
||
November 19, 2008

Thanks to the efforts of Mark “Mr. Roboto” Stanfill, the official Essential Business Server blog just posted arguably its best article to date.
http://blogs.technet.com/essentialbusinessserver/archive/2008/11/18/how-to-change-the-sce-run-as-and-data-warehouse-accounts-in-ebs.aspx
Changing the service account SCE uses from the default of Administrator is prolly one of the first steps that should be taken with every new EBS installation. Mainly because doing that totally avoids the whole “Holy crap my Administrator password was changed and now SCE doesn’t gather data anymore” issue, plus offers a couple of other handy benefits to boot.
I won’t rehash the whole article, but here’s a quick overview of the steps…
- Create new service account for SCE
- Assign new service account using SCE
- Create new SQL account for SCE instance
- Assign new SQL account using SQL Management Studio Express
- Restart SQL and SCE services
Trust me…it’s way more involved than that overview might make you think.You’lll want to get the full-on details before you start.
And just like any other major service or data storage change you make post-installation on EBS, completing a replacement mode install will revert the services back to using the Administrator account.
|| posted by chris under essential business server, it pro, migration, rx || comments (0) ||
||
November 6, 2008

Microsoft just released an official deployment guide for implementing Windows Mobile 6 devices in an Essential Business Server 2008 environment.
Download details: Windows EBS2008 w/WM6 Deployment Guide:
http://www.microsoft.com/downloads/details.aspx?familyid=69d1b397-86fc-46ed-afb3-b2882d324650&displaylang=en&tm
This document provides step-by-step instructions for deploying devices powered with Windows Mobile® 6 in an IT infrastructure that is based on the Windows® Essential Business Server 2008 (Windows EBS 2008) server solution.
Some errors and omission I noticed in the document…
- The only method for issuing a remote wipe command covered in the document is through the Exchange Management Console on the Messaging Server. Remote wipe of a user’s device can also be initiated by that user in Outlook Web Access.
- Certain advanced device security policy options require Enterprise CALs for Exchange. Basically anything located on either the Device or Advanced tabs of a Mailbox Policy require an Enterprise CAL. Also, these advanced options are only supported by devices running Windows Mobile 6.1, not 6.0.
- The screenshot on page 36 is from an SBS box (look at the title bar).
|| posted by chris under essential business server, it pro, mobility || comments (0) ||
||