Manuals / Brands / Computer Equipment / Desktops / HP / Computer Equipment / Desktops

HP xw2x220c Regionalization of Data Centers, Multiple SQL Databases

1 110

Download 110 pages, 3.8 Mb

If you want to avoid continuing to increase memory and processor cores on the HP SAM Server, create multiple gateway servers and split user populations to limit the number of users using a particular gateway as their primary target. You may also split resources between HP SAM servers to distribute the load between servers.

Regionalization of Data Centers

When placing users in one region and blades in another:

●As population size increases, the HP SAM Server should be local to the blades/resources as opposed to local to the users for the following reasons:

◦Because the database of users has to be pulled across the network to HP SAM Server memory, the WAN could impact performance if this database becomes too large.

◦If the two servers (SQL and HP SAM) are in the same data center, their communication can occur over the high speed backbone with little to no performance impact from the network.

●With relatively small population sizes (fewer than 3,000), you may place the HP SAM Server local to the users as opposed to local to the blades/resources for the following reasons:

◦The database of users being pulled across the network to HP SAM Server is small and impacted very little by the WAN.

◦The local HP SAM Server limits the number of users hitting that server, so the server can be smaller.

Disaster Recovery designs

●Multiple HP SAM servers can be configured so that users and resources will failover to another HP SAM server if a server becomes unreachable. It is recommended that the HP SAM servers be installed in different locations for a greater likelihood that at least one server will remain accessible.

Multiple SQL Databases

Typically, one SQL database should be shared between all HP SAM servers. Only in some situations does it make sense to use more than one distinct SQL database:

●When customers can keep user and resource populations in entirely separate support arenas and users do not need to migrate between them.

●When user populations go beyond 40,000.

●When large user populations log on and off extremely frequently, because this will impact performance for everyone on that SQL database.

Otherwise, you should only have a single SQL database

14 Chapter 2 Requirements

Contents

Page Page About This Book WARNING CAUTION: Page Table of contents 4 Administration Page Page 1 Introduction What's New in This Release Key Features Overview How HP SAM Works Authenticate Before Allocation Page HP SAM Software Components HP SAM Client HP SAM Web Server Common Tasks Page Setting up a User with Static (Dedicated) Resources Connect In Use Configuring a Monitor Layout for a User Page 2 Requirements HP SAM Hardware and Software Requirements Server Sizing SQL Database Considerations Number of HP SAM Servers Regionalization of Data Centers Multiple SQL Databases HP SAM Web Server Hardware Requirements HP SAM Web Server Software Requirements HP SAM SQL Database Server Hardware Requirements Page Page Page HP SAM SQL Database Server Software Requirements HP SAM Registration Service Requirements Access Device Requirements Mobile Thin Client Desktop or Notebook PC Blade Workstation Clients Personal Workstation Clients Other requirements Page 3 Installation Order of Installation Install the HP SAM Web Server and SQL Software HP SAM Web Site HP SAM Database Browse User Name Password Properties ASP.NET ASP.NET version Grant Users HP SAM Administrator Access Configure HP SAM System Settings Install and Validate the HP SAM Registration Service Software Save As Create the HP SAM Registration Service Configuration File C:\Program Files\Hewlett- Packard\HP SAM Registration Service [WebServerList] [RolesList] [AssetGroupList] ServicePort DnsDomain Install and Validate the HP SAM Client Software Internet Explorer-BasedClient HP SAM ActiveX Controls Customization Steps HP Blade Workstation Client Series HP ThinPro GT Client for the HP gt7725 Thin Client Red Hat Enterprise Linux (RHEL) Client Options DefaultPolicy Autodial DefaultUsername DefaultInsecurePassword Debug ConnectionBar.EnableCloseAll Disconnect All ConnectionBar.EnableReconnectAll Reconnect All ConnectionBar.EnableDisconnectInstance Smart Card Settings User Interface Customization Settings EnableServer HP SAM Server EnableDomain KioskMode Bit Policy Entries Themes Animation Caching AutoReconnect MapDrives ClearType ComposedUI Autosize MapClipboard MapDrivesList Global and Local Client Configuration Files Legal Banner Access Device Client: Windows: Workstation Client OS: Linux: Deploy the HP SAM Registration Service to All HP SAM Computing Resources Deploy HP SAM Client Software to All HP SAM Access Devices 4 Administration Log In General Navigation and User Interface Design Managing the HP SAM Administrator Access List Add Security Groups or Organizational Units to the HP SAM Administrator Group a.In Search By, select Organizations (OU) or Security Groups View Remove Users or Groups From the HP SAM Administrator Group Users and Roles HP SAM Administrative Console Tabs Manage Resource Roles Manage Asset Groups Manage Administrative Permissions Manage Users Selected To Assign Resources To Assign Resources Manually 1.Click Manage users Assign Resources Friendly Name Backup Resource Remove To Assign Resources Automatically from Template User To Assign Resources Automatically from Role 5.Select Assign Resources from Role To Assign and Configure a Monitor Layout for the User Assign Monitor Layouts Monitor Layouts for <username Add New Users External Active Directory To Grant Access to Security Groups or Organization Units 2.Set Search By to Organizations (OU) or Security Groups Resources tab Manage Resources Customize View Manage Access Devices Manage Monitor Layout To Create a Data Center To Change a Data Center To Add Enclosures into a Data Center To Delete Enclosures from a Data Center To Delete a Data Center Policies Tab Steps: ●to a role (User and Roles > Manage resource roles) User and Roles > Manage users Create or Update a Policy View Effective Policy General Web Client Active Directory Auto Schedules Licensing Resource Capacity Consumption Report Resource Capacity Consumption Trend Report Resource Utilization Report Total Disabled Log Tab all Security Setting Up Smart Card Logon on the Access Device Configuring Session Time Limits for Remote Sessions Page Session Timers for Linux Resource Reservations (AKA Access Restrictions) Authenticate Before Allocation Authentication before Allocation Allow Expired Password A Firewall Rules Web Server Clients Resources SQL Server B Frequently Asked Questions Page Page Page Page Page C Registration Service Error Codes Page Page D Glossary Registration RDP Roaming profile Session Index