Thursday, December 11, 2008

How long does it take for an Exchange 2007 Transport rule to re-check a group membership?

Exchange 2007 Transport rules are a GREAT feature to control mail flow for business and security reasons. One of my favorite uses is to base a rule on group membership. Unfortunately, the first time I tested this, I was making a rule to block Internet Email from members of the "No Internet Email" group. I created the group, added myself, and created the rule.


It worked flawlessly, and I then removed myself from the group. Then I tested again and found I still got a bounce error from the rule firing.


I found out (quickly) that restarting the transport service fixed this, but I never did find the reason why this was occurring.


Then I found this article that explains it all:

http://technet.microsoft.com/en-us/library/bb124703.aspx

"Each Hub Transport server maintains a recipient cache that is used to look up recipient and distribution list information. The recipient cache reduces the number of requests that each Hub Transport server must make to an Active Directory domain controller. The recipient cache updates every four hours. You can't modify the recipient cache update interval. Therefore, changes to transport rule recipients, such as the addition or removal of distribution list members, may not be applied to transport rules until the recipient cache is updated. To force an immediate update of the recipient cache, you must stop and start the Microsoft Exchange Transport service. You must do this for each Hub Transport server where you want to forcibly update the recipient cache."


So in short, testing can be unpredictable because once the transport rule fires on a DL membership rule, it caches that membership for 4 hours.


Saturday, December 06, 2008

Hyper-V - Code 12 on Virtual Machine Bus and Integration Tools not working

Stumbled upon this and found the fix here:

http://blogs.technet.com/jhoward/archive/2008/02/29/vmbus-fails-to-load-device-cannot-find-enough-free-resources-code-12-on-a-windows-server-2008-x86-virtual-machine-under-hyper-v.aspx


(2/29? Yea, so this is OLD news, but a nice fix either way!)


Was getting this error:












Tada!

Monday, December 01, 2008


Performing an Exchange 2007 mailbox restore using Backup Exec 12.5

  1. Create the recovery storage group using the Exchange Management Console's toolbox. Confirm you will have enough disk space to do the restore to the drives it chooses!
  2. If you run the "restore wizard" in Backup Exec 12.5, it doesn't prompt for redirection options. However, Exchange 2007 by default will find and use a RSG for you. If there is not an RSG, the job will fail.
  3. I used the non wizard in the screenshots below to create a Restore job, selecting the Exchange Storage group and Database to be restored, and choose the RSG redirection as well as unchecking the "commit after restore" (the restore will work either way, I just like manually mounting stores) Remember, you do NOT need to restore all databases, only the one you want data from!




  4. Mount your RSG database



  5. Launch the Exchange Recovery Toolbox again, and it's now time to "Merge or copy contents"


  6. Here is where I found a very ODD issue. As you can see above, the DMNotify mailbox is in the High limit store, and this is the one I restored from. However, When I go to merge data, the Staff and High limit DB's are flip flopped. So even though Backup Exec 12.5 restored the data, when I go to mount the databases, the high limit is 2gb (empty) and the staff is 17GB (the size of my data restored)




  7. However, I was still able to merge the mailbox I wanted out by choosing the Staff DB





  8. Mail data was all successfully restored!









Sunday, November 30, 2008

Exchange 2007 OWA redirect configuration using URL Rewrite

This is a quick write up on how to configure your Windows 2008 x64 IIS server on how to rewrite URL's so users can easily get to their HTTPS based OWA without entering the entire URL including https://...


  • First, download and install URL rewrite for x64 here http://www.iis.net/extensions/URLRewrite, This will require a reboot.
  • Second, by default "force SSL is ENABLED on an Exchange server. Open the SSL settings on your default site and disable the HTTPS requirement, as this rule will force it.
  • Go into IIS manager and open URL rewrite:


  • Create a new Blank rule


  • You will be recreating these two rules:

  • Force HTTPS Rule and Conditions:


  • Redirect Root Rule Action:


  • Now, http://machine/ and http://machine/owa and https://machine/ all redirect to https://machine/owa making the end user a happy camper who can't goof up the URL!




Tuesday, November 04, 2008

Live Meeting and Live Meeting Outlook Add in URL's for download.

LM: http://r.office.microsoft.com/r/rlidOCS?clid=1033&p1=LiveMeeting
Addin: http://office.microsoft.com/en-us/help/HA102368901033.aspx

These URL's are PAINFULLY hard to find. Go ahead and google "live meeting 2007 download"

File Under: OCS, communicator, livemeeting
How to publish your OCS 2007 address book externally without using ISA 2006 reverse proxying for external group expansion.

After much back and forth about Microsoft's requirement for ISA 2006 and reverse proxy for the address book publishing, I decided to try to find an alternate way.

Of course, per the OCS deployment guidelines, reverse proxy with ISA 2006 is the recommended solution, because you are not allowing direct access to the HTTPS server on your internal front end server.

Here's how to do it using a regular NAT translation and opening 443 to your front end server.

  1. Change your group expansion URL using wbemtest (from here and here)
  2. Configure an external DNS name, a NAT translation to your OCS Front End, and allow TCP/443 inbound. I used ocsab.domainname.com as a convention for the name.
  3. Request a new FE certificate using the OCS certificate wizard that includes existing names + ocsab.domainname.com. If you are only supporting Access Edge Remote connectivity from domain based PC's, you can still use your internal Enterprise PKI. If you want to support non domain workstations, you have two choices, have them install your internal SSL chain locally, or send this cert request to a third party trusted Certificate Authority.
  4. Install the certificate and assign it in OCS. After doing this, you will likely need to restart your OCS services.
  5. Finally, in IIS Manager, you will need to select this new certificate as the certificate to be used for the Default Web Site. This is a critical step, as the OCS certificate wizard does NOT seem to change this for you.

Enjoy having External group expansion while sticking to your guns on your choice of firewall vendor.