Home » Lenovo Manuals » Servers » Lenovo Secure Managed Client » Manual Viewer

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

Management Core Server IP address has changed, Provisioning fails, No user image, LANDesk logs

View all Lenovo Secure Managed Client manuals

Add to My Manuals
Save this manual to your list of manuals

Page 62 highlights

4. When the authentication is verified, browse to tcm\dist\\SMCBoot.img and select Update. It will take a few minutes to load, but all the information should be up-to-date, and the clients should be able to boot. Management Core Server IP address has changed If the core server has been moved and the DHCP IP address for that server has changed, do the following to fix it. 1. Reset the IP to original IP address (set static) 2. Reboot the core to cause another inventory scan so that the inventory is synchronized. If you do not want to reboot, enter this from the command line: \\ManagementSuite\ldlogon\ldiscn32 /ntt= NATIONWI-IX4CN8 /s= NATIONWI-IX4CN8 /sync /v Provisioning fails When provisioning fails, check the following: v If LANDesk was attempted to be installed multiple times on the server, check that the certificate in c:\Program Files\LANDesk\Shared Files\certs folder and ensure it matches with the protect.ini file. v Make sure that pinging occurs from the Secure Managed Client Storage Array to the Secure Managed Client Management Console Server and from the Management Console Server back to the storage array. The problem could be the firewall on the core server. Check this: C:\program files\landesk\shared files\keys\Protect.ini. No user image If the user creation operation appears to complete successfully and produces a user entry in the users branch of the storage array but no image is created for that user, there is a lack space on the storage array for that image. LANDesk logs When troubleshooting Secure Managed Client problems, there are two LANDesk logs and two Web sites that you can use for troubleshooting: 1. Program Files/LANDesk/Management Suite/console.exe.log. 2. Program Files/LANDesk/Management Suite/logs/san_portal.log . 3. https://localhost/connectionmanager/connectionmgr.asmx. 4. https://localhost/san_portal/sanportal.asmx. Unique network failure points Table 5. Network failure points Symptom Possible reason Client system crashes, lockups Windows driver/app Switch failure Storage array failure Bad Ethernet cable Impact One to a few clients report crashes All systems on switch are affected All clients on storage array affected System attached to cable effected 54 Secure Managed Client Version 2.0 Deployment Guide

Section	Page
Preface	5
Contents	7
Chapter 1. Overview	9
Chapter 2. General setup	11
Networking	11
Installing and configuring LANDesk	11
Provisioning the storage array	11
Building a base image	11
Creating user images	11
Selecting the type of image you wish to use	11
Chapter 3. Networking considerations	13
Infrastructure requirements	13
Diskless client architecture	14
Active Directory considerations	14
iSCSI boot	15
Capacity	15
Link aggregation (Bonding)	15
Packet loss	16
Network topology	16
Chapter 4. Secure Managed Client specific installation	17
Prerequisites	17
Secure Managed Client manual setup	18
Secure Managed Client switches	19
Secure Managed Client - Storage Array setup	19
Secure Managed Client management core installation	20
Secure Managed Client Storage Array provisioning	20
Chapter 5. LANDesk Information	21
Secure Managed Client / LANDesk setup	21
Retrieving the Secure Managed Client Console	21
Prerequisites	21
Internet packages	21
Internet Information Services (IIS) configuration	21
Secure Managed Client server	22
Installing LANDesk	22
Upgrading from Secure Managed Client version 1.2 to 2.0	22
Installing the LANDesk Service Pack and the SMC 2.0 Management Console	22
Updating the boot image on the Storage Array	23
Configuring the LANDesk Secure Managed Client console	23
Starting LANDesk Management Suite	23
Provisioning the storage array	24
Creating a standard base image	24
Populating a base image	24
Creating a standard image or single image user image	24
License upgrades	25
Off-core connection manager	26
Image types	26
Standard image	26
Single image	26
Creating a single image base image	27
Creating a single image user image	27
Local cache image	27
Creating a local cache base image	27
Enabling SMC clients for local cache	27
Creating local cache user images	27
Deploying local cache on SMC clients	28
Assigned seating	28
Pristine image	29
Chapter 6. Secure Managed Client image creation and tuning	31
Creating Sysprep images	31
Preparing a Windows XP image	31
Cloning an existing Windows XP image	32
Preparing a Windows Vista image	32
Preparing a new Windows Vista image for Secure Managed Client	33
Preparing a Windows Vista preload on a Lenovo M57 with service partition but no separate active system partition for Secure M	34
Preparing regular Windows Vista for Secure Managed Client	36
Redeploying the Lenovo M58p Vista preload image to the Secure Managed Client environment	38
Cloning an existing Windows Vista image	42
Image optimization	42
Scheduled tasks	42
Antivirus	42
Indexing and search utilities	43
Bridge Connections	43
Defragmentation	43
Updates	44
Image protection	44
Application compatibility testing	44
Collecting Windows performance traces (WPT)	44
Identifying slow services and processes	45
Identifying erratic behavior	45
Operating system services	45
Automatic	45
Automatic (delayed)	45
Manual / Disabled	45
Recommendations	46
Windows XP services	46
Windows Vista services	46
ThinkVantage® Technologies	46
Optimize the Sysprep image for best performance	46
Improving Vista performance	47
Roaming user profiles and folder redirection	47
Chapter 7. Populating a base image	49
Using bootable CD/DVD media	49
SMCWinPE.iso	50
Connecting to a target image LUN on an SMC Storage Array using the iSCSI Initiator	50
Copying a multiple partition image to the storage array, version 1.x	51
Copying a multiple partition image to the storage array, Version 2.0	52
Deploying the image directly to the storage array	53
Boot acceleration	54
Hints and tips	54
If not using a Lenovo CD	55
Chapter 8. Setting up network shares	57
Chapter 9. Configuring synchronous and asynchronous replication	59
Prerequisites	59
Creating synchronous replication	59
Creating asynchronous replication	60
Manual failover	60
Chapter 10. Troubleshooting	61
Problems	61
Storage array diagnostics	61
Secure Managed Client will not boot	61
Clients will not boot after moving the Management Console	61
Management Core Server IP address has changed	62
Provisioning fails	62
No user image	62
LANDesk logs	62
Unique network failure points	62
Binding order in the Secure Managed Client environment	63
Changing the binding order for Windows XP	63
Changing the binding order for Windows Vista	63
Limitations	64
Appendix. Notices	67
Trademarks	68

Match case Limit results 1 per page

When the authentication is verified, browse to

tcm\dist\\SMCBoot-

version

>.img

and select

Update

It will take a few minutes to load, but all the information should be up-to-date,

and the clients should be able to boot.

Management Core Server IP address has changed

If the core server has been moved and the DHCP IP address for that server has

changed, do the following to fix it.

Reset the IP to original IP address (set static)

Reboot the core to cause another inventory scan so that the inventory is

synchronized. If you do not want to reboot, enter this from the command line:

path to landesk install

>\ManagementSuite\ldlogon\ldiscn32

/ntt= NATIONWI-IX4CN8

/s= NATIONWI-IX4CN8

/sync

Provisioning fails

When provisioning fails, check the following:

If LANDesk was attempted to be installed multiple times on the server, check

that the certificate in c:\Program Files\LANDesk\Shared Files\certs folder and

ensure it matches with the protect.ini file.

Make sure that pinging occurs from the Secure Managed Client Storage Array to

the Secure Managed Client Management Console Server and from the

Management Console Server back to the storage array. The problem could be the

firewall on the core server. Check this: C:\program files\landesk\shared

files\keys\Protect.ini.

No user image

If the user creation operation appears to complete successfully and produces a user

entry in the users branch of the storage array but no image is created for that user,

there is a lack space on the storage array for that image.

LANDesk logs

When troubleshooting Secure Managed Client problems, there are two LANDesk

logs and two Web sites that you can use for troubleshooting:

Program Files/LANDesk/Management Suite/console.exe.log.

Program Files/LANDesk/Management Suite/logs/san_portal.log .

https://localhost/connectionmanager/connectionmgr.asmx.

https://localhost/san_portal/sanportal.asmx.

Unique network failure points

Table 5. Network failure points

Symptom

Possible reason

Impact

Client system crashes,

lockups

Windows driver/app

Switch failure

Storage array failure

Bad Ethernet cable

One to a few clients report crashes

All systems on switch are affected

All clients on storage array affected

System attached to cable effected

Secure Managed Client Version 2.0 Deployment Guide