Relay issue from Unix across Exchange 2003 OWA server in Exchange 2010 environment

Hi,
I'm trying to resolve an issue. We have one Exchange 2003 server left in our environment. The rest is now Exchange 2010. We are working to decommission this server. Monitoring the SMTP logs, I am working with the various groups to get the traffic
off this server and onto the Exchange 2010 environment.
The issue we are finding is with a work flow. This Java app for eBis sends email to users. This is done correctly through Exchange 2010 and gets delivered from our HUB/CAS servers to the target user mailbox. This email has several links the user must click
for approving or rejecting requests. Upon clicking Approve, a new email window opens (we use Outlook 2010). The TO address is in the format of [email protected] Upon clicking Send, our Exchange 2010 HUB/CAS servers accept the
email, because one of our send connectors has, as address space, *.domain.corp. However, the email address being used it not an alias on any Exchange 2010 mailbox, so it appears Exchange 2010 is sending this email on to the Exchange 2003 server, which
also is an SMTP server. I *think* this server is looking at the address after @ to determine where to send it (ebisserver.domain.corp, which is valid in our DNS), and sends it on to that server, where the java "listener" program intercepts
the mail, processes it and then saves it to a file somewhere.
We are at a loss as to how to get Exchange 2010 to do this instead of Exchange 2003... once this traffic is eliminted from Exchange 2003, I can proceed with decommission of this server. Any help troubleshooting this issue is appreciated.

The only reason the Exchange 2010 server would route outbound mail through an Exchange 2003 server is that you have an SMTP Connector defined on the Exchange 2003 server that has a more specific domain than you have on the Exchange 2010 server. You
should be able to see all your Send Connectors (an SMTP Connector on Exchange 2003 looks like a Send Connector in Exchange 2010) by running Get-SendConnector.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Similar Messages

How to delete string or line from unix file(dataset) of application server

Hi All,
After transfer workarea information or all records into dataset(unix file). When I see the file in application server automatically the last line is shown a blank line. I am not passing any blank line.
I have tried for single record than also the file generates the last line(2nd line) also a blank line.
When I m reading the dataset, it is not reading the last blank line but why it is showing the last blank line?
How to delete string or line from unix file(dataset) of application server?
Please give your comments to resolve this.
Thanks
Tirumula Rao Chinni

Hi Rio,
I faced similar kind of issue working with files on UNIX platform.
The line is a line feed to remove it use
DATA : lv_carr_linefd TYPE abap_cr_lf VALUE cl_abap_char_utilities=>cr_lf.
DATA : lv_carr_return TYPE char1,
         lv_line_feed   TYPE char1.
lv_line_feed   = lv_carr_linefd(1).
lv_carr_return = lv_carr_linefd+1(1).
Note: IMP: The character in ' ' is not space but is a special
character set by pressing ALT and +255 simultaneosly
REPLACE ALL OCCURRENCES OF lv_line_feed IN l_string WITH ' '.
REPLACE ALL OCCURRENCES OF lv_carr_return IN l_string WITH ' '.

Have you moved from Unix/Oracle to Windows/SQL Server

I am looking for people that have moved from Unix/Oracle to Windows/SQL Server...
Would you do it again ?
Did you save money ?
Were you using Zones to virutalize on Unix ?
Did you gain or loose overall Performance ?
Have you had to perform a recovery on SQL Server ?
Have you done a recovery in Oracle ?
Were you using Rman ?
Which worked better ?
We are going through an analysis of does it really make sense, save money and effect performance to move from a strong unix/oracle environment to a MS/SQL environment.
THanks Rob
[email protected]

Hi,
All our R/3 legacy systems are Windows/Oracle.
All the new systems (BW, SRM, CRM, XI) are Windows/MSSQL.
It was an order from the management to make the switch because of the high prices of Oracle licences.
The official motto is now Oracle on Unix only and SQL server on Windows only.
We get the same level of performance as with Oracle, but we, old SAP Oracle grumpy admins, are much more comfortable with Oracle admin than SQL server admin.
imho, SQL server may seem simplier but it is much easier to look under the hood whith Oracle.
We have to reinvent the wheel and it's kind of frustrating but we will cope with it...
I would say that SQL server is not a good choice for BW usage because there is a lot more litterature on BW database optimisation for Oracle than MSSQL.
The official SAP class does not speak at all about SQL server but has several chapters on Oracle...
Regards,
Olivier

Exchange 2003 OWA + Blackberry Internet Service : very weird issue

Hi,
We use OWA protocol for retrieving the emails of our company which has its own domain : @eyeka.com.
Here are 3 scenarios of mail sending from a Blackberry device :
1) When a message is sent to an external address (i.e not with @eyeka.com), say yahoo, hotmail, gmail (...), the mail is sent properly and the device show a "OK" status for the message. The recipient will receive the e-mail without problems, and the proper behavior would be that the mail will appear in "sent Items" in the Exchange account. It doesn't, when connecting to OWA interface, we see that the mail is stuck in the Outbox folder!
2) When sending a message to an internal address (@eyeka.com), the mail is sent properly and is present in Sent items (nothing in Outbox).
3) When sending a message to an external address with an internal address as second recipient of "To" or "Cc", the mail will act as scenario 2 : it's OK.
We have no problem with OWA, we use Entourage (mac), and by Web, we never encounter such issues. All blackberry have no problems with retrieving and sending mails, but why the hell would each mail be stuck every time we send to an external address ?
It's a very awkward situation as every time the Exchange server is restarted, every items stuck in Outbox is re-sent again to recipients!
Any help of you guys will really be appreciated, I'm desperate.
Cheers,
Eric P.

Hi have the same problem.
But for me, if i sent an email to an internal person, i got the same problem.
I have my server reboot and all message i sent (about 2000) was resent to all people. (3 times because my server crahs 3 time during the week end)
I try to reset my blackberry - same problem
i try to reset my bis.na accout - same problem
i update my blackberry - same problem.
Next step :
re-install service pack on exchange server 2003
to try this : http://support.microsoft.com/kb/948984
to try this : http://support.microsoft.com/kb/948716/en-us
"Start"
"Settings"
"Control Panel"
"Mail"
"Data Files"
"E-mail Accounts"
Double Clicked on "Microsoft Exchange Server"
Removed the check from "Use Cached Exchange Mode"
"Close"
"Close"
Need help too, if anybody have a solutions.
Exchange 2003 Version : 6.5.7638.1
Outlook 2007 Version : 12.0.6514.5000 sp2 mso (12.0.6425.1000)
blackberry v: 4.5.0.127

Upgrading from Exchange 2003 Bridgehead servers to Exchange 2010 Transport Hub servers for routing SMTP only

Our company moved from on-premises Exchange 2003 to Office365 and only have 4 Exchange 2003 servers on-prem that we use for Routing email from application servers to Office365. We need to migrate these servers to Exchange 2010 then to Exchange 2013 and
only route email only. Is it possible to upgrade to Exchange 2010 by installing the transport Hub & Mailbox server options only? Our OAB and EWS services come from the CAS servers located on Office365 so we should not need a CAS server to set up Transport
rules or route mail would we? Any assistance with this would be greatly appreciated! - Thanks, DWB
Dave

Since it is not internet facing we will not have to worry about configuring an Internet Domain Name when installing the first server, correct? in my planning I was going to
install the Exchange 2010 CAS/Mailbox/Transport Hub roles on one server, then upgrade it to Exchange 2013. Once this is completed I'll then install the 2 mailbox role servers in one Datacenter, and 3 more in our DRP DC. If something happens to the
primary Datacenter I would want it to fail over to the other site. For this I would have to install another CAS/mailbox server in the secondary DC. Would this plan sound about right? Since we moved to Office365 in 2010 I have not had a chance to deal with
actual servers except for the Exchange 2003 servers we still have on-premises. Each of these are located in 4 Regional offices along with single Windows 2008 R2 servers using only the IIS SMTP service for routing mail from on-prem application servers
and print/scanners which email back to the users. The plan is to move to a routing system which will provide both MTA and redundancy if one has an issue.
Dave

Migration from an exchange 2003 organisation A (Exchange 2003 sp2) to another Exchange 2010 organisation B

Hello,
We have two Exchange organisations:
- A (Exchange 2003 SP2)
- B (Exchange 2010)
we want to migrate from A to B. the two organisations have to coexist during the migration (6 months). during this time the users have to share the same GAL and Calendar (Busy/Free informations).
What are the steps to follow ?
is there any docs/links treat this subject ?
Regards

Hi,
You can use FIM for GALSYNC.
REF:http://setspn.blogspot.in/2010/05/global-address-list-synchronization-gal.html
For calendar sharing follow the below blog:
REF:http://blogs.technet.com/b/exchange/archive/2011/03/28/iorepl-and-exchange-2010-sp1.aspx
Regards
Vickram

OUTLOOK 2013 permission shared calendar Free/Busy doesn't work for some the users Exchange 2010 and Exchange 2003 that use outlook 2007/2010

Hello,
We are in coexitence organisation (transition Migration) Exchange 2003 sp2 and Exchange 2010 sp1.
Users in Exchange 2003 use outlook 2007 and outlook 2010
Users in Exchange 2010 use outlook 2007, outlook 2010 and outlook 2013.
Issue: users in Exchange 2003 can't open outlook 2013 user calendar when he has Busy/Free information as default permission in his calendar.
User in Exchange 2010 with outlook 2007 can't also open outlook 2013 user calendar when he has Busy/Free information as default permission in his calendar.
Is it normal ? or exist some configurations to do in order to coexist all thoses clients and servers ?
Thanks in advance

Hi,
Does this issue occur on Outlook only or both Outlook and OWA?
Since you have double checked the permissions via multiple methods, it seems there is nothing problem on permission. Please make sure the migration from Exchange 2003 server completed successfully.
If in OWA everything goes well (cannot see details), it should be an issue on the Outlook client side.
I suggest run Outlook under safe mode to avoid some AVs and add-ins.
I suggest re-create profile to refresh the caches.
Thanks
Mavis
Mavis Huang
TechNet Community Support

SBS 2003 to Server 2008/Exchange 2007

We are in the process of moving our location and are in need of moving
from SBS to something with more CALs. I want to make this as seemless
as possible for the end-users.
We are currently on SBS 2003.
My plan:
Purchase new 64 bit server with Server 2008 and Exchange 2007.
Add new server to existing domain.
Move/migrate exchange from SBS to new server.
Make sure the user info and and Group profiles move to the new server
(not sure how to do that)
Remove the SBS, and promote the new 2008 to DC.
Possibly rename the 2008 to the same name and IP as the old SBS (so
outlook users do not have to change anything)
Would that be the correct route? If so, what am I missing? (Looks
easy on paper)
Thanks,
Mike

hi
here is a lead
Start by installing Windows Server 2008 on the server you’re intending on using for mail. In our example we installed all the Exchange functionality on a single server – in practice you’ll probably want to separate out the Hub and Storage
functions, and use a separate Edge server for mail traffic and user access to mail. There’s no problem with connecting to the network while you’re doing the install – Windows Server 2008 installs as a workgroup server – and you’ll
automatically be delivered the latest drivers and the most up to date OS patches. You’ll also need to give the server an appropriate fixed IP address, as it’s going to become a key component of the network infrastructure.on the role and feature-based
install model introduced with Windows Server 2003 and enhanced in Windows Server 2003 R2. Make sure you use these tools to install Internet Information Server – as Exchange 2007 will use it for Outlook Web Access and Exchange ActiveSync. Exchange 2007
requires that servers have the PowerShell management scripting environment and the
.NET framework. We’d also recommend installing Terminal Services as part of any Windows Server installation, as using Remote Desktop to access the new server and the existing SBS 2003 domain controller will let you handle much of the
migration process from the comfort of your desk.Once Windows Server 2008 has been installed, take out the install DVD and shut the server down. As you’re going to be adding a Windows Server 2008 machine to what’s really a Windows Server 2003 network,
you need to upgrade the Active Directory schema on our SBS 2003 server. This will allow you to manage the Windows Server 2008 machine from the SBS 2003 machine. You may need to update your version of Remote Desktop to one that supports the latest versions
of the RDP protocol.Put the Windows Server 2008 DVD in your SBS 2003 machine’s DVD drive (a network accessible DVD drive is suitable, especially if access to any machine room is limited, and you’re using Remote Desktop to manage
the server). Open a command line and change directory to SOURCES\ADPREP. You need to use ADPREP.EXE to update the Active Directory schema. Start by typing the following command to update the Active Directory forest.adprep.exe /forestprep.This will
begin the process of updating the schema. Be prepared to wait some time, especially if you’re working with SBS 2003 rather than SBS 2003 R2. Once the forest schema has been updated you can update the domain schema. Type the following command:adprep.exe
/domainprep.You’re now ready to bring the new Windows Server 2008 machine into your existing domain. Turn on the server, and then log in as a local administrator. Again, you can use Remote Desktop to work with the server, so you don’t need
to sit in the machine room.to the existing SBS-managed domain. Once the server is part of the domain, you will to promote it from a member server to a domain controller. Launch DCPROMO
using the Start menu search bar to find the program. Choose to add a domain controller to an existing domain. You’ll need to use the credentials of an existing domain administrator to start the process.Make the server a Global Catalog server.
If you’re going to be keeping the existing SBS 2003 system there’s no need to make the new server a DNS server. DCPROMO will then add the requisite Active Directory Domain Services to your Windows Server 2008 machine. This can take some time, especially
if you’re working with a large SBS-managed network with more than 50 users. Once the DCPROMO process is complete you’ll need to restart the server. You can now log in as a domain administrator.Now you can start the process of installing Exchange
2007 on the new server. There’s one key issue that needs to be dealt with first. Exchange 2007 needs to install on a server that’s a Schema Master.
One of the limitations of SBS 2003 is that the SBS server needs to own all five of the FSMO
roles. The Flexible Single Master Operations are key domain management tasks, and in a standard Active Directory implementation, these roles can be parcelled out across several servers. Microsoft’s restrictions on SBS can be overcome –
as the SBS licence allows FSMO roles to be temporarily transferred to other servers for the purpose of server migration and major hardware upgrades. You can continue to run SBS for up to seven days (there is an option to install an update that extends this
to 21 days) with the FSMO roles on other servers. Don’t let the migration drag on as after that point, the server will reboot every hour, until the roles are transferred back.You’ll need to be logged in to your SBS server to move the Schema Master
to the Windows Server 2008 machine. Start by registering SCHMMGMT.DLL. This allows you to use the Windows Schema Master management tools to transfer the Schema Master role to the Windows Server 2008 machine. Open a command line and type the following command.regsvr32
schmmgmt.dll
You’ll next need to open the Windows Management Console. Once you’ve done this, by typing
mmc at a command prompt or from the Run option on the start menu, you can load the Active Directory Schema management snap-in. From the File menu click Add/Remove Snap-in. This opens a dialog box where you can choose to add the appropriate
tools. Choose Active Directory Schema. This will load the schema management tools, which you can use to move the Schema Master to a new machine.In the Schema Manager console, right click on Active Directory Schema and then choose Change Domain Controller.
You’ll see a list of available servers. Choose the new Windows Server 2008 machine, and then click Change to move the Schema Master role to your new Exchange machine. Right click Active Directory Schema again, and choose Operations Master. This allows
you to make the new server the operations master for the FSMO role we’ve just transferred.
Now you can start the Exchange 2007 installation. Log on to the server, and load the Exchange 2007 DVD; using an Exchange 2007 SP1 DVD reduces the amount of time you’ll need to set aside for downloading and installing uploads. Choose the appropriate Exchange
installation for your network needs – a typical install with Hub Transport, Client Access and Mailbox roles should be sufficient for most small networks. Once Exchange has installed, restart the Windows Server 2008 machine and then open the Exchange
Management console to confirm that your install completed successfully.You will now have added your new Exchange server to the existing SBS Exchange network. On the SBS server open the Exchange System Manager.Expand the Administrative Groups tab to see the
available administrative groups. Your new server should have added itself as Exchange Administrative Group (FYDIBOHF23SPDLT). Do not move it out of this Administrative Group or the associated routing group, Exchange Routing Group (DWBGZMFD01QNBJR) –
these are required to allow Exchange 2007 to interoperate with Exchange 2003. (As a side note, there’s definitely a sense of humour in the Exchange team at Microsoft, as the default administrative group and routing group names are both Caesar Ciphers
of EXCHANGE12ROCKS).If you’re planning to run the two servers together, you can now move the Schema Master FSMO role back to the SBS server; if you’re not, you now have seven days to finish your complete server migration before the reboots start.
To move the role back use the Active Directory Schema MMC snap-in and change both Domain Controller and Operations Master to point to your SBS server.Now you can start to move mailboxes between the two servers. This is where things can start to take time,
so schedule mailbox moves for evenings and weekends – and make sure that you’ve backed up all the existing mailboxes before you start the migration.
You’ll also need to make sure that both servers have the same mailbox size limits – otherwise large mailboxes will fail to move successfully. If you’re unable to make moves at night, you can do them during working hours –
but users will be unable to connect to the Exchange server while their mailboxes are being transferred (remember to warn them in advance). Any mail that’s been delivered to the server during a mailbox transfer will be queued and delivered once the mailbox
is on the new server.
The actual process of moving mailboxes from the SBS Exchange 2003 server to Exchange 2007 is relatively simple. Log on to your Exchange 2007 server, and open the Exchange Management Console. Expand Recipient Configuration, and select the Mailbox
view. This lets you see the organisation’s mailboxes, along with where they’re currently stored. A pane on the right gives you various Actions you can perform on the mailboxes. These include the Move Mailbox wizard.
This wizard is the simplest way of moving mailboxes between servers – and, along with the underlying move – Mailbox PowerShell commandlet, is the only supported way of moving mail to an Exchange 2007 server. If you’re moving a large set of
mailboxes it’s worth writing a PowerShell script to handle the move for you.
Use the Move Mailbox wizard to move either an individual mailbox or groups of mailboxes (shift-click to select several at once). As the wizard is multi-threaded it can handle up to four mailbox moves at once. First select the target database, and then choose
the move options. You can choose to abort the move if corrupted messages exist, as well as choosing the appropriate Active Directory servers. You can also schedule the moves for out of hours – so you don’t have to be on site for a move to take
place – as well as making sure that any moves that haven’t taken place inside a set time limit are cancelled. The wizard will check mailbox quotas before making a move to make sure that the system limits allow the mailbox to transfer to a new server.
Once a move’s started you’ll see a progress bar showing the status of the move, with descriptive text for the current step in the move process. When a move completes there’s a summary screen with the results. There’s also an XML
format report you can use for further analysis.
We found that a large 4GB mailbox took about 3 hours to move, over a gigabit network. In practice, most mailboxes are a lot smaller, so expect to be able to move many more SBS mailboxes in a single overnight session. Once the mailboxes have been moved, your
Outlook users will automatically be switched to the new Exchange server. There’s no need to change anything on the desktop – the Exchange organisation will handle the changes for you. There’s one exception; if you have used a self-certified
certificate for the SBS Exchange server, you may need to delete it from all client devices (including Windows Mobile) so they can connect – especially if you’re using the same external DNS name.While Outlook handles the changes gracefully, things
aren’t so easy for users working with ActiveSync connections to mobile devices or for secure IMAP and POP3
connections. Mobile users will need to perform a manual sync on their phone (they’ll get a message in ActiveSync reminding them to do this) and accept the server policies before mail will start arriving. POP3 and IMAP connections will only continue
to work if you make sure that your new mail server has the same external CNAME as the old SBS install. If you’re not using the same DNS name, you’ll need to recreate connections for external mail clients.
Naeem Bhatti MCITP EA, MCITP, MCTS Exchange 2007 MCSE security,MCSE AD, MCSE in Messaging, MCDST SBS2003 and SBS2008 Specialist

Exchange 2003 will migrate to Exchange 2010 or Exchange 2013

Hi,
Exchange server is on exchange 2003 on windows 2003 R2.
I had an architecture of parent & child domain controllers, Where parent company is closed Down. But we have an additional Domain Controller
of parent DC in our premise.
Due to this fact exchange organization is also unavailable & cannot make modification on my exchange server configurations (Global Settings, such as changing recipients attachment restrictions, everything is grayed out).
Is there any way where we can have staged migration. I mean can I keep old & new server running together & keep few users on new Exchange organization & rest of them be on an existing server itself. (I tried testing this too, but email delivers
to mailbox store, so, it checks a name & say “Mailbox not available”)
If I create a new domain environment, I have challenge of migrating users (This I can achieve with ADMT, but actual story starts with mailbox migration)
Real pain is, I have more than 500 users, can I achieve direct migration over a weekend. (few are POP & OWA users, around 50)
Can anyone help in this please.
Imran

So, you have exchange 2003 which is inaccessible! Database files .EDB and .STM is there, but Mailboxes are not available.
And you are planning to create new environment (As you don't have any other option).
This is a cross forest migration. Which exchange you are planning to install in new environment? I would suggest 2013.
The only available option you have (As current environment is Inaccessible), Export the PST from EDB files.
Create Mailbox on Exchange 2013 and Import the PST.
Do you have Public Folder Database?
If yes, apply the same process on it.
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

SAP to Exchange 2003 Mail Server

Hi,
We have upgraded our exchange servers to 2003 but when I point SCOT at the new SMTP node I am getting an error message on a couple of lines inthe trace:
<b>[email protected] 806
806=501 5.5.4 Invalid Address</b>when I look in SOST.
I can telnet onto the exchange server from I-series without problem.
Is there any difference in set up for an Exchange 2003 server from SAP ? We can use SMTP to this server from non-SAP.
Many Thanks
David

Hi David,
We configured SMTP on WAS 6.40 based on Note 455140 long time ago. When the exchanged server was upgraded to 2003, we simply changed the hostname in SCOT, just like what you did, and it worked.
Note 751332 says that kernel upgrade is needed to a similar message, but it was very low patch level.
One time I reconfigured the whole thing to fix an issue I don't remember now... Or make the new node look like original one by keeping same hostname/IP address?
Good luck,
Victor

Exchange 2013 OWA server accessing mailboxes on Exchange 2007

Hi All-
I just completed the installation of Exchange 2013, co-existing with Exchange 2007. I have 2013 CU1 and 2007 SP3 RU10. The issue I have is that I cannot access mailboxes existing in the 2007 mailbox servers through my 2013 OWA server. Is
there some advanced configuration that I need to do, on either 2007 or 2013? The documentation I have read seems to indicated that I should be able to use OWA 2013 to access 2007 mailbox.
TIA,
Chris

Just the HTTP 500 error through the website. I found this in the HTTPProxy logs:
2013-04-30T16:17:12.093Z,100f0d73-0d2c-4bee-aa7d-54ada2c4e050,15,0,620,16,,Owa,/owa,,FBA,True,Domain\username,,Sid~xxxxxx,Mozilla/5.0 (compatible; MSIE 10.0; Windows NT 6.1; WOW64; Trident/6.0),10.1.200.21,servername,500,,ServerNotFound,GET,,,,,WindowsIdentity,,,,0,,,,2,0,,0,,0,,0,0,0,0,,-1,0,0,3,,,,2,,,OnBeginRequest=1;,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
Unable to find proper HTTP service. ---> Microsoft.Exchange.Data.Storage.ServerNotFoundException: Unable to find proper HTTP service.    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetBestBackEndServiceForVersion[ServiceType](TopologyWithSites
topology ClientAccessType clientAccessType Predicate`1 versionNumberCondition)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetE12ExternalUrl[ServiceType](BackEndServer mailboxServer)
at Microsoft.Exchange.HttpProxy.OwaProxyRequestHandler.GetE12TargetServer(BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.BEServerCookieProxyRequestHandler`1.GetDownLevelClientAccessServer(AnchorMailbox anchorMailbox BackEndServer
mailboxServer)    at Microsoft.Exchange.HttpProxy.LatencyTracker.GetLatency[T](Func`1 operationToTrack Int64& latency)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon
beacon)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass2b.<OnCalculateTargetBackEndCompleted>b__2a()    --- End of inner exception stack trace ---;

Exchange 2010 MBX with a Exchange 2003 Frontend server. Coexist?

We currently have a exchange 2003 environment with 5 mailbox server and 1 front end server. We would like to introduce a 2010 Exchange MBX server. Is that possible? Do we just install the MBX role with CAS/HT?
Thnaks,

Hi
You need to have MBX,CAS and HUB all the three in Exchange 2010 else they wont be functioning without any one of them.
You can introduce Exchange 2010 server in Exchange 2003 server environment
Ensure you have at-least Exchange server 2003 SP2 else the it wont allow you to install Exchange 2010
You can only deploy Exchange 2010 in an Exchange 2003 organization that operates in native mode
Below article for your reference
http://technet.microsoft.com/en-us/library/aa998604(v=exchg.141).aspx
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish

Move-mailbox from forest A exchange 2003 to Forest B exchange 2010

i got this error after any idea ?
Get-MailUser "usertest" |New-MoveRequest -RemoteLegacy -TargetDatabase "test01" -baditemlimit 10 -RemoteGlobalCatalog $remoteGC -RemoteCredential $remoteCredentials -TargetDeliveryDomain $domainTarget
MapiExceptionNetworkError: Unable to make connection to the server. (hr=0x80004005, ec=2423)
Diagnostic context:
Lid: 15000 dwParam: 0x6BA Msg: EEInfo: prm[2]: Pointer val: 0x51C8A8C000000000
Lid: 16280 dwParam: 0x6BA Msg: EEInfo: ComputerName: n/a
Lid: 8600 dwParam: 0x6BA Msg: EEInfo: ProcessID: 19796
Lid: 12696 dwParam: 0x6BA Msg: EEInfo: Generation Time: 2015-01-14 20:21:54:210
Lid: 10648 dwParam: 0x6BA Msg: EEInfo: Generating component: 18
Lid: 14744 dwParam: 0x6BA Msg: EEInfo: Status: 10060
Lid: 9624 dwParam: 0x6BA Msg: EEInfo: Detection location: 318
Lid: 13720 dwParam: 0x6BA Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6BA Msg: EEInfo: NumberOfParameters: 0
Lid: 45169 StoreEc: 0x977
Lid: 52465 StoreEc: 0x977
Lid: 60065
Lid: 33777 StoreEc: 0x977
Lid: 59805
Lid: 52209 StoreEc: 0x977
Lid: 56583
Lid: 52487 StoreEc: 0x977
Lid: 19778
Lid: 27970 StoreEc: 0x977
Lid: 17730
Lid: 25922 StoreEc: 0x977
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemoteTransientException
+ FullyQualifiedErrorId : FBB4FBA6,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest

See this error, sounds like some ports are blocked between tow forests...
Check James Chong's blog post - http://msexchangetips.blogspot.com/2010/11/mapiexceptionnetworkerror-unable-to.html
Amit Tank | Exchange - MVP | Blog:
exchangeshare.wordpress.com

Exchange 2003, SBS Server, Outlook 2010, User Over Limit, 2 GIgs

I have a user's who's account is over limit. I have recently done a clean install of Windows 7 Professional and Office 2010. I keep trying to have his computer archive old emails but in the process the machine keeps hanging. I try to crash out Outlook
but the outlook.exe process will not let me shut it down telling me access denied. The only way to recover is to completely shut down the computer (which I cannot do VIA the regular shutdown option because of outlook hanging). What do I have to do to resolve
this problem? Kind of urgent as it's affecting his receiving emails.
Vern

Hello,
According to your description, the issue seems to be related to outlook profile or your PC. I recommend you check if the issue occurs when other users use the PC. If the issue doesn't occurs, it means your outlook profile should be problem.
If the issue persists, please check if there is related error in application log.
If there is any update, please free let me know.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2003 legacy server

Hi
We have 2010 exch currently and would like to upgrade to 2013.
before proceeding I have a question about exch 2003.
when exch 2003 was removed and decommissioned its not entirely gone yet we still see exch 2003 exists in organisation and we want to total remove this now.
can you please assist or suggest something please. thank you.
p.s. we currently decommissioning exch 2007 as well.
regards
KB

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

Relay issue from Unix across Exchange 2003 OWA server in Exchange 2010 environment

Similar Messages

Maybe you are looking for