Exchange 2003 - Backup / Restore

Hi all,
I have inherited an exchange 2003 server (I know it is EOL, but stuck with it for now) I have had a situation were there are 4 mailbox stores on a storage group and the HQ office has requested a mailbox restore from a year ago. There is a third party backup
software which runs a full backup nightly onto tape, fortunately there are monthly tapes and I have located the relevant tape.
I recently ran a restore onto the recovery storage group of the mailbox store which I believe had required mailbox, however I set the restore job not to auto mount it, after the backup completed I got the following error in the application log when I tried
to mount the mailstore in the RSG, eventid 619 source ESE.
I have located a microsoft article that explains that the restore did not complete a hard recovery and this can be performed using the eseutil with the /cc switch. I have looked at the following articles in regards to using the /cc switch (hard recovery)
- https://technet.microsoft.com/en-gb/library/aa997478(v=exchg.65).aspx.
My query is as follows: the restored job copied the .edb and .stm files to a single location on the data drive and then the log files are on the same drive but a different folder called temp. In this folder there are 10 E00.log files and 1 restore.env file,
also this server has 3 other storage groups each with 4 mailbox stores. Obviously one of these is the one in the RSG. If I run the eseutil /cc command against restore.env will this only replay the logs from the same directory. For example eseutil /cc d:\restore\temp
The restore.env and E00.logs are in the temp directory and the edb and stm are in d:\restore\mailstore, I just want to ensure the the E00.log files from live mailstores does not get effected.

Hi,
As you know, after April 8, 2014, Microsoft will no longer provide security updates, offer free or paid support options, or update online content such as KB articles for Exchange Server 2003. Online content may remain available as long as Exchange 2003
remains in the Self-Help online support phase.
Companies running Exchange 2003 after April 8, 2014 will be responsible for their own for support. More importantly, because Microsoft will no longer provide security updates, companies that choose to continue running Exchange 2003 accept the risk associated
with that.
Best regards,
Regards, Please mark it as an answer if it really helps you.

Similar Messages

IPhone Backup / Restore questions

Maybe this has been covered here, but I am confused about backing up the data on my new iPhone -
1) When iTunes says "backing up iPhone" before the sync . . . what is it backing up? Contacts? Music? Pictures? Applications?
2) What does Restore do? It seems to indicate you will lose all of your data on the phone if you run restore.
3) If I replace my phone . . . or Apple does at some point for a battery . . . will the Backup/Restore features in iTunes restore all of my contacts, music, pictures and applications to the new phone?
While most things with the iPhone seem pretty intuitive, this whole process has me confused.
Dave

The backup that is created and maintained by iTunes stores data such as most iPhone settings, email account settings, SMS messages, notes created with the Notes application, recent calls, call favorites, data created and stored by 3rd party applications, and photos captured by your iPhone.
No need to backup iTunes content since your iTunes content remains on your computer and should be included with your computer's backup.
Regarding contact information and calendar events, the iPhone is designed to be synced with a supported application on your computer. The exception to this is with an Exchange account or MobileMe account, which provides for over the air syncing with this data.
With Vista, you can sync contact information and calendar events with Outlook 2003 or 2007, or Windows Contacts for contact information.
A Restore completely erases your iPhone followed by re-installing the current firmware version. After the current firmware version is re-installed, you are prompted to restore your iPhone from your iPhone's backup (which is the default selection), or as a new iPhone or not from your iPhone's backup.
This must be followed by a sync with iTunes to re-transfer data not included with your iPhone's backup such as all iTunes content, 3rd party applications, contact information, calendar events, bookmarks, and photos transferred from your computer to your iPhone.

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!

Lost LAN Connection in MS Exchange 2003 network

Hi everybody.
I have a connection problem which my ICT consultant can't solve or even figure out the cause.
In my company there's a MS Exchange 2003 network. I'm the only one running a Mac (Air bought in early 2011), as the others need to work on Solidworks and need Win machines. In order to connect with email and calendar I'm forced to use Parallels Desktop with Win7 installed to use Outlook and Access for our Internal Self made database.
What is happening is that sometimes when connected through WiFi the server connection is lost, causing loss of work if I had some files open from the server.
Considering that we have some interferences in our area I got the USB Ethernet adapter.
Worse than ****.
When cable connected the connection to server is lost every minute, not only if the Mac goes to sleep, but even during normal work. Unless I "stimulate" the finder every 30 seconds the server connection get lost, sometimes is sufficient to click on the saved preferred positions in the side bar to wake it up, but most of the times if I'm working on files on the server this is not sufficient and the job done is lost.
Also this sometime cause a major failure in the system and I'm forced to shut down the Mac by holding the button.
Any clues?
Thanks

Thanks for the help on making restore points, and on getting Boot Camp 2.1; I recently updated Apple Software Update to 2.1.1, so that's working, and it did suggest BC 2.1 as a downloadable. I'll probably do it manually, though, just to be on the safe side of things, as I don't trust Software Update even in OS X for most things (except to tell me what updates are available; I usually download and install everything manually anyway). Windows Update is a different matter, as I can't get most of the patches it offers by myself (not that I haven't tried--most are available only through the utility).
As for backing up and restoring from a clone on a second hard drive: I can't afford to do that at the moment, as I can't afford the hardware, software, or time needed to prepare a clone backup. And besides, as I said before, I don't do enough in the Windows partition that demands such backup work be done. I use Vista primarily for things I can't do in OS X, with Windows-specific apps.
Still not sure how to go about updating the LAN port driver, or if it even needs to be updated. If BC 2.1 doesn't do it, I'll look up the vendor through whatever link Windows Update provides for me. And I haven't received any word from Verizon about my modem needing a firmware update, but then again I haven't contacted them about it yet, and I'm not sure I need to, or if it really needs to be updated. I'm just hoping that if the connection drops again that it won't be necessary to update or replace the modem, that the problem remains in software. (Of course, I'll take whatever precautionary measures I can, but I can only do so much myself.)

Having problems connecting iPhone 5 with our company's Exchange 2003. Is this a known issue and is there a fix?

I'm not the only one in our company experiencing this, so far i haven't heard of anyone with an iPhone 5 who is able to connect. I'm wondering if people in other companies that have Exchange 2003 also have the same issue or is this isolated to ours.
The errors i get are not being able to verify: "Unable to verify account information." This used to happen before but when i chose to save settings, it would usually work after a while. But this time, with the iPhone 5, i kept getting "Cannot Get Mail" "The connection to the server failed".
I did this with a restore from back up, and a wiped phone, same results. My colleague with a fresh out of the box phone with no previous IOS backups, also has the same errors.
So, anyone else still using Exchange 2003 and experiencing the issues?

Hi Guys,
I got exchange mail working. It seems issue is around "Push". I enabled "push", account verified & all worked well. After that I disabled push (I do not want it & to save mobile data use).
By googling, I found many have got it up & apple may fix it in it next iOS udpate.
Regards,
Mathew

Will the email client on my MacBook Pro remove mail from my Exchange 2003 in order to receive it?

I just received my new MacBook Pro yesterday and I have an Exchange 2003 server that I would like to work with the email client. now I know some email clients in certain modes will download the mail from the mail server removing it from there at the same time. My question is will the email client remove the mail from the server in order to receive it? I want the mail to remain in the mailbox so I will still have it available at my office later. I am honestly not certain what version of OS X it is, and I don't have it handy, but I just bought it last week. Thanks!

Try trash the com.apple.iPhoto.plist file from the HD/Users/ Your Name / library / preferences folder. (Remember you'll need to reset your User options afterwards. These include minor settings like the window colour and so on. Note: If you've moved your library you'll need to point iPhoto at it again.)
What's the plist file?
For new users: Every application on your Mac has an accompanying plist file. It records certain User choices. For instance, in your favourite Word Processor it remembers your choice of Default Font, on your Web Browser is remembers things like your choice of Home Page. It even recalls what windows you had open last if your app allows you to pick up from where you left off last. The iPhoto plist file remembers things like the location of the Library, your choice of background colour, whether you are running a Referenced or Managed Library, what preferences you have for autosplitting events and so on. Trashing the plist file forces the app to generate a new one on the next launch, and this restores things to the Factory Defaults. Hence, if you've changed any of these things you'll need to reset them. If you haven't, then no bother. Trashing the plist file is Mac troubleshooting 101.
If that fails:
Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. .
Regards
TD

Uninstall/Reinstall Exchange 2010 in coexisting Exchange 2003

Hi,
Can we uninstall Exchange 2010 without any affect to Exchange 2003 in the co-existing environment? I installed Exchange 2010 in existing Exchange 2003 and tried to configure for both Exchange exist in our domain. Somehow the Exchange 2010 crashed
and now it cannot start, only stuck in Initializing process. I want to uninstall and then reinstall but I don't know if doing this will cause any problem to the Existing Exchange 2003. Could someone tell me?
Thanks,
Jim

You don't have to uninstall and reinstall server, just rebuild base server with OS with what it had earlier and recover Exchange 2010 with /m:recoverserver switch.
Recover an Exchange Server
I assume you still have Exchange 2010 database backup or original files for restore if needed and this is just OS crash and can not be repaired scenario
Blog:
http://exchangeshare.wordpress.com/

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

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!!

IPhone 4 OS 4.3.3 Exchange 2003 Calendar issue

I have a user that is reporting the calendar entries on her iPhone (iPhone 4 - iOS 4.3.3) randomly disappears and reappears without any changes being made to the device. The email and contact portion of the device seems to be working fine. User took the iPhone to an Apple store and after some troubleshooting, they replaced the phone. This did not resolve the issue. The Apple tech said it was an issue with the Exchange Server. The user’s account was working fine for months. I disabled and re-enabled the user’s Web Services in Active Directory, no luck.
Why would the calendar be the only service being affected and how do I fix this?

No solution but just want to chime in that I'm encountering similar issues. Updated to 4.3.3 and I can no longer sync my work calendar, Exchange 2003. Connecting to the calendar works but only my sub calendars are recognized. My main work calendar isn't displayed. Various attempts to fix this have triggered a message that server identity cannot be verified. MuSt HaVe ExChAnGe SyNc... Please help.
restored, deleted account and reconnected. Apple says it's an Exchange issue. But I seem to be one of the few that are encountering the issue. Co-workers with lower versions do not have a problem syncing with exchange. Awh...progress

Exchange 2003 to GroupWise 7

We are not able to successfully complete a migration of all users from
Exchange 2003 to GroupWise 7 on Netware. Issues below:
** NOT Necessarily in exact order of sequence **
System config:
Netware OES fully service packed, new server, 4GB RAM, 4 Processors.
GroupWise 7.0.1 IR1 Post Office installed. Domain located on an older,
existing server.
Microsoft Windows Server 2003, Exchange 2003 single server. Nothing
special or unusual about this setup for Exchange, pretty generic.
1. Issue attempting to install Migration utility. Utility unable to run
after installation on any workstation. Various errors from "unable to
create GroupWise account" to "unable to login to Exchange mailbox" and a
few others. We also got "fatal errors when trying to extract .csv file".
This was resolved later by running fixmapi.
2. After nearly 18 hours attempting to get the utility to work, we were
able to successfully load it onto 2 workstations. It appeared that it
would work on both.
3. We tried many things to install and run the utility on 15 additional
workstations with no success.
4. Found that the only 2 workstations that appeared to run the utility
were fairly new, less than 2 months old. We then tried fresh installations
of WINXP and WIN2000 on 2 workstations with no success. One of the 2
workstations that did work, later no longer would run the utility. After
running fixmapi.exe on that workstation, it did again work.
5. A suggestion from Novell NTS was to run fixmapi.exe. This appeared to
have corrected 4 of the 10 workstations on which we tried it.
6. Found on 2 workstations that if ZEN DLU (Dynamic Local User) was used,
the migration utility did not work. We found this by logging in as
"Workstation Only" which connected the workstation to the domain, then a
login to eDirectory. The utility did work. So, again we tried to login on
startup to eDirectory and again were not able to run the utility. So, the
fact that some workstations here use DLU may be an issue for this utility.
7. Found that on other workstations, the utility would run ONLY if
"Workstation Only" was selected, then login to eDirectory. We were able to
repeat this sequence multiple times. This is on a workstation not running
ZEN DLU.
8. Of the 6 workstations we were able to run the utility, 1 failed in the
first 5 minutes and would no longer work. So, we split the .csv file from
the Exchange server into 5 parts and started the migration on the 5
available operating workstations. Of the 5, only 2 completed the utility.
Of those 2, only 7 of the 45 users to be migrated completed on 1
workstation and 15 of 45 completed on another.
9. On the 2 workstations that completed, all user accounts were created
but the utility was unable to access the GroupWise account. Login to
GroupWise account failed.
10. Migration utility rules creation issue. There are 2 issues here.
10a. The utility suggests to create a rule using a sub-domain and a
forward rule in Exchange to the new GroupWise system. We are migrating
from: royalmouldings.com to ggc.com. So, the sub-domain is
marexch.ggc.com. The rule would read "forward all mail to
[email protected]. However, Exchange cannot forward to an external
domain at the client level. The only means to do so is to create a contact
in AD with an SMTP email address of the domain to be forwarded to. Then,
in the users account a rule may be created to forward to that newly
created contact. The fact that we are forwarding to an external internet
domain, as in NOT the same one currently used in Exchange, is not
indicated in the documentation. Additionally, if anyone is to do this, a
lot of manual work must be done to accomplish this task. Not too practical
to do for hundreds or thousands of users. This has been a big problem as a
result of the large amount of users in the system and the time it takes to
create each of these contacts.
10b. The second issue is the fact that the rule was created for 1 user,
then no other users had the rule created. So, even if the rule were to
work or we were migrating from and to the same domain name, we'd still
have the rule issue as it was never again created by the utility after the
first user was migrated.
Any help would be greatly appreciated.
Thanks

Bill, you're understandably frustrated. I have a couple of comments.
1. The network authentication system used by Microsoft Exchange requires that you log in to your workstation with the same user ID and password as your account on Exchange. If they don't match, Exchange returns errors that are not always understandable. That might explain why Zen DLU has problems.
2. It seems that every application that deals with e-mail has its own version of MAPI, and they're not always compatible with each other. Outlook, GroupWise, and the migration utility all use MAPI. The fixmapi utility will restore the MAPI DLLs that Outlook expects, which is usually the version that works best.
3. The migration utility should be improved to detect potential errors like these.
>>> Bill Long<[email protected]> 5/19/07 11:59 AM >>>
We are not able to successfully complete a migration of all users from
Exchange 2003 to GroupWise 7 on Netware. Issues below:
** NOT Necessarily in exact order of sequence **
System config:
Netware OES fully service packed, new server, 4GB RAM, 4 Processors.
GroupWise 7.0.1 IR1 Post Office installed. Domain located on an older,
existing server.
Microsoft Windows Server 2003, Exchange 2003 single server. Nothing
special or unusual about this setup for Exchange, pretty generic.
1. Issue attempting to install Migration utility. Utility unable to run
after installation on any workstation. Various errors from "unable to
create GroupWise account" to "unable to login to Exchange mailbox" and a
few others. We also got "fatal errors when trying to extract .csv file".
This was resolved later by running fixmapi.
2. After nearly 18 hours attempting to get the utility to work, we were
able to successfully load it onto 2 workstations. It appeared that it
would work on both.
3. We tried many things to install and run the utility on 15 additional
workstations with no success.
4. Found that the only 2 workstations that appeared to run the utility
were fairly new, less than 2 months old. We then tried fresh installations
of WINXP and WIN2000 on 2 workstations with no success. One of the 2
workstations that did work, later no longer would run the utility. After
running fixmapi.exe on that workstation, it did again work.
5. A suggestion from Novell NTS was to run fixmapi.exe. This appeared to
have corrected 4 of the 10 workstations on which we tried it.
6. Found on 2 workstations that if ZEN DLU (Dynamic Local User) was used,
the migration utility did not work. We found this by logging in as
"Workstation Only" which connected the workstation to the domain, then a
login to eDirectory. The utility did work. So, again we tried to login on
startup to eDirectory and again were not able to run the utility. So, the
fact that some workstations here use DLU may be an issue for this utility.
7. Found that on other workstations, the utility would run ONLY if
"Workstation Only" was selected, then login to eDirectory. We were able to
repeat this sequence multiple times. This is on a workstation not running
ZEN DLU.
8. Of the 6 workstations we were able to run the utility, 1 failed in the
first 5 minutes and would no longer work. So, we split the .csv file from
the Exchange server into 5 parts and started the migration on the 5
available operating workstations. Of the 5, only 2 completed the utility.
Of those 2, only 7 of the 45 users to be migrated completed on 1
workstation and 15 of 45 completed on another.
9. On the 2 workstations that completed, all user accounts were created
but the utility was unable to access the GroupWise account. Login to
GroupWise account failed.
10. Migration utility rules creation issue. There are 2 issues here.
10a. The utility suggests to create a rule using a sub-domain and a
forward rule in Exchange to the new GroupWise system. We are migrating
from: royalmouldings.com to ggc.com. So, the sub-domain is
marexch.ggc.com. The rule would read "forward all mail to
[email protected]. However, Exchange cannot forward to an external
domain at the client level. The only means to do so is to create a contact
in AD with an SMTP email address of the domain to be forwarded to. Then,
in the users account a rule may be created to forward to that newly
created contact. The fact that we are forwarding to an external internet
domain, as in NOT the same one currently used in Exchange, is not
indicated in the documentation. Additionally, if anyone is to do this, a
lot of manual work must be done to accomplish this task. Not too practical
to do for hundreds or thousands of users. This has been a big problem as a
result of the large amount of users in the system and the time it takes to
create each of these contacts.
10b. The second issue is the fact that the rule was created for 1 user,
then no other users had the rule created. So, even if the rule were to
work or we were migrating from and to the same domain name, we'd still
have the rule issue as it was never again created by the utility after the
first user was migrated.
Any help would be greatly appreciated.
Thanks

Exchange 2003 - Cannot search my GAL

Took me a while, but I finally got connected to my Exchange server. (Exchange 2003 for Small Business, SP2 running on Win 2003)
My E-Mail syncs
My Calendars sync
My Contacts... sort of sync
I get my raw Outlook contacts, and I can see the "Exchange Global Address List >" in Contacts.
But when I fill out a name, it returns "No Results"
I am also having difficulties with OMA (Outlook Mobile Access) which may, or may not, cause the problem I am having; since OMA needs to be running in a Virtual Directory to get my iPhone to sync.
When I go to log in to OMA:
https://<server>/oma
Insert Username & Password
https://<server>/oma/(S(pmxg5gvaahzmfmoqddhocogh))/oma.aspx But the page appears blank
OMA should be all text and would act like a webpage circa '95 with only text based hyperlinks. And in fact, it was working before we updated to SP2.
Would OMA's semi-broken response affect my ability to search the GAL at all?
Is there a known solution to this GAL problem?

Some good documents to clarify your client's concerns are available at below links that shows and explains in depth about "Exchange server 2003 data backup and volume shadow copy services" :
http://support.microsoft.com/kb/822896
http://support.microsoft.com/kb/296788/en-us
Also, you can download complete disaster recovery guide from Microsoft download center : http://www.microsoft.com/en-us/download/details.aspx?id=85
Meanwhile, to avoid the risks and proceed error-free migration between exchange 2003 and 2007, a very helpful resource is available at website(http://www.exchangemigrationtool.com/) that could also be a
good approach to accomplish mailbox migration in a hassle-free manner.

Installing a Windows 2012 Domain Controller into a 2000/2003 domain with Exchange 2003

Hello,
    I have a client that we are planning to migrate to 2012 over time. They currently have a Windows 200 DC and 2 member servers running Windows 2003, one of which is running Exchange 2003.
    We first are going to introduce a 2012 server into the domain and my plan was to DCPromo the 2003 server that isn't running Exchange and raise domain level to 2003 and then demote the 2000 server. I was then going to install the
2012 server into the domain and make it a backup Domain Controller for the time being and leave the newly promoted Windows 2003 server as the primary Domain Controller with all the roles and global catalog. My question is will Exchange 2003 still function
normally in this scenario?
   I've been doing research and read some things about Exchange 2003 not working with 2012 Domain Controllers, but I was thinking if the 2003 is still the primary, it might work. We will eventually migrate to 2003, they just don't want to
do it all at once, due to costs and other issues.
Thanks.

I didn't ask if it was supported, I just wanted to know if Exchange 2003 would continue
to function if the Windows 2003 DC still held all the FSMO roles and Global Catalog.
A not supported situation means that it is a situation where Microsoft made no testing or do not guarantee that you can operate with no problems. Following a not supported scenario could be done but is on your own risk.
If it won't, can the 2012 server be a member server in the 2003 AD? The 2000
DC it is replacing, just shares files on the network in addition to being the lone AD server
Yes, it can be a member server.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Server 2003 backup

i search from the internet and find some recommendation for server 2003 backup solution, i wonder which is better. the only requirment is userfriendly, and cheap of course. i am not intend to put too much energy into this. i know Acronis, Aomei and macrium,
they seem good. are they? is there a possibity to get free edtion for server?

Hi,
We could use NTBackup.exe to back up data for Windows Server 2003. If you just need to back up a single server and the backup device is local, Ntbackup will most likely fit the bill.
For more detailed information, please refer to the links below:
Recommended backup software for windows 2003 server
https://social.technet.microsoft.com/Forums/sharepoint/en-US/24fad745-3aaa-43ec-8210-db106ff88fa7/recommended-backup-software-for-windows-2003-server?forum=winserverfiles
Backing Up and Restoring Data for Windows Server 2003
http://technet.microsoft.com/en-us/library/cc875820.aspx
Preserve Your Data With The Backup Tool You Already Have
http://technet.microsoft.com/en-us/magazine/2005.05.ntbackup.aspx
Best Regards,
Mandy
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Backup & Restore SQL Server 2005

Dear Experts,
One of our SAP system got crash due to some hardware problem . we have rectified the problem and installed the OS again.
Now could you please tell me how to restore taken SQL to bring the system up to date. Now I have Backup datas in my External HDD. I don't have Tape Drive media for that system.
I would appreciate the procedure and steps to be followed backup restore on the SQL 2005 & windows 2003 server system
Please Let me know.
Thanks in advance
Regards
Thomas.T

hi,
you have to install SAP on that machine then
1. Detach the database from newly installed sap.
if you had offline backup
2. copy the database from the external HDD to newly installed location for e.g if on installation you had
     database location on E:\ then copy to E:\
3. attach the database.
if online backup
3. you have to use Restore method in SQL server.
     start SQL 2005 server, right click on database option-->select Restore database, select from device -->specify backup
     Backup media> file, click on Add> select file (external HDD location), in To database -->specify name of database (like PRD,DEV your SAP database name), in option, give the proper path for the restore.
4. run STM tool.
Thanks
Ganesh

Exchange 2003 - Backup / Restore

Similar Messages

Maybe you are looking for