Hp Consolidated Client Infrastructure v1.4 Static Configuration

Static Configuration for the HP Consolidated Client Infrastructure (CCI) v1.4

Abstract.............................................................................................................................................. 2

Document Scope ................................................................................................................................. 2

Static model description ....................................................................................................................... 2

Static Topology ................................................................................................................................... 3

Static configuration design considerations .............................................................................................. 5

Basic Static Configuration ................................................................................................................. 5

CCI User-based Configuration options................................................................................................ 6

Hard drive File Access .................................................................................................................. 6

Roaming profile ........................................................................................................................... 7

Folder Redirection ........................................................................................................................ 7

Ability for user to shut down blade PCs ........................................................................................... 7

Session timer values...................................................................................................................... 8

Methods of granting a user remote access to the blade PC................................................................ 8

CCI design considerations .................................................................................................................... 9

CCI static configuration network considerations................................................................................... 9

When to and when NOT to collocate blade PCs in a Data Center ......................................................... 9

Additional Active Directory information .................................................................................................. 9

Using an alias record in DNS............................................................................................................ 9

Using a static IP address ................................................................................................................... 9

Using a dynamic register through DHCP ............................................................................................. 9

Using security groups ....................................................................................................................... 9

For more information.......................................................................................................................... 10

Abstract

This document provides information on design considerations specific for the Static model implementation of the HP Consolidated Client Infrastructure (CCI) Solution. The static configuration is for customers who do not wish to dynamically allocate users to blade PCs. Instead, each user connects directly to a statically assigned blade PC that is dedicated for use by that specific user.

Document Scope

This paper assumes that the reader already has a basic understanding of how CCI works and how it is deployed in a dynamic configuration that allocates clients to blade PCs on-demand. To provide a working example, this document describes a CCI Static implementation with the least amount of user restriction to make the implementation as simple as possible. It will also cover static design options to be considered when customizing the implementation to satisfy the customer’s requirements. This paper provides information on design considerations specific for the Static implementation and is not intended to communicate a baseline static configuration. Each customer site will require customization for each of the CCI configurable items described in the following sections.

Static confguration description

The CCI Static configuration requires each user to be assigned to a specific blade PC. Every time the user logs on, the user connects to their assigned blade PC. The CCI Static configuration does not require use of an allocation engine, which can result in a simplified design and installation of a CCI solution. Though generally simpler to implement, an increase in manual effort is required to manage the user-to-blade PC assignments. As the number of users and blade PCs increase, the management of a static CCI model can be more challenging due to:

• The IT staff having to establish procedures for assigning users to individual blades.

• The possibility of a catastrophic blade PC failure, requiring the user to phone the help desk, report

the issue, and be reassigned to another available blade PC. In contrast, dynamic CCI model users are automatically assigned to different blade PCs in the event of blade failure.

Conversely, the static CCI model offers some design flexibility that is not available in a typical dynamic CCI model.

• Although not recommended, user data files can be stored on the local hard drive of the blade PC. However, without the use of an enterprise data backup solution deployed on each blade PC, end users would be giving up the data protection provided by using network storage and backup processes. IT staff would be giving up the ability to easily manage the blade PC image. The image restore process will have to consider the user’s data files stored on the blade PC.

• A static configuration could offer less-restrictive policies on the blade PC, such as application installation. With the dynamic CCI model, it is not logical to allow users to install software directly to the blade PC because there is no guarantee that the user will connect to the same blade PC in future logins. In a dynamic model, a ‘locked-down’ image ensures fewer calls to the Help Desk asking for assistance in fixing image problems or eradicating viruses. When business requirements make such restrictive policies inappropriate, the static CCI model may be a better option even though many of the cost savings of a dynamic CCI implementation may not be realized.

• The static model can be configured so that the “follow-me roaming” feature is enabled. This means that because each user is assigned to one specific blade PC, the user can move to another access device, log in from there, and take over their active session.

• The static model can be configured to allow the user to disconnect from their blade PC without logging off of their session. They will then be able to reconnect to their session and have access to any open applications and data unchanged from when they disconnected.

Static Topology

Note:

Network Infrastructure Design can and should change to fit into the customers existing network and or business requirements. Figure 1 below depicts an example of a simple network using just one VLAN.

Figure 1. CCI static topology with single VLAN

NIC B

Blade 1

Blade 4

Blade 3

Blade 2

HP PC Blade Enclosure

NIC B

Blade 5

LAN Segment 2

NIC B

Blade 8

Blade 7

Blade 6

NIC B

Blade 10

Blade 9

NIC B

Blade 12

Blade 11

NIC B

Blade 14

Blade 13

NIC B

Blade 16

Blade 15

NIC B

Blade 17

Blade 18

NIC B

Blade 20

Blade 19

(NIC Bs disabled)

NIC A

Thin

Clients

Domain Controller/

DHCP/DNS

Altiris/

HPSIM (RDP)

Generic

Devices

NAS – File Shares

NIC A

LAN Segment 1

NIC A

L2 Switch

NIC A

(NIC A IPs

assigned by DHCP)

WAN

Router

+ 7 hidden pages