Darin R Camp
1. HTTP VS's - Backend standalone versus clusters
I'm trying to build out a simple front-end back-end (not
clustered) development environment as close to my
production build (clustered BE Exchange) as possible. With
a single BE Exchange server you can create new HTTP
Virtual Servers in ESM but you can't delete the original
http VS and with it the corresponding Exchange VD's in the
Default Web site in IIS. You CAN delete the VD's in IIS
but after you restart, they reappear. In fact, you can't
even get a "delete" option by right clicking the default
Exchange http VS in ESM even though you may have created a
new VS with all of the same containers. As well, you can't
pull up the properties when right clicking it, it tells
you to go to IIS admin to configure it. This is not the
case with my Exchange HTTP VS on my clustered Exchange
Backend, you CAN delete, rename, etc. these on my cluster.
My goal here is to remove the default HTTP VS in ESM on my
standalone Exch 2000 Adv Server SP1 and the corresponding
VD's in IIS in the Default Web Site.
3. Exchange 5.5 non cluster to Exchange 2000 Cluster
4. OWA
5. outlook address book vs pab vs global address books with exch server 4.0
6. Inbound Messages awaiting delivery - why?
7. Business/technical argument for Exchange 2k cluster vs. Exchange 5.5 cluster
9. AntiVirus : F-Secure vs Network Associate vs TrendMicro vs Norton Antivirus
10. OST vs PST - OL97 vs OL98 vs OL2000
11. Business/technical argument for Exchange 2k cluster vs. Exchange 5.5 cluster
12. Exchange 2K Server vs Exchange 2K Enterprise Server
13. Exchange 2000 Server vs. Exchange 2000 Enterprise Server