exchangefaq.org
brought to you by Simpler-Webb

Table of Contents

  1. Administrivia
  2. Definitions
  3. Installation
  4. Migration & Interoperability
  5. Administration & Maintenance
  6. Exchange 2000 Move Server Method
  7. Additional Resources
  8. What is the M: Drive?
  9. Disable SMTP Access
  10. Martin Blackstone's List of Danger


Other FAQs

Exchange 2003 FAQ
Exchange 2000 FAQ
Exchange 5.5 FAQ


Exchange Resource Manager

Find out how you can manage rooms and resources though Exchange with out the hassles and complications of scripting!

ยป Download a free trial today

FAQs / Exchange 2000 / Migration & Interoperability

01


No. The enhanced OWA is built directly into the store technology and only a mailbox residing on an Exchange 2000 server can be accessed using the enhanced OWA interface. Nice try, though.

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1153)
Categories: Exchange 2000/Migration & Interoperability |

02


Yes.

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1154)
Categories: Exchange 2000/Migration & Interoperability |

03


First, you need to use the Exchange 5.5 Admin program to delete the directory replication connectors (Org | Site | Configuration | Connections). Once you have deleted the connections, you need to be logged on with an account with Schema Admin privileges to delete the ADC connector.

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1155)
Categories: Exchange 2000/Migration & Interoperability |

04


There is no hard and fast rule in this regard. Some potential guidelines include:
  1. At least 1 per routing group
  2. One for every 4 Exchange servers in a routing group
  3. One (or more) for each physical location


Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1156)
Categories: Exchange 2000/Migration & Interoperability |

05


After converting from Exchange 5.5 OWA to 2000 OWA, all the users had book marked the URL of mail.company.com/exchange/logon.asp, since in 5.5 OWA it automatically would pull the user from the root URL into a logon page (since it used ASP) but now the user only sees the same base URL of mail.company.com/exchange. So once the users used the book mark or in some cases the "autocomplete" feature in IE they would be pulled to a dead address. But... since you can't really edit the M:\ drive the /EXCHANGE points to you couldn't build a ASP page to do a response.redirect in ASP.
  • Go into the front-end server that is hosting your OWA.
  • Start up IIS admin and locate the /Exchange virtual directory
  • Right click on the /Exchange directory and using the "wizard" create a new virtual directory called logon.asp. When it prompts where the content is located just put something like c:\inetpub\wwwroot
  • Once the virtual root has been created, right click it, select properties then select the tab labeled "Virtual Directory"
  • Select the "A redirection to a URL" and then in the "Redirect to" URL enter /exchange/
What happens is when the user hits the virtual root of /exchange/logon.asp it pulls the user back to only /exchange

Last Updated by Simpler-Webb on 8/7/2003 1:59:40 PM (QID #1157)
Categories: Exchange 2000/Migration & Interoperability |