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

Limitations, SMCBoot, Network Devices

Page 64 highlights

Limitations Note: Some users may need to press the Alt key to display this menu. 7. In the Connections box, move the Local Area Connection entry that has an IP address of 172.30.0.2 to the bottom of the list, if it is not on the bottom of the Connections list already. 8. Shut down and restart your system. v Hibernation over LAN is not supported. v After updating the BIOS to the latest version on an ThinkCentre M57p eco client, the SMCBoot option is not available in Network Devices. In this case, the ThinkCentre M57p eco client was probably purchased before Secure Managed Client development began. The NIC firmware in this system needs to be updated to support the iSCSI boot that Secure Managed Client requires. Please refer to the Secure Managed Client support Web site for more information about downloading this utility. v The SMCWinPE CD is only meant to copy service partition data to the normal bootable drive. v Using the SMC WinPE CD, the Lenovo Service Partition is not copied to the user's image on the storage array. The Secure Managed Client WinPE CD was only designed to copy a single user partition, not an entire hard drive. To copy the service partition, do the following: 1. Clean the image on the storage array. 2. Create the service partition on LUN [ diskpart -> create partition primary size=6131 ]. 3. Create the system partition on LUN [ diskpart -> create partition primary ]. 4. Set system partition as active. 5. Copy the service partition from the local HDD to the LUN. 6. Copy the system partition from the local HDD to the LUN. 7. Remove the local hard disk drive. 8. Set the service partition label to SERVICEV002. 9. Hide the service partition [ set id=27 ]. 10. Set the system partition label to SW_Preload. 11. Boot to the desktop and uninstall Rescue and Recovery. 12. Reinstall Rescue and Recovery. v Recovery CDs booted on a client with a physical hard disk drive will restore to the physical hard disk drive instead of the image on the storage array. Recovery CDs always restore to Disk 0. With a physical hard disk drive in the system, that drive is Disk 0 and the storage array drive is Disk 1. Remove the local physical hard disk drive before using a set of preload recovery CDs. v Secure Managed Client does not fix any problems cloning Microsoft images. Any issues or problems cloning Windows images will still be present when cloning with Secure Managed Client. v The Windows system clock will delay about 3 seconds within 24 hours over a normal workload. The Secure Managed Client boot manager uses system clock cycles and may delay the Windows system clock with higher workloads. Use the automatic feature of Windows to sync the clock to an internet time server. v Remote Assistance may not be able to connect to the desired system. The client uses two NICs in Windows. One is for communication on the regular network and one is for communication to the Secure Managed Client boot manager. 56 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

Note:
Some users may need to press the
Alt
key to display this menu.
7.
In the Connections box, move the Local Area Connection entry that has an IP
address of 172.30.0.2 to the bottom of the list, if it is not on the bottom of the
Connections list already.
8.
Shut down and restart your system.
Limitations
v
Hibernation over LAN is not supported.
v
After updating the BIOS to the latest version on an ThinkCentre M57p eco client,
the
SMCBoot
option is not available in
Network Devices
. In this case, the
ThinkCentre M57p eco client was probably purchased before Secure Managed
Client development began. The NIC firmware in this system needs to be
updated to support the iSCSI boot that Secure Managed Client requires. Please
refer to the Secure Managed Client support Web site for more information about
downloading this utility.
v
The SMCWinPE CD is only meant to copy service partition data to the normal
bootable drive.
v
Using the SMC WinPE CD, the Lenovo Service Partition is not copied to the
user’s image on the storage array. The Secure Managed Client WinPE CD was
only designed to copy a single user partition, not an entire hard drive. To copy
the service partition, do the following:
1.
Clean the image on the storage array.
2.
Create the service partition on LUN [ diskpart -> create partition primary
size=6131 ].
3.
Create the system partition on LUN [ diskpart -> create partition primary ].
4.
Set system partition as active.
5.
Copy the service partition from the local HDD to the LUN.
6.
Copy the system partition from the local HDD to the LUN.
7.
Remove the local hard disk drive.
8.
Set the service partition label to SERVICEV002.
9.
Hide the service partition [ set id=27 ].
10.
Set the system partition label to SW_Preload.
11.
Boot to the desktop and uninstall Rescue and Recovery.
12.
Reinstall Rescue and Recovery.
v
Recovery CDs booted on a client with a physical hard disk drive will restore to
the physical hard disk drive instead of the image on the storage array. Recovery
CDs always restore to Disk 0. With a physical hard disk drive in the system, that
drive is Disk 0 and the storage array drive is Disk 1. Remove the local physical
hard disk drive before using a set of preload recovery CDs.
v
Secure Managed Client does not fix any problems cloning Microsoft images. Any
issues or problems cloning Windows images will still be present when cloning
with Secure Managed Client.
v
The Windows system clock will delay about 3 seconds within 24 hours over a
normal workload. The Secure Managed Client boot manager uses system clock
cycles and may delay the Windows system clock with higher workloads. Use the
automatic feature of Windows to sync the clock to an internet time server.
v
Remote Assistance may not be able to connect to the desired system. The client
uses two NICs in Windows. One is for communication on the regular network
and one is for communication to the Secure Managed Client boot manager.
56
Secure Managed Client Version 2.0 Deployment Guide