HP Systems Insight Manager 7.2 Installation and Configuration Guide for Microsoft Windows

2. Open the Local Security Policies folder, and then open the Security Options
subfolder.
3. Disable the policy.
12.12.2.2 I cannot sign in to Systems Insight Manager on Windows XP.
If using a blank password, see the preceding problem. Otherwise, change the
following Local Security Policy on the Windows XP machine: Network Access:
Sharing and security model for local accounts from Guest Only to Classic.
NOTE: This setting does not affect remote sign-ins using domain accounts.
Modifying this policy allows remote sign-ins over the network using any local account
configured to do so, not just the Guest account. Ensure all local accounts have
appropriate passwords.
Procedure 28 Changing local security settings
1. Open Local Security Settings MMC Application by selecting
ProgramsAdministrative ToolsLocal Security Policy.
2. Open the Local Security Policies folder, and then open the Security Options
subfolder.
3. Change the setting from Guest Only to Classic.
If Guest Only is the preferred policy setting, perform the preceding steps, sign in
to Systems Insight Manager, and then add domain accounts (not local accounts)
or the local Guest account as accounts to Systems Insight Manager. Restore the
local policy setting back to Guest when done.
12.12.2.3 Single Sign On fails on cluster systems.
Single Sign On does not work on a virtual cluster system. It works on the physical
systems that comprise the cluster.
12.12.2.4 By using a proxy server, you might inadvertently or intentionally bypass IP address
login restrictions configured for the user.
You can use a proxy server to bypass specific IP exclusions, if the proxy server IP
address is not included in the IP exclusion ranges on the Login IP Address Restrictions
page. Likewise, the possibility that a valid proxy server is included in the IP exclusion
ranges prevents a valid user from signing in through that proxy server.
Ensure valid proxy servers are within a valid Inclusion ranges, and make the
Inclusion ranges as small as possible. Using IP inclusion ranges is more effective
than using IP exclusion ranges because Inclusion ranges exclude all addresses not
specified in the IP inclusion range.
12.12.2.5 I cannot sign in to Systems Insight Manager using Internet Explorer 6.0.
If your Systems Insight Manager server has an underscore in the name, use the IP
address of the Systems Insight Manager server instead of the name in the Internet
Explorer address field. Internet Explorer has a problem with underscores in system
names, which prevents the authentication cookie from working properly.
12.12.2.6 I cannot sign in to Systems Insight Manager or to managed systems browsing from
Systems Insight Manager using Internet Explorer 6.0.
Reason 1: Internet Explorer has a problem with underscores in system names, which
prevents the authentication cookie from working properly.
If the names of the systems have an underscore, use the IP address of the system.
1. Browse and sign-in to Systems Insight Manager.
2. Select OptionsSecuritySystem Link Configuration. The System Link
Configuration page appears.
3. Select Use the system IP address.
4. Click OK.
89