Lenovo Secure Managed Client (English) Secure Managed Client Deployment Guide - Page 26

Off-core connection manager, Image types, Standard image, Single image

Get Lenovo Secure Managed Client PDF manuals and user guides View all Lenovo Secure Managed Client manuals
Add to My Manuals
Save this manual to your list of manuals

Page 26 highlights

e. Click Apply. The Update storage array license window opens. Follow the directions in the window to finish updating. Off-core connection manager In order to provide redundant Secure Managed Client ULOS (User Log On Screen) authentication capability in case the main LANDesk server is offline, an off-core connection manager can be configured. This Windows Server 2003 system must be joined to the same domain as the LANDesk server and accessible by all SMC clients. Once configured, this system will provide backup authentication for SMC users attempting to login to the ULOS on SMC clients. To install: 1. Double-click on Autorun.exe from the SMC 2.0 installation directory. 2. Click Install SMC Connection Manager. 3. After the prerequisite checker runs, click Install now. If the prerequisite checker fails, see "Prerequisites" on page 13 for assistance on installing necessary components. 4. Click Next and then Install. 5. In the Install SMC Certificate window, enter the IP address or DNS name of the LANDesk server, the location of the PKCS#12 certificate file generated during the LANDesk server installation, and the password for the certificate file. The name of the certificate file should be ldms4smc.p12. 6. Click Install and then OK when the certificate installation is complete. Click Finish. 7. Close the LANDesk prerequisite checker window. To configure the off-core connection manager: 1. From the SMC Manager in the SMC Management Console on the main LANDesk server, right-click on a storage array and select Properties. 2. In the left pane select Connection manager. The name of the computer you just installed the Off-core Connection Manager on should appear in the Available connection managers list in the right pane. 3. Highlight the computer name and click Add. The computer name will move to the Connection managers in use by this storage array list. 4. Click Save to activate your changes. Image types There are three types of images used in Secure Managed Client 2.0. Here is a discussion of each. Standard image A standard image is a Secure Managed Client image type that is a full copy of the base image for each user. See "Creating a single image base image" on page 19 for information on creating base and user standard images. Single image A single image is an image type where the user's data is stored as a thin provisioned addition to the common single base image. This image type provides space saving advantages because the common data for each user is not duplicated on the storage array. This common data storage also provides some measure of increased performance at SMC client boot time. 18 Secure Managed Client Version 2.0 Deployment Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
e.
Click
Apply
. The Update storage array license window opens. Follow the
directions in the window to finish updating.
Off-core connection manager
In order to provide redundant Secure Managed Client ULOS (User Log On Screen)
authentication capability in case the main LANDesk server is offline, an off-core
connection manager can be configured. This Windows Server 2003 system must be
joined to the same domain as the LANDesk server and accessible by all SMC
clients. Once configured, this system will provide backup authentication for SMC
users attempting to login to the ULOS on SMC clients.
To install:
1.
Double-click on Autorun.exe from the SMC 2.0 installation directory.
2.
Click
Install SMC Connection Manager
.
3.
After the prerequisite checker runs, click
Install now
. If the prerequisite checker
fails, see “Prerequisites” on page 13 for assistance on installing necessary
components.
4.
Click
Next
and then
Install
.
5.
In the Install SMC Certificate window, enter the IP address or DNS name of the
LANDesk server, the location of the PKCS#12 certificate file generated during
the LANDesk server installation, and the password for the certificate file. The
name of the certificate file should be ldms4smc.p12.
6.
Click
Install
and then
OK
when the certificate installation is complete. Click
Finish
.
7.
Close the LANDesk prerequisite checker window.
To configure the off-core connection manager:
1.
From the SMC Manager in the SMC Management Console on the main
LANDesk server, right-click on a storage array and select
Properties
.
2.
In the left pane select
Connection manager
. The name of the computer you just
installed the Off-core Connection Manager on should appear in the Available
connection managers list in the right pane.
3.
Highlight the computer name and click
Add
. The computer name will move to
the Connection managers in use by this storage array list.
4.
Click
Save
to activate your changes.
Image types
There are three types of images used in Secure Managed Client 2.0. Here is a
discussion of each.
Standard image
A standard image is a Secure Managed Client image type that is a full copy of the
base image for each user. See “Creating a single image base image” on page 19 for
information on creating base and user standard images.
Single image
A single image is an image type where the user’s data is stored as a thin
provisioned addition to the common single base image. This image type provides
space saving advantages because the common data for each user is not duplicated
on the storage array. This common data storage also provides some measure of
increased performance at SMC client boot time.
18
Secure Managed Client Version 2.0 Deployment Guide