RSS Subscription 168 Posts and 2,769 Comments

Archive for October, 2007

Microsoft Exchange Server 2007 Management Pack for Operations Manager 2007

Management Pack Download:
http://www.microsoft.com/downloads/details.aspx?familyid=1a83e112-8677-4e03-83c3-f

Release Notes Download:
http://www.microsoft.com/downloads/details.aspx?FamilyId=62F22988-B326-4112-A5A

Requires Backward Compatibility Version 6.0.5000.16 (or above):
http://www.microsoft.com/downloads/info.aspx?na=90&p=&SrcDisplayLang=en&Src

Share

ADaccess errors causing Exchange services to fail

Previously, I was at a client to deploy Exchange 2007 . After having everything configured flawlessly, we shut down Exchange 2007, and brought it to the co-location office nearby. When we started it up, it took a couple hours for it to come up and we saw services were stuck in a failing state. The odd thing, is this server had a direct private link directly to where we configured the server, and the server was still on the same subnet but had a firewall in between the locations. At first, I thought the issue might be a firewall issue, but it was not.

So lots of troubleshooting ensued which involved checking ports, checking connectivity, and several other things. The painful thing, was that we had to reboot the server many times to test and wait for it to finally time out and allow us to log in. This client had four domain controllers, two of which were Windows 2000 Server and two of which were Windows Server 2003 SP1.

The first thing I did was use the following command to ensure ADAccess was using only the two available Server 2003 SP1 Domain Controllers:

Set-ExchangeServer -identity Exch01 -DomainController dc01.domain.com -StaticDomainControllers ‘dc01.domain.com’, ‘dc02.domain.com’ -StaticGlobalCatalogs ‘dc01.domain.com’, dc02.domain.com’ -StaticConfigDomainController ‘dc01.domain.com’, ‘dc02.domain.com’

Note: If you need to reverse this, you can run the following command:

Set-ExchangeServer -identity Exch01 -staticDomainControllers $NULL -staticGlobalCatalogs $NULL -staticConfigDomainController $NULL

To be quite honest, the command above should not be needed and I recommend against it since the Topology service should automatically find SP1 Domain Controllers and use those Domain Controller’s accordingly after Exchange 2007 is installed.  You should ensure that your Active Directory Sites and Subnets are all properly defined.  Exchange 2007’s Topology service will choose the appropriate DC/GC to use for ADAccess.

As a side note, for the installation of Exchange 2007, the installer is not intelligent enough to find Server 2003 SP1 Domain Controllers, so you will need to use the command prompt to install Exchange 2007 so you can specify a Server 2003 SP1 Domain Controller. With Exchange 2007 SP1 (which contains the install binaries on it), the installer has been revised to automatically use a Server 2003 SP1 Domain Controller in a mixed environment if you’re using the GUI.

So the next step I did, was researching. I found some information to check whether the Exchange Servers group had the ability to “Manage auditing and security log” in the Default Domain Controllers Policy. The Exchange Servers group was NOT in this policy. I added the Exchange Servers group to this group policy setting, waited 5 minutes for the Domain Controllers to apply the new policy (gpupdate /force if you’re impatient), and then I decided to reboot Exchange 2007.

During the reboot, I prayed that Exchange 2007 would come back up normally instead of the usual 2 hour wait. Fortunately, Exchange 2007 did come up as if it never had problems. I checked services.msc to ensure that all services were working as intended; and fortunately, they were. We went ahead and checked Outlook Web Access, SMTP, POP3S, IMAP4S, etc.. Everything worked! To be safe, I rebooted Exchange 2007 again to ensure it would come back up normally, which it did.

Share

.Net Framework 2.0 Update for Exchange 2007

Microsoft has released an update to their .Net 2.0 Framework. Microsoft highly recommends to apply this to all Exchange 2007 Servers, especially your Client Access Servers with multiple protocols. This update will be included in .Net Framework 2.0 SP1. Currently, there is no ETA as to when .Net Framework 2.0 SP1 is coming out.

More Information:
http://support.microsoft.com/kb/942027/
http://blogs.technet.com/scottschnoll/archive/2007/10/04/net-framework-2-0-update-recommended-for-exchange

Download:
https://connect.microsoft.com/content/content.aspx?ContentID=3705&wa=wsignin1.0&siteid=210

Share

Certifying in Windows Server 2008

For those who are planning to go after their Windows Server 2008 certification, here is some new information you might deem worthy to check out:

Windows Server 2008 Step-by-Step Guides

Live Meeting: Transition to Windows Server 2008 Certifications

Previously, I blogged about a free beta exam for upgrading to Server 2008 which included help guides, blog sites, and screen casts that would help you prepare for the Windows Server 2008 exam. While the beta exam period is over, the help guides, blog sites, and screen casts still exist which will also assist you in your preparation. You can view my previous blog entry here.

Share

Scan to e-mail not working on your printer?

So, I was at a client today and they had issues with their printer’s scan to e-mail functionality not working properly with Exchange 2003. It’s a pretty simple fix really: Just go to the relay configuration and allow that printer and/or print server (depending on configuration) to relay to the Exchange 2003 server. The reason is, your printer is not joined to the domain and the print server you are using may not be joined to the domain. Because of this, Exchange won’t allow that printer to scan to e-mail. Just add the ip to the allowed list of your relay configuration, and it will begin functioning right away.

Share

« Prev