Exchange 2003 compatability

hey, i'm a new mac user and have upgraded to snow leopard. my college uses outlook on the exchange 2003 server and I can't seem to set it up with snow leopard. I'm guessing it's because it's not exchange 2007. Anyone have any tips or suggestions about how to set up my college email? I'd be grateful for any help!
--Colton

I agree with David above, I purchased Snow leopard thinking it would work like my Iphone works with our office Exchange 2003 server (brilliantly). I have Snow Leopard Mail working to a fashion using the IMAP exchange account but I'm going to give up and delete it as it clearly has some compatibility issues. It is constantly in sync/download mode, often hanging. Sure it "sort of works" but it looks to me if it is trying to sync the whole account every mail every time it checks for mail rather than new messages(new sent/Inbox items etc).
Is there a way to configure the feature to work as per my Iphone which works seamlessly??? If not why not?
Another gripe I have is the total lack of support from Apple, there is no contactable support centre...well at least there isn't here in UK. Looks like Apple use these forums as product development...let the customer find a solution.
Andrew

Similar Messages

Outlook 2013 not compatible with Exchange 2003

Hello
Some of my customers bought SBS 2003 R2 just before SBS 2008 was released so they have systems which are only 4+ years old. SBS 2003 came with Exchange 2003 pre-installed. Outlook 2013 does not support Exchange 2003. So they cannot upgrade their Outlook
clients to 2013 version.
Microsoft, is this correct?!

If this post is hard to read, it's because of Dragonsoft!! (sometimes it is like auto-correct on the phone - "I said WHAT!??")
Overall I think this is the most interesting thread that I have ever read on Microsoft.com.
As a computer for professional for over 30 years, I've always followed the context that software products are designed for a three to five-year term, to have more is a luxury.
When I was first in the industry (1983), Microsoft had a tendency to change the software versions every year to two years. As we approached the era of Windows XP there was an expected lifetime use of three years. Every two years a new product would appear.
So, when windows XP lasted well beyond the three-year term, it was pretty exciting to not have to spend money on new product, and we all enjoyed the decade of Windows XP.
The new generation of IT professionals has somehow believe that software products should live more than five years, and it just blows my mind!
The reason that I make this post, is because I've used SBS ever since Back Office Server 4.5, and the versions of small business server (now called Small Business Server) have always appeared on the market 1 to 3 years after the primary versions of
Windows for which they are named. So I always felt that there was a disadvantage to using small business server in that the products appearing inside of SBS had been on the market for a few years before being incorporated into the SBS package. It
made me feel, at first, that Microsoft was waiting on the level of maturity within the product before creating the SBS package. Now that I look back on the whole process it made me think that the SBS team had some difficulty merging the products into a install
package which could handle the intricacies of the licensing limitations on the SBS system.
SBS 2003 was a great tool when it came out, but I found that it was riddled with security holes. To say the least some of my first SBS 2003 servers had their exchange system hacked by outside influences. (These were external facing servers who had websites
and exchange server running with public domain names, even though there were firewalls!) After a few patches, DNS modifications, reverse DNS entries, and some changes in the exchange system, I was finally able to make the system secure and solid.
My first real nightmare with SBS was when upgrading to SBS 2003 R2, which, yes, appeared around 2005. You cannot simply upgrade a machine from SBS to a new version. You must purchase a new server, install the new SBS version, and migrate your
entire installation to this new host. (While running SBS 2003 for several years and making backups on a tape, I realized that the new hardware on the market would not support a restore from my tape backup!) The whole process is rather daunting as not
all of the detailed steps to upgrade work as expected. I had to call, and pay, Microsoft to complete the process because exchange had trouble during the migration.
So off we went with our new installation of SBS 2003 R2. Then along came SBS 2008! I went through the same steps again... new hardware, new software, and, yes, paid Microsoft, again, for support to migrate.
When SBS 2011 appeared on the scene I was willing to upgrade again. Having gone through this, twice now, I fully prepared the client to purchase a new system and to purchase the new software. But because I was faced with the whole entire
nightmare of new hardware, migration, and having to call Microsoft to complete the process, I decided on a new approach. This time we were going to buy server which would run VMware. (I was not going to get stuck in a hardware box that I could not replace
if I ever needed to restore the operating system due to a massive failure.) So off I went, purchasing a new box, installing VMware, and installing my favorite operating system, Microsoft SBS!
Well, to say the least, it wasn't exactly as exciting as I had expected. Had some trouble getting VMware to settle into the new hardware, as there seemed to be some compatibility issues, but was able to work it out. Eventually, I was able to get started
on the migration. Things went well up until the point that I got to the exchange migration, and ran into a similar problem as before! A call to Microsoft revealed that it was even a little daunting for the support personnel, but as I documented the things
that they modified, and even performed a little cleanup, after they performed their cleanup! I can happily say that I'm no longer worried about hardware issues, when it comes to restoring my SBS server in case of a failure!
Overall I'm pleased with having used Microsoft SBS solutions over the past 10 years, but I would never expect, nor would I lead my customer to expect, that a product should last 10 years!
Previous comments have indicated that server should last seven years because they can be depreciated that way, I believe that to be entirely false! I live in Texas, and the state of Texas DIR program has adopted standards which state that
you should replace your hardware every five years! State agencies have this as a requirement, and it is not optional! Many state agencies have gone to leasing their equipment, which is a three-year term. (Where do you think off-lease equipment comes
from, anyway?)
One of my primary clients looked at me one day, and directly ask, "Okay, if we spend the $10,000 on the new server and software, how long should it last?"
Obviously, I wanted to say, "Forever!" But, remembering something that my mother had said (always plan for the worst and you always come out on top!), I said back to them, "I believe we should plan for a three-year lifespan, and if we get
any more than that, it will be a luxury." Needless to say, there have been some upgrades which lasted well more than three years, but there have been some which have been spot on.
The SBS server is a huge savings over purchasing the individual products separately. But there have always been some drawbacks during the upgrade process which makes the entire feasibility of the installation top-heavy when it comes to support costs.
I have noticed is that the SBS servers require more labor to keep them running smooth, especially with backup procedures and backup software, as SBS always requires a third-party product to make a "real" (restorable) backup.
A client's expectations should be that you are taking care of their business without them having to worry about what takes place in the tech room. They understand, and realize, that they can pay you a specific amount of money for your support without necessarily
having to purchase new hardware. But a good, healthy relationship with your client means that they should always be willing to upgrade, whether it is a workstation or server.
If you allow a client to be painted in a corner, then it's not their fault, it's your fault! Because, they have no idea what the new technology can do, and don't realize what's on the market. It's your job to keep up with what's current and to deliver
expectations which make them realize that each year has a dollar value attached to it, whether it is spent, or not.
If you have a client is unwilling to spend money to upgrade their equipment, then there's something else wrong with their business, and you should probably consider that they may not be in business for very long. So don't make it your problem when
they are unwilling to spend money. You don't work for free.
One last, quick example of the conversation that I had with a client who was unwilling to upgrade because things seem to be working so well. I put it like this, "You pay me to make certain that your business operates in good times and in
bad. Right now, everything is fine. If your building were to burn, and the only thing we had were the backups, I cannot go out and purchase new hardware and restore your system successfully. The equipment that we have operating here is no longer
available on the market. If I were to find the equipment, it would be out-of-date, and most likely, used, and I cannot guarantee its compatibility or functionality. So, if I can't restore your system to an operational status, then what would you do?
I don't believe there are any number of man-hours you can use to recover the information lost. You would probably have to go out of business! If your business becomes my business, then I would try to move to a position where my data is safe and my business
can continue in the case of catastrophe. The only way I can do this, is to purchase new hardware, new software, and put you back in a position of compatibility with the market. One of the things I always try to do is keep your business operations at a point
where if I die, someone else can come in and take my place. The whole idea here is to keep your business going."
It didn't take them long to come back and surprise me, "Make a list of what you need. Don't give us a list of what we need to get by, tell us what we need to be productive for several years. We don't want to patch this together
and always have problems."
And just as a note, your customer can write off $10,000+ per year for new equipment purchases. I think the number may be higher now. I had one customer who purchased a $15,000 system in December and wrote off $10,000 in one year and the other $5000,
a month later, in the next year!

Exchange 2003 to 2010 SP3 migrate system PF

Hello.
We on the road to move to Exchange 2010 and i have a question
Which system PF i need to replicate to Exchange 2010
I have:
Offline address book:
/o=orgname=cn addrlists/cn=oabs/cn=Defaul Offline Address Book (which replicated between exch 2003 and 2010) and subfolders there:
OAB version 2 (replicated between 2003 and 2010)
OAB version 3a (replicated between 2003 and 2010)
OAB version 4 (replicated between 2003 and 2010)
EX:/o=sovbank/ou=Exchange Administrative Group (FYDIBOHF23SPDLT) (don't have any replica at all)
EX:/o=sovbank/ou=First Administrative Group (replicated between 2003 and 2010)
Shedule and Free Busy folder which contain subfolder:
EX:/o=sovbank/ou=Exchange Administrative Group (FYDIBOHF23SPDLT) (don't have any replica at all)
EX:/O=SOVBANK/OU=EXTERNAL (FYDIBOHF23SPDLT) (don't have any replica at all)
EX:/o=sovbank/ou=First Administrative Group (replicated between 2003 and 2010)
Question is - did i add all replica right?
Can i execute MoveAllReplica.ps1 or i miss something?
P.S. We don't use EFORM so i don't repicate it at all

Each time you create a new user mailbox, the user account receive the LegacyExchangeDN property.
This property is set only once and will match the administrative group that the mailbox server belong to.
In a Exchange 2003/2010 migration, your old user will have a legacyDN strting with EX:/o=sovbank/ou=First Administrative Group[..] while the user recently created in E2010 will have EX:/o=sovbank/ou=Exchange
Administrative Group (FYDIBOHF23SPDLT) [...]
So what is the link between this and the PF? The answer is outlook.
When an outlook client, with a mailbox hosted on E2003, create a meeting request with other users and check for the availability, that query is against the public folder Schedule freebusy folder of each users.
That folder is updated, by outlook, each time you create an appointement or accept a meeting request. In the background outlook "push" your free/busy status to his "local"public folder. see here
http://technet.microsoft.com/en-us/library/aa996946(EXCHG.65).aspx
In E2010 native, the query are handled by the availability service however that service is not reachable by E2003, or outlook 2003, therefore for backward compatibility any outlook client (even outlook 2010) connected to an E2010 mailbox will also
"push" the free busy data to the local PF.
If you see "unable to read FREE busy data" when creating a meeting,between E2003 and E2010, that is because your local PF does not have a replica of that information for this user.
So to answer the question, yes the folder Shedule and Free busy -EX:/o=sovbank/ou=Exchange Administrative Group
(FYDIBOHF23SPDLT) need to be replicated on all servers.

Exchange 2003 with Windows Server 2012 DC's only. Migrate to Exchange 2010.

I have the following situation:
An Exchange 2003 SP2 server in an 2003 FFL and DFL domain with 2 Windows Server 2012 DC's. There are no Windows Server 2003 DC's anymore. Exchange 2003 is still functioning properly, but the eventlog is showing me some errors about LDAP which is unable to
find an old 2003 DC.
I know this is not supported, so we want to migrate to Exchange 2010 as soon as possible.
What is the best way to do this? Will coexsitence still work? Do I have to add an 2003 DC's again?
Please advice. Thank's in advance!

Oh thank GOD I found this thread!
I am facing a similar situation:
http://social.technet.microsoft.com/Forums/exchange/en-US/9a8bc14b-1a45-4b8b-ac3a-38d63e66a7da/exchange-predeployment-analyzer-exchange-2010-compatibility-check-does-not-recognize-windows?forum=exchangesvrdeploylegacy
And this is the first post I have seen marked as an answer by a Microsoft Contingent Staff affiliated person.
Thanks Steve and Simon, you have saved me a bunch of grey hairs.
C.
"Time is an illusion, Lunchtime, doubly so..." - Ford Prefect

How configure mail.app with webmail, exchange 2003?

Hi,
I would like to configure mail.app with webmail, exchange 2003.
I have certified file of this serverver, and the webmail used https and port 443,listener port.
And webmail address is https://webmail.abc.com/exchange.
How configure mail.app with webmail?
Best regard and I'm pleased to thank you for you kind support in advance.
nautiluzth

For the best Mac compatibility with Exchange, I suggest you use Microsoft Entourage, part of Microsoft Office.

How to synchronize iPod touch with Microsoft Exchange 2003?

I just bought the iPod touch and would like to synchronize it with my calendar and contacts. I use Outlook 2003 SP3 on PC and it is connect to an exchange-server. I have the latest version of iTunes (v7.4.3.1). When I connect my iPod (v1.1.1) to my computer, I have no problem with synchronizing music, video, pictures or Podcasts. When I look under Devices and Info-tap, I cannot select any contacts, calendar or bookmarks. Under calendar, it says: There is no supported calendar program. I have tried to read all posted threads, but non-helpful. How do I fix this, please help?

Yeah, unfortunately, Apple didn't get compatibility for Exchange 2003 working for OSX (it does for iPhone, but not desktop OSX.)
Me personally I'm on Exchange 2007, but I also use [Google Calendar Sync|http://www.google.com/sync/index.html] to sync Outlook. My Macs and iPad go directly to Google Calendar and the PC use Google Calendar Sync to sync Outlook to Google Calendar. Google Sync only works for Outlook calendar and must be Outlook 2003 or later. (I've used Outlook 2007 and currently Outlook 2010.) Google Calendar is free so this may be an acceptable way to sync, assuming your work PC has internet access and can be left on for the sync app to run.

Any ideas for how to sync to Exchange 2003 - contacts and calendar

Hi
I am still searching for a mechanism to give me the sync solution I want, which is as follows:
At work I have a PC running Outlook 2003 via an Exchange Server 2003 setup.
At home I have an iMac running Snow Leopard
In the middle I have an iPhone 3G
I want to sync Calendar and Contacts across all three machines.
I want to sync work email between the Exchange server and the iphone, but do NOT need this to sync on my iMac at home
That's it.
At the moment I can sync email, calendars and contacts successfully between the Exchange server and iPhone, using the over-the-air Exchange Sync on the iPhone. But sadly my iMac will not sync contacts and calendars to the exchange server 2003 as Snow Leopard only supports exchange 2007.
Ironically (because I don't need this bit to work) I have managed to get my iMac to sync with my Exchange server EMAIL, by selecting the Exchange IMAP option when setting up the mail account on my iMac (as opposed to the Exchange 2007 option). However, I cannot get iCal or Address book to sync with Exchange 2003, regardless of the options I select when setting up the new accounts in Address book or iCal. I guess these just do not work with Exchange 2003
I know that I cannot use mobileme as a solution, as you cannot have two over-the-air syncs going on, and I need to maintain my iphone link to the exchange server via activesync
I also know that using itunes to sync via the cable will not work, as this creates separate contacts and calendar files on the iphone and so does not provide the syncing solution I seek.
I have tried using google to act as the middle man between my iMac and Exchange server data - getting the iMac to sync to Google Calandar and Google Address Book, and then using a third party piece of software called gsyncit to sync from google to the .ost outlook file on my PC workstation. This works some of the time, but keeps crashing and leaving me with multiple duplicates to have to sort out - much too much hard work on a regular basis.
So I still do not have a solution. Unfortunately upgrading to Exchange server 2007 is not a solution.....
Any new ideas out there
Thanks

I don't think there will be a solution to this. Exchange 2003 just isn't supported.

Cannot Move Mailbox from Exchange 2003 to Exchange 2007

Hello,
I am migrating exchange 2003 to Exchange 2007 and have moved almost all the mailboxes without any issue, but there are some mailboxes which are not being moved since they are giving me the below error.
Error:
Error was found for John Doe ([email protected]) because: Error occurred in the step: Opening source mailbox. Failed to open mailbox with error: ClassFactory cannot supply requested class, error code: -1056749262
Initially I found that the account was disabled from Active
Directory so enabled it but and also replicated the active Directory but still the problem is there, its not hidden in the GAL aswell.
http://www.arabitpro.com

Thanks everybody .. I have solved the problem myself.
To resolve this issue I had to give the account "SELF" permissions for "Associated external account". If the user does not have these
permissions to its own account it is unable to set the msExchMasterAccountSID attribute for the disabled account causing the error. By setting this permission on the disabled account, it allows it to mark the msExchMasterAccountSID attribute.
To do this follow this procedure:
1. In the Active Directory Users and Computers snap-in, on the View menu, click Advanced Features.
2. In the Exchange Advanced properties of the disabled user object that owns the mailbox, click Mailbox Rights, and then search the list of accounts for one
that has the Associated External Account permission.
4. If no account has this permission, grant the SELF account Associated External Account and Full Mailbox Access permissions.
https://support.microsoft.com/kb/278966?wa=wsignin1.0
http://www.arabitpro.com

Exchange 2003 Permissions Error when attempting to forward emails

Server 2003 R2 (fully patched as of 11/2013) running Exchange 2003 SP2 (Built 7638.x2) on ESXi 4.1; WinXP clients and Server 2003 Terminal Servers running Outlook 2003; Domain and Forest are running at 2008 Functional Levels.
Occasionally, some users are receiving this error message: "You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator" intermittently when attempting
to 1) forward email both to and from senders/recipients inside and outside the domain, 2) When attempting to modify the subject of a previously received email (I didn't know you could do that), 3) When attempting to open received attachments.
There is no discernible pattern to the users or the original senders of the emails.
Most of the results I've found when searching relate to NTFS permissions or a ReadOnly propery on items in the users's profile folder, or sending on behalf of another user - these either do not apply or have been verified as not the cause.
During the initial rash of problems when there was a problem with an attachment and we absolutely needed it, I was able to connect to OWA using a special administrative account with access to the mailbox, open the attachment and log out. Once I had
done so with this account, the end user was able to open the attachment on their own without a warning.
Changes made to the environment prior to this issue that may be related (nobody remembers when exactly this started, so I can't state that it definitively happened after this change):
All servers were virtualized on ESXi 4.1 in late 2011; subsequently converted and migrated to Hyper-V Server 2012 in early 2013 (with the exception of the Exchange and SQL servers).
All 2003/R2 domain controllers demoted and removed; DFL/FFL raised to 2008; SYSVOL replication was migrated from FRS to DFS-R.
Troubleshooting steps:
Exchange server and affected client computers have been restarted several times; the various exchange services have been restarted; permissions on the mailboxes and AD objects have been verified; event logs are generally clean with the exception of ActiveSync
errors for a single user not currently affected by forwarding emails, there are no other errors reported.
Per recommendations on another forum, I had enabled several diagnostic logs in the diagnostic logging tab of the server. Unfortunately not much was found in the Application log even after filtering out the basics. There were occasional errors
referencing User A failed to modify an item in User B's mailbox because access was denied; however, I was unable to correlate these errors to any reported incidence of the above message.
I created a new mailbox database on the same server and migrated all the mailboxes to the new database, there was no change; users immediately began seeing these errors.
Over a holiday weekend, I then spun up a new Win 2003 R2 server, with a fresh installation of Server 2003 R2 (also fully patched through 11/2013) running the same version of Exchange 2003 SP2 this time running as a virtual guest on Hyper-V Server 2012.
I migrated all mailboxes from the original mail server to the new mail server and it appeared that the problem was remedied; however, it has slowly started up again and is starting to become more frequent.
I'm really at my wits end with this problem and would like to get it resolved before we purchase and install our new Exchange Server later this year.

Updates
Users have reported that they can forward the email from OWA; even after doing so, they are unable to forward from Outlook. So either my previous notes on the issue were wrong, or this is just more of the "intermittent" nature of the problem.
I will have to investigate what logging options are available to me at the Outlook client level - any thoughts on that subject are also welcome.
Users have now reported that a previous (rarely used) workaround (the administrative account opening the email in OWA) no longer enables them to view attachments or forward emails in Outlook.
I'm still adjusting the various diagnostic logging settings to see if I can spot an event which corresponds to a reported occurrence. The most unusual warning reported is the following:
Source:MSExchangeIS Mailbox Store
Category: Access Control
Event ID: 1029
[email protected] failed an operation because the user did not have the following access rights:
'Delete' 'Read Property' 'Write Property' 'Create Message' 'View Item' 'Create Subfolder' 'Write Security Descriptor' 'Write Owner' 'Read Security Descriptor' 'Contact'
The distinguished name of the owning mailbox is /O=DOMAIN/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=USER_B. The folder ID is in the data section of this event.
However odd these occasional warnings are, they do not appears to correlate to the reported permissions issue. Everytime I've seen one of these events, I've inquired with "user_A" to see if they've recently seen the popup and in each case they have
not.

Unity 4.2 voice mail only with Exchange 2003

Hi Team,
we are replacing window 2000 OS with Win 2003 for unity 4.2. This is a single box solution. Exchange 2000 is installed on same unity server. Now we are upgrading the OS from 2000 to 2003. With window 2003 we have to installed the Exchange 2003. In unity installation 4.0(5) following paragraph is mentioned which means we need separate hardware for Exchange. Kindly advise whether we need a separate server for Exchange 2003 or we can install on the on unity box.
If you are using Exchange 2003, install Exchange 2003 administration software on the Cisco Unity server. (Exchange 2003 is installed on a separate server.)
If you are using Exchange 2000, you can install Exchange 2000 either on the Cisco Unity server or on a separate server. If you install Exchange 2000 on a separate server (typically for systems with a large number of subscribers), install Exchange 2000 administration software on the Cisco Unity server.
BR
Muhammad Irfan

Thank you Javalenc,
I can understand from following that Exchange 2003 can be installed on same server.
Voice Messaging
•Exchange 2003 on the Cisco Unity server or on a separate server. If you want to install Exchange 2003 on the Cisco Unity server, note the following:
–The Cisco Unity server must be running Windows Server 2003.
–Exchange 2003 can be installed only on the currently shipping servers supported for use with Cisco Unity 4.2 (MCS-78xx-x2, MCS-78xx-x3, or later, including IBM and HP equivalents). Currently shipping servers are listed in the Cisco Unity Supported Platforms List at http://www.cisco.com/en/US/products/sw/voicesw/ps2237/
As you know we are just replacing the OS, from win 2K to 2k3. So any thing I need to take care to back up the existing Unity with win 2000 and exchange 2000..
I am taking the back up of my unity 4.2 installed on window 2000 with DiRT and will restore on unity 4.2 with win 2003 and Exchange 2003.
Kindly advise.
BR

Exchange 2003 & Mail not syncing

All,
In Leopard Mail, I have a .Mac account as well as an Exchange account set up with the Exchange server where I work. The .Mac account works great, does everything I want it to do; the Exchange account, however, simply will NOT sync email & what I do with it with Exchange.
For the Exchange account setup, I have Mail set up to "Move Deleted Messages to the Trash Mailbox" checked, to "Store Deleted Messages on the Server," and to "Permanently Erase Deleted Messages When: Quitting Mail."
So during the day, I'll move some messages to the Exchange folders that Mail did set up correctly, delete messages I don't want anymore, and then I'll hit "Synchronize All Accounts." When that's done, I quit Mail.
About 5 minutes or so later, I'll log in to Windows using Parallels, open up Outlook, and see that the ENTIRE DAY'S MESSAGES are still in the Outlook inbox. They're shown as "read," but none of the messages that I'd moved to other folders in Mail or the ones I deleted in Mail are appropriately placed where they should be (either in their respective folders or in the "Deleted Items" folder in Outlook).
Is anyone else having this problem?
I do have a copy of Entourage 2008 with Exchange support, and that works fine (though it tends to crash 2-3 times per week). The thing is, I don't really like Entourage, am used to Mail, and prefer it to Entourage...and badly wish I could get Mail to work correctly with Exchange (2003).
BTW, our Exchange server does have IMAP turned on, which works great with the iPhone. But Mail just simply won't work with Exchange no matter what I try.
Any hints/ideas/something obvious I'm overlooking?

We are having problems where I work as well. The problem is that Mail is constantly syncing with the server and takes FOREVER to complete it. I've tried every combination of settings you could do in Mail, and we've had both Mac & PC IT guys in that can't figure out why it takes so long to sync, and why it feels it's necessary to sync when I simply click on my Sent folder, or Trash folder...any little click causes the program to want to sync something. Even my calendar events of which i have zero, take 10 - 15 minutes to sync.
Can anyone suggest a fix to my problem or the original poster's problem?
Thanks in advance.

IPhone 3G will not sync with Exchange 2003 after updating to 4.0.1

I keep reading a lot of posts about users who updated to 4.0 not being able to get Exchange to sync and 4.0.1 was supposed to fix that however I just updated from 3.something to 4.0.1 and now my Exchange 2003 server email will not sync (kind of) and my Contacts are slowly disappearing.
I tried to delete and re-enter the exchange account however after 5 hours I only have about a dozen emails out of the hundreds that should be there. Also the contacts that were there are now slowly disappearing.
I saw somewhere that I should try to access www.myserver.com/oma and www.myserver.com/exchange to see if I can log in there. I am able to get into OMA without an issue however when I go to /Exchange I am able to login and get the left window pane to start (inbox, contact, notes, etc buttons), but no other pane has anything.
I don't know if this is related, but I did notice that on some sites that use script for the menus I am no longer able to navigate the menus. They drop, but clicking a link in the menu does nothing.
I have another 3G that is working fine with the 4.0.1 and all the BB and Windows Mobile and Droids are working fine.

You know, yesterday I deleted the entire Exchange account, rebooted, added it -- nothing... then I deleted it again, rebooted again, etc... after about the 3rd time of doing this and allowing the Internet Accounts to automatically discover the account, it started working again.
You might want to give it the brute-force-angry-uninstall-and-reboot-multiple-times-while-shaking-angry-fists -and-cursing routine and see if that helps you!

I bought a new imac running Loin and Office 2011. The server we use to access emails runs exchange 2003 and my IT person says the imac is not compatible with the server. The server does not want to let me access using any email software.

I bought a new imac running Loin with Office 2011. I am the only mac in the office and the Server we use to access emails runs exchange 2003 and my IT person says the imac is not compatible with the server. The server does not want to let me access using any email software other than webmail access through our website. It looks as though 2011 is not compatible with 2003 per some searches online, but what are some options I have to gain full access again? I purchased parallels in hopes that this my help and I am able to use remote desktop connection to log on to server but can not drag and drop files I need. There is a shared drive on that Server we all use to exchange files.
The two main issues are gaining access to my email again and ability to drag and drop files from mac to pc. I hope this is enough info to get some solutions.
PS - IT person says my iMac's IP is what his server does not understand so that is why I can not login.

Office 2011 is not compatbile with Exchange 2003.
I suggest you post further Office related questions on Microsoft's own forums for their Mac software:
http://answers.microsoft.com/en-us/mac

Trying to recover a mailbox from an old Exchange 2003 server

I still have a 2003 server in my environment but all functions and mailboxes are on Exchange 2010. The only reason the 2003 server is still around is for the off chance of requiring a restoration which has now come up. I have successfully restored a
mail store to a recovery storage group but I am unable to export mailboxes from it using exmerge.
I get the following error:
[10:16:16] Copying data from mailbox 'Jacques Legare' ('LEGARE') on Server 'MAIL-SERVER' to file 'C:\TEMP\LEGARE.PST'.
[10:16:16] Error opening message store (MSEMS). Verify that the Microsoft Exchange Information Store service is running and that you have the correct permissions to log on. (0x8004011d)
[10:16:16] Errors encountered. Copy process aborted for mailbox 'Jacques Legare' ('LEGARE').
I have read many, many articles regarding the requirement for “send as” permission. I have granted send as permissions to several different domain accounts and local accounts on the Exchange server but I get the same result with all of them.
It looks like the problem may be because the mailbox no longer exists on the Exchange 2003 server.
So what do I have to do to recover this mailbox? Can I create a mailbox for this user on the 2003 server without messing up his the mailbox on the 2010 server? Instead of restoring to the recovery storage group, should I restore and overwrite the original mailbox
store? Again, will that mess up anything with the 2010 server?

0x8004011d is permission related Error.
Refer to the link below and download EXMERGE guide which has complete procedure documented.
https://gallery.technet.microsoft.com/office/Guide-to-Use-Exmerge-to-fd00af49
If the mailbox that need to be restored has to be extracted from RSG is already moved to Exchange 2010 then you will not be able to run exmerge against it.
You might have to update the attribute MsExchOrigMDB on the RSG to point to Exchange 2010 Database where the mailbox is now located.
even this information is enclosed in the EMERGE Guide.
Revert back for any queries/outcome.
Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

Account Lockout issue between Apple devices and Exchange 2003

I have been having an ongoing issue for a couple of months with a few different users Apple devices locking out their accounts in AD when they try to authenticate to ActiveSync. This doesn't happen every time they authenticate, it seems to be random,
while the rest of the time they have access to their email. It might occasionally happen with an Android, but not on a repetitive basis like this.
Primarily this has been four different iPads, running different versions of iOS, and an iPhone running the latest release of iOS 7. Other iPhones and iPads function without having the problem, including iPhones on iOS 7.
The user accounts in question are set to never have their passwords expire, but again, they aren't the only users that are set like this, and those other users, even with Apple devices are not having the same problem.
I used NetWrix to trace out the source machine, which is my Exchange 2003 server and times, and I've checked the W3SVC1 log file, and come up with the following as an example with identification details masked:
<internal IP>, <Domain\Username>, 4/30/2014, 8:10:04, W3SVC1, <ServerName>, <internal IP>, 15, 329, 3367926, 200, 0, GET, /exchange-oma/<[email protected]>/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/iPad/ApplV50462*****/eb53cd5d5b9fcf40****************-20ef44,
As I was typing this, the owner of the iPad from the log file above came by my desk, so I asked a couple more questions. He's never had another iPad, it's a gen 1, and he's never updated the iOS on it. I know one of the other iPads in question
has the most up to date iOS, and the other one is brand new, replacing one that was broken, but the owner of that one had the same issue on a 3 year old iOS.
There is nothing special about the user accounts, no special privileges or restrictions.
Has anyone encountered this before? Exchange 2003, Server 2003 in a 2008 domain. Promotion to the 2008 domain was 2 years ago.

Hi Brian,
I am so sorry for the delay.
Do you have any progress by now?
Since there are lots of devices which use user accounts to log on, failed logon attempts on these devices could be the cause for account lockout.
If this issue persists, I suggest you refer to these troubleshooting articles below:
Troubleshooting account lockout the PSS way
http://blogs.technet.com/b/instan/archive/2009/09/01/troubleshooting-account-lockout-the-pss-way.aspx
Troubleshooting Account Lockout
http://technet.microsoft.com/en-us/library/cc773155(v=WS.10).aspx
In addition, you can also get efficient support at Active Sync forum below:
http://social.technet.microsoft.com/Forums/exchange/en-US/home?forum=exchangesvrmobilitylegacy
Best Regards,
Amy

Exchange 2003 compatability

Similar Messages

Maybe you are looking for