Ehlo All,
I've decided, that it's more important for me and others to share more of the Exchange Server related news I read about than to create original content. There's too much information already out there, so better I expand it's reach. So, I'm going to start posting shorter and make it more of a clearing house for Exchange Server related news (a la /. style). This should be a win-win for all.
I also changed the layout and many of the fonts. If folks don't like them, let me know.
I'm also considering letting others post Exchange Server related news at some point in the future.
-Ben
Sunday, March 29, 2009
Tuesday, March 17, 2009
Microsoft's Support Policy on VMware Virtualization
Ehlo All,
An attendee at our March NY Exchange User Group meeting asked about Microsoft's support policy on the industry leader of virtualization which is running at 100% of all Fortune 100 companies, VMware. There is a lot of fear, uncertainty, and doubt in this realm. So, let me make it crystal clear! Microsoft WILL SUPPORT VMware's SVVP (explained below) solution which is ESX 3.5 update 2. Microsoft virtualized support is for over 30+ server applications & operating systems as per KB ID 957006. Just to clarify, for Exchange 2003 & 2007 SP1 are supported.
Quoted from MS KB # 897615
Additionally, for vendors with whom Microsoft has established a support relationship that covers virtualization solutions, or for vendors who have Server Virtualization Validation Program (SVVP) validated solutions, Microsoft will support server operating systems subject to the Microsoft Support Lifecycle policy for its customers who have support agreements when the operating system runs virtualized on non-Microsoft hardware virtualization software. This support will include coordinating with the vendor to jointly investigate support issues. As part of the investigation, Microsoft may still require the issue to be reproduced independently from the non-Microsoft hardware virtualization software. Where issues are confirmed to be unrelated to the non-Microsoft hardware virtualization software, Microsoft will support its software in a manner that is consistent with support provided when that software is not running together with non-Microsoft hardware virtualization software.
VMware's Exchange support information for ISV support.
VMware Press Release about ESX 3.5 update 2 support Exchange, SQL, SharePpint, and more. They even quote a 50k seat install on ESX with Exchange by the University of Plymouth in England.
Just to be clear, make sure your issue is non-virtualization related. e.g. not performance or other, and more a configuration or those types of problems. If you have an I/O issue, it could easily be a VM issue, so make sure those subsystems working well and you're 100% sure it's not VM related.
Now, you know the real story behind Microsoft support for virtualization and you can now rest easy. Or the other solution is to have a very good back process running on non-virtualized hardware. That's what I do. Sleep is over-rated.
-Ben
An attendee at our March NY Exchange User Group meeting asked about Microsoft's support policy on the industry leader of virtualization which is running at 100% of all Fortune 100 companies, VMware. There is a lot of fear, uncertainty, and doubt in this realm. So, let me make it crystal clear! Microsoft WILL SUPPORT VMware's SVVP (explained below) solution which is ESX 3.5 update 2. Microsoft virtualized support is for over 30+ server applications & operating systems as per KB ID 957006. Just to clarify, for Exchange 2003 & 2007 SP1 are supported.
Quoted from MS KB # 897615
Additionally, for vendors with whom Microsoft has established a support relationship that covers virtualization solutions, or for vendors who have Server Virtualization Validation Program (SVVP) validated solutions, Microsoft will support server operating systems subject to the Microsoft Support Lifecycle policy for its customers who have support agreements when the operating system runs virtualized on non-Microsoft hardware virtualization software. This support will include coordinating with the vendor to jointly investigate support issues. As part of the investigation, Microsoft may still require the issue to be reproduced independently from the non-Microsoft hardware virtualization software. Where issues are confirmed to be unrelated to the non-Microsoft hardware virtualization software, Microsoft will support its software in a manner that is consistent with support provided when that software is not running together with non-Microsoft hardware virtualization software.
VMware's Exchange support information for ISV support.
VMware Press Release about ESX 3.5 update 2 support Exchange, SQL, SharePpint, and more. They even quote a 50k seat install on ESX with Exchange by the University of Plymouth in England.
Just to be clear, make sure your issue is non-virtualization related. e.g. not performance or other, and more a configuration or those types of problems. If you have an I/O issue, it could easily be a VM issue, so make sure those subsystems working well and you're 100% sure it's not VM related.
Now, you know the real story behind Microsoft support for virtualization and you can now rest easy. Or the other solution is to have a very good back process running on non-virtualized hardware. That's what I do. Sleep is over-rated.
-Ben
Microsoft Addresses a MAJOR Issue I have with Exchange 2007's OWA
Ehlo All,
I heard great news last week that addresses the reduced set of functionality in Exchange 2007's Outlook Web Access. Exchange 14's OWA will be support 3 browsers, Internet Explorer, Firefox, and Safari. I did a triple-take when I read it the first time. Y-E-S. 3 browsers supported in E14's OWA. No decision on which platform for these browsers since they are dual platform apps.
I actually lost functionality in upgrading to the latest greatest version of Exchange 2007 from 2003. OWA Basic in 2003 supported access to Public Folders, in OWA Lite (aka Basic mode), access disappeared. Thankfully enough people complained that Microsoft is planning according to a Exchange rockstar Paul Robichaux, aka Exchange MVP. You can read the full article by Paul here & his reference to the MS blog that announced this amazing information.
I'll definitely be upgrading to E14 when it's released. And adios to ActiveX for OWA. There won't be a wet eye in my house for this loss.
-Ben
I heard great news last week that addresses the reduced set of functionality in Exchange 2007's Outlook Web Access. Exchange 14's OWA will be support 3 browsers, Internet Explorer, Firefox, and Safari. I did a triple-take when I read it the first time. Y-E-S. 3 browsers supported in E14's OWA. No decision on which platform for these browsers since they are dual platform apps.
I actually lost functionality in upgrading to the latest greatest version of Exchange 2007 from 2003. OWA Basic in 2003 supported access to Public Folders, in OWA Lite (aka Basic mode), access disappeared. Thankfully enough people complained that Microsoft is planning according to a Exchange rockstar Paul Robichaux, aka Exchange MVP. You can read the full article by Paul here & his reference to the MS blog that announced this amazing information.
I'll definitely be upgrading to E14 when it's released. And adios to ActiveX for OWA. There won't be a wet eye in my house for this loss.
-Ben
Monday, March 16, 2009
Easy access to .edb/.stm files via Ontrack PowerControls
Ehlo All,
So, I recently upgraded to Exchange 2007, and realized one day I might need access to my old Exchange 2003 data. Even though I performed move mailboxes for most accounts, I didn't did it for all. I figured, I should save the databases, .edb & .stm files "just in case". Well, the "just in case" time came almost one month later after my upgrade.
So, while I run AppAssure's MailRetriever which is designed to mount offline Exchange 2003/2007 databases, it's at my datacenter and I had the .edb/.stm files at my home office. I considered transfering the files, but they are close to 40GBs, so I decided to test out under a virtual machine Ontrack's PowerControls. So, I fired up my handy VMware Workstation 6.5 & XP Pro w/Office 2003 and mounted over a 100Mb network via UNC/drive the folder share containing the files. Once mapping to a drive letter, the .edb/.stm files quickly and easily exported the data (some task items) to a PST. Opening the 23GB .edb w/o logs took about 15 seconds which was mindblowing which was OVER a network connection. I then tested the PST data in Outlook which looked good and compressed it and emailed the 1.3Mb off to the user that needed it. That's it. It was so easy, I was shocked. It literally took me maybe 10 minutes if that long.
Overall, Ontrack's PowerControls software package is very impressive.
-Ben
So, I recently upgraded to Exchange 2007, and realized one day I might need access to my old Exchange 2003 data. Even though I performed move mailboxes for most accounts, I didn't did it for all. I figured, I should save the databases, .edb & .stm files "just in case". Well, the "just in case" time came almost one month later after my upgrade.
So, while I run AppAssure's MailRetriever which is designed to mount offline Exchange 2003/2007 databases, it's at my datacenter and I had the .edb/.stm files at my home office. I considered transfering the files, but they are close to 40GBs, so I decided to test out under a virtual machine Ontrack's PowerControls. So, I fired up my handy VMware Workstation 6.5 & XP Pro w/Office 2003 and mounted over a 100Mb network via UNC/drive the folder share containing the files. Once mapping to a drive letter, the .edb/.stm files quickly and easily exported the data (some task items) to a PST. Opening the 23GB .edb w/o logs took about 15 seconds which was mindblowing which was OVER a network connection. I then tested the PST data in Outlook which looked good and compressed it and emailed the 1.3Mb off to the user that needed it. That's it. It was so easy, I was shocked. It literally took me maybe 10 minutes if that long.
Overall, Ontrack's PowerControls software package is very impressive.
-Ben
Tuesday, January 27, 2009
Non-Windows Mobile Issue relating to ActiveSync with Exchange 2007 SP1
Ehlo All,
If you attended the October 08 meeting of the NY Exchange Server User group (NYExUG), you would have learned that ActiveSync is a different beast for Windows Mobile (e.g. HTC Touch, iPAW Hwxxx, etc) & licensed ActiveSync devices (e.g. iPhone, Palm Treo, etc). So, when I recently upgraded from Exchange 2003 to Exchange 2007 SP1 (on Windows 2008 - I like pain), I was hoping ActiveSync would just work. Nope, I was out of luck. End user Palm 700p error of AirSAMStateMachine.c 1913 4628. But the fix was pretty easy IF you know the PowerShell command. IF is the key word there.
So, as always, first step of troubleshooting, is to Google the error and see what comes up. I quickly found that ActiveSync's default security policy was probably the cause of the issue. And I crossed my fingers and ran the following command (bold italics on 1 line) below. Also, don't just run commands like I recklessly did, but find out what exactly it's doing and how to reverse it in case all hell breaks loose. This is a mission critical application.
Start --> Programs --> Microsoft Exchange Server 2007 --> Exchange Management Shell
Remove-ActiveSyncMailboxPolicy -Identity "Default"
Then magically, ActiveSync started working. Just so you know, below is the Microsoft TechNet article that explains the various options available in ActiveSync policies. There are many more settings that can be controlled in Exchange 2007. I'm not sure which setting caused the issue, but at least I have 1 less screaming user which makes exploring and research the options more enjoyable.
http://technet.microsoft.com/en-us/library/cc182294.aspx
-Ben
If you attended the October 08 meeting of the NY Exchange Server User group (NYExUG), you would have learned that ActiveSync is a different beast for Windows Mobile (e.g. HTC Touch, iPAW Hwxxx, etc) & licensed ActiveSync devices (e.g. iPhone, Palm Treo, etc). So, when I recently upgraded from Exchange 2003 to Exchange 2007 SP1 (on Windows 2008 - I like pain), I was hoping ActiveSync would just work. Nope, I was out of luck. End user Palm 700p error of AirSAMStateMachine.c 1913 4628. But the fix was pretty easy IF you know the PowerShell command. IF is the key word there.
So, as always, first step of troubleshooting, is to Google the error and see what comes up. I quickly found that ActiveSync's default security policy was probably the cause of the issue. And I crossed my fingers and ran the following command (bold italics on 1 line) below. Also, don't just run commands like I recklessly did, but find out what exactly it's doing and how to reverse it in case all hell breaks loose. This is a mission critical application.
Start --> Programs --> Microsoft Exchange Server 2007 --> Exchange Management Shell
Remove-ActiveSyncMailboxPolicy -Identity "Default"
Then magically, ActiveSync started working. Just so you know, below is the Microsoft TechNet article that explains the various options available in ActiveSync policies. There are many more settings that can be controlled in Exchange 2007. I'm not sure which setting caused the issue, but at least I have 1 less screaming user which makes exploring and research the options more enjoyable.
http://technet.microsoft.com/en-us/library/cc182294.aspx
-Ben
Monday, January 19, 2009
OWA Light Comparison from Exchange 2003 to 2007
Ehlo All,
So, I upgraded to Exchange 2007 this past week. The primary focus of this blog post is OWA Light difference between 2003 and 2007. Reason is, I frequently use OWA on non-IE browser to access Public Folders and was surprised to see existing features in OWA 2003 removed. So, I wondered what else was missing in action (or added) from OWA Light on 2007. Here is the list. [-] means feature is missing from new version. [+] means feature is added in 2007.
If you have a lot of OWA Light users, I would seriously consider staying on Exchange 2003 or leaving OWA users on Exchange 2003 while having other users on Exchange 2007.
What others talked about....
Exchange Product Team Discussing OWA Light 2007 - it seems OWA Light only gained feature according to the Exchange Team.
Figured I would share since OWA is discussed...
Exchange Product Team Discussing Exchange 14 (aka E14). Not much detail except talk about the 3.5 million beta testers and "empowering" end users with distribution list & GAL control. Not very sexy.
OWA 2007 OWA Light - to summarize, is the bare essential in webmail. So, that's email, calendar, & contacts. Nada mas.
[-] Calendar (Daily View Only)
[-] NO Public Folders Access
[-] NO Tasks
[+] Quickly jump to a subfolder (via drop-down)
[+] Easily rename/move/delete folders
[+] Ability to search in Address Book
[+] Ability to change AD password
[+] View a partnered Windows Mobile device
OWA 2003 OWA Light
[+] Calendar (Daily & Weekly)
[+] Public Folders
[+] Tasks
To say I'm disappointed would be an understatement. Come on Microsoft, add features, don't remove otherwise folks will jump to other web based email products like GMa... you know what I'm talking about. :-)
I'll blog more about differences in the future and the migration in general.
-Ben
So, I upgraded to Exchange 2007 this past week. The primary focus of this blog post is OWA Light difference between 2003 and 2007. Reason is, I frequently use OWA on non-IE browser to access Public Folders and was surprised to see existing features in OWA 2003 removed. So, I wondered what else was missing in action (or added) from OWA Light on 2007. Here is the list. [-] means feature is missing from new version. [+] means feature is added in 2007.
If you have a lot of OWA Light users, I would seriously consider staying on Exchange 2003 or leaving OWA users on Exchange 2003 while having other users on Exchange 2007.
What others talked about....
Exchange Product Team Discussing OWA Light 2007 - it seems OWA Light only gained feature according to the Exchange Team.
Figured I would share since OWA is discussed...
Exchange Product Team Discussing Exchange 14 (aka E14). Not much detail except talk about the 3.5 million beta testers and "empowering" end users with distribution list & GAL control. Not very sexy.
OWA 2007 OWA Light - to summarize, is the bare essential in webmail. So, that's email, calendar, & contacts. Nada mas.
[-] Calendar (Daily View Only)
[-] NO Public Folders Access
[-] NO Tasks
[+] Quickly jump to a subfolder (via drop-down)
[+] Easily rename/move/delete folders
[+] Ability to search in Address Book
[+] Ability to change AD password
[+] View a partnered Windows Mobile device
OWA 2003 OWA Light
[+] Calendar (Daily & Weekly)
[+] Public Folders
[+] Tasks
To say I'm disappointed would be an understatement. Come on Microsoft, add features, don't remove otherwise folks will jump to other web based email products like GMa... you know what I'm talking about. :-)
I'll blog more about differences in the future and the migration in general.
-Ben
Monday, January 5, 2009
Handy Free Tool to Test Connections to other Mail Servers - Time Saver Tip
Ehlo All,
When you need to test another mail server connection, to make sure it's accepting emails, I normally do the following: RDP to mail server, open telnet, open some ip:25 and then enter in smtp commands and make sure the other mail server accepts the email. I recently heard about a tool that expedites this process by handling DNS lookups, smtp commands, etc. It's called TestMX.
About TestMX. It's a very small free Windows application (command line, but don't be afraid, it's very easy). All you need to do is enter the domain to test, and it handles everything for you. The download is 2 files, help file and the .exe program. Below is what I did. I downloaded TestMX, and ran it against my domain (testmx -dreefsolutions.com). See, so easy. So, let's see what happens.
Play by Play
1) it performs a DNS lookup. It shows my local PC's DNS is 4.2.2.2 and 4.2.2.3.
2) it shows the MX records for reefsolutions.com, which are 3 servers.
3) attempts to connect to the lowest preference number (lower is priority connection). If it fails, the tool is suppose to attempt to connect to next preference number.
4) creates a connection to the MX record it found and is successful since the servers responds with "Spam Be Afraid" which indicates my server would be willing to accept more commands to send an email. This does NOT guarantee an email will be accepted though. It simply is testing that the other server is alive and responding.
5) quits connection.
Or, if you want to actually test sending of email you'll need to use an email client or perform the smtp commands by telnet. I recently found a better smtp command site than my old favorite (Microsoft's KB article on the process). Like I said before, the TestMX is only to insure the other mail server responds.
Old School way to test smtp (command by command). Favorite site to explain smtp command sending and is more accurate than the one below.
http://exchangeninjas.com/SpeakSMTP
Old Favorite for testing via smtp commands (XFOR: Telnet to Port 25 to Test SMTP Communication)
http://support.microsoft.com/kb/153119
-Ben
When you need to test another mail server connection, to make sure it's accepting emails, I normally do the following: RDP to mail server, open telnet, open some ip:25 and then enter in smtp commands and make sure the other mail server accepts the email. I recently heard about a tool that expedites this process by handling DNS lookups, smtp commands, etc. It's called TestMX.
About TestMX. It's a very small free Windows application (command line, but don't be afraid, it's very easy). All you need to do is enter the domain to test, and it handles everything for you. The download is 2 files, help file and the .exe program. Below is what I did. I downloaded TestMX, and ran it against my domain (testmx -dreefsolutions.com). See, so easy. So, let's see what happens.
Play by Play
1) it performs a DNS lookup. It shows my local PC's DNS is 4.2.2.2 and 4.2.2.3.
2) it shows the MX records for reefsolutions.com, which are 3 servers.
3) attempts to connect to the lowest preference number (lower is priority connection). If it fails, the tool is suppose to attempt to connect to next preference number.
4) creates a connection to the MX record it found and is successful since the servers responds with "Spam Be Afraid" which indicates my server would be willing to accept more commands to send an email. This does NOT guarantee an email will be accepted though. It simply is testing that the other server is alive and responding.
5) quits connection.
D:\>testmx -dreefsolutions.com
Testing MX connection with domain reefsolutions.com
Using nameserver 4.2.2.2 4.2.2.3
MX for reefsolutions.com is spamcopcluster1.reefsolutions.com [69.31.40.115]
MX for reefsolutions.com is b.reefsolutions.com [72.68.143.91]
MX for reefsolutions.com is spamcopcluster2.reefsolutions.com [72.68.143.92]
Connecting with spamcopcluster1.reefsolutions.com [69.31.40.115]
Connection established with spamcopcluster1.reefsolutions.com [69.31.40.115]
< 220 Spam Be Afraid
> HELO BlackThunder
< 250 spamcopcluster1.reefsolutions.com Hello static-xx-xx-xx-xx.nycmny.fios.ve
rizon.net [xx.xx.xx.xx], pleased to meet you
> QUIT
< 221 Bye
Connection closed with spamcopcluster1.reefsolutions.com [69.31.40.115]
D:\>
Or, if you want to actually test sending of email you'll need to use an email client or perform the smtp commands by telnet. I recently found a better smtp command site than my old favorite (Microsoft's KB article on the process). Like I said before, the TestMX is only to insure the other mail server responds.
Old School way to test smtp (command by command). Favorite site to explain smtp command sending and is more accurate than the one below.
http://exchangeninjas.com/SpeakSMTP
Old Favorite for testing via smtp commands (XFOR: Telnet to Port 25 to Test SMTP Communication)
http://support.microsoft.com/kb/153119
-Ben
Subscribe to:
Posts (Atom)
