• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 552
  • Last Modified:

Outlook Anywhere (RPC-over-HTTPS) broken in SBS2008

My first time posting here, so bear with me...

Here's the summary:

Friday afternoon, everything was working.  Tuesday RPC/HTTPS stopped working for no obvious reason.  After spending several hours on Google, EE, MSDN over the last two days, I'm at a loss.

Here's what I've done:

RPC-over-HTTPS feature has been removed using Server Manager, TS Gateway removed (after reading about a potential conflict with Outlook Anywhere - bad move?), rebooted SBS.  Added RPC registry key and Website string value pointing the RPC virtual directory to the SBS Web Applications site.  Installed RPC-over-HTTPS using server manager.

Here's where I think I am:

IIS has the virtual directories in the right site but when I do Get-OutlookAnywhere in the powershell, Exchange thinks the virtual directories are in the Default Website.

Has anyone seen this and know how to fix it?  What additional information is useful in diagnosing the issue?  I'm sure I've left out a ton but wanted to get the question submitted initially and can provide additional info as needed.

Rusty
New Orleans
0
belltec
Asked:
belltec
  • 5
  • 4
1 Solution
 
endital1097Commented:
did you run
set-outlookanywhere -Name "Rpc (SBS Web Applications)"
0
 
belltecAuthor Commented:
Thanks for the reply.  I looked into the Set-OutlookAnywhere cmdlet but hadn't tried it since I didn't see any switches for setting the Identity.  Does that set all the website info or just the Name property?

Also, I killed OWA a couple times during the troubleshooting process by running scripts that didn't appear to be OWA related, so I'm waiting until after hours to make any changes.  I'll give this a shot this evening and post an update.
0
 
endital1097Commented:
Rpc should be installed under the SBS Web Applications site
this change will update AD with the appropriate location
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
belltecAuthor Commented:
Thanks again.  I'll try it tonight and post an update in the morning.
0
 
belltecAuthor Commented:
Ok, tried to set the name.  When I ran the cmdlet, it asked for the Identity.  When I tried using the "SBS\Rpc (SBS Web Applications) as the Identity, both with and without quotes, it returned an error that it could not be found.  Do I need to give it the current Identity in Default Website or is there something else I'm missing?
0
 
endital1097Commented:
the current identity
you can just run get-outlookanywhere | set-outlookanywhere
0
 
belltecAuthor Commented:
Is there any reason at all that I should wait until close of business to try this?  I'm gun-shy since breaking OWA by running a couple cmdlets that for some reason reverted web services to the self-signed SSL.
0
 
endital1097Commented:
no, this one will not affect anyone
0
 
belltecAuthor Commented:
Just note that when you're asked for the Identity, you use the current Identity, not the one you're trying to use.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 5
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now