BlackBerry Enterprise Server Resource Kit

Extra tools for managing your BES server.

Link

Importing n2k file in Outlook 2010

Link

Video Conferencing Equipment

Link

Importing certificates from IE8

How to make IE8 trust a self-signed certificate in 20 steps.

1. Browse to the site whose certificate you want to trust.
2. When told "There is a problem with this website's security certificate.", choose "Continue to this website (not recommended)."
3. Select Tools->Internet Options.
4. Select Security->Trusted sites->Sites.
5. Confirm the URL matches, and click "Add" then "Close".
6. Close the "Internet Options" dialog box with either "OK" or "Cancel".
7. Refresh the current page.
8. When told "There is a problem with this website's security certificate.", choose "Continue to this website (not recommended)."
9. Click on "Certificate Error" at the right of the address bar and select "View certificates".
10. Click on "Install Certificate...", then in the wizard, click "Next".
11. On the next page select "Place all certificates in the following store".
12. Click "Browse", select "Trusted Root Certification Authorities", and click "OK".
13. Back in the wizard, click "Next", the "Finish".
14. If you get a "Security Warning" message box, click "Yes".
15. Dismiss the message box with "OK".
16. Select Tools->Internet Options.
17. Select Security->Trusted sites->Sites.
18. Select the URL you just added, click "Remove", then "Close".
19. Now shut down all running instances of IE, and start up IE again.
20. The site's certificate should now be trusted.

Link to original  article 

Rate My Network Diagram

Site that has hundreds of network diagrams.   Great place to see examples of how people document their networks.

Rate My Network Diagram

Alternatives to Visio

Network Notepad

yWorks

Gliffy

Add additional domains to exchange 2003

Link

SBS 2003 multiple email domains relay error

Copy from a thread  here

The issue was that the Directory service to metabase service (DS2MB) wasn't able to update the metabase with the new Recipient Policy (or any SMTP changes, for that matter).  I found this after upping the diagnostic logging on ALL services.  I found Event ID 1040 for source MSExchangeMU, and proceeded to debug.  I started looking for "Metabase 5.7.1" in Google Groups and came up with: 

http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/15e831409481765a/8af1d59e381aaa1d?lnk=st&q=5.7.1+metabase&rnum=2&utoken=axmcE0YAAACAT_kPml7nPanGq5_khmjXgP-tS31hakRaUqJOki041qG2zFZkc34ScLXYq7vPwUPqy7LpN0kInhmnPrax4xrQTloHJX-orWmzzl4LCDoLUA

The Microsoft tech's (Nathan) suggestion to delete specific keys then have the Microsoft Exchange System Attendant rebuild the metabase upon restarting the service worked. 

Thank you very much for your help! 


Step-by-step Fix: 
http://www.eventid.net/display.asp?eventid=1040&eventno=3972&source=MSExchangeMU&phase=1 (see Error code 80070003) 

An explanation of the DS2MB service is explained here: 
http://www.microsoft.com/technet/prodtechnol/exchange/guides/E2k3TransnRouting/1b311041-2443-472b-8e9f-e26b2090ba78.mspx