Diskless client architecture, Active directory considerations – Lenovo Secure Managed Client User Manual

Page 14

Advertising
background image

Diskless client architecture

The following is an overview of the Secure Managed Client boot sequence:

v

The physical hardware is connected to the storage array and LANDesk
Management Suite (LDMS). There is no local disk storage. The boot manager
boots from a common boot image over iSCSI using the iSCSI services built into
the physical NIC.

v

The user logs on to the boot manager. The LDMS server validates the user and
finds the image on the storage array.

v

The user operating system is booted and any local hardware, depending on the
policy, is given to Windows. For example, the policy could limit access to the
local CD ROM or USB ports.

Active Directory considerations

Active Directory allows you to assign policies and deploy software and updates to
individual clients in an organization. You can utilize current Active Directory
settings in their environment if the Secure Managed Client infrastructure is
properly connected to the existing network topology.

You can make changes to the Active Directory settings based on the Secure
Managed Client image or images. Some settings might have a performance impact
based on how the image was deployed to the clients. You can create an isolated
test infrastructure to determine if there are any conflicts. Consider the following:

v

The LANDesk Secure Managed Client Console cannot be installed on the Active
Directory server for the domain.

v

The LANDesk server and the user logged on to that server must be joined to the
domain to be able to create Secure Managed Client users from that domain.

v

Only users in the domain or forest of the LANDesk server can be created in the
LANDesk Secure Managed Client console. A forest is a collection of every object,
its attributes, and rules in Active Directory

SMC Management

Console

SMC Management

Server

DHCP

Active Directory

Network

Lenovo

SMC Storage Array

Disc traffic goes directly to switches.

This keeps it off the backbone.

20 systems per gigabit
Connection to the
SMC storage array

20 systems per gigabit
Connection to the
SMC storage array

20 systems per gigabit

Connection to the

SMC storage array

Gigabit Switch

Gigabit Switch

Corp Network

SMC mgt

SAN HDD traffic

SAN HDD traffic

SAN HDD traffic

SAN HDD traffic

Corp Network

Figure 1. Secure Managed Client design

6

Secure Managed Client Version 2.0 Deployment Guide

Advertising