Why do we need to add the HP/Microfocus ALM URL to the trusted zones?

  • Questions
  • Why do we need to add the HP/Microfocus ALM URL to the trusted zones?
Question ID: 107893
1
0

Hell,
We have the need to install the ALM client on many systems and have found that due security needs and setting within the IE that are managed by policies and the IT department, that we need to add the URL to the trusted zones and Privacy tab. Both of these are maintained and managed by the IT department for the bulk of the users within the network and we are having a hard time convincing the department head that this kid a necessary option for them to add it on the policy and push to the users. Is there a reason that this is needed from the manufacturer, some reasoning to provide to the department head to justify this addition.

Thanks,
HomerJ

Marked as spam
Posted by (Questions: 327, Answers: 19)
Asked on October 17, 2017 3:20 pm
4 views
Answers (1)
2
Private answer

Hi HomerJ,
Putting the site into the Trusted Zones can allow the client to install without issues.

Per Microsoft on Internet Protected Mode:
Configuring Protected Mode
Protected Mode can be configured in Internet Explorer's Internet Options dialog. To configure Protected Mode, click the Security tab, select a Web content zone, and then change the Enable Protected Mode check box. By default, Protected Mode is enabled for the Internet, Intranet, and Restricted Sites zones. To verify that Internet Explorer is running in Protected mode, look for the words ''Protected Mode: On'' next to the Web content zone displayed in Internet Explorer's status bar.

As you see the Trusted Zones by default doesn't have protected mode enabled.

This shows the need to add to the trusted zones as it allows the client to be installed by loosening the restrictions that certain other zones can place on the files being installed..

Hope this helps,
Dan

Marked as spam
Posted by (Questions: 0, Answers: 721)
Answered on October 17, 2017 3:45 pm
The above explained everything very well and corrected our issue. Thanks
( at October 24, 2017 3:48 pm)