OV Operations for Windows 7.x

Size: px
Start display at page:

Download "OV Operations for Windows 7.x"

Transcription

1 OV Operations for Windows 7.x Common questions about OV Operations for Windows Security Setup, Users and groups Whitepaper V.1.01 August 6, 2003 New: Updated for OV Operations for Windows 7.20 Troubleshoot and Common Tasks Section Abstract This Whitepaper provides insight into the OV Operations for Windows Security and permissions setup and describes common issues and how to avoid these issues during initial installation and agent deployment. This revision of the white paper has been expanded to include other typical setup questions. Page 1/21

2 1 Before you install OV Operations for Windows HP-OVE-User/HP-OVE-Group Related What is a Domain (Networked) and Standalone Installation? What is HP-OVE-User and HP-OVE-Group used for? Automatic Windows agent software installation OVOW Services running as HP-OVE-User NNM (Network Node Manager) Adapter installation and runtime The difference between automatically and manually installed Windows Agents Does the HP-OVE-User need to be member of Domain Admins? Should I select existing accounts as the HP-OVE-User and HP-OVE-Group? I have multiple Domains with trusts. Where should the HP-OVE-User and HP-OVE-Group be created? What happens if the managed node is an NT 4.0 PDC, or a Windows 200X DC, or a Windows 200X DC in mixed mode? Company security policies regarding HP-OVE-Group as member of local administrators Select the HP-OVE-User and HP-OVE-Group correctly Problem: Creating the HP-OVE-User and HP-OVE-Group fails Problem: Adding of HP-OVE-Group to a managed node fails Management Across Domains w/o trust Defining OVOW administrators and operators Windows Agent Runtime related Windows Agent running as Local System and running as HP ITO Account Local System Account: opc_op no longer available Important aspects of running as local SYSTEM account Using the Command line tool SetMgmtServer Implementation for OVO for Windows 7.00 and Implementation for OVO for Windows User selection for the Manual Agent Installation Example Scenario: Upgrading OVOW 7.10 agents to run as System: Details on HP ITO Account and opc_op Running the agent as SYSTEM Sub-authentication DLL opcauth.dll (SetMgmtServer /auth) Troubleshooting of common OVOW problems Does OVOW work with Personal / Desktop Firewall software? Page 2/21

3 5.2 Problem: Policies cannot be saved anymore, the error is: 5 (Access Denied) Error: The VPO management server.. is not authorized OVOW will be reinstalled, and the previously used HP-OVE-User/ HP-OVE-Group removed OVOW Common Tasks How to change FQDN (Fully Qualified Domain Name) on the Windows server running OVOW How to change the OVOW Management Server Name configured on the managed nodes? Changing HP-OVE-User Using ovchgpass Changing the password for HP-OVE-User Changing the HP-OVE-User to a different user (same domain) Moving an OVOW Windows mgmt server from standalone installation to a networked installation Page 3/21

4 1 Before you install OV Operations for Windows If you plan to operate your OVO for Windows Server in a Windows Domain, make sure that you join the server to the domain prior to installation. Ensure that the DNS suffix of the Windows 200X server is set to a valid setting, reflecting a FQDN (Fully qualified Domain Name, e.g. ov_server.domain.com ). This FQDN has to be resolvable on the server as well as on all managed nodes. It must be possible to resolve the FQDN to IP-address, as well as the IP-Address ( reverse lookup ) to the FQDN (PTR maps). Join the server to the Windows Domain the OVOW Management server will be using if you wish to perform a Domain (Networked) installation. Set the DNS suffix. Check your DNS setup (name resolution). 2 HP-OVE-User/HP-OVE-Group Related These chapters describe usage and common issue around selecting HP-OVE-User and HP-OVE-Group. 2.1 What is a Domain (Networked) and Standalone Installation? Note: With OVOW 7.20 the term Networked has changed to Domain. The term 200X refers to Windows 2000 and Windows The first choice is to install the server in a Domain (Networked) vs. a Standalone installation. Domain (Networked) here means that the product is installed into an existing Windows 200X/NT domain. Standalone means that OVOW is installed on a system, that is not member of a Windows Domain or should not be installed using Windows Domain accounts. The Standalone installation still allows you to manage remote Windows and Unix managed nodes; all agents packages however have to be installed manually. Please see the section Management across Domains for a detailed explanation. For this section we assume a Domain (Networked) installation, which allows the OVO Windows management server to automatically install (and update) agent software on Windows managed nodes within the same domain and within domains that trust the domain of the OVOW server. During the installation of the OVO Windows Management server (short OVOW Server), you will get prompted with a Security Setup dialog box, which requires you to enter a Domain, a Domain User (default HP-OVE-User) and a Domain Group (default HP-OVE-Group). Page 4/21

5 2.2 What is HP-OVE-User and HP-OVE-Group used for? Automatic Windows agent software installation The Domain User HP-OVE-User and Domain HP-OVE-Group are used to allow the OVOW Server administrative access to a Windows managed node in order to install the agent software package(s) automatically. The HP-OVE-User is member of the HP- OVE-Group. OVOW Server process Runs as HP-OVE-User Installs OVO agent Windows Managed Node HP-OVE-Group is member of local administrators group The OVOW Server deployment process runs in the context of the HP-OVE-User. This process contacts a Windows managed node and a managed node needs to be able to authenticate the Domain User HP-OVE-User as a valid user with local administrative privileges. This authentication is accomplished via the following indirection: HP-OVE-User is member of HP-OVE-Group, which is member of the local administrators group on a managed node. The HP-OVE-Group is added to the local admin group automatically after a Windows managed node is added to the OVOW server, to via the Tool Openview Tools -> Windows security setup (OveConfig.exe) Note that the tool OveConfig.exe is run in the Windows security context of the user running the OVOW Console, and it requires that this user context has sufficient rights to add the HP-OVE-Group, typically Domain or Enterprise administrative rights OVOW Services running as HP-OVE-User The OVOW server services OvAutoDiscovery Server and OvDnsDiscoveryService run as the HP-OVE-User, which is local administrator in both the Domain (Networked) and Standalone installation NNM (Network Node Manager) Adapter installation and runtime The NNM adapter uses the HP-OVE-User to obtain administrative access to the managed node running NNM to install an additional deployment package. 2.3 The difference between automatically and manually installed Windows Agents The automatic agent installation procedure pushes an agent bootstrap component via DCOM and copies the files via the administrative share (C$) (which needs to be enabled). After the agent software (Core Operations Agent and optional Configuration Policy Deployment Package) is installed, the communication between agent and server uses DCE-RPC and socket (HTTP Protocol), which does not use Windows authentication. The post agent installation runtime communication includes message, actions, and deployment of policies and instrumentations files. Page 5/21

6 This implies that after installation of the agent software package, the HP-OVE-User and HP-OVE-Group are no longer used or required, unless you are upgrading the agent, or install additional agent packages via the server based (push) deployment If your Windows agent is manually installed using the Manual Agent Installation Package, the HP-OVE-Group is not added onto a managed node. Since the manual agent installation package contains also the Configuration Policy Deployment Package, the manual agent package is equivalent to the automatically installed agent in terms of runtime functionality. Currently the only other Deployment Package is the Network Node Manager (NNM) Adapter package, which is installed and automatically deployed to the system running NNM. This requires that the agent on the NNM system (if NNM is running on a remote system) to be using the Domain (Networked) installation only. 2.4 Does the HP-OVE-User need to be member of Domain Admins? No, the HP-OVE-User should be a regular Domain user account. In fact it is recommend that this user is not a member of Domain Admins, since admin credential grants the OVOW Server administrative access to all Windows nodes in a given domain, which is usually not desired. What other credentials does the HP-OVE-Group have on a managed node? HP-OVE-Group is member of the local administrative group Additional local security settings o Access this computer from the network o Logon as batch 2.5 Should I select existing accounts as the HP-OVE-User and HP-OVE- Group? Yes, you can select existing users and group. However is not recommended to choose an account that is used by a physical user to log on. The HP-OVE-User is an administrative account and the Windows Domain administrator only should know the password. Selecting an existing group implies that all members of this group get an implicit administrative privilege to all OVOW managed nodes, including the OVOW Server. The password for the HP-OVE-User (or whichever user is selected during OVOW server installation) should be set to no expiration, if this is not possible see Common Tasks I have multiple Domains with trusts. Where should the HP-OVE-User and HP-OVE-Group be created? If you are planning to manage nodes within a different Domain than the domain in which the OVOW Server is located, it may be required to create the HP-OVE-User and HP-OVE-Group at a different level. Since there are many possible scenarios, including ADS Forests, NT 4.0 logon and resource domains, one-way or two-way trusts, the requirement comes down to the following: Page 6/21

7 A Windows node has to be able to authenticate the Domain User HP-OVE- User as a valid member of the local administrators, via the Domain Group HP-OVE-Group in order to grant administrative access and to be able to install software on the system. Since this authentication only happens when installing and upgrading agent packages (and for connecting remote consoles), there is usually no performance considerations required such as AD trust shortcuts. 2.7 What happens if the managed node is an NT 4.0 PDC, or a Windows 200X DC, or a Windows 200X DC in mixed mode? Domain controllers don t have local users, that is all users created are Domain users A Domain controller however does have local groups (PDC NT 4.0 term Local Group, DC Windows 200X term built-in ). Specifically these systems have local administrative groups. Note that these groups are not truly local, since they are shared with the Backup domain controller (BDC) in Windows NT 4.0 environments or other DCs in a Windows 200X environment. The HP-OVE-Group is added to the local/built-in group administrators, not to Domain Admins. Adding the HP-OVE-Group group to the local administrators group does not imply that HP-OVE-User/HP-OVE-Group now has Domain Admin privileges. Note that a Domain group can be a member of a local group, but a Domain group cannot be member of another Domain group. Note: Although HP-OVE-Group is not directly a member of Domain Admins, being in the local administrative group on a DC already provides the HP-OVE-Group elevated security credentials. 2.8 Company security policies regarding HP-OVE-Group as member of local administrators Due to security requirements (security policies, GPOs), it is possible that your company policies specify that DCs cannot have any group other than Domain Admins or Enterprise Admins as a member of the local administrative group. The recommended solution here is to only use the manually installable agent in this environment. Another possibility is to remove the HP-OVE-Group from the local administrative group after the OVO agent is installed. 2.9 Select the HP-OVE-User and HP-OVE-Group correctly OVOW does not allow you to change the security context after the OVOW server is installed. A change usually requires the OVOW server to be reinstalled. Therefore make sure that you plan your requirements prior to installation of the OVOW Server and select an appropriate HP-OVE-User account and HP-OVE-Group group Problem: Creating the HP-OVE-User and HP-OVE-Group fails Page 7/21

8 The Security Setup performs either one of two different tasks: 1) If the HP-OVE-User/HP-OVE-Group is not already created in the selected Domain, it will attempt to create the user and group. In order to succeed, the Windows user running the OVOW Server installation needs sufficient privileges on the PDC (Primary Domain controller NT 4.0) or DC (Domain Controller Windows 200X) to create a group and a user. If you are planning to create this user/group in e.g. the Log-on Domain (rather than the Resource Domain NT 4.0 context) or in the parent ADS Domain (Windows 200X), you may not have sufficient privileges to add a user even if you are Domain Admin to your Resource or Child Domain (Administrative trusts are typically not transitive or one-way). If you have such a requirement, create the HP- OVE-User and HP-OVE-Group manually at the appropriate level prior to installing the OVOW Server. 2) If the HP-OVE-User/HP-OVE-Group is already available, the Security Setup performs a regular authentication of the HP-OVE-User (valid password required). In this case it is not necessary to hold Domain Admin privileges for the user installing the OVOW Server, local admin is sufficient Problem: Adding of HP-OVE-Group to a managed node fails After adding a Windows managed node, a dialog box opens and indicates a failure or an error: After the task of adding a node the OVOW Server (Console) executes a tool called Windows Node Security Setup which attempts to add the HP-OVE-Group to the local administrators group of the newly added managed node. This tool is executed in the user context of the Windows user running this tool, which is the user running the OVOW console. Failure to run this tool successfully indicates that you don t have enough privileges to bring this node under management. This does not indicate that OVOW Server generally lacks the ability to manage this node it may simply be that the user that you are logged onto (whilst running the OVOW MMC console) lacks the necessary privileges. There are two types of administrative roles that have to be considered: The OVOW Admin credential (via the OVE-ADMINS group) and the Windows admin credential to add a Domain group (HP-OVE-Group) to the local administrators group on a Windows node. The first credential allows you to add/remove/modify nodes on the OVOW Server, the second one allows you to bring additional nodes under management. To make the Windows Node Security Setup tool run successful, you either have to logon as a different user combining the above mentioned credentials, or you have to ask e.g. your Windows Domain Admin to manually add the HP-OVE-Group to the systems which should be managed by OVOW. Note that with the latter process, a Windows Domain Admin maintains control over the environment, granting the OVOW Admin selective access to the nodes in the Windows Domain(s). The tool Windows Node Security Setup (OveConfig.exe) is available to run outside the Node Configuration in the tools section Openview Tools -> Windows Node Security Setup. Page 8/21

9 You can run the tools multiple times, to verify if a node is already configured (= the HP-OVE-Group is added to the local administrators group) 2.12 Management Across Domains w/o trust If your Windows managed node cannot be in the same Windows Domain, or you cannot establish a trust relation, or the system is inside or outside a Firewall (which is blocking Windows authentication request), you can still manage this node by manually installing the Agent software on this node (new feature of OVOW 7). During the installation you are prompted for the FQDN of your OVOW Server. As mentioned previously, the agent requires Windows authentication only for the initial agent installation NOT for the manually installed agent, regular operation is not affected by Windows security requirements. If you chose to install all Windows agents (except for the agent on the OVOW Server) manually, then you can either use a Standalone or a Networked installation. The default agent installation requires manual interaction - setting the OVOW Server FQDN in a pop-up window. If you want to perform bulk installation with the Windows manual agent package, e.g. using 3 rd party installation tools, you can pre-set the FQDN of the OVOW Server in the AgentConfig.ini file that is part of the manually installed agent package. Note that if you are planning to use the Network Node Manager (NNM) integration and running NNM on another system than the OVOW Management Server (which is recommended), you must install the Agent on the NNM system automatically, using an OVOW domain installation. 3 Defining OVOW administrators and operators An OVOW Server distinguishes between an Administrator and an Operator user role. Within these roles, the User Role configuration allows further refinement. Generally an Operator does not have access to the Configuration editors for Nodes, Services, Tools and the Policy management. Note that an OVOW Administrator is not the same as a Windows Domain Administrator. However, users who hold local administrative credentials on the OVOW Server will always be considered as an OVOW Administrator (this includes Domain Admins). This means that User Roles DO NOT APPLY to these users they will always be given full OVOW administrative access. Note that the OVOW Administrator has to be an authorized user since it does have (via the Agent) near administrative possibilities on all managed nodes. If a user starts the OVOW console, the OVOW Server performs the following checks: User is OVOW Administrator if the user is a member of the local administrators group on the OVOW Server system (regardless of whether the Console is launched locally on the OVOW or it is a remote Console) User is OVOW Administrator if user is a member of the local group OVE- ADMINS User is OVOW Operator if user is a member of the local group OVE- OPERATORS User will be denied access to OVOW otherwise Page 9/21

10 NOTE: Don t mix up the concept of the HP-OVE-User and HP-OVE-Group with the OVE-ADMINS and OVE-OPERATORS. HP-OVE-User/HP-OVE-Group is used to grant the server administrative access to a managed node. OVE-ADMINS and OVE-OPERATORS are used to identify valid users of the OVOW product and grant access to the OVOW server User Interfaces (MMC & Web UI). Page 10/21

11 4 Windows Agent Runtime related 4.1 Windows Agent running as Local System and running as HP ITO Account Background information: The original design of the OVO Agent for Windows uses a local administrative account for the OVO Agent service ( HP ITO Agent ). However several issue are known regarding the creation and maintenance of HP ITO Account Failure to create HP ITO Account automatically on Active Directory controllers Company policy to not allow any local administrative accounts (GPO) Company policy to not allow any local accounts Randomly generated password does not meet password policies Password expiration required for all accounts HP ITO Account member of Domain Admins if agent is installed on DC/PDC These issues have lead to the decision to now with the 7.20 release install the HP ITO Agent service to run as local System account by default. To facilitate the transition for tools and policies running as HP ITO Account, a special agent feature has been implemented which automatically translates action requests for the HP ITO Account and SYSTEM to be executed in the current agent context. This means that if you are changing or upgrading the OVO agent on Windows to run as SYSTEM, it is not necessary to update any existing policies or tools when using OVOW Furthermore the agent now accepts a variable user directive $AGENT_USER, which enables Tools and Scheduled Tasks to run in the user context of the agent (typically HP ITO Account or SYSTEM ) Local System Account: opc_op no longer available If you are change your Windows agents to run as local System the agent s handling of HP ITO Account and SYSTEM allow you to keep tools and policies unmodified. Policies using opc_op however need to be changed; the local user opc_op is no longer available if the agent is installed as local System. See Change user name in Scheduled Tasks and Tools under Common Tasks Important aspects of running as local SYSTEM account The local System account has privileges equivalent to an Administrator on a local system, however - unlike a regular account the local System account does not have network credentials. This means in the Windows security context, the OVO Agent running as System cannot access shares (e.g. monitoring log files on shares), cannot access remote Perflib or registry data, and cannot connect to a remote WMI instance. (It does allow remote MIB polling, since this method uses SNMP security) You still can create custom solutions to access remote Windows systems by utilizing the Scheduled Tasks policy, which allows the policy to run in a different (Domain) user context by providing network credentials. Page 11/21

12 All available HP SPIs currently work with either the Agent running as HP ITO Account or local System, for details please refer to the SYSTEM Account Whitepaper Using the Command line tool SetMgmtServer SetMgmtServer version that is included as part of patch OVOW_00030 or OVOW 7.20 Note that this section does not describe all available features of the SetMgmtServer tool. Setting HP ITO Account or SYSTEM Open cmd prompt and run SetMgmtServer /system to display the current setting. Enabled indicates that OVO agent using the automatic installation method will be will run as the local System context, Disabled means that the user context of HP ITO Account will be used. To actually change the logon setting of the OVO agent, you need to redeploy ( All Tasks -> Redeploy All ) the agent (incl. the OVOW Management Server itself). If you are upgrading or reinstalling an existing OVO agent, the state ( HP ITO Account or System) will be maintained, regardless of the /system setting. In order to change an existing agent from HP ITO Account to SYSTEM the /forced switch has to be turned on. o SetMgmtServer /forced displays the current setting. o Set to off by default Examples are shown below Implementation for OVO for Windows 7.00 and 7.10 Install the patch OVOW_00030 (available from (please always check for superceding patches) and utilize the command line tool SetMgmtServer (see below) Implementation for OVO for Windows 7.20 No special settings are required, new default agent installations will use the Local System installation. If you are upgrading existing OVO Agents for Windows, please see the detailed description for the command line tool SetMgmtServer below. In addition you will notice a change in the Scheduled Tasks Policy Editor as well as the Tool configuration screen in OVOW 7.20: There is now a selection to Run as Agent User which is the equivalent of the above mentioned $AGENT_USER User selection for the Manual Agent Installation The Windows manual installable package will prompt for a choice between Local System Account (default) and HP ITO Account. For unattended installation set the value in the AgentConfig.ini file, the directive is UseSystemAccount= Example Scenario: Upgrading OVOW 7.10 agents to run as System: Install patch OVOW_00030 (or superceding) on OVOW Mgmt server Run: SetMgmtServer /system /on /forced /on Page 12/21

13 Perform Redeploy All on all agents 4.2 Details on HP ITO Account and opc_op NOTE: The default is Local System however, for legacy requirements you can run the agent as HP ITO Account. Using the local System account is strongly recommended to for new OVOW Implementations. The agent service HP ITO Agent runs as the local user HP ITO Account. This local user account is created during installation of the agent. HP ITO Account is member of the local administrators group and has a couple of additional security credentials, e.g.: Act as part of the operating system Log on as Service Shutdown the system During the agent installation the HP ITO Account gets created and receives a randomly generated password. This password is different for each installed agent (except NT 4.0 BDC/PDC), and also reinstallation of the agent creates a different password each time. The password is used to configure the HP ITO Agent service to run in this context. Note that the HP ITO Account password is set to never expire and - although the password is not known to anyone - it may cause conflicts with an (external) security policy (see note about running the agent as SYSTEM below). If you set the password to expire, the password will have to be periodically changed and updated in the Log on as section of the HP ITO Agent. It is therefore not recommended to require expiration or manually change the password of the HP ITO Account. Important Note for DC: Do not change the password for the HP ITO Account on Domain Controllers. Note: If the agent software is installed on a PDC (NT 4.0) or a DC (Windows 200X), the HP ITO Account is a global Domain account, which is also made a member of Domain Admins. Again the password is randomly generated, and nobody can utilize this account to logon to the PDC or any other system in that Domain, it may, however cause conflicts with existing security policies. The other user that is created is the opc_op user. Beside the ability to shutdown the system, this account is a regular user account without administrative privileges. It is typically used for Tools and Scheduled Tasks, which only need regular, nonadministrative privileges. The user opc_op is available on all Windows nodes as well as on UNIX managed nodes. This allows the configuration of platform independent tools and scheduled tasks, using the common account opc_op. The opc_op user can be used in a tool or scheduled command with a blank password. This account also has a randomly generated password and is also is a Domain account if a PDC or DC is a managed node. Important Note: A Domain HP ITO Account is not the same as a local HP ITO Account. Each instance of the HP ITO Account has a different SID and a different password. Page 13/21

14 4.3 Running the agent as SYSTEM Most of the Windows OS related services use the built in SYSTEM account as their user context. The SYSTEM account is a built-in account without a configurable password, which has almost equivalent privileges as a local administrator. Since it is not a regular user account, it cannot be assigned additional credentials providing access to remote systems (Network Credentials) If the agent runs as SYSTEM, the following restrictions and changes apply: The agent running as SYSTEM can impersonate other users (local and domain) using the username/password configuration in Tools and in policies of the type Scheduled Task. No local user is created: No HP ITO Account and no opc_op Tools and Scheduled commands which are currently configured to use these accounts have to be modified to use SYSTEM (without a password), or the local administrator, or another local or Domain user (with password) 4.4 Sub-authentication DLL opcauth.dll (SetMgmtServer /auth) Background: Unlike on UNIX system, Windows security does not allow for an administrative user to change to a different user context (switch user) without a valid password. Policies and SPIs however require the ability to switch user in order to connect to applications, or to access resources that require a different set of credentials than System or HP ITO Account. For this purpose the OVO agent introduces a sub-authentication DLL (opcauth.dll) that can only be called by the OVO Agent (Action subagent). This DLL allows the OVO Agent to switch to a different user context without requiring a valid password. The agent can switch context to both local and domain users (requires the PDC/DC to have an opcauth.dll active). The user context switch never grants the action agent network access. Changing to a different user context may not be desirable in environments with higher security requirements, and the SetMgmtServer tool can be used to disable this sub-authentication DLL for Scheduled Task policies and Tools: SetMgmtServer /auth /on - Any switch user (change to a different user by tool or policy) requires a valid password SetMgmtServer /auth /off Sub-authentication is enabled, password-less switch enabled (default setting) Note that agent has to be redeployed to enable changes. Page 14/21

15 5 Troubleshooting of common OVOW problems 5.1 Does OVOW work with Personal / Desktop Firewall software? Personal Firewall e.g. Symantec Desktop Firewall, ZoneAlarm, Windows XP embedded Firewall With a default configuration, which typically includes block all external incoming requests, OVOW does not work. It is recommended to disable the personal firewall for usage with OVOW. If you need to run Personal Firewall software, the rules configuration should contain roughly OVOW Management Server: Allow incoming, UDP TCP, all ports the IP- Address or FQDN for each managed node and remote console add the OVOW server itself as well. OVOW Agents: Allow incoming, UDP TCP, all ports the IP-Address or FQDN for the OVOW management server and the agent address itself OVOW Remote Console - Allow incoming, UDP TCP, all ports the IP-Address or FQDN of the OVOW Management server. The OVOW Server sends async events to the Remote Console and a Personal Firewall would typically block these. For more details on Firewall setup and OVOW see the Firewall Configuration Whitepaper. Note that if you are planning to use the Network Node Manager (NNM) integration and running NNM on another system than the OVOW Management Server (which is recommended), you must install the Agent on the NNM system automatically, using an OVOW domain installation. 5.2 Problem: Policies cannot be saved anymore, the error is: 5 (Access Denied) Explanation: The group HP-OVE-Group has been removed from the local administrators group on the OVOW Management server. The process ovpmad.exe impersonating HP-OVE-User does not have credentials to write to OVOW folders. Unless the HP-OVE-Group has been manually removed from the local administrators group, the reason typically is that a GPO (Global Policy Object) has a rule to remove all foreign users and groups from the local administrators group Solution: Add the HP-OVE-Group back to the local administrators group. If applicable, change the GPO to allow the HP-OVE-Group to remain in the local administrators group. Page 15/21

16 5.3 Error: The VPO management server.. is not authorized Problem: A managed node was added (both automatic, or manually Windows or Unix), however no policies can be deployed: The error is: The VPO management server sending the config request is not an authorized VPO management server for the managed node Explanation: The authentication between the OVOW management server and a managed node is done via the FQDN and IP address of the OVOW management server. The agent takes the configured server FQDN from its file opcinfo, resolves the IP address and compares this address with the incoming request of the OVOW management server, and will only allow access if these match. Typical scenarios for this to happen are: 1) OVOW server installed on a system where the DNS suffix was not set before OVOW was installed. In this case the server is configured with the short name, the Windows agent s opcinfo file contains the short name as well and cannot resolve. To solve this problem, follow A.3, changing the OVOW mgmt server name to the FQDN and change the setting on each agent by either redeploying the Windows agent package, or changing the setting in opcinfo manually. 2) OVOW server is correctly installed with DNS suffix, however the agent cannot resolve the FQDN of the OVOW management server. To solve this problem make sure that the agent s DNS setting will resolve the OVOW FQDN correctly. If changes to DNS are not possible, you can setup a hosts entry, or use the opcinfo switch OPC_RESOLVE_IP <IP-of-OVOW-Mgmt-Srv>. 3) Scenario where the agent and server use different DNS servers and domain settings. This typically happens if the OVOW management server is installed in an AD environment with integrated DNS, where the domain suffix incorporates the AD domain name, and other parts of the environment, e.g. Unix nodes, use different DNS servers without the AD domain name in the FQDN. The solution here is the same as in 2) to ensure that the agent can resolve the OVOW management server correctly. Note: What is a VPO server anyway? VPO stands for VantagePoint Operations, which was the previous product name of OV Operations. Most of the internal error messages haven t been updated. Page 16/21

17 5.4 OVOW will be reinstalled, and the previously used HP-OVE-User/HP- OVE-Group removed. Problem: Reinstalling OVOW and specifying the just removed HP-OVE-User/HP-OVE- Group will cause a failure, the HP-OVE-User and HP-OVE-Group cannot be recreated or authenticated. Explanation: Windows DCs and the local security of a member server are caching users and groups. It may take some time to resync all DCs and member servers. Solution: Pick a different account (string) name for HP-OVE-User and HP-OVE- Group and OVOW install will be successful. 6 OVOW Common Tasks 6.1 How to change FQDN (Fully Qualified Domain Name) on the Windows server running OVOW. Note: This also applies to installations which used the short DNS name or have a new domain member ship which has a different domain extension. Solution: 1) Close all Consoles including any Remote console connected to this OVOW server 2) Run regedit and change the following keys [HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett- Packard\OVEnterprise\Management Server\MsgActSrv] "MGMT_SERVER"="ovow_serv.domain.com" "NAMESRV_LOCAL_NAME"="ovow_serv.domain.com" [HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett-Packard\OpenView\ITO] "Hostname"="ovow_serv.domain.com" 3) Open a cmd prompt and run SetMgmtServer, the output will indicate a from <old_fqdn> to <new_fqdn> 4) Change the FQDN of the Windows Server; make sure the new FQDN resolves correctly. Reboot the OVOW server. 5) Each managed node currently managed by this management server needs to be updated with the new FQDN of the OVOW server. This includes the agent on OVOW server itself (see 6.2 for details) Page 17/21

18 6.2 How to change the OVOW Management Server Name configured on the managed nodes? On Windows managed nodes run %OvAgentDir%\bin\OpC\install\mgmt_sv.vbs. This tool prompts you for the new FQDN of the OVOW Management server and restarts the agent. Alternatively you can manually change the setting, as described in the section for UNIX agents below. (The filename for Windows agents is %OvAgentDir%\bin\OpC\install\opcinfo) On UNIX managed node locate the file opcinfo (usually /opt/ov/bin/opc/install/opcinfo), edit the file and change the value of OPC_MGMT_SERVER to the new OVOW server FQDN. e.g. OPC_MGMT_SERVER ovow_serv.domain.com Run opcagt kill followed by opcagt start 6.3 Changing HP-OVE-User Using ovchgpass IMPORTANT NOTE: ovchgpass updates the password within the Windows local or Domain authority first, then changes the settings for the OVOW product (service logins, DCOM settings, and within tools and policies). Ovchgpass cannot be used to change HP-OVE-Group. 6.4 Changing the password for HP-OVE-User Changing the password for the HP-OVE-User is a straightforward task. It may be required in environments where there is a mandatory password expiration enforced for all domain users. 1) Close all consoles including any remote console connected to the OVOW server 2) Open a CMD Window and run ovchgpass which starts a GUI Page 18/21

19 3) Type the new password and press ok 4) You ll see a progress bar and unless there is an error the dialog box will just close which indicates successful change Error you may encounter: If the user is not available, or the password does not meet the requirements (length and/or special characters) 6.5 Changing the HP-OVE-User to a different user (same domain) The HP-OVE-User is only used on the OVOW mgmt server in the service logon and DCOM security configuration. The HP-OVE-User is only used indirectly (via HP-OVE- Group) on Windows managed nodes, so if the new HP-OVE-User account is also a member of the HP-OVE-Group, there is no impact on configured Windows managed nodes. 1) Create a new domain user e.g. NEW-OVE-User, set the password to never expires 2) NEW-OVE-User must be a member of HP-OVE-Group (if not see below) 3) Run ovchgpass and enter the new account name and set the password. Changing user name in Scheduled Tasks and Tools Tools and Scheduled Tasks policies can be modified individually, or change in bulk operations via the following tools. Note that both tools perform the change globally to all tools/policies of the same user name Notes: Tools: Select "Openview Tools" - > "Modify Tools login/password" (GUI only) Scheduled Tasks: %OvInstallDir%\bin\ovpmpwutil (command line only) use /? for help. Ovpmpwutil creates a new version of each Scheduled Tasks. In the view Policy Groups references only a specific version and to update you need to select Update to Latest The switch /p for the Password is not optional, although you cannot specific a password for HP ITO Account or SYSTEM. To specify an empty password use the switch /P Ovpmpwutil may take a several minutes to complete Page 19/21

20 6.6 Moving an OVOW Windows mgmt server from standalone installation to a networked installation. WARNING: This procedure is unsupported. It requires you to obtain a user and group SID, and to change registry settings. If you are not familiar with the procedures below, please uninstall and reinstall OVOW rather than using this procedure. 1) If the Windows server running the OVOW server is standalone (in a Workgroup), change it to a domain membership. a. Make sure no Consoles are running b. Check for any stale ovpmad.exe process and terminate them if required. (If you get an Access Denied use kill from the Resource Kit) 2) Ensure the a domain user and group is created and the password is known. The rest of these instruction reference this new user as DOM\HP-OVE-User and DOM\HP-OVE-Group, where DOM is the domain name. 3) Run ovchgpass, enter DOM in the domain field and HP-OVE-User as the account and the current password in the New password field. 4) Run the DCOM configuration tool dcomcnfg a. Select from the Application list ovpmad and press Properties b. Select the identity tab c. The field This user is select; enter here the new DOM\HP-OVE-User with the password; retype the password. d. Press Ok twice to apply and close e. Don t restart the services yet (see step 8) 5) You need to obtain the SID for DOM\HP-OVE-User and DOM\HP-OVE-Group. You can use the tool PsGetSID available from under PSTools. 6) Run regedit and locate the keys: a. HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett- Packard\OVEnterprise\Security\Aliases b. Change the Data of Value HP-OVE-User to DOM\HP-OVE-User c. Change the Data of Value HP-OVE-Group to DOM\HP-OVE-Group d. Locate HKEY_LOCAL_MACHINE\SOFTWARE\Hewlett- Packard\OVEnterprise\Security\Registered Accounts e. Remove both Values (SIDs) f. Create a new String Value, the name of the Value is the SID of the HP- OVE-Group, the data is DOM\HP-OVE-Group g. Create a new String Value, the name of the Value is the SID of the HP- OVE-User, the data is DOM\HP-OVE-User h. Exit regedit Page 20/21

21 7) Open the Services panel and change the log-on as configuration for the following 2 Services to Log-on as DOM\HP-OVE-User; Restart the services a. OvAutoDiscovery Server b. OvDnsDiscoveryService 8) The group DOM\HP-OVE-User has to be member of the local administrators group on the OVOW management server. You can either do that manually, or by following step 9) below, running Windows Node Security Setup on the OVOW management server. 9) If you have manually installed remote Windows agent, run Windows Node Security Setup if you are planning to upgrade these agents eventually using the automatic agent installation method. 10) Depending on your Windows domain and DNS setup, a change in Domain may include a change to your FQDN. If this is the case, please refer to 6.1/6.2 how to change the FQDN. Page 21/21

DC Agent Troubleshooting

DC Agent Troubleshooting DC Agent Troubleshooting Topic 50320 DC Agent Troubleshooting Web Security Solutions v7.7.x, 7.8.x 27-Mar-2013 This collection includes the following articles to help you troubleshoot DC Agent installation

More information

WhatsUp Gold v16.3 Installation and Configuration Guide

WhatsUp Gold v16.3 Installation and Configuration Guide WhatsUp Gold v16.3 Installation and Configuration Guide Contents Installing and Configuring WhatsUp Gold using WhatsUp Setup Installation Overview... 1 Overview... 1 Security considerations... 2 Standard

More information

User Manual. Onsight Management Suite Version 5.1. Another Innovation by Librestream

User Manual. Onsight Management Suite Version 5.1. Another Innovation by Librestream User Manual Onsight Management Suite Version 5.1 Another Innovation by Librestream Doc #: 400075-06 May 2012 Information in this document is subject to change without notice. Reproduction in any manner

More information

ILTA HANDS ON Securing Windows 7

ILTA HANDS ON Securing Windows 7 Securing Windows 7 8/23/2011 Table of Contents About this lab... 3 About the Laboratory Environment... 4 Lab 1: Restricting Users... 5 Exercise 1. Verify the default rights of users... 5 Exercise 2. Adding

More information

IIS, FTP Server and Windows

IIS, FTP Server and Windows IIS, FTP Server and Windows The Objective: To setup, configure and test FTP server. Requirement: Any version of the Windows 2000 Server. FTP Windows s component. Internet Information Services, IIS. Steps:

More information

Kepware Technologies Remote OPC DA Quick Start Guide (DCOM)

Kepware Technologies Remote OPC DA Quick Start Guide (DCOM) Kepware Technologies Remote OPC DA Quick Start Guide (DCOM) March, 2013 Ref. 03.10 Kepware Technologies Table of Contents 1. Overview... 1 1.1 What is DCOM?... 1 1.2 What is OPCEnum?... 1 2. Users and

More information

Installing and Configuring Active Directory Agent

Installing and Configuring Active Directory Agent CHAPTER 2 Active Directory Agent is a software application that comes packaged as a Windows installer. You must install it on a Windows machine and configure it with client devices and AD domain controllers.

More information

NSi Mobile Installation Guide. Version 6.2

NSi Mobile Installation Guide. Version 6.2 NSi Mobile Installation Guide Version 6.2 Revision History Version Date 1.0 October 2, 2012 2.0 September 18, 2013 2 CONTENTS TABLE OF CONTENTS PREFACE... 5 Purpose of this Document... 5 Version Compatibility...

More information

Setting up DCOM for Windows XP. Research

Setting up DCOM for Windows XP. Research Setting up DCOM for Windows XP Research 1- Setting up DCOM for Windows XP This document has been produced as a guide to configuring DCOM settings on machines with Windows XP SP2 installed. You must make

More information

Installation Notes for Outpost Network Security (ONS) version 3.2

Installation Notes for Outpost Network Security (ONS) version 3.2 Outpost Network Security Installation Notes version 3.2 Page 1 Installation Notes for Outpost Network Security (ONS) version 3.2 Contents Installation Notes for Outpost Network Security (ONS) version 3.2...

More information

How To Create An Easybelle History Database On A Microsoft Powerbook 2.5.2 (Windows)

How To Create An Easybelle History Database On A Microsoft Powerbook 2.5.2 (Windows) Introduction EASYLABEL 6 has several new features for saving the history of label formats. This history can include information about when label formats were edited and printed. In order to save this history,

More information

Using DC Agent for Transparent User Identification

Using DC Agent for Transparent User Identification Using DC Agent for Transparent User Identification Using DC Agent Web Security Solutions v7.7, 7.8 If your organization uses Microsoft Windows Active Directory, you can use Websense DC Agent to identify

More information

Sharp Remote Device Manager (SRDM) Server Software Setup Guide

Sharp Remote Device Manager (SRDM) Server Software Setup Guide Sharp Remote Device Manager (SRDM) Server Software Setup Guide This Guide explains how to install the software which is required in order to use Sharp Remote Device Manager (SRDM). SRDM is a web-based

More information

HP ProLiant Essentials Vulnerability and Patch Management Pack Release Notes

HP ProLiant Essentials Vulnerability and Patch Management Pack Release Notes HP ProLiant Essentials Vulnerability and Patch Management Pack Release Notes Supported platforms... 2 What s new in version 2.1... 2 What s new in version 2.0.3... 2 What s new in version 2.0.2... 2 What

More information

CXM 4.5 Deployed on Windows 2008. Chad Adams October 28, 2009

CXM 4.5 Deployed on Windows 2008. Chad Adams October 28, 2009 CXM 4.5 Deployed on Windows 2008 By Chad Adams October 28, 2009 This document describes issues and resolutions encountered when testing CXM on Windows 2008 (32-bit) and Windows 2008 (64-bit). CXM on Windows

More information

How to - Install EventTracker and Change Audit Agent

How to - Install EventTracker and Change Audit Agent How to - Install EventTracker and Change Audit Agent Agent Deployment User Manual Publication Date: Oct.17, 2015 EventTracker 8815 Centre Park Drive Columbia MD 21045 www.eventtracker.com Abstract EventTracker

More information

How To - Implement Clientless Single Sign On Authentication with Active Directory

How To - Implement Clientless Single Sign On Authentication with Active Directory How To Implement Clientless Single Sign On in Single Active Directory Domain Controller Environment How To - Implement Clientless Single Sign On Authentication with Active Directory Applicable Version:

More information

Step-By-Step Guide to Deploying Lync Server 2010 Enterprise Edition

Step-By-Step Guide to Deploying Lync Server 2010 Enterprise Edition Step-By-Step Guide to Deploying Lync Server 2010 Enterprise Edition The installation of Lync Server 2010 is a fairly task-intensive process. In this article, I will walk you through each of the tasks,

More information

Building the SAP Business One Cloud Landscape Part of the SAP Business One Cloud Landscape Workshop

Building the SAP Business One Cloud Landscape Part of the SAP Business One Cloud Landscape Workshop Building the SAP Business One Cloud Landscape Part of the SAP Business One Cloud Landscape Workshop TABLE OF CONTENTS 1 INTRODUCTION... 3 2 LANDSCAPE DETAILS... 3 2.1 Server Details... 3 2.2 Landscape

More information

Using Logon Agent for Transparent User Identification

Using Logon Agent for Transparent User Identification Using Logon Agent for Transparent User Identification Websense Logon Agent (also called Authentication Server) identifies users in real time, as they log on to domains. Logon Agent works with the Websense

More information

Guide to deploy MyUSBOnly via Windows Logon Script Revision 1.1. Menu

Guide to deploy MyUSBOnly via Windows Logon Script Revision 1.1. Menu Menu INTRODUCTION...2 HOW DO I DEPLOY MYUSBONLY ON ALL OF MY COMPUTERS...3 ADMIN KIT...4 HOW TO SETUP A LOGON SCRIPTS...5 Why would I choose one method over another?...5 Can I use both methods to assign

More information

Configuring Sponsor Authentication

Configuring Sponsor Authentication CHAPTER 4 Sponsors are the people who use Cisco NAC Guest Server to create guest accounts. Sponsor authentication authenticates sponsor users to the Sponsor interface of the Guest Server. There are five

More information

TECHNICAL DOCUMENTATION SPECOPS DEPLOY / APP 4.7 DOCUMENTATION

TECHNICAL DOCUMENTATION SPECOPS DEPLOY / APP 4.7 DOCUMENTATION TECHNICAL DOCUMENTATION SPECOPS DEPLOY / APP 4.7 DOCUMENTATION Contents 1. Getting Started... 4 1.1 Specops Deploy Supported Configurations... 4 2. Specops Deploy and Active Directory...5 3. Specops Deploy

More information

WhatsUp Gold v16.1 Installation and Configuration Guide

WhatsUp Gold v16.1 Installation and Configuration Guide WhatsUp Gold v16.1 Installation and Configuration Guide Contents Installing and Configuring Ipswitch WhatsUp Gold v16.1 using WhatsUp Setup Installing WhatsUp Gold using WhatsUp Setup... 1 Security guidelines

More information

ms-help://ms.technet.2005mar.1033/security/tnoffline/security/smbiz/winxp/fwgrppol...

ms-help://ms.technet.2005mar.1033/security/tnoffline/security/smbiz/winxp/fwgrppol... Page 1 of 16 Security How to Configure Windows Firewall in a Small Business Environment using Group Policy Introduction This document explains how to configure the features of Windows Firewall on computers

More information

XStream Remote Control: Configuring DCOM Connectivity

XStream Remote Control: Configuring DCOM Connectivity XStream Remote Control: Configuring DCOM Connectivity APPLICATION BRIEF March 2009 Summary The application running the graphical user interface of LeCroy Windows-based oscilloscopes is a COM Automation

More information

Step by step guide for installing highly available System Centre 2012 Virtual Machine Manager Management server:

Step by step guide for installing highly available System Centre 2012 Virtual Machine Manager Management server: Step by step guide for installing highly available System Centre 2012 Virtual Machine Manager Management server: Here are the pre-requisites for a HA VMM server installation: 1. Failover clustering feature

More information

TSM for Windows Installation Instructions: Download the latest TSM Client Using the following link:

TSM for Windows Installation Instructions: Download the latest TSM Client Using the following link: TSM for Windows Installation Instructions: Download the latest TSM Client Using the following link: ftp://ftp.software.ibm.com/storage/tivoli-storagemanagement/maintenance/client/v6r2/windows/x32/v623/

More information

Virtual CD v10. Network Management Server Manual. H+H Software GmbH

Virtual CD v10. Network Management Server Manual. H+H Software GmbH Virtual CD v10 Network Management Server Manual H+H Software GmbH Table of Contents Table of Contents Introduction 1 Legal Notices... 2 What Virtual CD NMS can do for you... 3 New Features in Virtual

More information

Installation Guide. . All right reserved. For more information about Specops Deploy and other Specops products, visit www.specopssoft.

Installation Guide. . All right reserved. For more information about Specops Deploy and other Specops products, visit www.specopssoft. . All right reserved. For more information about Specops Deploy and other Specops products, visit www.specopssoft.com Copyright and Trademarks Specops Deploy is a trademark owned by Specops Software. All

More information

PC Power Down. MSI Deployment Guide

PC Power Down. MSI Deployment Guide PC Power Down MSI Deployment Guide 1. Introduction 1.1. Outline The client software for PC Power Down can be pushed out across a network, saving the effort of individually visiting each computer to install

More information

WhatsUp Gold v16.2 Installation and Configuration Guide

WhatsUp Gold v16.2 Installation and Configuration Guide WhatsUp Gold v16.2 Installation and Configuration Guide Contents Installing and Configuring Ipswitch WhatsUp Gold v16.2 using WhatsUp Setup Installing WhatsUp Gold using WhatsUp Setup... 1 Security guidelines

More information

How to monitor AD security with MOM

How to monitor AD security with MOM How to monitor AD security with MOM A article about monitor Active Directory security with Microsoft Operations Manager 2005 Anders Bengtsson, MCSE http://www.momresources.org November 2006 (1) Table of

More information

ACTIVE DIRECTORY DEPLOYMENT

ACTIVE DIRECTORY DEPLOYMENT ACTIVE DIRECTORY DEPLOYMENT CASAS Technical Support 800.255.1036 2009 Comprehensive Adult Student Assessment Systems. All rights reserved. Version 031809 CONTENTS 1. INTRODUCTION... 1 1.1 LAN PREREQUISITES...

More information

How To Manage Storage With Novell Storage Manager 3.X For Active Directory

How To Manage Storage With Novell Storage Manager 3.X For Active Directory www.novell.com/documentation Installation Guide Novell Storage Manager 4.1 for Active Directory September 10, 2015 Legal Notices Condrey Corporation makes no representations or warranties with respect

More information

In the Active Directory Domain Services Window, click Active Directory Domain Services.

In the Active Directory Domain Services Window, click Active Directory Domain Services. Installing the Active Directory Domain Services Role Press the Ctrl-Alt-Del on the xxrwdc computer. Log in as the default administrator of the local computer with the username Administrator and cisisthebest!

More information

Websense Support Webinar: Questions and Answers

Websense Support Webinar: Questions and Answers Websense Support Webinar: Questions and Answers Configuring Websense Web Security v7 with Your Directory Service Can updating to Native Mode from Active Directory (AD) Mixed Mode affect transparent user

More information

HP OpenView Operations 7.x for Windows. Firewall Configuration white paper. Version 2.2. Publication Date: 08/2003

HP OpenView Operations 7.x for Windows. Firewall Configuration white paper. Version 2.2. Publication Date: 08/2003 HP OpenView Operations 7.x for Windows Firewall Configuration white paper Version 2.2 Publication Date: 08/2003 Warranty Information The information contained in this document is subject to change without

More information

Metalogix SharePoint Backup. Advanced Installation Guide. Publication Date: August 24, 2015

Metalogix SharePoint Backup. Advanced Installation Guide. Publication Date: August 24, 2015 Metalogix SharePoint Backup Publication Date: August 24, 2015 All Rights Reserved. This software is protected by copyright law and international treaties. Unauthorized reproduction or distribution of this

More information

User Migration Tool. Note. Staging Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted Release 9.0(1) 1

User Migration Tool. Note. Staging Guide for Cisco Unified ICM/Contact Center Enterprise & Hosted Release 9.0(1) 1 The (UMT): Is a stand-alone Windows command-line application that performs migration in the granularity of a Unified ICM instance. It migrates only Unified ICM AD user accounts (config/setup and supervisors)

More information

DCOM Setup. User Manual

DCOM Setup. User Manual DCOM Setup User Manual Contents Introduction... 2 Host Computer DCOM Setup... 3 Operation System Windows XP... 3 Setting up DCOM Properties under Windows XP... 3 Setting up Enhanced DCOM Properties under

More information

IBM Security QRadar Version 7.1.0 (MR1) WinCollect User Guide

IBM Security QRadar Version 7.1.0 (MR1) WinCollect User Guide IBM Security QRadar Version 7.1.0 (MR1) WinCollect User Guide Note: Before using this information and the product that it supports, read the information in Notices and Trademarks on page 59. Copyright

More information

Installing Active Directory

Installing Active Directory Installing Active Directory 119 Installing Active Directory Installing Active Directory is an easy and straightforward process as long as you planned adequately and made the necessary decisions beforehand.

More information

Diamond II v2.3 Service Pack 4 Installation Manual

Diamond II v2.3 Service Pack 4 Installation Manual Diamond II v2.3 Service Pack 4 Installation Manual P/N 460987001B ISS 26APR11 Copyright Disclaimer Trademarks and patents Intended use Software license agreement FCC compliance Certification and compliance

More information

How to Enable LDAP Directory Services Authentication to Microsoft Active Directory in the HP cclass Onboard Administrator

How to Enable LDAP Directory Services Authentication to Microsoft Active Directory in the HP cclass Onboard Administrator How to Enable LDAP Directory Services Authentication to Microsoft Active Directory in the HP cclass Onboard Administrator I. Certificate Services a. Install a Certificate Authority onto a Windows server

More information

Installing Kaspersky Security Center 10.0 on Microsoft Windows Server 2012 Core Mode

Installing Kaspersky Security Center 10.0 on Microsoft Windows Server 2012 Core Mode Installing Kaspersky Security Center 10.0 on Microsoft Windows Server 2012 Core Mode Version Date Editor Comments 1.0 17 th January 2012 Pavel Polyansky Initial version. Introduction Server Core is a minimal

More information

2. Using Notepad, create a file called c:\demote.txt containing the following information:

2. Using Notepad, create a file called c:\demote.txt containing the following information: Unit 4 Additional Projects Configuring the Local Computer Policy You need to prepare your test lab for your upcoming experiments. First, remove a child domain that you have configured. Then, configure

More information

Installation Guide for Pulse on Windows Server 2008R2

Installation Guide for Pulse on Windows Server 2008R2 MadCap Software Installation Guide for Pulse on Windows Server 2008R2 Pulse Copyright 2014 MadCap Software. All rights reserved. Information in this document is subject to change without notice. The software

More information

SpamTitan Outlook Addin V2.0

SpamTitan Outlook Addin V2.0 SpamTitan Outlook Addin V2.0 The SpamTitan Outlook Addin v2.0 allows users to do a varity of spam filtering management from the outlook client, including Report Spam and Ham messages to the SpamTitan Bayesian

More information

RSA Security Analytics

RSA Security Analytics RSA Security Analytics Event Source Log Configuration Guide Microsoft Windows using Eventing Collection Last Modified: Thursday, July 30, 2015 Event Source Product Information: Vendor: Microsoft Event

More information

NNAS-D5 Quick Installation Guide

NNAS-D5 Quick Installation Guide NNAS-D5 Quick Installation Guide NOTE: By default, LAN0 (eth0) is set to DHCP. If a DHCP server is available or detected, LAN0 will be assigned a DHCP IP address. If a DHCP server is not available, LAN0

More information

Deploying System Center 2012 R2 Configuration Manager

Deploying System Center 2012 R2 Configuration Manager Deploying System Center 2012 R2 Configuration Manager This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, AS TO THE INFORMATION IN THIS DOCUMENT.

More information

Installing, Uninstalling, and Upgrading Service Monitor

Installing, Uninstalling, and Upgrading Service Monitor CHAPTER 2 Installing, Uninstalling, and Upgrading Service Monitor This section contains the following topics: Preparing to Install Service Monitor, page 2-1 Installing Cisco Unified Service Monitor, page

More information

Installing and Trouble-Shooting SmartSystems

Installing and Trouble-Shooting SmartSystems Installing and Trouble-Shooting SmartSystems Requirements: Processor: 2 GHz is recommended for optimum performance Memory/RAM: 2GB is required Disk space: 60MB is required for SmartSystems Server Operating

More information

Outpost Network Security

Outpost Network Security Administrator Guide Reference Outpost Network Security Office Firewall Software from Agnitum Abstract This document provides information on deploying Outpost Network Security in a corporate network. It

More information

Citrix Access Gateway Plug-in for Windows User Guide

Citrix Access Gateway Plug-in for Windows User Guide Citrix Access Gateway Plug-in for Windows User Guide Access Gateway 9.2, Enterprise Edition Copyright and Trademark Notice Use of the product documented in this guide is subject to your prior acceptance

More information

safend a w a v e s y s t e m s c o m p a n y

safend a w a v e s y s t e m s c o m p a n y safend a w a v e s y s t e m s c o m p a n y SAFEND Data Protection Suite Installation Guide Version 3.4.5 Important Notice This guide is delivered subject to the following conditions and restrictions:

More information

Installation Guide for Pulse on Windows Server 2012

Installation Guide for Pulse on Windows Server 2012 MadCap Software Installation Guide for Pulse on Windows Server 2012 Pulse Copyright 2014 MadCap Software. All rights reserved. Information in this document is subject to change without notice. The software

More information

Administration Guide. . All right reserved. For more information about Specops Deploy and other Specops products, visit www.specopssoft.

Administration Guide. . All right reserved. For more information about Specops Deploy and other Specops products, visit www.specopssoft. . All right reserved. For more information about Specops Deploy and other Specops products, visit www.specopssoft.com Copyright and Trademarks Specops Deploy is a trademark owned by Specops Software. All

More information

DCA Local Print Agent Push Install

DCA Local Print Agent Push Install DCA Local Print Agent Push Install PageTrac Support DCA Local Print Agent Push Install System Requirements Each workstation on which you install Local Print Agent must have the following: Windows operating

More information

Create, Link, or Edit a GPO with Active Directory Users and Computers

Create, Link, or Edit a GPO with Active Directory Users and Computers How to Edit Local Computer Policy Settings To edit the local computer policy settings, you must be a local computer administrator or a member of the Domain Admins or Enterprise Admins groups. 1. Add the

More information

Aspera Connect User Guide

Aspera Connect User Guide Aspera Connect User Guide Windows XP/2003/Vista/2008/7 Browser: Firefox 2+, IE 6+ Version 2.3.1 Chapter 1 Chapter 2 Introduction Setting Up 2.1 Installation 2.2 Configure the Network Environment 2.3 Connect

More information

Pcounter Web Report 3.x Installation Guide - v2014-11-30. Pcounter Web Report Installation Guide Version 3.4

Pcounter Web Report 3.x Installation Guide - v2014-11-30. Pcounter Web Report Installation Guide Version 3.4 Pcounter Web Report 3.x Installation Guide - v2014-11-30 Pcounter Web Report Installation Guide Version 3.4 Table of Contents Table of Contents... 2 Installation Overview... 3 Installation Prerequisites

More information

Oracle Enterprise Manager. Description. Versions Supported

Oracle Enterprise Manager. Description. Versions Supported Oracle Enterprise Manager System Monitoring Plug-in Installation Guide for Microsoft SQL Server Release 12 (4.1.3.2.0) E18740-01 November 2010 This document provides a brief description about the Oracle

More information

SOS Suite Installation Guide

SOS Suite Installation Guide SOS Suite Installation Guide rev. 8/31/2010 Contents Overview Upgrading from SOS 2009 and Older Pre-Installation Recommendations Network Installations System Requirements Preparing for Installation Installing

More information

Nagios XI Monitoring Windows Using WMI

Nagios XI Monitoring Windows Using WMI Purpose The Industry Standard in IT Infrastructure Monitoring This document describes how to monitor Windows machines with Nagios XI using WMI. WMI (Windows Management Instrumentation) allows for agentless

More information

Test Note Phone Manager Deployment Windows Group Policy Sever 2003 and XP SPII Clients

Test Note Phone Manager Deployment Windows Group Policy Sever 2003 and XP SPII Clients Test Note Phone Manager Deployment Windows Group Policy Sever 2003 and XP SPII Clients Note: I have only tested these procedures on Server 2003 SP1 (DC) and XP SPII client, in a controlled lab environment,

More information

HP OpenView Internet Services. SNMP Integration with HP Operations Manager for Windows White Paper

HP OpenView Internet Services. SNMP Integration with HP Operations Manager for Windows White Paper HP OpenView Internet Services SNMP Integration with HP Operations Manager for Windows White Paper Version: 1.00 Overview... 2 Prerequisites... 2 For HPOM Management Server... 2 For OVIS... 2 Configuration...

More information

nappliance misa Server 2006 Standard Edition Users Guide For use with misa Appliances 2006 nappliance Networks, Inc.

nappliance misa Server 2006 Standard Edition Users Guide For use with misa Appliances 2006 nappliance Networks, Inc. nappliance misa Server 2006 Standard Edition Users Guide For use with misa Appliances The information contained in this document represents the current view of Microsoft Corporation on the issues discussed

More information

How To Upgrade A Websense Log Server On A Windows 7.6 On A Powerbook (Windows) On A Thumbdrive Or Ipad (Windows 7.5) On An Ubuntu 7.3.2 (Windows 8) Or Windows

How To Upgrade A Websense Log Server On A Windows 7.6 On A Powerbook (Windows) On A Thumbdrive Or Ipad (Windows 7.5) On An Ubuntu 7.3.2 (Windows 8) Or Windows Websense v7.6 Install or Upgrade Checklist Greetings from Websense Technical Support. Most Websense upgrades complete successfully, and from my years of troubleshooting, I have learned a number of steps

More information

TrueEdit Remote Connection Brief

TrueEdit Remote Connection Brief MicroPress Server Configuration Guide for Remote Applications Date Issued: February 3, 2009 Document Number: 45082597 TrueEdit Remote Connection Brief Background TrueEdit Remote (TER) is actually the same

More information

Backup and Restore the HPOM for Windows 8.16 Management Server

Backup and Restore the HPOM for Windows 8.16 Management Server Backup and Restore the HPOM for Windows 8.16 Management Server White Paper version 2.0 Backup and Restore the HPOM for Windows 8.16 Management Server... 1 Change record... 2 Conceptual Overview... 3 Understanding

More information

NETWRIX ACCOUNT LOCKOUT EXAMINER

NETWRIX ACCOUNT LOCKOUT EXAMINER NETWRIX ACCOUNT LOCKOUT EXAMINER ADMINISTRATOR S GUIDE Product Version: 4.1 July 2014. Legal Notice The information in this publication is furnished for information use only, and does not constitute a

More information

LifeCyclePlus Version 1

LifeCyclePlus Version 1 LifeCyclePlus Version 1 Last updated: 2014-04-25 Information in this document is subject to change without notice. Companies, names and data used in examples herein are fictitious unless otherwise noted.

More information

Active Directory Infrastructure Design Document

Active Directory Infrastructure Design Document Active Directory Infrastructure Design Document Written By Sainath KEV Microsoft MVP Directory Services Microsoft Author TechNet Magazine, Microsoft Operations Framework Microsoft Speaker - Singapore Document

More information

Rebasoft Auditor Quick Start Guide

Rebasoft Auditor Quick Start Guide Copyright Rebasoft Limited: 2009-2011 1 Release 2.1, Rev. 1 Copyright Notice Copyright 2009-2011 Rebasoft Ltd. All rights reserved. REBASOFT Software, the Rebasoft logo, Rebasoft Auditor are registered

More information

Dell SupportAssist Version 2.0 for Dell OpenManage Essentials Quick Start Guide

Dell SupportAssist Version 2.0 for Dell OpenManage Essentials Quick Start Guide Dell SupportAssist Version 2.0 for Dell OpenManage Essentials Quick Start Guide Notes, Cautions, and Warnings NOTE: A NOTE indicates important information that helps you make better use of your computer.

More information

OUTLOOK ADDIN V1.5 ABOUT THE ADDIN

OUTLOOK ADDIN V1.5 ABOUT THE ADDIN OUTLOOK ADDIN V1.5 ABOUT THE ADDIN The SpamTitan Outlook Addin v1.5 allows reporting of SPAM and HAM messages to the SpamTitan appliance, these messages are then examined by the SpamTitan Bayesian filter

More information

IBM WebSphere Application Server Version 7.0

IBM WebSphere Application Server Version 7.0 IBM WebSphere Application Server Version 7.0 Centralized Installation Manager for IBM WebSphere Application Server Network Deployment Version 7.0 Note: Before using this information, be sure to read the

More information

Networking Best Practices Guide. Version 6.5

Networking Best Practices Guide. Version 6.5 Networking Best Practices Guide Version 6.5 Summer 2010 Copyright: 2010, CCH, a Wolters Kluwer business. All rights reserved. Material in this publication may not be reproduced or transmitted in any form

More information

Use of Commercial Backup Software with Juris (Juris 2.x w/msde)

Use of Commercial Backup Software with Juris (Juris 2.x w/msde) Use of Commercial Backup Software with Juris (Juris 2.x w/msde) Juris databases hosted on a Microsoft SQL Server 2000 Desktop Engine (MSDE) instance can be backed up manually through the Juris Management

More information

Moldplus Server Installation Guide Version 3.10 Revision date: February 05, 2006

Moldplus Server Installation Guide Version 3.10 Revision date: February 05, 2006 Moldplus Server Installation Guide Version 3.10 Revision date: February 05, 2006 INTRODUCTION... 2 PRODUCTS SUPPORTED BY MOLDPLUS SERVER V3.10... 3 WHAT S NEW IN VERSION 3.10... 4 CUSTOMER REQUIREMENTS:...

More information

Migrating Exchange Server to Office 365

Migrating Exchange Server to Office 365 Migrating Exchange Server to Office 365 By: Brien M. Posey CONTENTS Domain Verification... 3 IMAP Migration... 4 Cut Over and Staged Migration Prep Work... 5 Cut Over Migrations... 6 Staged Migration...

More information

Oracle Enterprise Manager. Description. Versions Supported

Oracle Enterprise Manager. Description. Versions Supported Oracle Enterprise Manager System Monitoring Plug-in Installation Guide for Microsoft SQL Server Release 10 (4.0.3.1.0) E14811-03 June 2009 This document provides a brief description about the Oracle System

More information

Setup Guide Revision A. WDS Connector

Setup Guide Revision A. WDS Connector Setup Guide Revision A WDS Connector COPYRIGHT Copyright 2013 McAfee, Inc. Do not copy without permission. TRADEMARK ATTRIBUTIONS McAfee, the McAfee logo, McAfee Active Protection, McAfee CleanBoot, McAfee

More information

NETASQ SSO Agent Installation and deployment

NETASQ SSO Agent Installation and deployment NETASQ SSO Agent Installation and deployment Document version: 1.3 Reference: naentno_sso_agent Page 1 / 20 Copyright NETASQ 2013 General information 3 Principle 3 Requirements 3 Active Directory user

More information

Managing an Active Directory Infrastructure

Managing an Active Directory Infrastructure 3 CHAPTER 3 Managing an Active Directory Infrastructure Objectives This chapter covers the following Microsoft-specified objectives for the Planning and Implementing an Active Directory Infrastructure

More information

Setting Up SSL on IIS6 for MEGA Advisor

Setting Up SSL on IIS6 for MEGA Advisor Setting Up SSL on IIS6 for MEGA Advisor Revised: July 5, 2012 Created: February 1, 2008 Author: Melinda BODROGI CONTENTS Contents... 2 Principle... 3 Requirements... 4 Install the certification authority

More information

Burst Technology bt-loganalyzer SE

Burst Technology bt-loganalyzer SE Burst Technology bt-loganalyzer SE Burst Technology Inc. 9240 Bonita Beach Rd, Bonita Springs, FL 34135 CONTENTS WELCOME... 3 1 SOFTWARE AND HARDWARE REQUIREMENTS... 3 2 SQL DESIGN... 3 3 INSTALLING BT-LOGANALYZER...

More information

HPOM 8.1 High Availability Utilizing Microsoft SQL Server Log Shipping

HPOM 8.1 High Availability Utilizing Microsoft SQL Server Log Shipping HPOM 8.1 High Availability Utilizing Microsoft SQL Server Log Shipping White Paper version 2.4 HPOM 8.1 High Availability Utilizing Microsoft SQL Server Log Shipping... 1 Change record... 3 Architectural

More information

SharePoint Server for Business Intelligence

SharePoint Server for Business Intelligence SharePoint Server for Business Intelligence SharePoint Business Intelligence Content Team Summary: Step-by-step, learn how to install and configure SharePoint Server 2010 and SQL Server 2008 to create

More information

OPC Server Machine Configuration

OPC Server Machine Configuration OPC Server Machine Configuration General Information For remote OPC Server operation, server must be running under Windows XP Pro, Windows Server 2003, Windows Vista (Business & Ultimate), Windows 7 (Professional

More information

Installation of MicroSoft Active Directory

Installation of MicroSoft Active Directory Installation of MicroSoft Active Directory Before you start following this article you must be aware this is simply a lab setup and you need to assign relevant ip address, hostnames & domain names which

More information

Application Server Installation

Application Server Installation Application Server Installation Guide ARGUS Enterprise 11.0 11/25/2015 ARGUS Software An Altus Group Company Application Server Installation ARGUS Enterprise Version 11.0 11/25/2015 Published by: ARGUS

More information

Using RADIUS Agent for Transparent User Identification

Using RADIUS Agent for Transparent User Identification Using RADIUS Agent for Transparent User Identification Using RADIUS Agent Web Security Solutions Version 7.7, 7.8 Websense RADIUS Agent works together with the RADIUS server and RADIUS clients in your

More information

SQL Server Hardening

SQL Server Hardening Considerations, page 1 SQL Server 2008 R2 Security Considerations, page 4 Considerations Top SQL Hardening Considerations Top SQL Hardening considerations: 1 Do not install SQL Server on an Active Directory

More information

Windows Server 2008 R2 Initial Configuration Tasks

Windows Server 2008 R2 Initial Configuration Tasks Windows Server 2008 R2 Initial Configuration Tasks I am not responsible for your actions or their outcomes, in any way, while reading and/or implementing this tutorial. I will not provide support for the

More information

Introduction to DirectAccess in Windows Server 2012

Introduction to DirectAccess in Windows Server 2012 Introduction to DirectAccess in Windows Server 2012 Windows Server 2012 Hands-on lab In this lab, you will configure a Windows 8 workgroup client to access the corporate network using DirectAccess technology,

More information

Connection and Printer Setup Guide

Connection and Printer Setup Guide Connection and Printer Setup Guide For connection issues, see the following sections of this document: "Connection Requirements" on page 1 "Log on" on page 2 "Troubleshooting Your Connection" on page 4

More information

Active Directory Restoration

Active Directory Restoration Active Directory Restoration This document outlines the steps required to recover an Active Directory Infrastructure, running on Windows 2003 R2 Server Standard. The scope of this document covers the scenario

More information