[isalist] Re: RPC Documentation -
- From: "Thor (Hammer of God)" <thor@xxxxxxxxxxxxxxx>
- To: "isalist@xxxxxxxxxxxxx" <isalist@xxxxxxxxxxxxx>
- Date: Fri, 11 Aug 2006 12:11:09 -0700
I can hit it...
t
On 8/11/06 12:06 PM, "D PIETRUSZKA USWRN INTERLINK INFRA ASST MGR"
<DPietruszka@xxxxxx> spoketh to all:
> Hey, your web site is still down.
>
>
> Regards
> Diego R. Pietruszka
>
>
>
> From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On
> Behalf Of ISA
> Sent: Friday, August 11, 2006 12:37 PM
> To: isalist@xxxxxxxxxxxxx
> Subject: [isalist] RPC Documentation -
>
> Tom:
>
> Where is the ISA 2004 version of this article?
>
> Publishing RPC over HTTP by Placing the RPC/HTTP Proxy on the ISA Server 2000
> Firewall
> http://www.isaserver.org/articles/isarpchttpproxy1.html
>
>
>
>
> Joseph Danielsen, MCSA-Messaging, MCP
> Network Blade Inc.
> 49 Marcy Street
> Somerset, NJ 08873
> 732-213-0600
> www.networkblade.com <http://www.networkblade.com/>
>
>
>
>
> From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On
> Behalf Of Thomas W Shinder
> Posted At: Friday, August 11, 2006 11:59 AM
> Posted To: ISA
> Conversation: [isalist] ISA Mistake or Exchange documentation ???
> Subject: [isalist] Re: ISA Mistake or Exchange documentation ???
>
> Hi Joseph,
>
> Yes, I should have included that stuff for change password, although it is
> included in some of my ISA 2000 stuff, but that's no excuse.
>
> Good news is that change password functionality (and password expiration
> warnings) are integrated into the ISA 2006 FBA ;)
>
> Tom
>
>
> Thomas W Shinder, M.D.
> Site: www.isaserver.org <http://www.isaserver.org/>
> Blog: http://blogs.isaserver.org/shinder/
> Book: http://tinyurl.com/3xqb7
> MVP -- ISA Firewalls
>
>
>>
>>
>>
>> From: isalist-bounce@xxxxxxxxxxxxx [mailto:isalist-bounce@xxxxxxxxxxxxx] On
>> Behalf Of ISA
>> Sent: Friday, August 11, 2006 10:04 AM
>> To: isalist@xxxxxxxxxxxxx
>> Subject: [isalist] ISA Mistake or Exchange documentation ???
>> I¹m not sure who to blame (starting with myself), but I ran into a few
>> interesting series of road bumps that could have been avoided with
>> better/different documentation.
>>
>> Steps:
>>
>> 1) Publish Exchange done!
>> 2) Publish OWA done!
>> 3) Publish OWA via Https done!
>> 4) Publish FBA done!
>> 5) Publish RPC/http done!
>>
>> 6) Then I tried to get the ³Change Password² option to work via OWA. Simply
>> received a 403 error URL not allowed.
>>
>> After spending unsuccessful hours searching for documentation I stumbled
>> upon the answer myself.
>>
>> My point is, is that it seems more logical that when documenting the
>> procedures for Step 2 or Step 3 above they could have simply listed the
>> minimum required PATH directories AND then added a suggestion of (additional)
>> PATH directories that might be needed in the future i.e. IISADMPWD, OMA, RPC
>> etc.
>>
>>
>>
>> Joseph Danielsen, MCSA-Messaging, MCP
>> Network Blade Inc.
>> 49 Marcy Street
>> Somerset, NJ 08873
>> 732-213-0600
>
Other related posts:
