Outlook Anywhere Virtual Directory - Can it be moved?

I have a native Exchange / Outlook 2007 Environment.  OWA is our main deployment venue, so in the beginning, we used a URL redirection on the Default Web Site to point via DNS to the OWA sign-in page.  Now that we are trying to enable Outlook Anywhere, I would like to move the RPC and RPCWithClient virtual dirs to another website on the CAS, using DNS to point to them.  The problem is:  when I enable RPC over HTTPS, and go to enable Outlook Anywhere, it points to the default location under the Default Web Site.  I can't find any way to change it.  I've run every cmdlet I can think of with every argument in the book, but when I try to specify another website name or location for the vdir, I always get the error that the object was not found on the DC.  Apparently the cmdlet is trying to specify the location of the SCP instead of changing the info in the SCP to use the new url/vdir.  Anyone else run into this?  The only workaround I can think of is to host OWA on another website, give it another listener IP, and change DNS to go there, but that could be messy in a production environment.
lhcitAsked:
Who is Participating?
 
SembeeConnect With a Mentor Commented:
I have moved it, and have it working when moved. However running get-outlookanywhere on my server also shows it using the default web site.

I should be clear - I have copied it, not moved it. The /rpc virtual directory still exists on the default web site.

Simon.
0
 
ATIGCommented:
question.... where are you trying to move the Vdir too? Under another web site?

those virtuals are installed with the service.....
0
 
lhcitAuthor Commented:
ATIG:  Yes, I'm trying to create another website specifically for the Outlook Anywhere feature, this will help me to simplify the URLs, DNS entries, and SSL certs.  I read that there is no PS cmdlet to create the RPC and RPCwithCert vdirs, that they have to be exported and re-imported as new sites.  Even when I do that, and it's successful, I don't see any way to update the SCP to point to the new vdirs.  
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
ATIGCommented:
Yeah.... you really cannot move that one but would I would do is leave that as default and move the EX piece....
0
 
SembeeConnect With a Mentor Commented:
It can be moved. You have to do an export of the virtual directory and then an import, BUT, it will then be outside of the management of Exchange, either for EMC or the Shell. I also don't believe that Microsoft will support Exchange components outside of the default web site.

Simon.
0
 
ATIGCommented:
Simon, you have a link for the move?
0
 
SembeeConnect With a Mentor Commented:
Its part of my controversial SSL certificate process on my blog.
http://www.sembee.co.uk/archive/2007/01/21/34.aspx

Works for Exchange 2003 as well. Basically an expert of the vdir after configuration and then an import.

Oooo - can you send me an email to sembee @ experts-exchange.com I have another thread I would like you to look at.

Simon.
0
 
lhcitAuthor Commented:
I've done the move, the problem is updating the SCP to point to the new directory.  Running a "get-outlookanywhere" shows the URLs I've configured for it, but always points to "Rpc (Default Web Site)."  This is what I am trying to change.  I've tried "Set-Outlookanywhere -name "servername\RPC (new web site name)", but it returns the error that "servername\rpc (new web site name) does not exist on server dc.mydomain.com."  I get the same if I try to use "set-outlookanywhere -identity.  Same error.  It looks like the metabasepath in the SCP is hard-coded and unchangeable.  
0
 
ATIGCommented:
did you try disable OL anywhere and then enable it back?
0
 
lhcitAuthor Commented:
Yes, it still only points to "Rpc (Default Web Site)."  The only argument to "Enable-OutlookAnywhere" that I can see would be the "-TemplateInstance (PSObject)" argument, but it doesn't really make sense to copy the attributes of any other object, and it still doesn't look like I'd be able to specify the metadatabase path.
0
 
ATIGCommented:
yeah... and I dont know of anywhat to set that .........that why I was saying that I dont know that you can move it but let me look into this a bit...
0
 
ATIGCommented:
Simon, I sent you an email......
0
 
ATIGCommented:
interesting..... lets see what I can did up :)
0
 
lhcitAuthor Commented:
Yeah, that's the same problem I'm having.  Moving the vdir is the easy part :).  Now try running "set-outlookanywhere -identity servername\rpc (new web site name)."  It'll tell you that the object doesn't exist on your domain controller.  Apparently the arguments work on the SCP rather than the iis attributes.  Looks like an oversight in design, they figured there'd be no reason to run outlook anywhere except from the default web site. I just don't see why you can use PS to create and manipulate the vdirs for ALL of the other outlook services / web services but this one you can't.  
0
 
Corcoran SmithCommented:
And 3 years later, this dreadful problem still exists - even inside their SBS product.

A shocking joke.
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.