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

Redeploying the Lenovo M58p Vista preload image to the Secure Managed Client environment, Value

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 38 highlights

v Locate your Secure Managed Client VNIF driver files and modify the provided OfflineUnattend.xml file accordingly. v Mount the wim file you created in step 12 on page 29. mkdir C:\wim_mount Imagex /mountrw D:\myimg\Vista32.wim 1 C:\wim_mount v Enable logging. This is optional, but a good practice. - Path: HKLM\Software\Microsoft\Windows\CurrentVersion\Device Installer - Key: DebugPkgMgr - Type: REG_DWORD - Value: 0x01 v Use Package Manager to install the VNIF drivers. Change your current directory to the directory where the pkgmgr.exe file is located. Pkgmgr /o:"C:\wim_mount\;C:\wim_mount\Windows" /n:"C:\tmp\OfflineUnattend.xml" /l:"C:\pkgmgrlogs\logfile.txt" v Check the logfile.txt file make sure there are no errors and a return code of 0. v Review the contents of the %WINDIR%\inf\ directory in the mounted Windows image to make sure that the .inf files were installed. Drivers added to the Windows image are named oem.inf. This is to ensure unique naming for new drivers that were added to the computer. For example, the files MyDriver1.inf and MyDriver2.inf are renamed oem0.inf and oem1.inf. v Now unmount the .wim file and commit the installation. Imagex /unmount /commit C:\wim_mount 14. The .wim file is ready to be restored to your LUN. Run ImageX /apply ... after you mount your LUN. Redeploying the Lenovo M58p Vista preload image to the Secure Managed Client environment When users redeploy the Lenovo M58P Windows Vista preload image to the Secure Managed Client environment using regular imaging tools such as ImageX and Ghost, the restored image may become non-bootable. Error messages such as Windows Boot Manager Windows failed to start... and The system registry contains invalid file paths.... may be displayed. This can occur on both Sysprep and non-Sysprep images. It can also happen to a regular Windows Vista image which has a separate system partition and OS partition. The M58 Vista Preload image contains three partitions. The first two are system partitions on which boot manager resides (S: ServiceV003) and an operating system partition on which the operating system boot loader resides (C: SW_Preload). The third partition (Q: Lenovo) is the backup data partition. 1. Install the Lenovo OEM Vista (either from install CD or from PreLoad) on your master system 2. Login as Administrator 3. Delete the extra user accounts you created during Windows Vista installation. You should only see Administrator and Guest (which is off) accounts from user account control panel 4. Fix any yellow marks in Device Manager and install other device drivers and applications as needed. Now your system should have everything you need except Lenovo Secure Managed Client VNIF drivers 5. Run the cmd.exe file (Run as administrator) and then change the directory to C:\windows\System32\sysprep. 30 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
v
Locate your Secure Managed Client VNIF driver files and modify the
provided OfflineUnattend.xml file accordingly.
v
Mount the wim file you created in step 12 on page 29.
mkdir
C:\wim_mount
Imagex /mountrw
D:\myimg\Vista32.wim 1 C:\wim_mount
v
Enable logging. This is optional, but a good practice.
–
Path:
HKLM\Software\Microsoft\Windows\CurrentVersion\Device
Installer
–
Key:
DebugPkgMgr
–
Type:
REG_DWORD
–
Value:
0x01
v
Use Package Manager to install the VNIF drivers. Change your current
directory to the directory where the pkgmgr.exe file is located.
Pkgmgr /o:”C:\wim_mount\;C:\wim_mount\Windows”
/n:”C:\tmp\OfflineUnattend.xml”
/l:”C:\pkgmgrlogs\logfile.txt”
v
Check the logfile.txt file make sure there are no errors and a return code of
0.
v
Review the contents of the %WINDIR%\inf\ directory in the mounted
Windows image to make sure that the .inf files were installed. Drivers
added to the Windows image are named oem.inf. This is to ensure unique
naming for new drivers that were added to the computer. For example, the
files MyDriver1.inf and MyDriver2.inf are renamed oem0.inf and oem1.inf.
v
Now unmount the .wim file and commit the installation.
Imagex /unmount /commit C:\wim_mount
14.
The .wim file is ready to be restored to your LUN. Run
ImageX /apply ...
after you mount your LUN.
Redeploying the Lenovo M58p Vista preload image to the Secure
Managed Client environment
When users redeploy the Lenovo M58P Windows Vista preload image to the
Secure Managed Client environment using regular imaging tools such as ImageX
and Ghost, the restored image may become non-bootable. Error messages such as
Windows Boot Manager Windows failed to start...
and
The system registry contains
invalid file paths
....
may be displayed. This can occur on both Sysprep and
non-Sysprep images. It can also happen to a regular Windows Vista image which
has a separate system partition and OS partition.
The M58 Vista Preload image contains three partitions. The first two are system
partitions on which boot manager resides (S: ServiceV003) and an operating system
partition on which the operating system boot loader resides (C: SW_Preload). The
third partition (Q: Lenovo) is the backup data partition.
1.
Install the Lenovo OEM Vista (either from install CD or from PreLoad) on
your master system
2.
Login as Administrator
3.
Delete the extra user accounts you created during Windows Vista installation.
You should only see Administrator and Guest (which is off) accounts from
user account control panel
4.
Fix any yellow marks in Device Manager and install other device drivers and
applications as needed. Now your system should have everything you need
except Lenovo Secure Managed Client VNIF drivers
5.
Run the cmd.exe file (Run as administrator) and then change the directory to
C:\windows\System32\sysprep.
30
Secure Managed Client Version 2.0 Deployment Guide