Activesync Mobile Admin Web Tool Installing incorrectly

Installing the Mobile Administration Web tool
Follow the instructions included with the download to install the Exchange ActiveSync Mobile Administration Web tool on a front-end server that runs Exchange Server 2003 SP2. The installation program creates the MobileAdmin virtual directory, through which the tool can be accessed.

When installed correctly, the Exchange ActiveSync Mobile Administration Web tool is available from any remote computer that has an Internet browser that can access the virtual directory that is associated with the tool.

However, to access the Exchange ActiveSync Mobile Administration Web tool from the same computer upon which it is installed, you must use one of the following approaches:

" Add the server name to the Local intranet list for Internet Explorer: In Internet Explorer, click Tools, click Internet Options, click Security, click Local intranet, and then click Sites.
 
" Use localhost as the server name when specifying the mobileAdmin URL in the browser (for example, https://localhost/mobileAdmin).
 
if that doesnt work then
try creating it manually.

You could try deleting the original default web site, leaving the newly created one?

The tool will usually go on to a separate site when there is something on the default site that conflicts with what it needs to work.
What you should find is that it is on a separate port. I cannot remember the default port it goes on, but you will need to access it in the format of https://host.domain.com:8080/mobileadmin

You must include the https:// bit and the port number.

DO NOT follow the advice above about deleting the default web site unless you are sure that there is nothing on the default web site that you need (like Exchange OWA, RPC over HTTPS etc).

Simon.

I definitely cannot delete the original default web site because that is where my OWA resides.  It was supposed to create the MobileAdmin virdir in the same area.  Still don't know why it didn't.  I'll try just creating it manually and then deleting the second site.  I followed the exact steps listed above in the first comment, and that's how I got where I'm at now.

I've noticed that in installed the files into c:\program files rather than to c:\inetpub\wwwroot, which is where the default web site is directed to.  Will the app still work if I pick up and move the files to wwwroot, then manually create the virdir?  I'll give it a try...

You could leave the files where they're at. In IIS, right click on the created virtual directory and select All Tasks -> Save configuration to a File.

Then, right click on the main default web site and select New -> Virtual Directory (from file)...and browse to the configuration you saved earlier.

Well, I ended up figuring it out after all.  I created the virdir and pointed it to the default installation location, modified the properties on the virdir to match the one that it created automatically.  I was then able to access it.  i still never figured out why it didn't install properly.

Do you think OWA is under \inetpub\wwwroot?
It isn't.

I would doubt if it will work if you move the files because there will be links to the files in their original locations.
Mobile Admin has installed correctly, it just isn't where you would expect it to be. WSUS does the same thing, usually on an SBS Server and has its own port 8530.

Simon.

No, I actually found that the OWA files are not in wwwroot either, you're right about that.  However, I still don't think it installed correctly or it would have created the MobilAdmin virdir under the existing Default Web Site, rather than creating a new one that no one can access.  There was no way to access the application because when you go to https://servername/mobileadmin, it's trying to find a "mobileadmin" virtual directory under the default web site, and it doesn't exist.  If that was a good installation, it should have listed all that manual manipulation in the installation instructions, and it did not.

Another way for MS to drive me insane!

Thanks for your help anyway...