Exchange Server 2007 migration

Hi everyone,
I have exchange 2007 server with all the roles installed on single server.
I want to do the transition from exchange 2007 to exchange 2013
Please do provide me with necessary articles and screenshots.

Hi i was referring this article
http://www.msexchange.org/articles-tutorials/exchange-server-2013/migration-deployment/planning-and-migrating-small-organization-exchange-2007-2013-part8.html
Configuring the Offline Address Book setting on existing Mailbox Databases
Please do refer the attachment , is thesetting correct for my offline address book. or do i need to run the below command
Get-MailboxDatabase | Where {$_.OfflineAddressBook -eq $null} | Set-MailboxDatabase -OfflineAddressBook (Get-OfflineAddressBook | Where {$_.IsDefault -eq $True})

Similar Messages

Migrate Notes from Exchange server 2007 to office 365

Hi,
Anyone help me to how to migrate notes from exchange server 2007 to office 365 . My customer having notes on his existing exchange account . We would like to move notes to office 365 .
Please help me or guide me .
Thanks & Regards,
Vinoth

The way you're doing it has two very high hurdles.
First, you have to get the data out of an offline server and into Office 365. That's hardly a trivial task. If the server were online and reachable by the Internet you could use a move request or a third-party tool like MigrationWiz.
Second, if you do get the mail moved, you will want to synchronize the legacyExchangeDN attribute from the old organization into an X500 proxy address in Office 365 for all mailboxes to preserve mail replyability.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Migrate Active Directory 2003 to 2012 R2 and Exchange Server 2007 to 2013.

My question is which one need to migration first. Active Directory 2003 to 2012 R2 and FFL & DFL or Exchange Server 2007 to 2013.
Md. Ramin Hossain

My question is which one need to migration first. Active Directory 2003 to 2012 R2 and FFL & DFL or Exchange Server 2007 to 2013.
Domain. For Exchange installation and upgrading to 2013, you need to make sure that your domain controllers can understand attributes of exchange 2013. Besides if you have DC/Exch on the same server which is 2003 is not supported. Because Windows Server
2003 is not supported.
Migrate your domain to at least 2008 R2 and then proceed with Exchange 2013.
Mahdi Tehrani |
|
www.mahditehrani.ir
Please click on Propose As Answer or to mark this post as
and helpful for other people.
This posting is provided AS-IS with no warranties, and confers no rights.
How to query members of 'Local Administrators' group in all computers?

Migration of Unity users from MS Exchange server 2007 to 2010

Hi,
I am having Unity 7.0 with MS Exchange server 2007,now want to transfer the users and Unity mailboxes to MS Exchange server 2010. Want to know the procedure. Can anyone help me out?

The way you're doing it has two very high hurdles.
First, you have to get the data out of an offline server and into Office 365. That's hardly a trivial task. If the server were online and reachable by the Internet you could use a move request or a third-party tool like MigrationWiz.
Second, if you do get the mail moved, you will want to synchronize the legacyExchangeDN attribute from the old organization into an X500 proxy address in Office 365 for all mailboxes to preserve mail replyability.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

MimeMessage.reply() issue with MS Exchange Server 2007 Emails

I have an application that retrieves emails from an MS Exchange Server 2003 mailbox. The data from each message is read, validated and conditionally loaded to a table. If the message doesn't pass validation, a rejection email is sent back to the sender with an error message and a copy of the email. (We're using Java 1.5. However, I test with both 1.5 and 1.6.)
Also, if the message passes validation, positive notification is sent back to the sender.
Both processes use the method: javax.mail.Message.reply()It's coded as:
MimeMessage reply = (MimeMessage) message.reply(false);My organization is in the process of migrating to MS Exchange Server 2007. We've found that the reply() method no longer finds the sender method, thus unable to create a reply message. The error message we receive is:
javax.mail.SendFailedException: No recipient addresses
     at javax.mail.Transport.send0(Transport.java:110)
     at javax.mail.Transport.send(Transport.java:80)
     at org.ccci.gms.datacollector.DataCollector.sendReply(DataCollector.java:514)
     at org.ccci.gms.datacollector.DataCollector.processMessages(DataCollector.java:162)
     at org.ccci.gms.datacollector.DataCollector.main(DataCollector.java:101)After creating the MimeMessage object from the reply() method, I printed out the email header detail from both 2003 and 2007 messages. You'll note from below that the "To" or recipient address is missing from Server 2007.
MS Exchange 2003 works fine
From: [email protected]
To: [email protected]
Subject: Re: Report
In-Reply-To: <[email protected]>MS Exchange 2007 no longer works
From: [email protected]
Subject: Re: Reports
In-Reply-To: <[email protected]>I know I could just use the "addRecipient()" method to get around this problem. I wanted to know if anyone has encountered this issue. Please share the resolution. Any suggestions will be greatly appreciated.
Thanks,
LaelW

When the original message is accessed using IMAP, the reply method uses the information in the
IMAP ENVELOPE to determine where to send the reply. It first looks for the Reply-To address
in the ENVELOPE, then the From address.
Interestingly, when not using IMAP, the getFrom method returns the Sender header if the From
header is empty. The IMAP-specific code doesn't do that, although perhaps it should.
It would be interesting to compare the ENVELOPE data from the protocol trace in the two cases.
The ENVELOPE data will follow this syntax:
envelope     = "(" env-date SP env-subject SP env-from SP
          env-sender SP env-reply-to SP env-to SP env-cc SP
          env-bcc SP env-in-reply-to SP env-message-id ")"
So it's the first three address fields after the Subject that are relevant. If the From and Reply-To
fields are NIL, but the Sender field has a valid address, let me know. I should probably fix the
IMAP provider to fall back to the Sender field if the From field is missing.

Grant Application Impersonation Rights for UPN on Exchange Server 2007

Hi,
I would like to know , how to grant application impersonation rights for UPN account in exchange server 2007 . As i am working for mailbox migration , i should have this rights . I can do impersonation rights for domain\username but not for [email protected]
Please anyone help me , how to grant permission for [email protected] .
Big thanks in advance.
.Thanks & Regards,
vinoth

Hi,
I have a test in my environment using Exchange 2007, you can use the following cmdlet to assign Application Impersonation rights to an account using UPN.
Get-ExchangeServer | where {$_.IsClientAccessServer -eq $TRUE} | ForEach-Object {Add-ADPermission -Identity $_.distinguishedname -User (Get-User -Identity
[email protected] | select-object).identity -extendedRight ms-Exch-EPI-Impersonation}
Get-MailboxDatabase | ForEach-Object {Add-ADPermission -Identity $_.DistinguishedName -User
[email protected] -ExtendedRights ms-Exch-EPI-May-Impersonate}
Note: Please change the "[email protected]" to the UPN you want to use.
Hope my clarification is helpful.
Best regards,
Amy Wang
TechNet Community Support

Autodiscover Exchange Server 2007 and 2013 Coexistence

Hello
We are having some issues where some users are not being notified when their mailbox is being migrated to E2013.
Before 2013, we never had a load balanced solution for CAS in Exchange Server 2007 or a single name space.
Below is our current config
AutoDiscoverServiceCN : Server2K7CASpd
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://legacy.domain.int/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {USChicago, UKLondon, SGSingapore}
AutoDiscoverServiceCN : Server2k7CASdr
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://legacy.domain.int/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {USChicago, UKLondon, SGSingapore}
AutoDiscoverServiceCN : Server2013CASPD01
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {UKLondon}
AutoDiscoverServiceCN : Server2013CASPD02
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {UKLondon}
AutoDiscoverServiceCN : Server2013CASDR02
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {UKLondon}
AutoDiscoverServiceCN : Server2013CASDR01
AutoDiscoverServiceClassName : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri : https://autodiscover.domain.int/autodiscover/autodiscover.xml
AutoDiscoverServiceGuid : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope : {UKLondon}
I believe that we should change the AutoDiscoverServiceInternalUri on the two 2007 CAS to ALSO be the same as our 2013 CAS.
We know that when Outlook is opened, Autodiscover will respond with any of the 6 available CAS, and we think that those Outlook clients that are misconfigured, are those that are not getting notified when their Mailbox is moved to E2013.
Thanks

We are also getting inconsistent results using the Test-OutlookWebServices PS
Test 1
Test-OutlookWebServices -Identity [email protected] | fl
Id : 1003
Type : Information
Message : About to test AutoDiscover with the e-mail address [email protected].
Id : 1006
Type : Information
Message : The Autodiscover service was contacted at https://legacy.domain.local/Autodiscover/Autodiscover.xml.
Id : 1016
Type : Success
Message : [EXCH]-Successfully contacted the AS service at https://ServerCASpd05.domain.local/EWS/Exchange.asmx. The elapsed
time was 76 milliseconds.
Id : 1015
Type : Success
Message : [EXCH]-Successfully contacted the OAB service at https://ServerCASpd05.domain.local/EWS/Exchange.asmx. The elapsed
time was 0 milliseconds.
Id : 1014
Type : Success
Message : [EXCH]-Successfully contacted the UM service at https://ServerCASdr05.domain.local/UnifiedMessaging/Service.asmx.
The elapsed time was 558 milliseconds.
Id : 1016
Type : Success
Message : [EXPR]-Successfully contacted the AS service at https://legacy.domain.local/EWS/Exchange.asmx. The elapsed time
was 46 milliseconds.
Id : 1015
Type : Information
Message : [EXPR]-The OAB is not configured for this user.
Id : 1014
Type : Information
Message : [EXPR]-The UM is not configured for this user.
Id : 1013
Type : Error
Message : When contacting https://mail.domain.local/Rpc received the error The remote server returned an error: (404) Not
Found.
Id : 1017
Type : Error
Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail.domain.local/Rpc. The elapsed time was 93
milliseconds.
Id : 1006
Type : Success
Message : The Autodiscover service was tested successfully.
Id : 1021
Type : Information
Message : The following web services generated errors.
Contacting server in EXPR
Please use the prior output to diagnose and correct the errors.
Test 2
Test-OutlookWebServices -Identity [email protected] | fl
Id : 1003
Type : Information
Message : About to test AutoDiscover with the e-mail address [email protected].
Id : 1006
Type : Information
Message : The Autodiscover service was contacted at https://legacy.Domain.local/Autodiscover/Autodiscover.xml.
Id : 1016
Type : Success
Message : [EXCH]-Successfully contacted the AS service at https://ServerCASpd05.Domain.local/EWS/Exchange.asmx. The elapsed
time was 46 milliseconds.
Id : 1015
Type : Success
Message : [EXCH]-Successfully contacted the OAB service at https://ServerCASpd05.Domain.local/EWS/Exchange.asmx. The elapsed
time was 0 milliseconds.
Id : 1014
Type : Success
Message : [EXCH]-Successfully contacted the UM service at https://ServerCASdr05.Domain.local/UnifiedMessaging/Service.asmx.
The elapsed time was 15 milliseconds.
Id : 1016
Type : Success
Message : [EXPR]-Successfully contacted the AS service at https://legacy.Domain.local/EWS/Exchange.asmx. The elapsed time
was 78 milliseconds.
Id : 1015
Type : Information
Message : [EXPR]-The OAB is not configured for this user.
Id : 1014
Type : Information
Message : [EXPR]-The UM is not configured for this user.
Id : 1017
Type : Success
Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://legacy.Domain.local/Rpc. The elapsed time was 187
milliseconds.
Id : 1006
Type : Success
Message : The Autodiscover service was tested successfully.

Exchange server 2007 still on version 8.1 even after applying sp3

hello,
I have exchange 2007 version 8.1 and I want to migrate to exchange 2013, so in order to to that I need to upgrade the exchange 2007 to sp3.
I install the sp3 without any issue but the version of the exchange 2007 still 8.1, I try to re install but it show that the sp3 already installed.
any idea about this issue?
thank you

Hi
As is well known, you
must patch Exchange 2007 to the very latest Service Pack and Update Rollup before you attempt to do anything with Exchange 2013.
According to your description, I suggest you should check the rangeUpper value by using ADSI Edit . If the value was 14625. This indicates
your schema is at Exchange 2007 SP3.
Here is the article for your reference: https://supertekboy.com/2014/05/01/check-exchange-schema-objects-adsi-edit/
Also you could re-install the patches in the following links .
Please download and install these patches from here:
Exchange Server 2007 Service Pack 3: https://www.microsoft.com/en-gb/download/details.aspx?id=24111
Exchange Server 2007 SP3 Update Rollup 10 : https://www.microsoft.com/en-us/download/details.aspx?id=36708
Hope it’s helpful to you .
Best Regards,
David

Upgrading from SBS 2008 and Exchange Server 2007 and Adding Modest Failover Protection

I haven't seen anyone describe this scenario, so maybe it can't be done, but it seems it should work. Can someone either confirm this is viable or set me straight and tell me it's not wise (and if not, why not).
I currently have SBS 2008 (2008 Server + Exchange Server 2007 + some other components). I use redirected folders so all my user data is stored primarily on the server, and then sync'd with their local harddrives for roaming use and as an additional
backup precaution. I want to upgrade to a modern version of Exchange (don't care too much about the underlying server OS, but seems like a good time to upgrade everything). I also want to improve the reliability for rapid recovery in the event of a system
failure. I have always felt nervous with SBS because it only runs on a single server.
My plan is:
Install Windows Server 2012 Standard on a new server machine
Join that new server to the existing SBS domain and sync the users, etc.
Install Exchange Server 2013 on the new 2012 Server
Migrate the existing Exchange data and account info to the new server
Demote the SBS Server and promote the new server to primary DC
Reformat the old SBS server and install Windows Server 2012 on it too, and join it to the domain as a second DC
Set up DFS Replication and keep all my user data folders between the two servers (so if one server fails, the other can take over, just not automatically like with a cluster)
Install Exchange Server 2013 on the reformatted 2012 Server box (so second instance on the domain) and set it up to sync with the first Exchange Server 2013 via DAG (so if either computer crashes, the other can take over for both Exchange Server and file
services)
Wouldn't that give me a complete slow-response failover system without the need for setting up a cluster (I know a cluster would provide instant failover protection, but I don't need that kind of speed - a manual switchover in the rare event of a server
failure is acceptable for us)? I could do this using cheap hardware for each server, because unless both servers fail at the same time, clients can point to the other server. And because it's not a formal cluster, I don't need to buy anything for a shared
SAN. This seems like such an obvious more cost-effective solution for a small network, I don't understand why this isn't a common approach, which makes me wonder if there is some reason it won't work.
Any suggestions or feedback? Are Redirected Folders still recommended for users on a Server 2012-based domain?
Thanks,
Colin
Colin

Ed, thanks again for your help. OK, so here's my updated plan (I realize I should probably check on some of these pieces on the Server group, instead of this Exchange group).
Constraints/objectives:
None of the machines are truly server grade hardware, but only 5 people on the network, so performance is generally not an issue, unless a given server is just pegged on CPU or HD due to its own internal maintenance tasks and can't respond to user requests.
Haven't seen any problems, since upgrading server from 4GB RAM to 8GB a few years ago.
Not going to buy any new hardware at this time, but do have several unused consumer-grade computers I can deploy as wimpy or moderate servers.
Main issue is to limit repair time in the event of a system failure (instant failover is not required, but want to be able to restore network functions within less than 24 hours in the event of a hardware failure) and minimize time spent on IT
maintenance.
Because of light IT maintenance (not anyone's primary job and we're too small to justify a dedicated IT person or to pay for outside help), almost every touch takes me research and time to re-learn what I haven't done in weeks, months, or years -- so also
want to keep all IT tasks as simple as possible.
We philosophically want to invest now for the next 5 years and avoid ongoing cloud fees (so zero interest in Windows Server Essentials with Exchange Online)
A little nervous about using VM's, just because I never have before, but I do respect that's probably the right way to do many of these things...
Currently I have SBS 2008 (Windows Server 2008 R2, Exchange Server 2007, WSUS 3, all with latest SP's, also includes SharePoint and other stuff, but I don't really care about most of it) on a single 8GB consumer grade system, which functions as a file
server and Exchange server. We use Redirected Folders and Offline files for all users, which works great for us and provides additional file redundancy (if server goes down, all of each user's files are also on their own machine and they can even continue
to work just fine w/o the server, losing only ability to send and receive e-mail). It has been sufficient, but I want to upgrade our version of Exchange and I am nervous that if that current one server fails, it would take me a long time to restore everything
from backup, easily many days, especially if I need to buy any replacement hardware. It is RAID1, so a single drive failure is easy to handle, but that's the only hardware redundancy for the current server.
New Plan:
Install Windows Server 2012 R2 Standard on a new modest machine (16GBR RAM, Core i7, 1TB RAID1 (may upgrade to 3 or 4 TB), 256 GB SSD boot drive, this had been my old personal computer)
Join that new server to the existing SBS domain (2008 R2/Exchange 2007), make it a DC, sync the users, etc.
Install Windows Server 2012 R2 Standard on a wimpy computer (4GB RAM Core i3 processor), leave it as a member server
Install Exchange Server 2013 on the wimpy new 2012 R2 Server (and nothing else, this will be dedicated to Exchange to make the most of such a wimpy machine)
Migrate the existing Exchange data from the old SBS Exchange 2007 server and account info to the new server
(or should I just create new accounts and copy the data from the user end through Outlook -- is that safer and cleaner than attempting any kind of server-level Exchange data migration?)
Demote the old SBS Server and promote the new 16GB server to primary DC. Now it's OK to take the old SBS server off the network.
Reformat the old SBS server and install Windows Server 2012 R2 on it too, and join it to the domain as a second DC (and possibly DCPROMO it to be the main server)
Install Exchange Server 2013 in a VM on the reformatted 2012 R2 Server box (so second instance on the domain for Exchange redundancy) and set it up to sync with the first Exchange Server 2013 via DAG OR set up another physical wimpy member server and install
it there. In any case, do NOT install Exchange directly on either DC.
Set up DFS Replication or a Failover Cluster (still need to research this, but I had planned on DFS, thinking Cluster required shared drive, but Ed corrected me on this) between the two DC's for redirected files and keep all my user data folders between
the two servers. We don't need automatic failover, like with a cluster, a manual switch would be acceptable, but if no additional cost or risk to clustering the two DC's, then the auto-failover protection that provides would be better than DFS.
I think this incorporates all of your points, Ed. Does this sound right now? What's your advice on #5 (how to best migrate user data)?
Thanks so much for all your help,
Colin

Is there a way to sync Pre-MS Exchange Server 2007 (Service Pack 1) Calendar?

Hello all,
I think my company must be using Pre-Microsoft Exchange Server 2007 with Service Pack 1 for our exchange server, because
I can only set up company Exchange account on MS Entourage, not the new Outlook
I can only set up the same exchange account only on iPad and iPhone (able to view in Mail, Calendar, Contacts & Reminders)
But
I am unable to use Lion's Mail, iCal and Address Book to see my Exchange account
For the moment, I am not really concern about mail and addresses,
but can I see my Exchange calendar on my desktop iCal? How do I set it up?
I guess the most obvious and straight forward way, for now, is to view on my iPad :-) But it is really funny that the iDevices are backward compatible but yet Lion OS cannot...
Thanks and cheers.

Hi,
Yes it will work, it says enterprise because it works there as well.
Thanks
Bifocals
Click Accept as Solution for posts that have solved your issue(s)!
Be sure to click Like! for those who have helped you.
Install BlackBerry Protect it's a free application designed to help find your lost BlackBerry smartphone, and keep the information on it secure.

Provisiong of users from OIM to Exchange Server 2007

Hi,
I am trying to Provisioning the users from OIM 9.1.0.1 to Exchange server 2007. For this i used Exchange Server Connector 9.1.1.1.0. By using AD_Base_connector 9.1.1.0.0 i can
provisioned the user details. But while provisioning to the Exchange server 2007 i am getting the following error
ERROR [XELLERATE.WEBAPP],Class/Method: tcLookupFieldAct ion/lookupByColumn encounter some problems: lookup Error in OIM
And i am unable to get the LookUp detais for the MailBox in Design Console as well as in the ScheduleTasks in OIM Admin Console..
Can anybody help me in solving this issue.
Thanks & Regards
SRI

Hi suren,
i am using the Remote Manager. I enabled logs in log.properties in both OIM server and Remote Manager.
I am observing the following message in Remote Manager command prompt.
DEBUG,30 Mar 2010 01:12:44,437,[XELLERATE.REMOTEMANAGER],Class/Method: RMISSLCli
entSocketFactory/createSocket left.
and i am getting the error in Weblogic server command prompt.
Running ISADAM
Target Class = java.lang.String
Running GETATTRIBUTEHASH
Target Class = com.thortech.xl.util.adapters.tcUtilHashTableOperations
Running Set User Attributes
ERROR,30 Mar 2010 01:13:39,484,[XELLERATE.WEBAPP],Class/Method: tcLookupFieldAct
ion/lookupByColumn encounter some problems: lookup Error
can u help me in resolving this issue.
Thanks in Advance,
SRI

Need Documentation on how to intehrate Exchange server 2007 with SAP portal

hi,
i need some documentation on how to integrate microsoft Exchange server 2007 with SAP portal.
can anybody help?

Hi Payel,
Pls check the links below..
<a href="http://help.sap.com/saphelp_nw2004s/helpdata/en/7a/ec015c8446d447a83776d40f31c84f/content.htm">Link</a>
Note : As specified in the document, only the following versions of Microsoft Exchange server are supported:
● Exchange Server 2000
● Exchange Server 2003
Regards,
Venkat.

How to setup microsoft outlook 2011 with exchange server 2007

How to setup microsoft outlook 2011 for Mac with Exchange server 2007?

The folks who set up the Exchange Server should be happy to help you.

M4E with N73 - MS Exchange server 2007

Hi Guys,
maybe I am stupid, but I can't seem to get this thing to work,
I have installed mail for exchange 2.3, finally the security setting is showing, I have approved the certificate but still I am getting the very general :
"Error in Exchange server. try again later."
to explain my steps:
1. configure the connection to use the HSDPA/Cellular link.
2. hostname: owa.domain.com , username and password.
server is Exchange server 2007 and configured behind an ISA server. OWA 2007 from a browser works fine.
please any assistance would be great, I don't even know how to approach it anymore.
thanks in advance,
Badsyntax (Simon)

Hi Imran,
As per my information Webcenter Suite 10.1.3.2 does not have any direct integration capability with MS Exchange Server due to DEEP LINK LIMITATION. Only possible work around is go for External Application SSO registration and then render that URL in IFRAME.
As far as WEBCENTER INTERACTION is concerned i think its seprately licensed and eventhough it's free you need extra Hardware to Install and Configure.
Regards,
Vindhyachal Sharma

HELP - Exchange Server 2007 Transport Rule Issue

Hi all,
sorry if here is not the place to put my question but I did not find another forum, so if anyone can help me I appreciate.
- I have an Exchange Server 2007 SP3 environment with 1 MBX Server and 3 CAS/HUB Servers.
- I have created a Transport Rule that said:
"all emails that have @test.com in BCC field are dropped off except one group can send" .
The issue is the rule doesn´t work.
Anyone can help me, please?
Thanks in advance.
Luiz

The Exchange previous versions forums are here:
http://social.technet.microsoft.com/Forums/en-US/category/exchangeserverlegacy
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange Server 2007 migration

Similar Messages

Maybe you are looking for