Connect existing non-default web site Exchange virtual directory into Exchange System Mnager?

The virtual directories on our Exchange 2003 Front End servers are not were not created in the Default Web Site in IIS and were created under another name using IIS and not ESM. So when I open ESM and look at the HTTP virtual directory, it shows stopped. Is it possible to link the existing new virtual directory to ESM or do I have to recreate the directories using ESM for them to show? I want to be able to managae as much as possible using ESM and not through IIS. Can I connect ESM to an existing virtual directoiry that is not the default web site?
LVL 1
maderosiaAsked:
Who is Participating?
 
SembeeCommented:
Are the Exchange virtual directories in the Default Web Site as well, or were they removed from there as well? If they were removed then I believe that is an unsupported configuration.

Either way, they should have been created through ESM, not any other method.

Simon.

--
If your question has been answered, please remember to accept the answer and close the question.
0
 
maderosiaAuthor Commented:
They are in the default web site as well but the default site is stopped. I told this was done because of the other webs on the box. We just replaced our 2 Exchange front end servers which are also web servers. I have been reading on the correct way to create them and I find that I was told wrong. I just want to be able to control the settings using ESM as it should be. It sounds like I will have to recreate the virtual directories using ESM and delete the manually created directories. Do you agree?
0
 
SembeeCommented:
My preference would be to use the default web site. That is how Exchange is designed to work. Having other web sites on the machine is not an issue, I do that at home. Although if those web sites are publicly accessible by anonymous traffic then you have bigger problems to worry about than whether ESM can manage them.

Simon.

--
If your question has been answered, please remember to accept the answer and close the question.
0
 
maderosiaAuthor Commented:
All new sites are set up correctly so I am not worried about the access. I asked a few more questions and I am told that this issue is because the SharePoint webs need to be in the Default Web site too and it caused conflict. I am trying to clean up and get our environment set up the best way and that is how I noticed this was not correct in our environment. Thanks for the thoughts. I will be creating new virtual directories using ESM that will match the default web site settings. I had seen that you explained that that is the correct process in this situation in another post even though it is not best and may cause problems down the road. At least that will get me closer to where I am now. I will still question the setup to see if Exchange and SharePoint can co-exist in the Default Web site.
Thanks Sembee,
Mark
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.