Exchange 5.5 to 2000 Upgrade horror story
This is just an informational post, you're welcome to comment on it but I'm not really asking any questions. Just thought folks out there getting ready to upgrade might want to hear the story. I just spent the night upgrading (or trying to upgrade) my exchange 5.5 server. We have a very simple network. 1 domain. 200 users. 1 exchange server. 2 domain controllers (not the exchange server). Started about 2 weeks ago prepping for upgrade. Armed with: White Paper in-place upgrade from msoft exchange 5.5 to msoft exchange 2000 Q316886 How To: Migrate from exchange server 5.5 to exchange 2000 server Q282309 upgrading exchange server 5.5 service pack 4 to exchange 2000 server Q295922 considerations when you upgrade to exchange 2000 server Q296260 how to configure a two-way recipient connection agreement for exchange server 5.5 users Q253829 description of the active directory connector deletion mechanism And, of course, monitored this list (and the sun-exchange) one for upgrade ideas! Now some of the documents have conflicting information. If you weed thru the dates and such you can usually figure out what is really true. For example, the white paper states you MUST have at least one domain running in native mode, but the HOW TO describes a scenario where all domains are in mixed mode. With the domain controllers upgraded to win2k active directory (mixed mode) last month I tackled the exchange upgrade this month. Went thru the white paper and how to, updating the schema (forestprep and domainprep) and ran all the tests listed in those docs to verify it was working. Got exactly the results they told me! First time I ran the actual upgrade got my first rude surprise. My vendor had shipped me the Exchange 2000 standard edition media (which doesn't really say standard on it, just Exchange 2000) and the upgrade process stopped immediately with You can't go from enterprise to standard you idiot Two days later I have the correct media. Take the server off the network and run an online backup (Veritas backup exec with exchange option). Verify the backup worked. With exchange services down get back on the network and run domain tests again. Everything ok! Run the upgrade! The upgrade goes thru several processes but hangs at Setup failed while installing sub-component Site Replication Service with error code 0xC007041D -- retry or cancel search MS knowledge base and looks like a permissions issue (Q278254 and Q273730). Hmm, make sure the exchange service account has all the permissions and click retry. Still no work. Rats. Getting late so time to make the $250 call to PSS! PSS steps me thru lots of stuff, nothing works. They have me change the service account user permissions at the ORG container from CUSTOM to SERVICE ACCOUNT (i'm probably not saying this exactly correct). Still no joy. Try to cancel out of that error message. Nada. Have to task manager/shut down process. They then refer me to the ultimate nightmare: Q264309 - How to Roll Back A failed Upgraded from Exchange Server 5.5. to Exchange 2000. Yuck. Go into registry and delete the stuff, rename the exchsrvr folders, uninstall IIS, restart server, install IIS, re-apply all service packs and hotfixes (that really sucks), delete the renamed exchsrvr folders, setup /r exchange 5.5, restore directory and info store. Restoring directory service doesn't work. Call PSS back. Directory service was trying to start and got hung, can't restore to hung service. Change to manual start and reboot. Directory restores!!! Restore info store. (8 gigs). 2 hours later ready to go! (almost) Now the internet mail connector isn't working. Dawn is breaking and panic begins to creep in. Users will be screaming in about 2 hours. Call PSS again. End up deleting the IMC and creating a new one. They very patiently step me through lots of good stuff, including making sure I'm not an internet relay and that I'm not doing circular logs. They even stand by while I reinstall my Anti-virus for exchange. Everything is working. It's now 7am and I'm back to my original pre-upgrade status from 7pm the night before. Problem summary: PSS thinks that the problem was caused by the mail service account user not having complete permissions at the org container. By the time this was corrected by PSS (and me) the upgrade was stuck. They are pretty sure and reasonably confident the upgrade will work next time. Moral: MAKE BACKUPS. PLAN FOR EXTRA TIME. PSS is your friend (I was on the phone with them for about 4 hours) This was so much fun we're planning another attempt. This will be on a Saturday morning so I'll have lots of time to recover (or celebrate). Tom Gray, Network Engineer All Kinds of Minds The Center for Development and Learning University of North Carolina at Chapel Hill Internet: [EMAIL PROTECTED] ATT Net: (919)960- List Charter and FAQ at: http://www.sunbelt
RE: Exchange 5.5 to 2000 Upgrade horror story
We are planning to do the same in the next month or two. Thanks for the post and I'm looking forward to hearing how it works out. Gene A Scruggs American College of Emergency Physicians Technical Support Manager -Original Message- From: Tom.Gray [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 9:05 AM To: MS-Exchange Admin Issues Subject: Exchange 5.5 to 2000 Upgrade horror story This is just an informational post, you're welcome to comment on it but I'm not really asking any questions. Just thought folks out there getting ready to upgrade might want to hear the story. I just spent the night upgrading (or trying to upgrade) my exchange 5.5 server. We have a very simple network. 1 domain. 200 users. 1 exchange server. 2 domain controllers (not the exchange server). Started about 2 weeks ago prepping for upgrade. Armed with: White Paper in-place upgrade from msoft exchange 5.5 to msoft exchange 2000 Q316886 How To: Migrate from exchange server 5.5 to exchange 2000 server Q282309 upgrading exchange server 5.5 service pack 4 to exchange 2000 server Q295922 considerations when you upgrade to exchange 2000 server Q296260 how to configure a two-way recipient connection agreement for exchange server 5.5 users Q253829 description of the active directory connector deletion mechanism And, of course, monitored this list (and the sun-exchange) one for upgrade ideas! Now some of the documents have conflicting information. If you weed thru the dates and such you can usually figure out what is really true. For example, the white paper states you MUST have at least one domain running in native mode, but the HOW TO describes a scenario where all domains are in mixed mode. With the domain controllers upgraded to win2k active directory (mixed mode) last month I tackled the exchange upgrade this month. Went thru the white paper and how to, updating the schema (forestprep and domainprep) and ran all the tests listed in those docs to verify it was working. Got exactly the results they told me! First time I ran the actual upgrade got my first rude surprise. My vendor had shipped me the Exchange 2000 standard edition media (which doesn't really say standard on it, just Exchange 2000) and the upgrade process stopped immediately with You can't go from enterprise to standard you idiot Two days later I have the correct media. Take the server off the network and run an online backup (Veritas backup exec with exchange option). Verify the backup worked. With exchange services down get back on the network and run domain tests again. Everything ok! Run the upgrade! The upgrade goes thru several processes but hangs at Setup failed while installing sub-component Site Replication Service with error code 0xC007041D -- retry or cancel search MS knowledge base and looks like a permissions issue (Q278254 and Q273730). Hmm, make sure the exchange service account has all the permissions and click retry. Still no work. Rats. Getting late so time to make the $250 call to PSS! PSS steps me thru lots of stuff, nothing works. They have me change the service account user permissions at the ORG container from CUSTOM to SERVICE ACCOUNT (i'm probably not saying this exactly correct). Still no joy. Try to cancel out of that error message. Nada. Have to task manager/shut down process. They then refer me to the ultimate nightmare: Q264309 - How to Roll Back A failed Upgraded from Exchange Server 5.5. to Exchange 2000. Yuck. Go into registry and delete the stuff, rename the exchsrvr folders, uninstall IIS, restart server, install IIS, re-apply all service packs and hotfixes (that really sucks), delete the renamed exchsrvr folders, setup /r exchange 5.5, restore directory and info store. Restoring directory service doesn't work. Call PSS back. Directory service was trying to start and got hung, can't restore to hung service. Change to manual start and reboot. Directory restores!!! Restore info store. (8 gigs). 2 hours later ready to go! (almost) Now the internet mail connector isn't working. Dawn is breaking and panic begins to creep in. Users will be screaming in about 2 hours. Call PSS again. End up deleting the IMC and creating a new one. They very patiently step me through lots of good stuff, including making sure I'm not an internet relay and that I'm not doing circular logs. They even stand by while I reinstall my Anti-virus for exchange. Everything is working. It's now 7am and I'm back to my original pre-upgrade status from 7pm the night before. Problem summary: PSS thinks that the problem was caused by the mail service account user not having complete permissions at the org container. By the time this was corrected by PSS (and me) the upgrade was stuck. They are pretty sure and reasonably confident the upgrade will work next time. Moral: MAKE BACKUPS. PLAN FOR EXTRA TIME. PSS is your friend (I was on the phone with them
RE: Exchange 5.5 to 2000 Upgrade horror story
This is just another reason that I do not like upgrades. Migrations - yes. Upgrades - NO. I do not think I would ever attempt to upgrade my 5.5 server to 2000. I would procure separate hardware for the new 2000 server. If any of you get MCP mag, you will read in one of the last issues almost the same exact story. Person attempts upgrade, upgrade fails. Lesson learned? Don't upgrade. Migrate. Ben Winzenz Network/Systems Administrator Peregrine Systems -Original Message- From: Tom.Gray [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 9:05 AM To: MS-Exchange Admin Issues Subject: Exchange 5.5 to 2000 Upgrade horror story This is just an informational post, you're welcome to comment on it but I'm not really asking any questions. Just thought folks out there getting ready to upgrade might want to hear the story. I just spent the night upgrading (or trying to upgrade) my exchange 5.5 server. We have a very simple network. 1 domain. 200 users. 1 exchange server. 2 domain controllers (not the exchange server). Started about 2 weeks ago prepping for upgrade. Armed with: White Paper in-place upgrade from msoft exchange 5.5 to msoft exchange 2000 Q316886 How To: Migrate from exchange server 5.5 to exchange 2000 server Q282309 upgrading exchange server 5.5 service pack 4 to exchange 2000 server Q295922 considerations when you upgrade to exchange 2000 server Q296260 how to configure a two-way recipient connection agreement for exchange server 5.5 users Q253829 description of the active directory connector deletion mechanism And, of course, monitored this list (and the sun-exchange) one for upgrade ideas! Now some of the documents have conflicting information. If you weed thru the dates and such you can usually figure out what is really true. For example, the white paper states you MUST have at least one domain running in native mode, but the HOW TO describes a scenario where all domains are in mixed mode. With the domain controllers upgraded to win2k active directory (mixed mode) last month I tackled the exchange upgrade this month. Went thru the white paper and how to, updating the schema (forestprep and domainprep) and ran all the tests listed in those docs to verify it was working. Got exactly the results they told me! First time I ran the actual upgrade got my first rude surprise. My vendor had shipped me the Exchange 2000 standard edition media (which doesn't really say standard on it, just Exchange 2000) and the upgrade process stopped immediately with You can't go from enterprise to standard you idiot Two days later I have the correct media. Take the server off the network and run an online backup (Veritas backup exec with exchange option). Verify the backup worked. With exchange services down get back on the network and run domain tests again. Everything ok! Run the upgrade! The upgrade goes thru several processes but hangs at Setup failed while installing sub-component Site Replication Service with error code 0xC007041D -- retry or cancel search MS knowledge base and looks like a permissions issue (Q278254 and Q273730). Hmm, make sure the exchange service account has all the permissions and click retry. Still no work. Rats. Getting late so time to make the $250 call to PSS! PSS steps me thru lots of stuff, nothing works. They have me change the service account user permissions at the ORG container from CUSTOM to SERVICE ACCOUNT (i'm probably not saying this exactly correct). Still no joy. Try to cancel out of that error message. Nada. Have to task manager/shut down process. They then refer me to the ultimate nightmare: Q264309 - How to Roll Back A failed Upgraded from Exchange Server 5.5. to Exchange 2000. Yuck. Go into registry and delete the stuff, rename the exchsrvr folders, uninstall IIS, restart server, install IIS, re-apply all service packs and hotfixes (that really sucks), delete the renamed exchsrvr folders, setup /r exchange 5.5, restore directory and info store. Restoring directory service doesn't work. Call PSS back. Directory service was trying to start and got hung, can't restore to hung service. Change to manual start and reboot. Directory restores!!! Restore info store. (8 gigs). 2 hours later ready to go! (almost) Now the internet mail connector isn't working. Dawn is breaking and panic begins to creep in. Users will be screaming in about 2 hours. Call PSS again. End up deleting the IMC and creating a new one. They very patiently step me through lots of good stuff, including making sure I'm not an internet relay and that I'm not doing circular logs. They even stand by while I reinstall my Anti-virus for exchange. Everything is working. It's now 7am and I'm back to my original pre-upgrade status from 7pm the night before. Problem summary: PSS thinks that the problem was caused by the mail service account user not having complete permissions at the org container
RE: Exchange 5.5 to 2000 Upgrade horror story
I agree, although some of us less fortunate don't have the ability to buy new hardware, so what we do is find a low-end server or high-end desktop and temporarily move Exchange 5.5 production to it. Rebuild the former 5.5 to 2000, then migrate the server. So your on a lower powered machine for a few days with some risk, but its better than what I always here happens (and unfortunately went through) when you try an in place upgrade. It's a swing migration. -Original Message- From: Ben Winzenz [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 1:37 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 to 2000 Upgrade horror story This is just another reason that I do not like upgrades. Migrations - yes. Upgrades - NO. I do not think I would ever attempt to upgrade my 5.5 server to 2000. I would procure separate hardware for the new 2000 server. If any of you get MCP mag, you will read in one of the last issues almost the same exact story. Person attempts upgrade, upgrade fails. Lesson learned? Don't upgrade. Migrate. Ben Winzenz Network/Systems Administrator Peregrine Systems -Original Message- From: Tom.Gray [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 9:05 AM To: MS-Exchange Admin Issues Subject: Exchange 5.5 to 2000 Upgrade horror story This is just an informational post, you're welcome to comment on it but I'm not really asking any questions. Just thought folks out there getting ready to upgrade might want to hear the story. I just spent the night upgrading (or trying to upgrade) my exchange 5.5 server. We have a very simple network. 1 domain. 200 users. 1 exchange server. 2 domain controllers (not the exchange server). Started about 2 weeks ago prepping for upgrade. Armed with: White Paper in-place upgrade from msoft exchange 5.5 to msoft exchange 2000 Q316886 How To: Migrate from exchange server 5.5 to exchange 2000 server Q282309 upgrading exchange server 5.5 service pack 4 to exchange 2000 server Q295922 considerations when you upgrade to exchange 2000 server Q296260 how to configure a two-way recipient connection agreement for exchange server 5.5 users Q253829 description of the active directory connector deletion mechanism And, of course, monitored this list (and the sun-exchange) one for upgrade ideas! Now some of the documents have conflicting information. If you weed thru the dates and such you can usually figure out what is really true. For example, the white paper states you MUST have at least one domain running in native mode, but the HOW TO describes a scenario where all domains are in mixed mode. With the domain controllers upgraded to win2k active directory (mixed mode) last month I tackled the exchange upgrade this month. Went thru the white paper and how to, updating the schema (forestprep and domainprep) and ran all the tests listed in those docs to verify it was working. Got exactly the results they told me! First time I ran the actual upgrade got my first rude surprise. My vendor had shipped me the Exchange 2000 standard edition media (which doesn't really say standard on it, just Exchange 2000) and the upgrade process stopped immediately with You can't go from enterprise to standard you idiot Two days later I have the correct media. Take the server off the network and run an online backup (Veritas backup exec with exchange option). Verify the backup worked. With exchange services down get back on the network and run domain tests again. Everything ok! Run the upgrade! The upgrade goes thru several processes but hangs at Setup failed while installing sub-component Site Replication Service with error code 0xC007041D -- retry or cancel search MS knowledge base and looks like a permissions issue (Q278254 and Q273730). Hmm, make sure the exchange service account has all the permissions and click retry. Still no work. Rats. Getting late so time to make the $250 call to PSS! PSS steps me thru lots of stuff, nothing works. They have me change the service account user permissions at the ORG container from CUSTOM to SERVICE ACCOUNT (i'm probably not saying this exactly correct). Still no joy. Try to cancel out of that error message. Nada. Have to task manager/shut down process. They then refer me to the ultimate nightmare: Q264309 - How to Roll Back A failed Upgraded from Exchange Server 5.5. to Exchange 2000. Yuck. Go into registry and delete the stuff, rename the exchsrvr folders, uninstall IIS, restart server, install IIS, re-apply all service packs and hotfixes (that really sucks), delete the renamed exchsrvr folders, setup /r exchange 5.5, restore directory and info store. Restoring directory service doesn't work. Call PSS back. Directory service was trying to start and got hung, can't restore to hung service. Change to manual start and reboot. Directory restores!!! Restore info store. (8 gigs). 2 hours later ready to go! (almost) Now
RE: Exchange 5.5 to 2000 Upgrade horror story
Ya... In-place upgrades suck. Let us know how Saturday goes. -Original Message- From: Tom.Gray [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 7:05 AM To: MS-Exchange Admin Issues Subject: Exchange 5.5 to 2000 Upgrade horror story This is just an informational post, you're welcome to comment on it but I'm not really asking any questions. Just thought folks out there getting ready to upgrade might want to hear the story. I just spent the night upgrading (or trying to upgrade) my exchange 5.5 server. We have a very simple network. 1 domain. 200 users. 1 exchange server. 2 domain controllers (not the exchange server). Started about 2 weeks ago prepping for upgrade. Armed with: White Paper in-place upgrade from msoft exchange 5.5 to msoft exchange 2000 Q316886 How To: Migrate from exchange server 5.5 to exchange 2000 server Q282309 upgrading exchange server 5.5 service pack 4 to exchange 2000 server Q295922 considerations when you upgrade to exchange 2000 server Q296260 how to configure a two-way recipient connection agreement for exchange server 5.5 users Q253829 description of the active directory connector deletion mechanism And, of course, monitored this list (and the sun-exchange) one for upgrade ideas! Now some of the documents have conflicting information. If you weed thru the dates and such you can usually figure out what is really true. For example, the white paper states you MUST have at least one domain running in native mode, but the HOW TO describes a scenario where all domains are in mixed mode. With the domain controllers upgraded to win2k active directory (mixed mode) last month I tackled the exchange upgrade this month. Went thru the white paper and how to, updating the schema (forestprep and domainprep) and ran all the tests listed in those docs to verify it was working. Got exactly the results they told me! First time I ran the actual upgrade got my first rude surprise. My vendor had shipped me the Exchange 2000 standard edition media (which doesn't really say standard on it, just Exchange 2000) and the upgrade process stopped immediately with You can't go from enterprise to standard you idiot Two days later I have the correct media. Take the server off the network and run an online backup (Veritas backup exec with exchange option). Verify the backup worked. With exchange services down get back on the network and run domain tests again. Everything ok! Run the upgrade! The upgrade goes thru several processes but hangs at Setup failed while installing sub-component Site Replication Service with error code 0xC007041D -- retry or cancel search MS knowledge base and looks like a permissions issue (Q278254 and Q273730). Hmm, make sure the exchange service account has all the permissions and click retry. Still no work. Rats. Getting late so time to make the $250 call to PSS! PSS steps me thru lots of stuff, nothing works. They have me change the service account user permissions at the ORG container from CUSTOM to SERVICE ACCOUNT (i'm probably not saying this exactly correct). Still no joy. Try to cancel out of that error message. Nada. Have to task manager/shut down process. They then refer me to the ultimate nightmare: Q264309 - How to Roll Back A failed Upgraded from Exchange Server 5.5. to Exchange 2000. Yuck. Go into registry and delete the stuff, rename the exchsrvr folders, uninstall IIS, restart server, install IIS, re-apply all service packs and hotfixes (that really sucks), delete the renamed exchsrvr folders, setup /r exchange 5.5, restore directory and info store. Restoring directory service doesn't work. Call PSS back. Directory service was trying to start and got hung, can't restore to hung service. Change to manual start and reboot. Directory restores!!! Restore info store. (8 gigs). 2 hours later ready to go! (almost) Now the internet mail connector isn't working. Dawn is breaking and panic begins to creep in. Users will be screaming in about 2 hours. Call PSS again. End up deleting the IMC and creating a new one. They very patiently step me through lots of good stuff, including making sure I'm not an internet relay and that I'm not doing circular logs. They even stand by while I reinstall my Anti-virus for exchange. Everything is working. It's now 7am and I'm back to my original pre-upgrade status from 7pm the night before. Problem summary: PSS thinks that the problem was caused by the mail service account user not having complete permissions at the org container. By the time this was corrected by PSS (and me) the upgrade was stuck. They are pretty sure and reasonably confident the upgrade will work next time. Moral: MAKE BACKUPS. PLAN FOR EXTRA TIME. PSS is your friend (I was on the phone with them for about 4 hours) This was so much fun we're planning another attempt. This will be on a Saturday morning so I'll have lots of time to recover
RE: Exchange 5.5 to 2000 Upgrade horror story
I think they are the simplest to perform. But the outcome is not always the prettiest. --Kevinm KMAP-SR, M, WLKMMAS, UCC+WCA, And Beyond http://www.daughtry.ca/ For Graphics and WebDesign, GO here! -Original Message- From: William Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 12:20 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 to 2000 Upgrade horror story Ya... In-place upgrades suck. Let us know how Saturday goes. -Original Message- From: Tom.Gray [mailto:[EMAIL PROTECTED]] Sent: Friday, August 02, 2002 7:05 AM To: MS-Exchange Admin Issues Subject: Exchange 5.5 to 2000 Upgrade horror story This is just an informational post, you're welcome to comment on it but I'm not really asking any questions. Just thought folks out there getting ready to upgrade might want to hear the story. I just spent the night upgrading (or trying to upgrade) my exchange 5.5 server. We have a very simple network. 1 domain. 200 users. 1 exchange server. 2 domain controllers (not the exchange server). Started about 2 weeks ago prepping for upgrade. Armed with: White Paper in-place upgrade from msoft exchange 5.5 to msoft exchange 2000 Q316886 How To: Migrate from exchange server 5.5 to exchange 2000 server Q282309 upgrading exchange server 5.5 service pack 4 to exchange 2000 server Q295922 considerations when you upgrade to exchange 2000 server Q296260 how to configure a two-way recipient connection agreement for exchange server 5.5 users Q253829 description of the active directory connector deletion mechanism And, of course, monitored this list (and the sun-exchange) one for upgrade ideas! Now some of the documents have conflicting information. If you weed thru the dates and such you can usually figure out what is really true. For example, the white paper states you MUST have at least one domain running in native mode, but the HOW TO describes a scenario where all domains are in mixed mode. With the domain controllers upgraded to win2k active directory (mixed mode) last month I tackled the exchange upgrade this month. Went thru the white paper and how to, updating the schema (forestprep and domainprep) and ran all the tests listed in those docs to verify it was working. Got exactly the results they told me! First time I ran the actual upgrade got my first rude surprise. My vendor had shipped me the Exchange 2000 standard edition media (which doesn't really say standard on it, just Exchange 2000) and the upgrade process stopped immediately with You can't go from enterprise to standard you idiot Two days later I have the correct media. Take the server off the network and run an online backup (Veritas backup exec with exchange option). Verify the backup worked. With exchange services down get back on the network and run domain tests again. Everything ok! Run the upgrade! The upgrade goes thru several processes but hangs at Setup failed while installing sub-component Site Replication Service with error code 0xC007041D -- retry or cancel search MS knowledge base and looks like a permissions issue (Q278254 and Q273730). Hmm, make sure the exchange service account has all the permissions and click retry. Still no work. Rats. Getting late so time to make the $250 call to PSS! PSS steps me thru lots of stuff, nothing works. They have me change the service account user permissions at the ORG container from CUSTOM to SERVICE ACCOUNT (i'm probably not saying this exactly correct). Still no joy. Try to cancel out of that error message. Nada. Have to task manager/shut down process. They then refer me to the ultimate nightmare: Q264309 - How to Roll Back A failed Upgraded from Exchange Server 5.5. to Exchange 2000. Yuck. Go into registry and delete the stuff, rename the exchsrvr folders, uninstall IIS, restart server, install IIS, re-apply all service packs and hotfixes (that really sucks), delete the renamed exchsrvr folders, setup /r exchange 5.5, restore directory and info store. Restoring directory service doesn't work. Call PSS back. Directory service was trying to start and got hung, can't restore to hung service. Change to manual start and reboot. Directory restores!!! Restore info store. (8 gigs). 2 hours later ready to go! (almost) Now the internet mail connector isn't working. Dawn is breaking and panic begins to creep in. Users will be screaming in about 2 hours. Call PSS again. End up deleting the IMC and creating a new one. They very patiently step me through lots of good stuff, including making sure I'm not an internet relay and that I'm not doing circular logs. They even stand by while I reinstall my Anti-virus for exchange. Everything is working. It's now 7am and I'm back to my original pre-upgrade status from 7pm the night before. Problem summary: PSS thinks that the problem was caused by the mail service account user not having complete permissions at the org
Exchange 5.5 to 2000 Upgrade
We just upgraded our network from nt4/exch5.5 to 2KAD/Exch2K. Quite often when someone opens Outlook on their desktop, they will get the Microsoft Exchange Server is Unavailable message. Upon clicking Retry the almost always get in, but this problem is quite annoying. Anyone have any experiences on this? Any help is appreciated, Thank you, Jim List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 to 2000 Upgrade
Your answer is well documented in the following Q Article. You can increase the time out value or suppress the message completely. PSS ID Number: Q293650 -Original Message- From: Frey, James [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 17, 2002 9:43 AM To: MS-Exchange Admin Issues Subject: Exchange 5.5 to 2000 Upgrade We just upgraded our network from nt4/exch5.5 to 2KAD/Exch2K. Quite often when someone opens Outlook on their desktop, they will get the Microsoft Exchange Server is Unavailable message. Upon clicking Retry the almost always get in, but this problem is quite annoying. Anyone have any experiences on this? Any help is appreciated, Thank you, Jim List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Exchange 5.5 to 2000
My exchange 5.5 box currently is NOT running IIS at all. According to MS documentation I need to install II and NNTP on my Exchange 5.5 box BEFORE upgrading to 2000. Is that true? I'd rather not have IIS on it if possible but it looks like its a core requirement now. thanks. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 to 2000
Yes, it is a core requirement. The SMTP service for example is extended from IIS. -Original Message- From: Jesse Rink [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 12:59 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 to 2000 My exchange 5.5 box currently is NOT running IIS at all. According to MS documentation I need to install II and NNTP on my Exchange 5.5 box BEFORE upgrading to 2000. Is that true? I'd rather not have IIS on it if possible but it looks like its a core requirement now. thanks. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 to 2000
Provided you have ADS already installed, unless you have the enterprise version and are looking at a FE/BE config, then yes, IIS is required for OWA and such... -Original Message- From: Jesse Rink [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 3:59 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 to 2000 My exchange 5.5 box currently is NOT running IIS at all. According to MS documentation I need to install II and NNTP on my Exchange 5.5 box BEFORE upgrading to 2000. Is that true? I'd rather not have IIS on it if possible but it looks like its a core requirement now. thanks. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 to 2000
Title: RE: Exchange 5.5 to 2000 Dude, you should and need IIS for exchange 2000 The exchange 2000 store is a web based engine. -Original Message- From: Jesse Rink [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 2:59 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 to 2000 My exchange 5.5 box currently is NOT running IIS at all. According to MS documentation I need to install II and NNTP on my Exchange 5.5 box BEFORE upgrading to 2000. Is that true? I'd rather not have IIS on it if possible but it looks like its a core requirement now. thanks. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 to 2000
IIS is needed for both. Indeed FE/BE communication is over port 80. -Original Message- From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 1:01 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 to 2000 Provided you have ADS already installed, unless you have the enterprise version and are looking at a FE/BE config, then yes, IIS is required for OWA and such... -Original Message- From: Jesse Rink [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 3:59 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 to 2000 My exchange 5.5 box currently is NOT running IIS at all. According to MS documentation I need to install II and NNTP on my Exchange 5.5 box BEFORE upgrading to 2000. Is that true? I'd rather not have IIS on it if possible but it looks like its a core requirement now. thanks. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 to 2000
I'm glad you clarified that, I confused myself with my own post... :o) -Original Message- From: William Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 4:20 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 to 2000 IIS is needed for both. Indeed FE/BE communication is over port 80. -Original Message- From: Ely, Don [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 1:01 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 to 2000 Provided you have ADS already installed, unless you have the enterprise version and are looking at a FE/BE config, then yes, IIS is required for OWA and such... -Original Message- From: Jesse Rink [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 10, 2002 3:59 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 to 2000 My exchange 5.5 box currently is NOT running IIS at all. According to MS documentation I need to install II and NNTP on my Exchange 5.5 box BEFORE upgrading to 2000. Is that true? I'd rather not have IIS on it if possible but it looks like its a core requirement now. thanks. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: exchange 5.5 to 2000 migration
I would think not long at all, your best bet is probably to exmerge the 3.4 gb and then exmerge it back in. If you do it this way you can bring the pst files local and be up much sooner. -Original Message- From: Dennis DeVries [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 3:38 PM To: MS-Exchange Admin Issues Subject: exchange 5.5 to 2000 migration All: We are a small business, 1 exchange server/PDC and 1 BDC all NT4 at this point We are slowly moving to win 2000 and our first task is to upgrade to exchange 2000 on a new machine from exchange 5.5 (on nt4 sp6). Do any of you have a feel for now long it will take to migrage a 3.4 gig information store? We have a 100mb network. Thanks in advance for your help. Dennis List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm This is a disclaimer.. and we disclaim anything that gets us in trouble. -Advanced PC List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
exchange 5.5 to 2000 migration
All: We are a small business, 1 exchange server/PDC and 1 BDC all NT4 at this point We are slowly moving to win 2000 and our first task is to upgrade to exchange 2000 on a new machine from exchange 5.5 (on nt4 sp6). Do any of you have a feel for now long it will take to migrage a 3.4 gig information store? We have a 100mb network. Thanks in advance for your help. Dennis List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: exchange 5.5 to 2000 migration
Umm.. The Exchange upgrade would be your second task. Moving to AD would be your first. -Original Message- From: Dennis DeVries [mailto:[EMAIL PROTECTED]] Sent: Friday, May 17, 2002 3:38 PM To: MS-Exchange Admin Issues Subject: exchange 5.5 to 2000 migration All: We are a small business, 1 exchange server/PDC and 1 BDC all NT4 at this point We are slowly moving to win 2000 and our first task is to upgrade to exchange 2000 on a new machine from exchange 5.5 (on nt4 sp6). Do any of you have a feel for now long it will take to migrage a 3.4 gig information store? We have a 100mb network. Thanks in advance for your help. Dennis List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server
Looks pretty conclusive, I'll schedule an upgrade. Thanks for all contributions. Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server
The ability to use NTBackup to backup Exchange to disk is worth it alone. William -Original Message- From: Tony Flannery [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 25, 2002 1:18 AM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 on 2000 server Looks pretty conclusive, I'll schedule an upgrade. Thanks for all contributions. Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server
More than happily. Fresh install or upgrade from NT underneath? William -Original Message- From: Tony Flannery [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 12:17 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 on 2000 server Does Exchange 5.5 run happily on Windows 2000 server ? Has anyone experienced problems with this configuration ? Thanks, Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Re: Exchange 5.5 on 2000 server
Works fine here. I had Exch 5.5 on NT4. Built Win2K from scratch, and loaded Exch 5.5 on it. Then MOVEd mailboxes over. Even installed OWA and it was able to keep up with me. About 25 users. The only caveat, make sure both Exch 5.5 had similar installations, same SP loaded, and were able to see each other before moving over. :-) - Mark -- - Original Message - From: Tony Flannery [EMAIL PROTECTED] To: MS-Exchange Admin Issues [EMAIL PROTECTED] Sent: Wednesday, April 24, 2002 03:16 PM Subject: Exchange 5.5 on 2000 server Does Exchange 5.5 run happily on Windows 2000 server ? Has anyone experienced problems with this configuration ? Thanks, Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server
Works great for me...(even with ArcserveIT)...on a clean install of Win2K. -Original Message- From: Tony Flannery [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:17 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 on 2000 server Does Exchange 5.5 run happily on Windows 2000 server ? Has anyone experienced problems with this configuration ? Thanks, Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server
Title: RE: Exchange 5.5 on 2000 server I am running E5.5 SP4 on our Windows 2000 DC's -Original Message- From: Tony Flannery [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:17 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 on 2000 server Does Exchange 5.5 run happily on Windows 2000 server ? Has anyone experienced problems with this configuration ? Thanks, Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server
Runs great, we have 8, 2K machines running 5.5 SP4. -Original Message- From: Tony Flannery [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 3:17 PM To: MS-Exchange Admin Issues Subject:Exchange 5.5 on 2000 server Does Exchange 5.5 run happily on Windows 2000 server ? Has anyone experienced problems with this configuration ? Thanks, Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server
Yes. I have 15 MSX 5.5 SP4 boxes all running W2K enterprise. Most have been upgrades from NT4 too. Nothing but good things to say about it so far. Especially the terminal service : ) Tim Jensen Cingular Wireless, Chicago -Original Message- From: Tony Flannery [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:17 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 on 2000 server Does Exchange 5.5 run happily on Windows 2000 server ? Has anyone experienced problems with this configuration ? Thanks, Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server (recovery server)
I am planning on testing this soon, but since I'm anxious, does anyone know if you are running an NT 4, Exchange 5.5 server, can you use a Windows 2000, Exchange 5.5 server as a recovery server? In other words, if I have Exchange 5.5 running the same service pack and patches and everything, could I just do an online restore to that server? This is assuming the old one goes down and I rename the recovery server to the same name as the original. -Original Message- From: JENSEN, TIMOTHY C [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:57 PM To: MS-Exchange Admin Issues Subject:RE: Exchange 5.5 on 2000 server Yes. I have 15 MSX 5.5 SP4 boxes all running W2K enterprise. Most have been upgrades from NT4 too. Nothing but good things to say about it so far. Especially the terminal service : ) Tim Jensen Cingular Wireless, Chicago -Original Message- From: Tony Flannery [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:17 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 on 2000 server Does Exchange 5.5 run happily on Windows 2000 server ? Has anyone experienced problems with this configuration ? Thanks, Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server
Title: RE: Exchange 5.5 on 2000 server Sheesh that is a lot of Exchanging! -Original Message- From: Cross, Tom [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:30 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 on 2000 server Runs great, we have 8, 2K machines running 5.5 SP4. -Original Message- From: Tony Flannery [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 3:17 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 on 2000 server Does Exchange 5.5 run happily on Windows 2000 server ? Has anyone experienced problems with this configuration ? Thanks, Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server
Title: RE: Exchange 5.5 on 2000 server just service pack 4 and 2 them !! Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. -Original Message- From: Tony Flannery [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 15:17 To: MS-Exchange Admin Issues Subject: Exchange 5.5 on 2000 server Does Exchange 5.5 run happily on Windows 2000 server ? Has anyone experienced problems with this configuration ? Thanks, Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server (recovery server)
Title: RE: Exchange 5.5 on 2000 server (recovery server) Allen, We went from an Exch 5.5 NT4 Server to an Exch 5.5 W2k Server, exactly the way you mentioned. Don Guyer Information Systems Citadel Federal Credit Union [EMAIL PROTECTED] Ph: 800.666.0191 x7072 Fax: 610.380.6083 www.citadelfcu.org -Original Message- From: Allen Crawford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 4:00 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 on 2000 server (recovery server) I am planning on testing this soon, but since I'm anxious, does anyone know if you are running an NT 4, Exchange 5.5 server, can you use a Windows 2000, Exchange 5.5 server as a recovery server? In other words, if I have Exchange 5.5 running the same service pack and patches and everything, could I just do an online restore to that server? This is assuming the old one goes down and I rename the recovery server to the same name as the original. -Original Message- From: JENSEN, TIMOTHY C [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:57 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 on 2000 server Yes. I have 15 MSX 5.5 SP4 boxes all running W2K enterprise. Most have been upgrades from NT4 too. Nothing but good things to say about it so far. Especially the terminal service : ) Tim Jensen Cingular Wireless, Chicago -Original Message- From: Tony Flannery [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:17 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 on 2000 server Does Exchange 5.5 run happily on Windows 2000 server ? Has anyone experienced problems with this configuration ? Thanks, Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server (recovery server)
I don't think so. Reason I say that is if you glanced at the event log after applying NT SP6 you would have noticed log msgs about changes to the edb's. I think it extended them or something. I tried to restore just the priv to an NT 4 box with a lower SP as in production and the IS would not start. I'm sure others will chime in on this one. Tim Jensen Cingular Wireless, Chicago -Original Message- From: Allen Crawford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 3:00 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 on 2000 server (recovery server) I am planning on testing this soon, but since I'm anxious, does anyone know if you are running an NT 4, Exchange 5.5 server, can you use a Windows 2000, Exchange 5.5 server as a recovery server? In other words, if I have Exchange 5.5 running the same service pack and patches and everything, could I just do an online restore to that server? This is assuming the old one goes down and I rename the recovery server to the same name as the original. -Original Message- From: JENSEN, TIMOTHY C [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:57 PM To: MS-Exchange Admin Issues Subject:RE: Exchange 5.5 on 2000 server Yes. I have 15 MSX 5.5 SP4 boxes all running W2K enterprise. Most have been upgrades from NT4 too. Nothing but good things to say about it so far. Especially the terminal service : ) Tim Jensen Cingular Wireless, Chicago -Original Message- From: Tony Flannery [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:17 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 on 2000 server Does Exchange 5.5 run happily on Windows 2000 server ? Has anyone experienced problems with this configuration ? Thanks, Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server
William, Will probably upgrade. Tony List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 on 2000 server (recovery server)
Title: Message the base os Version does not matter as long as exchange is on the same SP when you try to mount to recovered store. --Kevinm TSSSBE, M, WLKMMAS, UCC+WCA, And Beyondhttp://www.daughtry.ca/ For Graphics and WebDesign, GO here! -Original Message-From: Don Guyer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:21 PMTo: MS-Exchange Admin IssuesSubject: RE: Exchange 5.5 on 2000 server (recovery server) Tim, I went from an NT4 SP6a Exchange 5.5 SP4 box, to an W2k SP1 Exchange 5.5 SP4 box. I installed Exchange on the new W2k box and configured it in an isolated environment, matching it to our live server. When I was ready to go with the new box, I copied the Exchange folders from the old to the new, and it worked like a champ. But, I had the luxury of taking the downtime to do it this way. Don Guyer Information Systems Citadel Federal Credit Union [EMAIL PROTECTED] Ph: 800.666.0191 x7072 Fax: 610.380.6083 www.citadelfcu.org -Original Message- From: JENSEN, TIMOTHY C [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 5:18 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 on 2000 server (recovery server) I don't think so. Reason I say that is if you glanced at the event log after applying NT SP6 you would have noticed log msgs about changes to the edb's. I think it extended them or something. I tried to restore just the priv to an NT 4 box with a lower SP as in production and the IS would not start. I'm sure others will chime in on this one. Tim Jensen Cingular Wireless, Chicago -Original Message- From: Allen Crawford [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 3:00 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 on 2000 server (recovery server) I am planning on testing this soon, but since I'm anxious, does anyone know if you are running an NT 4, Exchange 5.5 server, can you use a Windows 2000, Exchange 5.5 server as a recovery server? In other words, if I have Exchange 5.5 running the same service pack and patches and everything, could I just do an online restore to that server? This is assuming the old one goes down and I rename the recovery server to the same name as the original. -Original Message- From: JENSEN, TIMOTHY C [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:57 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 on 2000 server Yes. I have 15 MSX 5.5 SP4 boxes all running W2K enterprise. Most have been upgrades from NT4 too. Nothing but good things to say about it so far. Especially the terminal service : ) Tim Jensen Cingular Wireless, Chicago -Original Message- From: Tony Flannery [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 24, 2002 2:17 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 on 2000 server Does Exchange 5.5 run happily on Windows 2000 server ? Has anyone experienced problems with this configuration ? Thanks, Tony. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at:http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
Exchange 5.5 to 2000 migration moving servers
I have been struggling with this for a couple of weeks. I am trying to move NT Domain that includes exchange 5.5 to Windows 2000 Active directory and Exchange 2000. The MS Migration tool seems to be fine but the Exchange mail box option is grayed out. Anyone have any experience with this? Thanks! List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 to 2000 migration moving servers
Title: RE: Exchange 5.5 to 2000 migration moving servers Use the Ed Crowley method: Exchange 5.5 - FAQ Appendix A - The Ed Crowley Server Move Method This method should create much less potential for grief because you can have practically zero perceived downtime. You can perform all of the steps below at your own pace and in just about any order, and most, if not all, of them during working hours. Furthermore, you can usually very easily back out of any of the steps if things don't go as expected. While not the easiest method technically, it is certainly the least risky and the least likely to deprive you of sleep. Important Note: Exchange 4.0 and 5.0 Standard Edition did not permit multiple servers in the same site. If you have only one server and are running Standard Edition, then you'll need to upgrade to Enterprise, or add the Exchange Connector. You might want to ask your friendly neighborhood Microsoft representative to see if he might be willing to loan you a copy since all you need it for is to upgrade to version 5.5. Important Acknowledgement: My thanks go to Rich Matheisen for his valuable input to this revision. The method: 1. Bring up a new server as a new server in the same site with a different name of course. 2. In the old server's Information Store properties, change the location of the mailboxes' Public Folder server to be the new server. This will take care of any newly created public folders. (You'll have to stop and restart the Exchange services before this will take effect.) 3. Check all distribution lists to ensure that none of them specifically name the old server as their expansion server. 4. Move the mailboxes using the Exchange Administrator. Move all at once, one at a time, or at some rate in between. In many cases, you can move the mailboxes during working hours because each user is affected only during the time his own mailbox is the one being moved. 5. Create replicas of the public folders on the new server. When the contents of the folders have replicated (do wait a little while!), remove the replicas from the old server. 6. Move any connectors from the old server to another server. 6a. For each site-type connector on the server you're replacing, create a parallel connector to all connected sites on the new server, including adding the sites in the Connected Sites tab. On the server you're replacing, in the connector's Connected Sites tab, remove the sites. Recalculate routing. Verify that messages flow through the new connector. Then remove the connector definitions from old server and from the server at the other end of those connectors. 6b. For each IMS Internet connector, create MX records pointing to the IMS on the new server as appropriate, and change the cost on the old MX record so that it is higher than the new one. In the properties for the IMS on server you're removing, remove all Address Space entries. When you have checked and verified that all messages are flowing through the new connector, remove the old one, then recalculate routing again. 6c. For each replication bridgehead server on the server being replaced, change the local bridgehead server property to the new server. Adjust the replication partner's remote bridgehead server property to the new server as well. 6d. For any other type of connector, including Microsoft Mail, move them too. 7. Follow the steps in Q152959. 8. Leave the old server up for a while so MAPI clients connect to the new server automatically. It's true! You don't have to do anything to MAPI clients! 9. Notify POP3 and IMAP4 users of how to reconfigure their clients to point to the new server. (If you have a WINS and/or DNS alias for this address, point it to the new server.) 10. If the old server has a Key Management Server, you'll need to move that too. 11. Stop the Exchange services, then remove the server from the site. To move Exchange to another server using the same name, follow Q155216. Exchange 5.5 - FAQ Appendix B - The Ed Crowley Never Restore Method If you run your system using the Ed Crowley Never Restore Method(tm), you will likely never have to restore a single mailbox. (No guarantees, but it has worked for us.) 1. Implement deleted item recovery for 30 days or more. MAPI Users will be able to restore anything THEMSELVES that they have deleted for at least that long. 2. Don't delete mailboxes right away. Hide them, remove SMTP addresses, make the departing user's boss the mailbox owner, and enter the termination date in the Notes field. Then wait at least 30 days. 3. To restore a message purged from Deleted Items, use Outlook to select the Deleted Items folder, then select Tools, Recover Deleted Items. By default, Outlook will only recover items purged from the Deleted Items folder. However, the dumpster keeps items deleted from all folders for the specified retention period. To make Outlook recover items purged from any folder, including public folders, see the TechNet
Exchange 5.5 or 2000
I want to implement Exchange but am not sure whether to install 5.5 or 2000. Is 2000 stable? Any suggestions would be appreciated. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 or 2000
# of users ? More info needed.. Yes, it is stable -Original Message- From: Henry Ward [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 16:06 To: MS-Exchange Admin Issues Subject: Exchange 5.5 or 2000 I want to implement Exchange but am not sure whether to install 5.5 or 2000. Is 2000 stable? Any suggestions would be appreciated. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 or 2000
This is for our in-house system. No more than 10-users. Primarily want to install to start learning the system. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 or 2000
Have you got Win2K with AD? You need it for E2K. -Original Message- From: Henry Ward [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 3:24 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 or 2000 This is for our in-house system. No more than 10-users. Primarily want to install to start learning the system. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 or 2000
What type of NT domain do you have? If you have an NT4 domain, E55. If you have AD, try E2K. -Original Message- From: Henry Ward [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 1:06 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 or 2000 I want to implement Exchange but am not sure whether to install 5.5 or 2000. Is 2000 stable? Any suggestions would be appreciated. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 or 2000
Yes, ADS is installed already. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 or 2000
Please be sure to include the text below your message so we know who you are replying too. -Original Message- From: Henry Ward [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 1:33 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 or 2000 Yes, ADS is installed already. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 or 2000
Exchange2000 is as stable as the person installing it. -Original Message- From: Henry Ward [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 1:06 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 or 2000 I want to implement Exchange but am not sure whether to install 5.5 or 2000. Is 2000 stable? Any suggestions would be appreciated. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 or 2000
Excellent point. Steve Clark Clark Systems Support, LLC AVIEN Charter Member Who's watching your network? www.clarksupport.com 301-610-9584 voice 240-465-0323 Efax The data furnished in connection with this document is deemed by Clark Systems Support, LLC., to contain proprietary and privileged information and shall not be disclosed or used for the benefit of others without the prior written permission of Clark Systems Support, LLC. -Original Message- From: William Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 4:56 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 or 2000 Exchange2000 is as stable as the person installing it. -Original Message- From: Henry Ward [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 1:06 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 or 2000 I want to implement Exchange but am not sure whether to install 5.5 or 2000. Is 2000 stable? Any suggestions would be appreciated. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 or 2000
Is your domain a win2k or NT4 domain? ~ -K.Borndale IT Manager Sybari Software 631.630.8569 -direct dial 631.439.0689 -fax http://www.sybari.com One man's ceiling is another man's floor |-+-- | | Henry Ward | | | henryw@wardassocia| | | tesinc.com| | | | | | 02/22/2002 04:24 PM| | | Please respond to | | | MS-Exchange Admin | | | Issues| | | | |-+-- --| | | | To: MS-Exchange Admin Issues [EMAIL PROTECTED] | | cc: | | Subject: RE: Exchange 5.5 or 2000 | --| This is for our in-house system. No more than 10-users. Primarily want to install to start learning the system. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 or 2000
We have W2K Server with ADS installed. Henry Ward List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
STU _ MAIL LOOP _ RE: Exchange 5.5 or 2000
-Original Message- From: Henry Ward [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 2:26 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 or 2000 We have W2K Server with ADS installed. Henry Ward List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: Exchange 5.5 or 2000
you calling my installs bad? --Kevinm M, WLKMMAS, UCC+WCA, And Beyond Did I just say that out loud? -Original Message- From: William Lefkovics [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 1:56 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 or 2000 Exchange2000 is as stable as the person installing it. -Original Message- From: Henry Ward [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 1:06 PM To: MS-Exchange Admin Issues Subject: Exchange 5.5 or 2000 I want to implement Exchange but am not sure whether to install 5.5 or 2000. Is 2000 stable? Any suggestions would be appreciated. List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
RE: STU _ MAIL LOOP _ RE: Exchange 5.5 or 2000
It must have stopped. -Original Message- From: David N. Precht [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 6:24 PM To: MS-Exchange Admin Issues Subject: RE: STU _ MAIL LOOP _ RE: Exchange 5.5 or 2000 What are you talking about, no mail loop from this end -Original Message- From: Martin Blackstone [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 18:13 To: MS-Exchange Admin Issues Subject: STU _ MAIL LOOP _ RE: Exchange 5.5 or 2000 -Original Message- From: Henry Ward [mailto:[EMAIL PROTECTED]] Sent: Friday, February 22, 2002 2:26 PM To: MS-Exchange Admin Issues Subject: RE: Exchange 5.5 or 2000 We have W2K Server with ADS installed. Henry Ward List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm List Charter and FAQ at: http://www.sunbelt-software.com/exchange_list_charter.htm
