Problem Description:

We have our Application client installed onto a network drive and various
workstations at respective local machines. All the workstation uses the
executables across the network. The help files .CHM files are also at network
drive. But, workstations are not able to access the .CHM files across the
network.

Workaround tried:

At workstation, we tried modifying the
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions registry
entry to enable a specific security zone. The above workaround resolved the
issue.

Limitation:

All workstation don’t have admin rights to modify the Registry entries.

Is there any way to enable accessing .CHM files across the network.

-Manoj R

Move the CHM files to the local drive or globally set the desired
restriction at login.

"Manoj R" <(E-Mail Removed)> wrote in message
news:E80D05F6-DEC3-451E-88B9-(E-Mail Removed)...
> Problem Description:
>
> We have our Application client installed onto a network drive and various
> workstations at respective local machines. All the workstation uses the
> executables across the network. The help files .CHM files are also at
> network
> drive. But, workstations are not able to access the .CHM files across the
> network.
>
> Workaround tried:
>
> At workstation, we tried modifying the
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions
> registry
> entry to enable a specific security zone. The above workaround resolved
> the
> issue.
>
> Limitation:
>
> All workstation don’t have admin rights to modify the Registry entries.
>
> Is there any way to enable accessing .CHM files across the network.
>
> -Manoj R

Hi,

Thanks for your help. But, moving the CHM files to the local drive is not
feasible as workstations need to open each CHM file individually.

Please explain in detail " How the desired restriction at login can be set
globally??"

Thanks in anticipation.



"Richard G. Harper" wrote:

> Move the CHM files to the local drive or globally set the desired
> restriction at login.
>
> "Manoj R" <(E-Mail Removed)> wrote in message
> news:E80D05F6-DEC3-451E-88B9-(E-Mail Removed)...
> > Problem Description:
> >
> > We have our Application client installed onto a network drive and various
> > workstations at respective local machines. All the workstation uses the
> > executables across the network. The help files .CHM files are also at
> > network
> > drive. But, workstations are not able to access the .CHM files across the
> > network.
> >
> > Workaround tried:
> >
> > At workstation, we tried modifying the
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions
> > registry
> > entry to enable a specific security zone. The above workaround resolved
> > the
> > issue.
> >
> > Limitation:
> >
> > All workstation don’t have admin rights to modify the Registry entries.
> >
> > Is there any way to enable accessing .CHM files across the network.
> >
> > -Manoj R
>
>

If you have a domain, you can set the required change to run at logon as
part of a logon script; otherwise you'd need to set it to run before logon,
probably using the HKLM\Software\Microsoft\Windows\Current Version\Run
registry key to load the edit you need.

"Manoj R" <(E-Mail Removed)> wrote in message
news:056BEBDB-75E1-4E63-8436-(E-Mail Removed)...
> Hi,
>
> Thanks for your help. But, moving the CHM files to the local drive is not
> feasible as workstations need to open each CHM file individually.
>
> Please explain in detail " How the desired restriction at login can be set
> globally??"
>
> Thanks in anticipation.
>
>
>
> "Richard G. Harper" wrote:
>
>> Move the CHM files to the local drive or globally set the desired
>> restriction at login.
>>
>> "Manoj R" <(E-Mail Removed)> wrote in message
>> news:E80D05F6-DEC3-451E-88B9-(E-Mail Removed)...
>> > Problem Description:
>> >
>> > We have our Application client installed onto a network drive and
>> > various
>> > workstations at respective local machines. All the workstation uses the
>> > executables across the network. The help files .CHM files are also at
>> > network
>> > drive. But, workstations are not able to access the .CHM files across
>> > the
>> > network.
>> >
>> > Workaround tried:
>> >
>> > At workstation, we tried modifying the
>> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\HTMLHelp\1.x\ItssRestrictions
>> > registry
>> > entry to enable a specific security zone. The above workaround resolved
>> > the
>> > issue.
>> >
>> > Limitation:
>> >
>> > All workstation don’t have admin rights to modify the Registry entries.
>> >
>> > Is there any way to enable accessing .CHM files across the network.
>> >
>> > -Manoj R
>>
>>