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

Inject the VNIF drivers to your Windows Vista Partition

Page 40 highlights

Note: You do not need to inject the VNIF driver files if you plan to run SMCSetup.exe since this will install the VNIF drivers on Windows Vista for you. v Locate your Secure Managed Client VNIF driver files and modify the provided OfflineUnattend.xml file accordingly . v Mount the .wim file that you already created in steps 12 on page 31, 13 on page 31, and step 14 on page 31. 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 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 the return code is 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 added to the computer. For example, the files MyDriver1.inf and MyDriver2.inf are now renamed oem0.inf and oem1.inf. v Now unmount the .wim file and commit the installation: Imagex /unmount /commit C:\wim_mount 16. Inject the VNIF drivers to your Windows Vista Partition. Note: The SMCSetup.exe file will not install the VNIF drivers to your Service Partition. If you need network access from your Service Partition after deployment, you must inject the drivers by performing the following steps: v Mount the .wim file. Imagex /mountrw D:\myimg\ServicePartition.wim 1 C:\wim_mount v Find the winpe.wim (under the tvtos directory) file and mount it. Note: you have to create c:\mype_mount first if it does not exist. Imagex /mountrw C:\wim_mount\tvtos\winpe.wim 1 C:\mype_mount v Assume your VNIF drivers are located in the E:\vnifdrivers directory. Peimg.exe /inf=E:\vnifdrivers\lndrvbus.inf C:\mype_mount\Windows Peimg.exe /inf=E:\vnifdrivers\netvnif.inf C:\mype_mount\Windows v If there are no errors, commit the wim file. Imagex /unmount /commit C:\mype_mount Imagex /unmount /commit C:\wim_mount The Vista32.wim and ServicePartition.wim files are now ready to be restored on your LUN. 17. Now both your "Vista32.wim" and "SystemPartition.wim" files are ready to be restored on your LUN. 32 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:
You do not need to inject the VNIF driver files if you plan to run
SMCSetup.exe since this will install the VNIF drivers on Windows Vista for
you.
v
Locate your Secure Managed Client VNIF driver files and modify the
provided OfflineUnattend.xml file accordingly .
v
Mount the .wim file that you already created in steps 12 on page 31, 13 on
page 31, and step 14 on page 31.
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 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 the return code
is 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 added to the computer. For example, the files
MyDriver1.inf and MyDriver2.inf are now renamed oem0.inf and oem1.inf.
v
Now unmount the .wim file and commit the installation:
Imagex /unmount /commit C:\wim_mount
16.
Inject the VNIF drivers to your Windows Vista Partition.
Note:
The SMCSetup.exe file will not install the VNIF drivers to your Service
Partition. If you need network access from your Service Partition after
deployment, you must inject the drivers by performing the following steps:
v
Mount the .wim file.
Imagex /mountrw
D:\myimg\ServicePartition.wim 1 C:\wim_mount
v
Find the winpe.wim (under the tvtos directory) file and mount it.
Note:
you have to create c:\mype_mount first if it does not exist.
Imagex /mountrw C:\wim_mount\tvtos\winpe.wim 1 C:\mype_mount
v
Assume your VNIF drivers are located in the E:\vnifdrivers directory.
Peimg.exe /inf=E:\vnifdrivers\lndrvbus.inf
C:\mype_mount\Windows
Peimg.exe /inf=E:\vnifdrivers\netvnif.inf
C:\mype_mount\Windows
v
If there are no errors, commit the wim file.
Imagex /unmount /commit C:\mype_mount
Imagex /unmount /commit C:\wim_mount
The Vista32.wim and ServicePartition.wim files are now ready to be restored
on your LUN.
17.
Now both your “Vista32.wim” and “SystemPartition.wim” files are ready to
be restored on your LUN.
32
Secure Managed Client Version 2.0 Deployment Guide