Dec 24 2008 3:53PM GMT
Posted by: Michael Khanin
Exchange 2007,
Exchange
Yesterday I passed additional MS exam, PRO: Deploying Messaging Solutions with Microsoft Exchange Server 2007 (70-238), this is a last exam in serial MCITP: Enterprise Messaging Administrator.
This one was pretty similar to the previous, 70-237, but with a more details and tricks. It was a lot of questions about CCR, CSR, NLB and RAID’s. It was many question about “How to deal with multi sites organizations…” and questions like “What if..”. It was 50 questions in this exam.
The study resources I used to pass are:
Book “Microsoft Exchange Server 2007″
http://technet.microsoft.com
http://www.msexchange.org
http://msexchangeteam.com
http://exchangepedia.com
http://www.exchangeprovip.com
http://www.exchangeninjas.com
http://searchexchange.techtarget.com/gen…
http://www.msexchange.org/articles_tutor…
http://www.msexchange.org/articles_tutor…
Dec 14 2008 11:26PM GMT
Posted by: Michael Khanin
Exchange 2007,
Exchange,
PRO: Designing Messaging Solutions with Microsoft Excha,
70-237
I’ve just passed additional MS exam, PRO: Designing Messaging Solutions with Microsoft Exchange Server 2007 (70-237)! Got 935 on it
.
This one was easy that previous, 70-236. I’ve got a lot of questions about clustering, HA and multi-sites design. It was just 37 questions in this exam.
The study resources I used to pass are:
Book “Microsoft Exchange Server 2007″ http://www.amazon.com/Microsoft-Exchange-Server-2007-Unleashed/dp/0672329204/ref=pd_sim_b_1/191-1807479-9996238 (yes, this book again
)
http://www.msexchange.org/
http://msexchangeteam.com/
http://technet.microsoft.com/
http://www.cbtnuggets.com/
Nov 29 2008 5:18PM GMT
Posted by: Michael Khanin
Exchange,
Exchange Server 2007,
Update Rollup
Update Rollup 5 for Exchange Server 2007 Service Pack 1 (SP1) resolves issues that were found in Exchange Server 2007 SP1 since the software was released. This update rollup is highly recommended for all Exchange Server 2007 SP1 customers.
For a list of changes that are included in this update rollup, see KB953467. Download at source: www.microsoft.com
Nov 29 2008 4:54PM GMT
Posted by: Michael Khanin
Outlook Web Access,
Exchange,
RPC over HTTP/S,
Outlook Web Access (OWA) on Apache,
OWA on Apache
Using Apache 2 with Outlook Web Access (OWA) it’s very easy. This solution is even working when Apache installed on Windows XP and this solution can save a lot of money :), not necessary to buy Windows Server, additional Exchange Server licence or ISA Server. First, we need to enable some useful modules:
proxy
headers
Now, we need to edit / create a VirtualHost section (or use Include conf/extra/httpd-vhosts. conf, remember to make following changes inside httpd-vhosts. conf ):
<VirtualHost 1.2.3.4:80>
ServerName exmail.admininfo.ca
DocumentRoot /var/www/html/exchange
RedirectMatch ^/(index.html?)$ https://exmail.admininfo.ca/exchange/
RedirectMatch ^/exchange$ https://exmail.admininfo.ca/exchange/
</VirtualHost>
<VirtualHost 1.2.3.4:443>
# This secures the server from being used as a third party
# proxy server
ProxyRequests Off
# Allows the proxying of a SSL connection
SSLProxyEngine On
ProxyVia On
DocumentRoot /home/user/mail_proxy/html/
RequestHeader set Front-End-Https “On”
ServerName mail
# Set up SSL to work with this host
SSLEngine On
SSLCertificateFile /etc/apache/webmail-proxy/server.crt
SSLCertificateKeyFile /etc/apache/webmail-proxy/server.key
SSLProxyMachineCertificateFile /etc/apache/webmail-proxy/certnew.cer
ProxyPass /exchange/ https://mail-internal/exchange/
ProxyPassReverse /exchange/ https://mail-internal/exchange/
ProxyPass /exchweb/ https://mail-internal/exchweb/
ProxyPassReverse /exchweb/ https://mail-internal/exchweb/
ProxyPass /public/ https://mail-internal/public/
ProxyPassReverse /public/ https://mail-internal/public/
ProxyPreserveHost On
</VirtualHost>
NOTE: If you are using Apache on Windows, remember to make changes accordingly.
Nov 29 2008 4:28PM GMT
Posted by: Michael Khanin
Exchange 2003,
Exchange,
Block Users from Sending Email
We can configure Exchange to prevent users from sending mail to the Internet (and receive mails). The user can only receive e-mail from other Exchange users in the same organization. To set this, follow the following steps:
- Create a new distribution group (mail-enabled) in Exchange.
- Add all the users which are not allowed to send mail outside your organisation.
- Modify (properties) the SMTP connector(s) that are used to send to the internet
- Under the Delivery Restrictions tab, REJECT MESSAGES FROM, add the distribution group.
- Start Registry Editor (Regedt32.exe).
- Locate and click the following registry key:
HKEY_LOCAL_MACHINE/System/CurrentControlSet/Services/Resvc/Parameters/
- On the Edit menu, click Add Value, and then add the following registry value:
Value Name: CheckConnectorRestrictions
Data Type: REG_DWORD
Radix: Hexadecimal
Value: 1
- Quit Registry Editor.
- Restart the Microsoft Exchange Routing Engine service and the Simple Mail Transfer Protocol (SMTP) services for this change to take effect.
Nov 29 2008 3:58PM GMT
Posted by: Michael Khanin
Exchange 2003,
Exchange
Over Internet you can find a lot of articles talking about one thing - NOT TO INSTALL IE7 on server machines :).
One of the reasons is a crash of Exchange System Manager (ESM).
Exchange System Manager (ESM) crashes when you press F1, or click on the Help menu option.
As result, inside Event Viewer you will see an Event ID 1000.
I really don’t want to recommend you uninstall IE7. The solution for this “issue” is very simple, remove (rename) the PSAPI.DLL from the Exchsrvr\bin subdirectory:
- Stop the Exchange System Attendant Service
- Stop the IIS Admin Service
- Open a Command Prompt rename the PSAPI.DLL in the exchsrvr\bin directory. to PSAPI.DLL.OLD
- Restart the Exchange and IIS services.
- Enjoy
Aug 22 2008 6:23PM GMT
Posted by: Michael Khanin
Virtualization,
vmware,
Exchange 2007,
Hyper-V,
Windows Server 2008
Few days ago Microsoft announced some significant changes to its licensing and support policies for applications in hardware virtualization environments. There are two key parts of the announcement worth highlighting for Exchange customers:
- Microsoft now supports Exchange Server 2007 SP1 running Hyper-V or hypervisors validated under the Microsoft Server Virtualization Validation Program (SVVP).
- Microsoft is waiving its 90-day license reassignment policy to enable customers who virtualize Exchange to move their licenses between servers within a data farm as often as necessary.
As part of the updated support policies, we have published an article called Microsoft Support Policies and Recommendations for Exchange Servers in Hardware Virtualization Environments. This article includes Microsoft’s support policy and recommendations for running Exchange Server 2003 in a Microsoft Virtual Server 2005 R2 environment. It replaces Microsoft Knowledge Base article 320220, which previously detailed the policy and recommendations for this environment. In addition, this article includes Microsoft’s support policy and Microsoft’s recommendations for running Exchange Server 2007 SP1 in a hardware virtualization environment.
Microsoft Support Policies and Recommendations for Exchange Servers in Hardware Virtualization Environments is a must-read for anyone considering a virtualized Exchange environment.
Jul 2 2008 7:53PM GMT
Posted by: Michael Khanin
Exchange 2003,
IPv6,
Exchange 2007,
Exchange,
Windows Server 2008,
RPC over HTTP/S,
Outlook Anywhere
It’s not a secret, that IPv6 has some “issues”. When I’ve been in Seattle, at last MVP summit, a lot of IT professionals said that, and all of them recommended to disable IPv6 on Windows 2008 or / and Vista machines. Kevin Reeuwijk from “Innovative Technology Weblog” posted a very good article; Outlook Anywhere is ‘broken’ on IPv6 in Windows Server 2008.
So, if you run Exchange 2007 on Windows Server 2008 and want to use Outlook Anywhere (aka RPC over HTTP) you probably get a problem. It would not work if the RPC-over-HTTP Proxy and the Exchange Mailbox installed on the same Windows 2008 Server.
To make the long story short, simply unselect IPv6 from the properties of your NIC AND (it’s very important) make a changes to the HOSTS file. Simply open up your hosts file and make the following changes:
- Comment out the line “:::1 localhost”
- Add the following two lines:
<IPv4 address> <hostname of the computer>
<IPv4 address> <FQDN of the computer>
This will resolve all queries for your computer’s name to its IPv4 address, effectively disabling the use of IPv6 for self-communication. You can confirm that this works by doing a “telnet localhost 6004″.