Category: exchange 2007



We all know the Exchange setting for “recover deleted items” is out of the box, set to 14 days. What if a user accidentally did a Shift + Delete of the message? well there is a nice work around that one of my students from this week’s Exchange class tipped me off on. it’s KB246153 and outlines via a registry hack on the client. this helps if you have hard deleted (permanently deleted) items in Outlook and want to recover them. For example, if you do not move items to the Deleted Items folder before you delete them, these items are hard deleted, and you cannot recover them from the Deleted Items folder normally.  This reg hack allows the user to view the dumpster.

By default, the Recover Deleted Items functionality is only enabled on the Deleted Items folder in a user’s private folders. Items that are hard deleted cannot be recovered. To enable the Recover Deleted Items functionality on mail folders other than the Deleted Items folder (for example, for the Sent Items, Drafts, Outbox and Inbox folders), make the following changes to the registry:

  1. Start Registry Editor.
  2. Locate and then click the following key in the registry:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Client\Options
  3. On the Edit menu, click Add Value, and then add the following registry value:
    Value name: DumpsterAlwaysOn
    Data type: DWORD
    Value data: 1
  4. Close Registry Editor.

Now does this dumpster change in Exchange 2010? Very much. Dumpster 2.0 is an interesting animal and had to be evolved to be able to support things like legal retention holds and other security requirements. Looking for more info on Dumpster 2.0? Our friends at the MSExchangeTeam.com site already outlined the before and after of Dumpster 1.0 vs. 2.0

Single Item recovery in Exchange 2010


Microsoft research figured out a way just to do this by modifying a few attributes of mail messages as they are being sent stopping people from doing just that!

No reply to all download

The primary function is to add a couple of buttons to the Outlook ribbon to prevent people from doing a reply-all to your message, or forwarding it (using a facility built into Outlook & Exchange which is really lightweight compared to using IRM machinery, but which is not exposed in the existing UI). However, it also includes a check for email goofs such as omitting attachments or subject lines.

This works with both Outlook 2007 and Outlook 2010, as long as you’re using an Exchange account.

Add-in buttons

When you install this thing, you’ll see a couple of extra buttons at the end of the ribbon: No Reply All and No Forward. As the names suggest, clicking on these will prevent recipients of your emails from performing those two actions; clicking again toggles the relevant option off again.

I ran into this info on the awesome MS tracker site..

bink


 

Paul from today’s 5050 Exchange 2007 class was looking for some more information on how SCR works and ways to set it up.. Here ya go Paul!

 

SCR explained by TechNet

Video series on SCR – You Had me at EHLO blog

How SCR works within Exchange 2007 SP1 – You had me at EHLO blog

Exchange SCR setup and recovery – MMMUG-UK

SCR explained – Exchange Genie


 
   This was shamelessly stolen from MsExchangeTeam.com
 

Updates to the Exchange Supportability Matrix

With the release of Exchange 2007 SP2 we provided a Supportability Matrix which outlined the supported configurations for Exchange 2000 SP3, Exchange 2003 SP2, and Exchange 2007 (RTM, SP1, and SP2).   But as many are aware, with the release of Windows Server 2008 R2 there have been a variety of questions raised about our support policies and a multitude of feedback.  Two pieces of feedback occurred numerous times –  the need to support Exchange 2007 on Windows Server 2008 R2 and the need to support Exchange 2003 against Windows Server 2008 R2 Active Directory servers. 

In response to this feedback we will be making several updates to the supportability matrix.

  • As I recently blogged about, we will be adding support for Exchange 2007 on the Windows Server 2008 R2 platform.   While we had hoped to add this application/operating system combination quickly, unfortunately adding this support requires code changes to setup in Exchange 2007.  Therefore, our vehicle for adding this support will be via a third Service Pack for Exchange 2007 in the second half of calendar year 2010.
  • Exchange 2003 SP2 will now be supported against writeable Windows Server 2008 R2 Active Directory Servers.  Additionally, with the General Availability of Exchange Server 2010, and those looking to standardize on Windows Server 2008 R2 we have enhanced the supportability of forest and domain functional levels up to Windows Server 2008 R2.  This change is effective immediately on Exchange 2003 SP2.
  • Exchange 2007 is now supported on servers running .NET Framework 3.5 SP1 provided that the .NET platform was upgraded from .NET Framework 2.0.  This change is also effective immediately on Exchange 2007 SP2.

Each of these changes are being made to provide the flexibility you requested – to change your operating system architecture without changing your messaging architecture.  In addition to the existing combinations, we will be adding supportability guidance for Exchange 2010 to the matrix.    Note that all of these changes may not immediately appear on the supportability matrix, but be assured that any documentation update lag will not affect your supportability with Microsoft Support.

Finally I do want to update all on one other piece of feedback we have received – allowing the in place upgrade of the operating system under Exchange.  Technically the work required to provide this capability is consistent with the work we would need to do to support an in-place upgrade of Exchange itself.  As such the amount of work needed is outside the scope and complexity of what we can do in a post release product update.  Still we do understand the demand and desire and it is something we will continue to look at for future versions of the product.

While we hope these changes are welcome news and address questions you may have had, we also understand we have areas to improve in.  Our desire is to simplify and improve the support experience with Exchange.   If you have more feedback, please continue to provide it.

Kevin Allison
General Manager, Exchange Customer Experience


 
 
     Today in my class Sherri asked, "this mail address policy thing is neat in exchange 2007, is there an equivalent in 2003?"
 
     Sure is Sherri! Exchange 2003 uses a slightly different terminology on how it handles organizational address changes. It uses Recipient Policies to perform bulk SMTP address changes. Scenarios where this may be applicable is may if you purchase a new domain name and want to add it as an alias to all of your existing mailboxes.
 
    Here are some handy links to some MSKB and technet documents with explinations and walk-throughs!
 
 
 

 
 
    One of the many "Gotcha’s" that most Exchange administrators miss when transitioning from Exchange 2k or 2k3 to 2007 is forgetting to move other resources to the new 2007 environment. Admins will never miss mailboxes, but what about our little friend the OAB (Offline address book) Alot of administrators miss this before they perform their uninstallation of Exchange from the generating server! I too have fallen prey to this.
 
     Best practice is to move the OAB from the one server to the 2007 environment. Steps for moving the OAB found here…
 
     One of the ways I have gotten around this issue if you’ve already blown the 2k3 server away and cannot restore it is to create a fresh one. Issue is there will already be a reference to the old one ( the one the clients are trying to pull ) that needs to be removed. Until you do, users will continue to get the dreaded  0X8004010F outlook errors during send and receive! Once the object is removed you can then create a new one with a new name and after about 24 hrs all the clients should have authenticated and queried for which OAB to get and from where.
 
      Note – this delete remove solution is NOT microsoft "approved" but what I was able to do with a few steps to get it going again.
 
Reference info..
 
 
 
 
      Step by step…
 
Liberated from… Here..
 
 How to Move OAB
1. Start the Exchange Management Console.
2. In the console tree, expand Organization Configuration, and then click Mailbox.
3. In the result pane, click the Offline Address Book tab, and then select the OAB for which you want to move the generation to a new server.
4. In the action pane, click Move. The Move Offline Address Book wizard appears.
5. On the Move Offline Address Book page, click Browse to open the Select Mailbox Server dialog box.
6. Select the server to which you want to move the OAB generation process, and then click OK.
7. Click Move to move the OAB generation process to the new server.
8. View the status of the move operation. The wizard will move the generation of your OAB to the new server and copy the existing files for the OAB to the new server.
9. On the Completion page, confirm whether the OAB generation process was moved successfully. A status of Completed indicates that the wizard completed the task successfully. A status of Failed indicates that the task was not completed. If the task fails, review the summary for an explanation, and then click Back to make any configuration changes.
10. Click Finish to complete the Move Offline Address Book wizard.

Click in the browse and select E2K7 and then click on move

If you want to perform it from powershell follow this command
Move-OfflineAddressBook -Identity "My OAB" -Server SERVER01

I hope this article is being very informative for you all. Thank you for your time and patience for going through this article.


 
    Here is a good one! The president of the company comes to me with an odd mail issue. I have since found it’s not that odd, just one I had not personally experienced before. Allow me to take you on the journey to troubleshoot and solve this..
 
    "Chad, I can’t seem to send mail to this one person. Yet they can send mail to me from scratch, just I cannot reply"
 
What do you begin to think right off the bat? Not our servers, they are stable as can be! Well my first instinct was that it was likely an issue on their end. I had dropped a mail message (From my personal acct obviously) to the point of contact there asking if their mail admin could look at some SMTP logs to confirm or deny our servers are even talking. My through process to this point is – firgure out what is or is not working to eliminate either their systems or ours.
 
to start the mass elimination process i then sent another few test mails from different POP and web based mail systems to their servers. So we know now that their system can accept incoming SMTP connections from multiple sources inluding new domains. Now I started to think it was an issue with my server. No users from my system could send mail to theirs, but they could send to us. That tells me that their servers can establish an SMTP session with mine. from there i hit up the Exchange server 2007 toolbox. I brought up the queue viewer and noted the namespace i was trying to send to and it had a retry status with an error of "451 4.4.0 DNS Query failed." I then attacked NSLOOKUP to see if i could resolve their domain name for MX and A records for the SMTP hosts. I was able to do this with no issues.
 
So this tells me outbound mail isn’t even hitting the submission queue on this local server to even be sent. this makes the mailflow troubleshooter useless to me. What shocked me was that it was still only one domain having this issue. If I had DNS issues, wouldn’t it affect ALL external namespaces? not so. the kicker is in HOW the external namespace is being resolved. Remember your exchange box REQUIRES IPv6 for installation and will try to resolve all domain names for sending and categorization by all means (IP Stacks) neccessary.  Here is where i started doing some research and found some nice posts / articles…
 
Technet mail transport troubleshooting document  – i know it says Edge Transport , but it can be used for Hub Transport too
 
 
The article i got my final answer from  – Scroll down to the bottom in the "Troubleshooting DNS" section
 
So my final fix was adjusting the organization’s single send connector. On the properties dialog box and Network tab, It was set to just "Use domain name system (DNS) "MX" records to route mail automatically". At the bottom of this page there is a check box for "Use the external DNS lookup settings on the transport server". Once i checked this and restarted the Microsoft Exchange Transport service the mail flew out of the queue when i restarted it 🙂

This is actually a pretty common error which I too have fallen to. As administrators we out of best practice efforts for security, disable ports, protocols and anything else we don’t think we need. Guess what? Exch 2007 install REQUIRES an IPv6 address for the installation! I ran into this while building a Hyper-V based test environment and confirmed it’s a known issue via this forum thread – enjoy!
 

There is a limited set of what you can do and manage within the MOSS calendar via an outlook 2007 client. You can add and even merge events if you wish. A really nice write up is listed for it here..

Integrating SharePoint and Outlook 2007

One of my students today asked a question…

"i know BES can enforce a device to be encrypted or have the mail on it encrypted, can EAS do that?"

Sure seems like it – I found this portion of the EAS policy..

Device encryption enabled

This
setting enables encryption on the device. Not all devices can enforce
encryption. For more information, see the device and mobile operating
system documentation.

Taken from this link..

Understanding Exchange ActiveSync Mailbox Policies