Prev: Firewall device recommendation
Next: Missing Servers Folder in Exchange system Manager
From: John on 24 Feb 2010 20:35
That link is placed there by the msgroups list.

Some further research leads me to this kb:
http://support.microsoft.com/default.aspx/kb/970259/EN-US

relevant commands being:
3) %windir%\system32\inetsrv\appcmd.exe set app "Default Web Site/Rpc" -applicationPool:RpcAppPool

4) %windir%\system32\inetsrv\appcmd.exe set app "Default Web Site/RpcWithCert" -applicationPool:RpcAppPool

One would think you could simply change the paths to say:
appcmd.exe set app "SBS Web Applications/RpcWithCert" -applicationPool:RpcAppPool

but - tried it, and nothing changes in the output of get-outlookanywhere |fl

WARNING: IIS://EXCH1.acme.local/W3SVC/1/ROOT/Rpc was not found.
Please make sure you have typed it correctly.

ServerName : EXCH1
SSLOffloading : False
ExternalHostname : remote.acme.com
ClientAuthenticationMethod : Basic
IISAuthenticationMethods : {Basic, Ntlm}
MetabasePath : IIS://EXCH1.acme.local/W3SVC/1/ROOT/Rpc
Path :
Server : EXCH1
AdminDisplayName :
ExchangeVersion : 0.1 (8.0.535.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=EXCH1,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First Organization,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=acme,DC=local
Identity : EXCH1\Rpc (Default Web Site)
Guid : 5b2ba1c6-936-41d3-9998-1d1c14be8e98
ObjectCategory : acme.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 1/3/2010 3:42:08 PM
WhenCreated : 1/3/2010 3:42:08 PM
OriginatingServer : EXCH1.acme.local
IsValid : True

silly server should not even mention the Default Website since its SBS.

-John

---
frmsrcurl: http://msgroups.net/microsoft.public.windows.server.sbs/Re-installation-of-RPC-HTTP-proxy-feature-leads-to-big-probl
From: Russ SBITS.Biz [SBS-MVP] on 24 Feb 2010 21:07
John,
The reason as you put it We Thump our MSCE Bible
is because SBS requires you to follow RULES!

People don't want to follow the rules with SBS
and when they don't and "assume" they know what they are doing and it
breaks.
They then complain that the product sucks, lacks documentation etc...

So when they call Microsoft for support and you don't use the rules for SBS
You definitely get a BIG Delay in support.

Why? Because they have to try and UNDO all you've done to break your server.

We are not after Rob to be "mean"
but to guide him in the best way to do things...

Using the wizards with SBS puts your server in a Supported Configuration
not using wizards puts SBS in a NON Supported Configuration.

You are free to do what you wish, however people need to realize the
consequences of their actions.

And that is the purpose of our many posts.
Not to harass, but to guide them so they may enjoy SBS not hate it!
Russ

PS John, if you avoid msgroups.net website
and post directly to msnews.microsoft.com with your favorite NNTP Reader
You will avoid broken links people not understanding your posts and reading
excessive ad's

--
Russell Grover - SBITS.Biz [SBS-MVP]
MCP, MCPS, MCNPS, SBSC
Microsoft Certified Small Business Specialist
SBS2003 SBS2008 Support - www.SBITS.Biz
Question or Second Opinion - www.PersonalITConsultant.com
Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com


"John" <user(a)msgroups.net/> wrote in message
news:OzhoPHbtKHA.3548(a)TK2MSFTNGP04.phx.gbl...
> I dont know why you guys are badgering Rob - but there should be a simple
> solution to properly register the RPC directory in IIS - what is it??
>
> I have a kind of mirrored problem of this issue - my RPC directory exists
> in the proper SBS Web Applications vdir(never changed or removed it), but
> several Exchange Power Shell tests show that RPC is broken, and the tests
> think the directory is missing from the "Default Website" vdir - DUH! of
> course its missing - cause its in SBS Web Applications - not many issues
> from this - somehow remote Outlooks still work fine - but TS Gateway
> features are broke.
>
> My gut feeling is to NOT run the wizards as they failed to setup the ssl
> cert with SANs properly configured with autodiscover in the first place. I
> feel deciphering that nasty guide that Rob posted that is loaded with
> Power Shell commands may be the only real solution. Working with SBS since
> Backoffice 4.0, I think I know my way around the block, and I have done my
> due diligence to research this - if I call MS support (which has crossed
> my mind) and they cant fix this in 15 minutes - where am I left?? - Means
> they tried the wizard and it didnt work. My last call to the Exchange
> department took 2 months to solve a problem, and the resolution was never
> known, except that its working again. Surely I respect these techs as
> being quite proficient, my hats are off to you guys, but sometimes it
> feels like you are thumping your MCSE bible at me.
>
> Point being - MS should definitely better document RPC and how its tied to
> IIS - something tells me part of that script Rob linked to has the 3-4
> lines that fix this hidden in there somewhere.
>
> ---
>
From: John on 25 Feb 2010 01:45
so - following the rules of SBS - used the Fix Network wizard, and Setup
your Internet address wizard - things are worse then before, this is a
relatively fresh server (2-3 months old). What happens after you installl
SBS - you fill out the Wizards to complete setup of your domain - this is
how it was done, and several features of SBS were disfunctional out of the
box.

Some settings needed to be adjusted in IIS and some ps commands were
performed to correct ssl certs - pretty simple and standard fixes which
the wizards have now broke again.

The Fix network wizard keeps going on about a TS Gateway issue, click fix
it, says it has resolved the problem, but if you run the wizard again it
identifies the same issue - it doesnt give any details, but most likely it
is not correcting the RPC issue.

Not to hijack a thread, but my issue is quite similar and hopefully
collaboration can aide in resolution, Rob may not have the symptom of
broken TS gateway, simply because he hasnt used it yet - he does have the
underlying disease of misconfigured RPC in IIS - this is the cause of the
symptom.

I definitely know that MS support has unfathomable resources, I have seen
a tech edit 20-30 deep reg keys to fix a problem for me, but sometimes I
see them just as stumped as I, running through the wizards takes about 5
minutes - give them 15 for good measure, talking to you guys gives me a
good feel for what I will get when I call MS.

So for the moment I will correct all the problems the wizards have made to
get basic remote features working again, in the morning we will open an
incident to see where it leads - any other advice?

On Wed, 24 Feb 2010 17:35:21 -0800, wrote:

> That link is placed there by the msgroups list.
>
> Some further research leads me to this kb:
> http://support.microsoft.com/default.aspx/kb/970259/EN-US
>
> relevant commands being:
> 3) %windir%\system32\inetsrv\appcmd.exe set app "Default Web Site/Rpc"
> -applicationPool:RpcAppPool
>
> 4) %windir%\system32\inetsrv\appcmd.exe set app "Default Web
> Site/RpcWithCert" -applicationPool:RpcAppPool
>
> One would think you could simply change the paths to say:
> appcmd.exe set app "SBS Web Applications/RpcWithCert"
> -applicationPool:RpcAppPool
>
> but - tried it, and nothing changes in the output of get-outlookanywhere
> |fl
>
> WARNING: IIS://EXCH1.acme.local/W3SVC/1/ROOT/Rpc was not found.
> Please make sure you have typed it correctly.
>
> ServerName : EXCH1
> SSLOffloading : False
> ExternalHostname : remote.acme.com
> ClientAuthenticationMethod : Basic
> IISAuthenticationMethods : {Basic, Ntlm}
> MetabasePath : IIS://EXCH1.acme.local/W3SVC/1/ROOT/Rpc
> Path :
> Server : EXCH1
> AdminDisplayName :
> ExchangeVersion : 0.1 (8.0.535.0)
> Name : Rpc (Default Web Site)
> DistinguishedName : CN=Rpc (Default Web
> Site),CN=HTTP,CN=Protocols,CN=EXCH1,CN=Servers,CN=Exchange
> Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First
> Organization,CN=Microsoft
> Exchange,CN=Services,CN=Configuration,DC=acme,DC=local
> Identity : EXCH1\Rpc (Default Web Site)
> Guid : 5b2ba1c6-936-41d3-9998-1d1c14be8e98
> ObjectCategory :
> acme.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
> ObjectClass : {top, msExchVirtualDirectory,
> msExchRpcHttpVirtualDirectory}
> WhenChanged : 1/3/2010 3:42:08 PM
> WhenCreated : 1/3/2010 3:42:08 PM
> OriginatingServer : EXCH1.acme.local
> IsValid : True
>
> silly server should not even mention the Default Website since its SBS.
>
> -John
>
> ---
> frmsrcurl:
> http://msgroups.net/microsoft.public.windows.server.sbs/Re-installation-of-RPC-HTTP-proxy-feature-leads-to-big-probl



--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/
From: Russ SBITS.Biz [SBS-MVP] on 25 Feb 2010 02:13
John,
Sorry you are having Problems with your SBS Server
I've had great success using the wizards and they are all running fine.
And RPC over HTTPS works fine in all my SBS servers
(I have never had to make any Changes in IIS to "FIX" things)

Wizards will not Break things but bring things in line with SBS standards.
If it breaks things usually this means that the server is not set to SBS
standards.

If you wish support on this issue,
Which seems different in Topic of the original thread,
I suggest a new thread or you may
Contact your SBS Specialist, or contact Microsoft.
Thanks
Russ
--
Russell Grover - SBITS.Biz [SBS-MVP]
MCP, MCPS, MCNPS, SBSC
Microsoft Certified Small Business Specialist
SBS2003 SBS2008 Support - www.SBITS.Biz
Question or Second Opinion - www.PersonalITConsultant.com
Free Trial Microsoft Online Services - www.Microsoft-Online-Services.com


"John" <j(a)dot.com> wrote in message news:op.u8n7qdgpvul11g(a)eee...
> so - following the rules of SBS - used the Fix Network wizard, and Setup
> your Internet address wizard - things are worse then before, this is a
> relatively fresh server (2-3 months old). What happens after you installl
> SBS - you fill out the Wizards to complete setup of your domain - this is
> how it was done, and several features of SBS were disfunctional out of the
> box.
>
> Some settings needed to be adjusted in IIS and some ps commands were
> performed to correct ssl certs - pretty simple and standard fixes which
> the wizards have now broke again.
>
> The Fix network wizard keeps going on about a TS Gateway issue, click fix
> it, says it has resolved the problem, but if you run the wizard again it
> identifies the same issue - it doesnt give any details, but most likely it
> is not correcting the RPC issue.
>
> Not to hijack a thread, but my issue is quite similar and hopefully
> collaboration can aide in resolution, Rob may not have the symptom of
> broken TS gateway, simply because he hasnt used it yet - he does have the
> underlying disease of misconfigured RPC in IIS - this is the cause of the
> symptom.
>
> I definitely know that MS support has unfathomable resources, I have seen
> a tech edit 20-30 deep reg keys to fix a problem for me, but sometimes I
> see them just as stumped as I, running through the wizards takes about 5
> minutes - give them 15 for good measure, talking to you guys gives me a
> good feel for what I will get when I call MS.
>
> So for the moment I will correct all the problems the wizards have made to
> get basic remote features working again, in the morning we will open an
> incident to see where it leads - any other advice?
>
> On Wed, 24 Feb 2010 17:35:21 -0800, wrote:
>
>> That link is placed there by the msgroups list.
>>
>> Some further research leads me to this kb:
>> http://support.microsoft.com/default.aspx/kb/970259/EN-US
>>
>> relevant commands being:
>> 3) %windir%\system32\inetsrv\appcmd.exe set app "Default Web
>> ite/Rpc" -applicationPool:RpcAppPool
>>
>> 4) %windir%\system32\inetsrv\appcmd.exe set app "Default Web
>> Site/RpcWithCert" -applicationPool:RpcAppPool
>>
>> One would think you could simply change the paths to say:
>> appcmd.exe set app "SBS Web
>> pplications/RpcWithCert" -applicationPool:RpcAppPool
>>
>> but - tried it, and nothing changes in the output of get-outlookanywhere
>> |fl
>>
>> WARNING: IIS://EXCH1.acme.local/W3SVC/1/ROOT/Rpc was not found.
>> Please make sure you have typed it correctly.
>>
>> ServerName : EXCH1
>> SSLOffloading : False
>> ExternalHostname : remote.acme.com
>> ClientAuthenticationMethod : Basic
>> IISAuthenticationMethods : {Basic, Ntlm}
>> MetabasePath : IIS://EXCH1.acme.local/W3SVC/1/ROOT/Rpc
>> Path :
>> Server : EXCH1
>> AdminDisplayName :
>> ExchangeVersion : 0.1 (8.0.535.0)
>> Name : Rpc (Default Web Site)
>> DistinguishedName : CN=Rpc (Default Web
>> Site),CN=HTTP,CN=Protocols,CN=EXCH1,CN=Servers,CN=Exchange
>> Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First
>> Organization,CN=Microsoft
>> Exchange,CN=Services,CN=Configuration,DC=acme,DC=local
>> Identity : EXCH1\Rpc (Default Web Site)
>> Guid : 5b2ba1c6-936-41d3-9998-1d1c14be8e98
>> ObjectCategory :
>> acme.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
>> ObjectClass : {top, msExchVirtualDirectory,
>> msExchRpcHttpVirtualDirectory}
>> WhenChanged : 1/3/2010 3:42:08 PM
>> WhenCreated : 1/3/2010 3:42:08 PM
>> OriginatingServer : EXCH1.acme.local
>> IsValid : True
>>
>> silly server should not even mention the Default Website since its SBS.
>>
>> -John
>>
>> ---
>> frmsrcurl:
>> http://msgroups.net/microsoft.public.windows.server.sbs/Re-installation-of-RPC-HTTP-proxy-feature-leads-to-big-probl
>
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

From: Cliff Galiher - MVP on 25 Feb 2010 02:48
John:

As with my previous reply, I will *STRONGLY* suggest you open a new thread.
If the symptoms end up pointing to the same cause, then we can always add
that information back here. But here is my short list:

1) You've "decided" that this is caused by RPC, but have given us no
information why. So I'll repeat my initial request. Start a new thread and
describe IN DETAIL the problem you are having.

2) It is rare that the wizards break something unless other things are
out-of-line as well. This is a good sign that you need to address the
underlying issues that are out of line with what the wizard expects.

3) Download and use the SBS BPA.

4) You mention changes to IIS *and* ps scripts, but again give no details.
It is possible that these changes are, in fact, more harmful than not.
There are many ways to disguise symptoms, but it doesn't make the process
correct. For example, I've seen people "fix" the outlook repeatedly asking
for authentication issue that appeared in December by loosening IIS
authentication rules. Does that work? Sure. But it also exposes OWA to
several security vulnerabilities. The correct fix is to apply Exchange SP1
rollup 9, which alters exchange appropriately so this becomes a non-issue.
Two ways to fix the symptoms, but only one is a real *FIX* for the
underlying problem. I *STRONGLY* suspect that the changes you made are part
of the cause, not the cure, based on the many SBS boxes I've set up that
have never required a single powershell command be run. Take that
experience for what is worth.

In short, there are plenty of people here that are willing to help you.
And, of course, you can open an incident with MS as well. I just want to
prepare you for what you may be in for when you call them. This box sounds
like it has been adjusted enough that they may take more than 5 or 15
minutes to fix this issue.

-Cliff


"John" <j(a)dot.com> wrote in message news:op.u8n7qdgpvul11g(a)eee...
> so - following the rules of SBS - used the Fix Network wizard, and Setup
> your Internet address wizard - things are worse then before, this is a
> relatively fresh server (2-3 months old). What happens after you installl
> SBS - you fill out the Wizards to complete setup of your domain - this is
> how it was done, and several features of SBS were disfunctional out of the
> box.
>
> Some settings needed to be adjusted in IIS and some ps commands were
> performed to correct ssl certs - pretty simple and standard fixes which
> the wizards have now broke again.
>
> The Fix network wizard keeps going on about a TS Gateway issue, click fix
> it, says it has resolved the problem, but if you run the wizard again it
> identifies the same issue - it doesnt give any details, but most likely it
> is not correcting the RPC issue.
>
> Not to hijack a thread, but my issue is quite similar and hopefully
> collaboration can aide in resolution, Rob may not have the symptom of
> broken TS gateway, simply because he hasnt used it yet - he does have the
> underlying disease of misconfigured RPC in IIS - this is the cause of the
> symptom.
>
> I definitely know that MS support has unfathomable resources, I have seen
> a tech edit 20-30 deep reg keys to fix a problem for me, but sometimes I
> see them just as stumped as I, running through the wizards takes about 5
> minutes - give them 15 for good measure, talking to you guys gives me a
> good feel for what I will get when I call MS.
>
> So for the moment I will correct all the problems the wizards have made to
> get basic remote features working again, in the morning we will open an
> incident to see where it leads - any other advice?
>
> On Wed, 24 Feb 2010 17:35:21 -0800, wrote:
>
>> That link is placed there by the msgroups list.
>>
>> Some further research leads me to this kb:
>> http://support.microsoft.com/default.aspx/kb/970259/EN-US
>>
>> relevant commands being:
>> 3) %windir%\system32\inetsrv\appcmd.exe set app "Default Web
>> ite/Rpc" -applicationPool:RpcAppPool
>>
>> 4) %windir%\system32\inetsrv\appcmd.exe set app "Default Web
>> Site/RpcWithCert" -applicationPool:RpcAppPool
>>
>> One would think you could simply change the paths to say:
>> appcmd.exe set app "SBS Web
>> pplications/RpcWithCert" -applicationPool:RpcAppPool
>>
>> but - tried it, and nothing changes in the output of get-outlookanywhere
>> |fl
>>
>> WARNING: IIS://EXCH1.acme.local/W3SVC/1/ROOT/Rpc was not found.
>> Please make sure you have typed it correctly.
>>
>> ServerName : EXCH1
>> SSLOffloading : False
>> ExternalHostname : remote.acme.com
>> ClientAuthenticationMethod : Basic
>> IISAuthenticationMethods : {Basic, Ntlm}
>> MetabasePath : IIS://EXCH1.acme.local/W3SVC/1/ROOT/Rpc
>> Path :
>> Server : EXCH1
>> AdminDisplayName :
>> ExchangeVersion : 0.1 (8.0.535.0)
>> Name : Rpc (Default Web Site)
>> DistinguishedName : CN=Rpc (Default Web
>> Site),CN=HTTP,CN=Protocols,CN=EXCH1,CN=Servers,CN=Exchange
>> Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=First
>> Organization,CN=Microsoft
>> Exchange,CN=Services,CN=Configuration,DC=acme,DC=local
>> Identity : EXCH1\Rpc (Default Web Site)
>> Guid : 5b2ba1c6-936-41d3-9998-1d1c14be8e98
>> ObjectCategory :
>> acme.local/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
>> ObjectClass : {top, msExchVirtualDirectory,
>> msExchRpcHttpVirtualDirectory}
>> WhenChanged : 1/3/2010 3:42:08 PM
>> WhenCreated : 1/3/2010 3:42:08 PM
>> OriginatingServer : EXCH1.acme.local
>> IsValid : True
>>
>> silly server should not even mention the Default Website since its SBS.
>>
>> -John
>>
>> ---
>> frmsrcurl:
>> http://msgroups.net/microsoft.public.windows.server.sbs/Re-installation-of-RPC-HTTP-proxy-feature-leads-to-big-probl
>
>
>
> --
> Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

First  |  Prev  |  Next  |  Last
Pages: 1 2 3
Prev: Firewall device recommendation
Next: Missing Servers Folder in Exchange system Manager