Prev: SBS2008 R2 ?? / Exchange 2010 ?? / SBS2010 ??
Next: Windows Hyper-V Server 2008 R2 with SBS 2008 running as guest
From: Takasumi Kanban on 6 Apr 2010 23:57
Hi Cliff - where can I find 2008 connect newsgroup please?
Have found this post on many sites and am dying to read to reply, I have
similar issue - cheers
Takasumi

"Cliff Galiher - MVP" wrote:

> I've replied to your repost of this issue in the 2008 connect newsgroup,
> just as an FYI. No reason to try and maintain two threads.
>
> -Cliff
>
>
> "John" <j(a)dot.com> wrote in message news:op.u8og5hmxvul11g(a)eee...
> > Hi all - per Cliff's kind coaxing here it is:
> >
> > Deployed an SBS2008 about 3 months ago, all standard windows updates,
> > Exchange is at SP1 rollup 9.
> >
> > My major issue is that the server appears to believe the RPC directories
> > are located under the IIS Default Website, when in fact they are located
> > under SBS Web Applications virtual dir (as they should), evidence of this
> > comes from these PS tests:
> >
> > [PS] C:\Windows\System32> 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
> > <<<<<<<<<<<<< should say W3SVC/3
> > Path :
> > Server : EXCH1
> > AdminDisplayName :
> > ExchangeVersion : 0.1 (8.0.535.0)
> > Name : Rpc (Default Web Site) <<<<<<<<<<<<<<<<<<<<<
> > this is the problem again!!!!!!!!!
> > 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
> > ===================================================================
> > Test-OutlookWebServices |Fl ----everything passes except:
> > Id : 1013
> > Type : Error
> > Message : When contacting https://remote.acme.com/Rpc received the error
> > The server committed a protocol violation.
> > Section=ResponseStatusLine
> >
> > Id : 1017
> > Type : Error
> > Message : [EXPR]-Error when contacting the RPC/HTTP service at
> > https://remote.acme.com/Rpc.
> > The elapsed time was 14 milliseconds.
> > ===================================================================
> > Set-OutlookAnywhere -ClientAuthenticationMethod Basic
> >
> > cmdlet Set-OutlookAnywhere at command pipeline position 1
> > Supply values for the following parameters:
> > Identity: exch1\rpc <SBS Web Applications>
> > Set-OutlookAnywhere : The operation could not be performed because object
> > 'exch1\rpc <SBS Web Applications>' could not be found on domain controller
> > 'exch1.acme.local'.
> > At line:1 char:20
> > + Set-OutlookAnywhere <<<< -ClientAuthenticationMethod Basic
> > ===================================================================
> >
> > The system was setup using the typical wizards - Connect to Internet,
> > Setup Internet Address...
> > Once complete Autodiscovery and Out of Office were not properly working,
> > and possibly other items, but these were the standouts.
> >
> > It was determined that SSL settings and service Urls were to blame - the
> > self signed cert generated by the wizard did not properly show the
> > internal and external DNS names used by the server, nor the default
> > Autodiscovery name.
> >
> > DNS is managed by the outside registrar, all records are duplicated
> > internally.
> >
> > I used power shell to generate the proper SSL cert with SANs for:
> > exch1.acme.local
> > exch1
> > remote.acme.com
> > autodiscover.acme.com
> > acme.com
> > and remote.acme.local being my primary Subject on the cert.
> >
> > I also used PS to correct the Internal and External Service Urls as
> > follows:
> > Set-ClientAccessServer -Identity Exch1 -AutodiscoverServiceInternalUri
> > https://Exch1.acme.local/autodiscover/autodiscover.xml
> > Set-WebServicesVirtualDirectory -Identity "Exch1\EWS (SBS Web
> > Applications)" -InternalUrl https://Exch1.acme.local/ews/exchange.asmx
> > Set-OABVirtualDirectory -Identity "Exch1\oab (SBS Web
> > pplications)" -InternalUrl https://Exch1.acme.local/oab
> > Set-UMVirtualDirectory -Identity "Exch1\unifiedmessaging (SBS Web
> > Applications)" -InternalUrl
> > https://Exch1.acme.local/unifiedmessaging/service.asmx
> > Set-ClientAccessServer –AutodiscoverServiceInternalUri
> > https://remote.acme.com/autodiscover/autodiscover.xml
> > Set-Outlookanywhere -Identity "Exch1\rpc (SBS Web
> > pplications)" -InternalUrl https://Exch1.acme.local/rpc
> >
> > I also had to change this ssl setting
> > SBS Web Applications > Remote > SSL Settings
> > Change "Client Certificates" from Required to Accept
> >
> > So after finding the RPC issues - and now consequently TS gateway is
> > broken in remote web workplace - I re-ran the wizards, starting with Fix
> > My Network - it comes up with an error regarding TS Gateway (no real
> > details), fixes it - however if I re-run the Fix my net wizard, it still
> > comes up with the same error (reboot changes nothing), I then attempt to
> > run the Setup Internet Address wizard, which fails at the configuring
> > Exchange part, and consquently re-hoses all my ssl certs and urls, it
> > recommends that I run the Fix My Network Wizard - does nothing, I have
> > also run the Connect to Internet wizard which works well.
> >
> > I am a consultant, this is only my 3rd SBS2008, but I have about 60-70
> > SBS2000-2003 deployments under my belt - and yes they all were done with
> > the wizard.
> >
> > Regards-
> > -John
>
From: Cliff Galiher - MVP on 7 Apr 2010 04:29
http://connect.microsoft.com/

Register there with a Live ID and from the web dashboard you can then add
groups that are available. If you prefer using an NNTP client, as I do, the
web interface includes instructions on how to access connect groups you've
registered for to your newsreader of choice.

HTH,

-Cliff


"Takasumi Kanban" <TakasumiKanban(a)discussions.microsoft.com> wrote in
message news:E5D21819-0D33-43C4-911C-D0B0E18DF944(a)microsoft.com...
> Hi Cliff - where can I find 2008 connect newsgroup please?
> Have found this post on many sites and am dying to read to reply, I have
> similar issue - cheers
> Takasumi
>
> "Cliff Galiher - MVP" wrote:
>
>> I've replied to your repost of this issue in the 2008 connect newsgroup,
>> just as an FYI. No reason to try and maintain two threads.
>>
>> -Cliff
>>
>>
>> "John" <j(a)dot.com> wrote in message news:op.u8og5hmxvul11g(a)eee...
>> > Hi all - per Cliff's kind coaxing here it is:
>> >
>> > Deployed an SBS2008 about 3 months ago, all standard windows updates,
>> > Exchange is at SP1 rollup 9.
>> >
>> > My major issue is that the server appears to believe the RPC
>> > directories
>> > are located under the IIS Default Website, when in fact they are
>> > located
>> > under SBS Web Applications virtual dir (as they should), evidence of
>> > this
>> > comes from these PS tests:
>> >
>> > [PS] C:\Windows\System32> 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
>> > <<<<<<<<<<<<< should say W3SVC/3
>> > Path :
>> > Server : EXCH1
>> > AdminDisplayName :
>> > ExchangeVersion : 0.1 (8.0.535.0)
>> > Name : Rpc (Default Web Site)
>> > <<<<<<<<<<<<<<<<<<<<<
>> > this is the problem again!!!!!!!!!
>> > 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
>> > ===================================================================
>> > Test-OutlookWebServices |Fl ----everything passes except:
>> > Id : 1013
>> > Type : Error
>> > Message : When contacting https://remote.acme.com/Rpc received the
>> > error
>> > The server committed a protocol violation.
>> > Section=ResponseStatusLine
>> >
>> > Id : 1017
>> > Type : Error
>> > Message : [EXPR]-Error when contacting the RPC/HTTP service at
>> > https://remote.acme.com/Rpc.
>> > The elapsed time was 14 milliseconds.
>> > ===================================================================
>> > Set-OutlookAnywhere -ClientAuthenticationMethod Basic
>> >
>> > cmdlet Set-OutlookAnywhere at command pipeline position 1
>> > Supply values for the following parameters:
>> > Identity: exch1\rpc <SBS Web Applications>
>> > Set-OutlookAnywhere : The operation could not be performed because
>> > object
>> > 'exch1\rpc <SBS Web Applications>' could not be found on domain
>> > controller
>> > 'exch1.acme.local'.
>> > At line:1 char:20
>> > + Set-OutlookAnywhere <<<< -ClientAuthenticationMethod Basic
>> > ===================================================================
>> >
>> > The system was setup using the typical wizards - Connect to Internet,
>> > Setup Internet Address...
>> > Once complete Autodiscovery and Out of Office were not properly
>> > working,
>> > and possibly other items, but these were the standouts.
>> >
>> > It was determined that SSL settings and service Urls were to blame -
>> > the
>> > self signed cert generated by the wizard did not properly show the
>> > internal and external DNS names used by the server, nor the default
>> > Autodiscovery name.
>> >
>> > DNS is managed by the outside registrar, all records are duplicated
>> > internally.
>> >
>> > I used power shell to generate the proper SSL cert with SANs for:
>> > exch1.acme.local
>> > exch1
>> > remote.acme.com
>> > autodiscover.acme.com
>> > acme.com
>> > and remote.acme.local being my primary Subject on the cert.
>> >
>> > I also used PS to correct the Internal and External Service Urls as
>> > follows:
>> > Set-ClientAccessServer -Identity Exch1 -AutodiscoverServiceInternalUri
>> > https://Exch1.acme.local/autodiscover/autodiscover.xml
>> > Set-WebServicesVirtualDirectory -Identity "Exch1\EWS (SBS Web
>> > Applications)" -InternalUrl https://Exch1.acme.local/ews/exchange.asmx
>> > Set-OABVirtualDirectory -Identity "Exch1\oab (SBS Web
>> > pplications)" -InternalUrl https://Exch1.acme.local/oab
>> > Set-UMVirtualDirectory -Identity "Exch1\unifiedmessaging (SBS Web
>> > Applications)" -InternalUrl
>> > https://Exch1.acme.local/unifiedmessaging/service.asmx
>> > Set-ClientAccessServer –AutodiscoverServiceInternalUri
>> > https://remote.acme.com/autodiscover/autodiscover.xml
>> > Set-Outlookanywhere -Identity "Exch1\rpc (SBS Web
>> > pplications)" -InternalUrl https://Exch1.acme.local/rpc
>> >
>> > I also had to change this ssl setting
>> > SBS Web Applications > Remote > SSL Settings
>> > Change "Client Certificates" from Required to Accept
>> >
>> > So after finding the RPC issues - and now consequently TS gateway is
>> > broken in remote web workplace - I re-ran the wizards, starting with
>> > Fix
>> > My Network - it comes up with an error regarding TS Gateway (no real
>> > details), fixes it - however if I re-run the Fix my net wizard, it
>> > still
>> > comes up with the same error (reboot changes nothing), I then attempt
>> > to
>> > run the Setup Internet Address wizard, which fails at the configuring
>> > Exchange part, and consquently re-hoses all my ssl certs and urls, it
>> > recommends that I run the Fix My Network Wizard - does nothing, I have
>> > also run the Connect to Internet wizard which works well.
>> >
>> > I am a consultant, this is only my 3rd SBS2008, but I have about 60-70
>> > SBS2000-2003 deployments under my belt - and yes they all were done
>> > with
>> > the wizard.
>> >
>> > Regards-
>> > -John
>>
From: Larry Struckmeyer[SBS-MVP] on 7 Apr 2010 08:04
SBS 2008...

http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-2008-newsgroups.aspx

-
Larry
Please post the resolution to your
issue so others may benefit
-
Get Your SBS Health Check at
www.sbsbpa.com


> Hi Cliff - where can I find 2008 connect newsgroup please?
> Have found this post on many sites and am dying to read to reply, I
> have
> similar issue - cheers
> Takasumi
> "Cliff Galiher - MVP" wrote:
>
>> I've replied to your repost of this issue in the 2008 connect
>> newsgroup, just as an FYI. No reason to try and maintain two
>> threads.
>>
>> -Cliff
>>
>> "John" <j(a)dot.com> wrote in message news:op.u8og5hmxvul11g(a)eee...
>>
>>> Hi all - per Cliff's kind coaxing here it is:
>>>
>>> Deployed an SBS2008 about 3 months ago, all standard windows
>>> updates, Exchange is at SP1 rollup 9.
>>>
>>> My major issue is that the server appears to believe the RPC
>>> directories are located under the IIS Default Website, when in fact
>>> they are located under SBS Web Applications virtual dir (as they
>>> should), evidence of this comes from these PS tests:
>>>
>>> [PS] C:\Windows\System32> 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
>>> <<<<<<<<<<<<< should say W3SVC/3
>>> Path :
>>> Server : EXCH1
>>> AdminDisplayName :
>>> ExchangeVersion : 0.1 (8.0.535.0)
>>> Name : Rpc (Default Web Site)
>>> <<<<<<<<<<<<<<<<<<<<<
>>> this is the problem again!!!!!!!!!
>>> 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
>>> ===================================================================
>>> Test-OutlookWebServices |Fl ----everything passes except:
>>> Id : 1013
>>> Type : Error
>>> Message : When contacting https://remote.acme.com/Rpc received the
>>> error
>>> The server committed a protocol violation.
>>> Section=ResponseStatusLine
>>> Id : 1017
>>> Type : Error
>>> Message : [EXPR]-Error when contacting the RPC/HTTP service at
>>> https://remote.acme.com/Rpc.
>>> The elapsed time was 14 milliseconds.
>>> ===================================================================
>>> Set-OutlookAnywhere -ClientAuthenticationMethod Basic
>>> cmdlet Set-OutlookAnywhere at command pipeline position 1
>>> Supply values for the following parameters:
>>> Identity: exch1\rpc <SBS Web Applications>
>>> Set-OutlookAnywhere : The operation could not be performed because
>>> object
>>> 'exch1\rpc <SBS Web Applications>' could not be found on domain
>>> controller
>>> 'exch1.acme.local'.
>>> At line:1 char:20
>>> + Set-OutlookAnywhere <<<< -ClientAuthenticationMethod Basic
>>> ===================================================================
>>> The system was setup using the typical wizards - Connect to
>>> Internet,
>>> Setup Internet Address...
>>> Once complete Autodiscovery and Out of Office were not properly
>>> working,
>>> and possibly other items, but these were the standouts.
>>> It was determined that SSL settings and service Urls were to blame -
>>> the self signed cert generated by the wizard did not properly show
>>> the internal and external DNS names used by the server, nor the
>>> default Autodiscovery name.
>>>
>>> DNS is managed by the outside registrar, all records are duplicated
>>> internally.
>>>
>>> I used power shell to generate the proper SSL cert with SANs for:
>>> exch1.acme.local
>>> exch1
>>> remote.acme.com
>>> autodiscover.acme.com
>>> acme.com
>>> and remote.acme.local being my primary Subject on the cert.
>>> I also used PS to correct the Internal and External Service Urls as
>>> follows:
>>> Set-ClientAccessServer -Identity Exch1
>>> -AutodiscoverServiceInternalUri
>>> https://Exch1.acme.local/autodiscover/autodiscover.xml
>>> Set-WebServicesVirtualDirectory -Identity "Exch1\EWS (SBS Web
>>> Applications)" -InternalUrl
>>> https://Exch1.acme.local/ews/exchange.asmx
>>> Set-OABVirtualDirectory -Identity "Exch1\oab (SBS Web
>>> pplications)" -InternalUrl https://Exch1.acme.local/oab
>>> Set-UMVirtualDirectory -Identity "Exch1\unifiedmessaging (SBS Web
>>> Applications)" -InternalUrl
>>> https://Exch1.acme.local/unifiedmessaging/service.asmx
>>> Set-ClientAccessServer –AutodiscoverServiceInternalUri
>>> https://remote.acme.com/autodiscover/autodiscover.xml
>>> Set-Outlookanywhere -Identity "Exch1\rpc (SBS Web
>>> pplications)" -InternalUrl https://Exch1.acme.local/rpc
>>> I also had to change this ssl setting
>>> SBS Web Applications > Remote > SSL Settings
>>> Change "Client Certificates" from Required to Accept
>>> So after finding the RPC issues - and now consequently TS gateway is
>>> broken in remote web workplace - I re-ran the wizards, starting with
>>> Fix My Network - it comes up with an error regarding TS Gateway (no
>>> real details), fixes it - however if I re-run the Fix my net wizard,
>>> it still comes up with the same error (reboot changes nothing), I
>>> then attempt to run the Setup Internet Address wizard, which fails
>>> at the configuring Exchange part, and consquently re-hoses all my
>>> ssl certs and urls, it recommends that I run the Fix My Network
>>> Wizard - does nothing, I have also run the Connect to Internet
>>> wizard which works well.
>>>
>>> I am a consultant, this is only my 3rd SBS2008, but I have about
>>> 60-70 SBS2000-2003 deployments under my belt - and yes they all were
>>> done with the wizard.
>>>
>>> Regards-
>>> -John


From: Chris Puckett [MSFT] on 7 Apr 2010 10:56
This happens because the RPCProxy or TSGateway feature has been uninstalled
and reinstalled on an SBS 2008 box.

Prior to reinstalling it, you need to create a REG_SZ (String value) in the
registry to tell the installer to put RPC under the SBS Web Applications
website.

HKLM\Software\Microsoft\Rpc\RpcProxy\Website REG_SZ SBS Web Applications

Item 3 in KB 969743.
969743 This computer can't connect to the remote computer because the
Terminal Services Gateway server is temporarily unavailable
http://support.microsoft.com/default.aspx?scid=kb;EN-US;969743

--
Chris Puckett

This posting is provided "AS IS" with no warranties, and confers no rights.



"Larry Struckmeyer[SBS-MVP]" <lstruckmeyer(a)mis-wizards.com> wrote in message
news:4e683515e4fd8cca4401c393e3c(a)news.microsoft.com...
> SBS 2008...
> http://msmvps.com/blogs/bradley/archive/2008/11/02/signing-up-for-the-sbs-2008-newsgroups.aspx
>
> -
> Larry
> Please post the resolution to your
> issue so others may benefit
> -
> Get Your SBS Health Check at
> www.sbsbpa.com
>
>
>> Hi Cliff - where can I find 2008 connect newsgroup please?
>> Have found this post on many sites and am dying to read to reply, I
>> have
>> similar issue - cheers
>> Takasumi
>> "Cliff Galiher - MVP" wrote:
>>
>>> I've replied to your repost of this issue in the 2008 connect
>>> newsgroup, just as an FYI. No reason to try and maintain two
>>> threads.
>>>
>>> -Cliff
>>>
>>> "John" <j(a)dot.com> wrote in message news:op.u8og5hmxvul11g(a)eee...
>>>
>>>> Hi all - per Cliff's kind coaxing here it is:
>>>>
>>>> Deployed an SBS2008 about 3 months ago, all standard windows
>>>> updates, Exchange is at SP1 rollup 9.
>>>>
>>>> My major issue is that the server appears to believe the RPC
>>>> directories are located under the IIS Default Website, when in fact
>>>> they are located under SBS Web Applications virtual dir (as they
>>>> should), evidence of this comes from these PS tests:
>>>>
>>>> [PS] C:\Windows\System32> 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
>>>> <<<<<<<<<<<<< should say W3SVC/3
>>>> Path :
>>>> Server : EXCH1
>>>> AdminDisplayName :
>>>> ExchangeVersion : 0.1 (8.0.535.0)
>>>> Name : Rpc (Default Web Site)
>>>> <<<<<<<<<<<<<<<<<<<<<
>>>> this is the problem again!!!!!!!!!
>>>> 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
>>>> ===================================================================
>>>> Test-OutlookWebServices |Fl ----everything passes except:
>>>> Id : 1013
>>>> Type : Error
>>>> Message : When contacting https://remote.acme.com/Rpc received the
>>>> error
>>>> The server committed a protocol violation.
>>>> Section=ResponseStatusLine
>>>> Id : 1017
>>>> Type : Error
>>>> Message : [EXPR]-Error when contacting the RPC/HTTP service at
>>>> https://remote.acme.com/Rpc.
>>>> The elapsed time was 14 milliseconds.
>>>> ===================================================================
>>>> Set-OutlookAnywhere -ClientAuthenticationMethod Basic
>>>> cmdlet Set-OutlookAnywhere at command pipeline position 1
>>>> Supply values for the following parameters:
>>>> Identity: exch1\rpc <SBS Web Applications>
>>>> Set-OutlookAnywhere : The operation could not be performed because
>>>> object
>>>> 'exch1\rpc <SBS Web Applications>' could not be found on domain
>>>> controller
>>>> 'exch1.acme.local'.
>>>> At line:1 char:20
>>>> + Set-OutlookAnywhere <<<< -ClientAuthenticationMethod Basic
>>>> ===================================================================
>>>> The system was setup using the typical wizards - Connect to
>>>> Internet,
>>>> Setup Internet Address...
>>>> Once complete Autodiscovery and Out of Office were not properly
>>>> working,
>>>> and possibly other items, but these were the standouts.
>>>> It was determined that SSL settings and service Urls were to blame -
>>>> the self signed cert generated by the wizard did not properly show
>>>> the internal and external DNS names used by the server, nor the
>>>> default Autodiscovery name.
>>>>
>>>> DNS is managed by the outside registrar, all records are duplicated
>>>> internally.
>>>>
>>>> I used power shell to generate the proper SSL cert with SANs for:
>>>> exch1.acme.local
>>>> exch1
>>>> remote.acme.com
>>>> autodiscover.acme.com
>>>> acme.com
>>>> and remote.acme.local being my primary Subject on the cert.
>>>> I also used PS to correct the Internal and External Service Urls as
>>>> follows:
>>>> Set-ClientAccessServer -Identity Exch1
>>>> -AutodiscoverServiceInternalUri
>>>> https://Exch1.acme.local/autodiscover/autodiscover.xml
>>>> Set-WebServicesVirtualDirectory -Identity "Exch1\EWS (SBS Web
>>>> Applications)" -InternalUrl
>>>> https://Exch1.acme.local/ews/exchange.asmx
>>>> Set-OABVirtualDirectory -Identity "Exch1\oab (SBS Web
>>>> pplications)" -InternalUrl https://Exch1.acme.local/oab
>>>> Set-UMVirtualDirectory -Identity "Exch1\unifiedmessaging (SBS Web
>>>> Applications)" -InternalUrl
>>>> https://Exch1.acme.local/unifiedmessaging/service.asmx
>>>> Set-ClientAccessServer –AutodiscoverServiceInternalUri
>>>> https://remote.acme.com/autodiscover/autodiscover.xml
>>>> Set-Outlookanywhere -Identity "Exch1\rpc (SBS Web
>>>> pplications)" -InternalUrl https://Exch1.acme.local/rpc
>>>> I also had to change this ssl setting
>>>> SBS Web Applications > Remote > SSL Settings
>>>> Change "Client Certificates" from Required to Accept
>>>> So after finding the RPC issues - and now consequently TS gateway is
>>>> broken in remote web workplace - I re-ran the wizards, starting with
>>>> Fix My Network - it comes up with an error regarding TS Gateway (no
>>>> real details), fixes it - however if I re-run the Fix my net wizard,
>>>> it still comes up with the same error (reboot changes nothing), I
>>>> then attempt to run the Setup Internet Address wizard, which fails
>>>> at the configuring Exchange part, and consquently re-hoses all my
>>>> ssl certs and urls, it recommends that I run the Fix My Network
>>>> Wizard - does nothing, I have also run the Connect to Internet
>>>> wizard which works well.
>>>>
>>>> I am a consultant, this is only my 3rd SBS2008, but I have about
>>>> 60-70 SBS2000-2003 deployments under my belt - and yes they all were
>>>> done with the wizard.
>>>>
>>>> Regards-
>>>> -John
>
>
 | 
Pages: 1
Prev: SBS2008 R2 ?? / Exchange 2010 ?? / SBS2010 ??
Next: Windows Hyper-V Server 2008 R2 with SBS 2008 running as guest