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.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
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.
Its part of my controversial SSL certificate process on my blog.
http://www.sembee.co.uk/ar
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.
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.
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.
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.
Business Accounts
Answer for Membership
by: ATIGPosted on 2007-12-03 at 07:09:32ID: 20395827
question.... where are you trying to move the Vdir too? Under another web site?
those virtuals are installed with the service.....