WinINSTALL 8.70.03 Desktop Management Suite and Desktop

WinINSTALL 8.70.03 Desktop Management Suite and Desktop Availability Suite Reference Guide Availability Suite
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Reference Guide
Disclaimer
The information contained in this publication is subject to change without notice. Attachmate Corporation makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. Attachmate Corporation shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual.
Copyright
. . .
. .
TABLE OF CONTENTS
Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
WinINSTALL Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
WinINSTALL Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Client Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
WinINSTALL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Reference Machine (clean machine on which packages are discovered) . . . . . . . . . . . . . . . . . . . 9 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
PXE Client Reset Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Basic PXE Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 WinINSTALL PXE Client Reset Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
WinINSTALL Administrator Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Chapter 3: WinINSTALL Directory Structures . . . . . . . . . . . . . . . . . . . . . . . . . .13 WinINSTALL Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
iv WinINSTALL Desktop Management Suite and Desktop Availability Suite
WinINSTALL Share . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 WinINSTALL MSDE 2000 Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 Machines with WinINSTALL Agent Deployed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Client Reset Folder Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Console Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Distrib folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 Logs folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 DosFiles folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 <Language> folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 MAC Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 RPClient folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
PXE Client Reset Folder Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 \ClientReset\nnnn Folders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 \ClientReset\data Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 \ClientReset\drivers Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 \ClientReset\sif Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 \ClientReset\utilities Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Chapter 4: The WinINSTALL Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31 WinINSTALL Sub-Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 IPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31 Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Wake . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Merge . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Publisher . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Housekeeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Client Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Agent Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 Secure Manual Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
. . .
. .
April, 2006 Reference Guide v
Agent Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Configuration and Transaction Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 Information Flow From the Database To the Workstation . . . . . . . . . . . . . . . . . . . . . . . . 40 Data Flow From the Workstation to the Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Share Configuration and Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 Share Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Share Ownership and Merge/Publish Responsibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Share Selection Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Section 2: WinINSTALL Database . . . . . . . . . . . . . . . . . . 45
Chapter 5: WinINSTALL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47 Database Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Supported Database Platforms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Microsoft® SQL Server 2000 Desktop Engine (MSDE 2000) . . . . . . . . . . . . . . . . . . . . 47 Microsoft® SQL Server 2000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Microsoft® SQL Server 2005 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47 Oracle® 9i or Later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Upgrading the Database Schema from Previous Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 Upgrading a Microsoft SQL Server or MSDE WinINSTALL Database . . . . . . . . . . . . . 48 Upgrading an Oracle WinINSTALL Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Chapter 6: WinINSTALL Database Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51 Database Version table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
WI_VERSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 Agent Infrastructure Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
WIAI_CHANGE_NOTICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 WIAI_EXCLUSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 WIAI_EXTENSION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 WIAI_HKSETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 WIAI_INVSETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 WIAI_JOBBIGPARAMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 WIAI_JOBCOMPLETION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 WIAI_JOBMACHINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
vi WinINSTALL Desktop Management Suite and Desktop Availability Suite
WIAI_JOBNETCRITERIA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 WIAI_JOBPARAMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 WIAI_JOBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 WIAI_LOGVARIABLE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 WIAI_MASETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 WIAI_MERGESETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 WIAI_PACKAGE_PATHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 WIAI_PACKAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 WIAI_PUBSETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 WAI_REASSIGNED_WORKSTATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58 WIAI_REPSETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 WIAI_SDSETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 WIAI_WAKESETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Conflict Assessment Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 WICA_ASSESSEDPACKAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 WICA_ASSESSMENTHISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 WICA_ASSESSMENTSETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 WICA_CONFLICTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 WICA_INIFILEADDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61 WICA_INIFILEREMOVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 WICA_JOBHISTORY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 WICA_PACKAGEDIRADDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 WICA_PACKAGEDIRREMOVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62 WICA_PACKAGEFILEADDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 WICA_PACKAGEFILEREMOVES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 WICA_PATHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63 WICA_REGISTRYKEYADDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 WICA_REGISTRYKEYDELETES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 WICA_REGISTRYVALUEADDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64 WICA_REGISTRYVALUEDELETES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 WICA_SHORTCUTADDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65 WICA_SHORTCUTDELETES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 WICA_WFILE_XREF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66 WICA_WFILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
. . .
. .
Console Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 WICON_ASSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 WICON_ASSETTYPE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 WICON_CLOB (Oracle-only Table) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67 WICON_INVAPPFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 WICON_LICENSE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 WICON_LOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 WICON_LOGDATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 WICON_MACHINEGROUPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69 WICON_MACHINEPATHS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70 WICON_MACHINES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 WICON_SEARCHCONDITIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 WICON_SEARCHES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 WICON_SECACC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72 WICON_SERVERSETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Client Reset Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 WICR_FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 WICR_LOOKUPMSDOSNICDRIVERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73 WICR_MSDOSADDITIONALFILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 WICR_MSDOSNICDRIVERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 WICR_OSLICENSEKEYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74 WICR_SHARES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75 WICR_TEMPLATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Inventory Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 WIINV_ARPAPPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 WIINV_CHANGELOG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 WIINV_DETECTEDFILEEXT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 WIINV_DETECTEDFILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 WIINV_DEVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 WIINV_LOCALLOGICALDRIVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 WIINV_MACHINEHW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80 WIINV_NTSERVICES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81 WIINV_OSINFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82 WIINV_PRINTER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
viii WinINSTALL Desktop Management Suite and Desktop Availability Suite
WIINV_RAMSLOT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 WIINV_REGISTEREDMSI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83 WIINV_REGISTEREDNAI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 WIINV_WINUPDATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Migration Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 WIMIG_JOBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84 WIMIG_SKIPPEDCONTENTNODES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 WIMIG_TASKS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85 WIMIG_USERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
PXE Client Reset Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 WIPXECR_CLIENTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 WIPXECR_CLIENTLicenseS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 WIPXECR_DRIVERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87 WIPXECR_LICENSEKEYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 WIPXECR_OPERATINGSYSTEMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88 WIPXECR_SERVERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 WIPXECR_TEMPLATES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89 WIPXECR_TEMPLATEACCOUNTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 WIPXECR_TEMPLATEFIREWALLEXCLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 WIPXECR_TEMPLATEPACKAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91 WIPXECR_TEMPLATEUTILITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 WIPXECR_UTILITIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92 WIPXECR_UTILITYSUPPORTFILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Replication Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 WIREP_JOBS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 WIREP_JOBSTATUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93 WIREP_JOBSTATUSLOGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 WIREP_MIGRATIONSOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 WIREP_MIGRATIONTARGETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94 WIREP_PACKAGESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 WIREP_PACKAGETARGETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 WIREP_PATCHSOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95 WIREP_PATCHTARGETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 WIREP_PXECRSOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
. . .
. .
WIREP_PXECRTARGETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 WIREP_TEMPLATESOURCES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 WIREP_TEMPLATESREPLICATED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 WIREP_TEMPLATETARGETS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Section 3: Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
User-defined Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Constant Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Global Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103 Application Prompts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104 URL Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Chapter 8: Conflict Assessment Categories . . . . . . . . . . . . . . . . . . . . . . . . . .105 Main conflict categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 File conflict subcategories and messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Registry conflict subcategories and messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 Shortcut conflict subcategories and messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106 INI File conflict subcategories and messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Chapter 9: MSI Custom Actions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .109 Defining the Custom Action: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
Specifying the Custom Action Sequence: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Section 4: Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . 113
x WinINSTALL Desktop Management Suite and Desktop Availability Suite
WinINSTALL Database log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115 Windows Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116 Console Log Event Codes and Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
WinINSTALL Agent logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119 Installer logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
Chapter 11: Special WinINSTALL Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . .121 Network Detection (NoNetNoGo.exe) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Creating a Baseline for Conflict Assessment (WIBaselineGen.exe) . . . . . . . . . . . . . . . . . . . . 121 Client Launch (WIClient.exe) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121 Script to Add a Database User (dbAddUser.cmd) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Procedure to Set the Dynamic List Publishing Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Procedure to Set the Interval Count for a Specific Server . . . . . . . . . . . . . . . . . . . . . . . 123 Procedure to Set the Interval Count for All Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123 Procedure to Set the Global Default Interval Count (for New Servers) . . . . . . . . . . . . . 124
Special Utility for Microsoft Patches (PatchCatalog.exe) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124 Generating mssecure Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125 PatchCatalog command syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126 Supported languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127 Patch Management Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Personality Transfer Command Line Utility (WIMigCmd.exe) . . . . . . . . . . . . . . . . . . . . . . . . 129 Sample Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Interactive Installer Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Run Automatic Installer at Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130 Enable E-Mail Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 Event Viewer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131 SNMP Get Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 SNMP Get and Set Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Backup User Data and Initiate Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132 Open XP Firewall Ports for WinINSTALL Operations . . . . . . . . . . . . . . . . . . . . . . . . . 134 Restore User Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Chapter 12: WinINSTALL Scripting Extensions . . . . . . . . . . . . . . . . . . . . . . .137 Installer Scripting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
. . .
. .
Installer Object Properties and Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137 Installer Script Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 Installer Event Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Console Scripting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 The Machines object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 The Machine object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Console Scripting Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .169
April, 2006 Reference Guide 1
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 WinINSTALL Desktop Management Suite and Desktop Availability Suite
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INTRODUCTION 1
he WinINSTALL Reference Guide is intended to provide in-depth information on the inner workings of the WinINSTALL product and methods for accomplishing advanced and involved tasks. It is not expected that anyone would read this
document from start to finish. Rather, as its title would suggest, this manual is intended to serve as a reference, to be consulted for specific information at times when you are trying to accomplish something more involved than usual. The guide is divided into sections to make it easier for you to find the information you are looking for.
This initial section presents installation requirements for all product components-- information which is available elsewhere, but which is included here for the sake of completeness. This introductory section also includes information on the directory structure of the WinINSTALL share and the WinINSTALL agent infrastructure, what the components are, and how they interact with one another.
The WinINSTALL Database section provides information on the various supported database management systems, on upgrading the database from one version of the product to another, and finally, a complete listing of all the tables and fields in the WinINSTALL database, including field types, sizes, and whether they are required or not.
The Applications section provides detailed information on certain of the intricacies of application packaging and distribution with WinINSTALL.
Finally, the Miscellaneous section includes information on WinINSTALL utilities, scripting, and other tools which don’t easily fit into any of the other categories.
T
I N T R O D U C T I O N
1
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INSTALLATION REQUIREMENTS 2
he minimum installation requirements for each of the WinINSTALL components is detailed below, along with a short explanation of what each component is and what role it plays in the WinINSTALL environment.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W I N I N S T A L L C O N S O L E The WinINSTALL Console is the graphical user interface (GUI) used to administer the entire WinINSTALL environment. Each machine on which you install a Console must meet the following requirements:
HARDWARE • 85 MB of disk space (for the local components of WinINSTALL).
SOFTWARE • Operating System - Windows 2000, SP4/Windows XP/2003.
• Microsoft Windows Installer 2.0 or greater.
WinINSTALL checks for the presence of this program during setup and will automatically install or upgrade it as required.
• Database Client Software.
If you are using Oracle® as your database, you must first manually install the client software in order to have database connectivity. Database connectivity is required for you to run the Console or use the Database Creation Wizard to initialize your WinINSTALL database.
The Microsoft SQL Server client software must be installed in order for you to use the Database Creation Wizard to create and initialize the WinINSTALL database. Except for the web-based installation, all other installation methods offer the option of installing the client software.
DISPLAY
R E S O L U T I O N • 1024 X 768 or higher.
T
I N S T A L L A T I O N R E Q U I R E M E N T S WinINSTALL Share
2
C O L O R • 16-bit or better.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W I N I N S T A L L S H A R E The WinINSTALL share serves multiple purposes. It holds the configuration files, executables, help files, reports, software packages, client reset templates, and other files used by the Console. It is used to store data that is moved by WinINSTALL agents between workstations and the database. Each machine on which you install a share must meet the following requirements:
HARDWARE • 235 MB of disk space (for the network components of WinINSTALL).
• Adequate disk space to store application packages and optional client reset templates.
SOFTWARE • Operating System.
The WinINSTALL share is a shared hierarchy of folders and files. As a result, the WinINSTALL share machine can be running any operating system.
The machine running setup must be running Windows 2000 or greater. The WinINSTALL share setup allows installing the share to a network drive.
• Windows Installer
Setup requires Microsoft Windows Installer 2.0 or greater. WinINSTALL checks for the presence of this program during setup and will automatically install or upgrade it as required.
. . .
. .I N S T A L L A T I O N R E Q U I R E M E N T S Client Workstations
Recommended: Windows Server 2000/2003.
Alternate: Windows NT 4.0 with SP 6a and IE5.5 or greater installed.
This file is included with Windows Server 2000/2003, but must be installed separately with Windows NT 4.0. WinINSTALL checks for the presence of this program during setup and will automatically install or upgrade it as required.
Deploying the WinINSTALL Agent will install or upgrade to Windows Installer 2.0 as necessary.
• Microsoft Data Access Components 2.71
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C L I E N T W O R K S T A T I O N S A WinINSTALL workstation is a machine with the WinINSTALL workstation agent deployed. A workstation performs workstation agent functions for itself only. Each machine with the role of WinINSTALL workstation must meet the following requirements:
HARDWARE • As required for applications being installed.
• 15 MB of disk space (for local components of WinINSTALL).
NOTE: WinINSTALL does not require a dedicated server. WinINSTALL servers may also be operating as file servers, print servers, application servers, database servers, etc.
WARNING: If an earlier version of MDAC is already installed on the server at the time when the WinINSTALL server agent is deployed, the MDAC upgrade is liable to cause the server to reboot.
I N S T A L L A T I O N R E Q U I R E M E N T S WinINSTALL Database
2
Windows XP/2000/98 with IE 4.0/95 with IE 4.0 and WinSock 2/NT 4.0 with SP 6a and IE5.5 or greater installed.
This program is included with Windows Server 2000/2003, but must be installed separately with Windows NT 4.0.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W I N I N S T A L L D A T A B A S E The WinINSTALL database holds all of the information used internally by WinINSTALL and displayed in the console.
HARDWARE • Adequate disk space for database.
NOTE: PXE client machines must have at least the Microsoft- recommended minimum amount of RAM for the operating system being installed (Windows 2000: 64MB, Windows XP and 2003: 128MB).
NOTE: Some non-English versions of Windows 95 and Windows NT 4.0 contain no native support for encryption/decryption. Because WinINSTALL uses encryption for agent deployment and communication, such systems require the addition of an update which includes CryptoAPI support, such as that provided in Internet Explorer v6.
. . .
. .I N S T A L L A T I O N R E Q U I R E M E N T S Reference Machine (clean machine on which packages are discovered)
SOFTWARE • Software for any of the following databases:
Microsoft® SQL Server 2000 Desktop Engine (MSDE 2000).
Microsoft® SQL Server 2000.
Microsoft® SQL Server 2005.
Oracle® 9i or later.
R E F E R E N C E M A C H I N E ( C L E A N M A C H I N E O N
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W H I C H P A C K A G E S A R E D I S C O V E R E D ) A reference machine is a special machine that is used solely for the purpose of building packages and the creation of transforms. No part of WinINSTALL is installed on a reference machine.
Technically, a reference machine should be a clean machine, with only the operating system and any necessary service packs installed. Because a reference machine does not need to be large and expensive, some administrators have two or more. In this way, they can create a package on one machine while returning a previously-used machine to its clean state. This practice reduces downtime - and the temptation to cut corners by using a dirty machine.
Today, a number of commercial products are available to simplify the process of returning a reference machine to its clean state. For instance, some products allow you to create a virtual machine and save it in a clean state, build a package on it, and then discard all changes and return to the original clean state during reboot. These virtual machines save a great deal of time because you install the operating system only once for each operating system used in your network. This convenience is particularly useful because each package must be created on a machine with the same operating system as the network client on which it will be installed.
HARDWARE • As required for applications being packaged.
Windows 2003/XP/2000/98 with IE 4.0/95 with IE 4.0/NT 4.0 with SP 6a and IE5.5 or greater installed.
I N S T A L L A T I O N R E Q U I R E M E N T S PXE Client Reset Requirements
2
This program is required to build Windows Installer packages. It is included with Windows 2003/XP/2000, but it must be installed separately on other operating systems. When Windows 9x or Windows NT 4.0 is installed on the reference machine, you cannot create a Windows Installer package directly with the Discover Wizard. You must first create a WinINSTALL package and then convert it to a Windows Installer package on a machine running Windows 2000 or later.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P X E C L I E N T R E S E T R E Q U I R E M E N T S
BASIC PXE REQUIREMENTS There are several requirements for a client machine to be PXE-bootable. The machine’s BIOS must support “Network” as a boot device. Also the machine’s NIC must support the PXE standard (first introduced in the PC98 specification). Optionally the NIC can contain the PXE boot ROM. NICs that contain the ROM are often called “managed NICs” or “NICs for managed PCs.” If the NIC supports PXE but does not contain the ROM image, a network boot is only possible by booting the system with a floppy disk containing the ROM image. Almost all PCs sold after 1998 support “Network” boot in the BIOS and most NICs support PXE.
There are two distinct versions of PXE; DHCP-based (Dynamic Host Configuration Protocol) and RPL (Remote Program Load). DHCP-based is used across most network environments, whereas RPL is most often used in NetWare environments. PXE-capable NICs support either DHCP-based, RPL-based, or both. A PXE-capable NIC that supports only RPL will not work in a Windows environment.
The fact that PXE requires DHCP imposes additional restrictions on the network setup. First, use of PXE is not possible in a static IP environment. Second, since DHCP does not typically cross subnets, each subnet containing a DHCP server must also contain a PXE server. For example, a company with offices in LA and NYC would typically have a DHCP server at each site. Such a setup would also require a PXE server at each site. Client machines in LA could not connect to a PXE server in NYC.
. . .
. .I N S T A L L A T I O N R E Q U I R E M E N T S WinINSTALL Administrator Requirements
WININSTALL PXE CLIENT RESET REQUIREMENTS WinINSTALL PXE Client Reset requires the following components, over and above those for the rest of the WinINSTALL product:
• DHCP Server
The network must be configured to use DHCP, and therefore it must include a DHCP server on or for each subnet where WinINSTALL PXE Client Reset will be configured. In addition, to support PXE, each DHCP server must have options 66 and 67 enabled. WinINSTALL can automatically set these options on Windows servers which are providing DHCP services. Other DHCP servers will need to have these options enabled manually.
• Windows Install Set
Operating system installation files must be provided (via the WinINSTALL PXE Client Reset Template Wizard, below) for installation on client machines. Windows 2000, Windows XP, and Windows 2003 can be installed in this fashion.
• PXE-Capable Client
Every client machine must be PXE-capable. This means the BIOS must support Network as a boot device and the NIC must be DHCP-PXE-capable.
W I N I N S T A L L A D M I N I S T R A T O R
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . R E Q U I R E M E N T S An effective WinINSTALL administrator should have an in-depth understanding of the organization’s network and security policies, and the necessary security rights to access appropriate network resources. In addition, it is helpful to have the following qualifications:
• A solid understanding of all the Windows platforms in use on the network.
WARNING: Windows 2000, XP, and 2003 can be installed through PXE. Windows 95/98/ME and NT cannot.
NOTE: PXE client machines must have at least the Microsoft- recommended minimum amount of RAM for the operating system being installed (Windows 2000: 64MB, Windows XP and 2003: 128MB).
I N S T A L L A T I O N R E Q U I R E M E N T S WinINSTALL Administrator Requirements
2
• A working knowledge of the Windows registry.
An understanding of the Windows registry can be invaluable when building packages. After WinINSTALL has Discovered an application, you may need to modify a registry entry to fit your network needs. You should be familiar with the use of REGEDIT.EXE and REGEDT32.EXE, and the differences between these two registry editors. These two utilities can be found in the \Winnt and \Winnt\System32 directories, respectively.
• An understanding of the Microsoft Windows Installer and MSI technology.
Knowledge of Windows Installer technology and terminology is helpful when you are working with MSI files. A solid understanding of the MSI table relationships and MSI properties is recommended if you will be building and using Windows Installer packages.
• Familiarity with scripting languages and writing scripts.
For certain complex situations, some users prefer to use scripts in their packages. This is usually unnecessary, but in the event that it is needed or desired, any scripting language supported by Windows Scripting Host can be used in WinINSTALL packages. Scripting in WinINSTALL packages is accomplished through external processes (see the WinINSTALL Reference Guide for more on scripting in WinINSTALL packages), while scripting in Windows Installer packages is accomplished through custom actions.
. . . . .
his section documents the directory structures installed and used by the different WinINSTALL components, including the console, server, workstation, and WinINSTALL share. In addition, special details are provided for the Client Reset
sub-folders within the WinINSTALL share.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W I N I N S T A L L C O N S O L E When the WinINSTALL Console is deployed, the following directories are created:
C:\Program Files\OnDemand\Tranxition
C:\Program Files\OnDemand\WinINSTALL
The executable and related binaries for the Console and/or Agents are stored in the following directory:
C:\Program Files\OnDemand\WinINSTALL\Bin
The following sub-folder is the location of the compiled help (.chm) files used by the WinINSTALL Console:
C:\Program Files\OnDemand\WinINSTALL\Help
The plugins for the Tranxition personality transfer engine (used only by the WinINSTALL Desktop Availability Suite) are stored in the following directory:
C:\Program Files\OnDemand\Tranxition\Plugins
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W I N I N S T A L L S H A R E When a WinINSTALL Share is installed, the following shared folder is created:
\WinINSTALL
• ReadMe.html
• ReadMePkgr.html
• WIShare.msi
T
W I N I N S TA L L D I R E C T O R Y ST R U C T U R E S WinINSTALL Share
3
In addition, the following subfolders are created within the shared folder:
\Bin
The \Bin subfolder of the share contains the binaries for the WinINSTALL program - including Discover, the Automatic Installer, the Interactive Installer, the conflict assessment baseline generator, the files to be deployed with the WinINSTALL Agent, and the MSI file that installs additional WinINSTALL Consoles - and the default exclusion files for Discover and for the conflict assessment baseline generator application.
\CFGFiles
This sub-folder of the share is the distribution point for .XML files containing configuration and job information being sent to workstations and servers. These files are published from the database by the Publisher sub-agent running on the WinINSTALL server. The files are then retrieved by each target machine’s WinINSTALL Agent, which periodically checks this shared folder for configuration changes to apply and jobs to run.
\CR
The CR sub-folder (used only by the WinINSTALL Desktop Management Suite and WinINSTALL Desktop Availability Suite) is the location of all files required for Client Reset Templates, such as binaries, operating system distribution files and images, service packs, and files needed to build a boot disk or reset partition. Additional details on each of these 7 folders and their contents are available in the Client Reset Folder Structure section, below:
• \CR\Console
• \CR\Distrib
• \CR\DOSFiles
• \CR\<language>
• \CR\Logs
• \CR\MAC
• \CR\RPClient
\Help
This sub-folder is the location of the compiled help (.chm) files for WinINSTALL, including copies of all the help files used by the Console (see the help file directory in the WinINSTALL Console section, above).
\MergeModules
. . .
. .W I N I N S TA L L D I R E C T O R Y ST R U C T U R E S WinINSTALL Share
The MergeModules sub-folder contains a 'cache' of merge modules that will be checked for possible use when packages are converted to a Windows Installer format. You can add your own merge modules to this folder as needed, including adding sub-folders for categories of merge modules, if desired.
\MergeModules\Microsoft
This sub-folder contains merge modules created by Microsoft Corporation. You can add additional merge modules to this folder.
\Migration
Personality transfer templates, personality transfer repositories, and the files required to run personality transfer tasks (used only by the WinINSTALL Desktop Management Suite and WinINSTALL Desktop Availability Suite) are all located beneath the Migration sub-folder of the share.
\Migration\Content Plugins
This sub-folder holds the files required to run all personality transfer tasks.
\Migration\Repository
The Migration\Repository sub-folder is the location for storing all of the personality transfer data that has been extracted from source machines, in three sub-folders, according to the type of personality transfer involved:
• \Migration\Repository\Backups
• \Migration\Repository\Migrations
• \Migration\Repository\Policies
\Packages
This folder contains all the default packages included in WinAPPS.LST and its sub-lists, plus (by default) any new list files and packages that are created with WinINSTALL This is also the default directory used by WinINSTALL replication.
TIP: Keep the \MergeModules\Microsoft folder up to date by periodically visiting the Microsoft web site to download new and updated merge modules.
W I N I N S TA L L D I R E C T O R Y ST R U C T U R E S WinINSTALL MSDE 2000 Database
3
\Patches
The Patches folder contains all the Microsoft Patch Management list files and patch packages.
\Reports
This folder contains all supplied Crystal Reports (.rpt files) that are available from the WinINSTALL Console. If you have Crystal Designer, you can create and store your own custom reports here as well.
\TxFiles
The TxFiles folder of the share is the collection point for .XML files transferred to the WinINSTALL share by workstation and server agents for merging into the WinINSTALL database. The WinINSTALL Merge sub-agent on the server periodically checks this folder for information, such as inventory data, that needs to be merged into the database for reporting and viewing in the Console.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W I N I N S T A L L M S D E 2 0 0 0 D A T A B A S E When you choose the WinINSTALL installation option that also installs the Microsoft® SQL Server 2000 Desktop Engine (MSDE 2000), it creates the following directory for the MSDE application:
C:\Program Files\Microsoft SQL Server\
. . .
. .W I N I N S TA L L D I R E C T O R Y ST R U C T U R E S Machines with WinINSTALL Agent Deployed
M A C H I N E S W I T H W I N I N S T A L L A G E N T
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D E P L O Y E D When you deploy the WinINSTALL Agent to a machine (server or workstation), it creates the following directory structure:
C:\Program Files\OnDemand\WinINSTALL
The following subfolders are created:
\Bin
The \Bin folder contains the binaries for the WinINSTALL Agent and sub-agents.
\CfgFiles
This folder contains .XML files retrieved from the WinINSTALL share. Such files contain local configuration settings and jobs for the local machine.
\TxFiles
This folder holds .XML files containing local information to be moved to the \TxFiles directory on the WinINSTALL Share. From there, the information will be merged into the WinINSTALL database by the server Merge sub-agent.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C L I E N T R E S E T F O L D E R S T R U C T U R E The Client Reset folder (\CR) is located under the WinINSTALL share, and it contains the following folders and files:
Console FOLDER Files in this folder are never replicated. They are used only by the console, either directly for Client Reset settings or as files to be copied to floppy folders and images.
AppText.<lng> files
These files provide language-specific messages for the MS-DOS phases of Client Reset. WinINSTALL currently supports English, French, and German. When a Client Reset Template is saved, one of these files, applicable for the currently selected Client Reset template’s language, is copied to AppText.ini; this is the actual file MS-DOS uses for language-specific messages. The AppText.ini file, in turn, is compressed into Apps.dat, which is itself copied to floppy folders and images.
Autoexec.bat file
W I N I N S TA L L D I R E C T O R Y ST R U C T U R E S Client Reset Folder Structure
3
This file is the master version of the Autoexec.bat file used during MS-DOS phases of Client Reset. This file is copied to floppy folders and images, and that copy is then modified according to each template’s Additional MS-DOS Files settings.
Config.ms file
This file is the master version of the Config.sys file used during MS-DOS phases of Client Reset. This file is used specifically for Microsoft networks; it is copied to floppy folders and images, and that copy is later modified according to each template’s Additional MS- DOS settings.
Config.nw file
This file is the master version of the Config.sys file used during MS-DOS phases of Client Reset. This file is used specifically for NetWare networks; it is copied to floppy folders and images, and that copy is later modified according to each template’s Additional MS-DOS settings.
Connect.exe file
During MS-DOS phases of Client Reset, this application connects the workstation to the network, then spawns SetOS.exe or SetRP.exe, depending on a parameter in OStart.ini. This file is copied to floppy folders and images.
FindRamD.exe file
During MS-DOS phases of Client Reset, this application determines the drive letter of the temporary RAM disk on which the MS-DOS code is running. This file is copied to floppy folders and images.
Finish.bat file
This file is the master version of the Finish.bat file that gets copied to floppy folders and images. This file may be modified during MS-DOS phases, depending on network type and target operating system.
Net.cfg file
This file is a required configuration file used during MS-DOS phases of Client Reset. It is compressed into Apps.dat, which in turn is copied to floppy folders and images.
PackApp.exe file
This application decompresses the Apps.dat file during MS-DOS phases of Client Reset. It is copied to floppy folders and images.
Protocol.ini file
. . .
. .W I N I N S TA L L D I R E C T O R Y ST R U C T U R E S Client Reset Folder Structure
StuffKey.exe file
This application ‘stuffs’ keystrokes into the keyboard buffer during MS-DOS phases of Client Reset; it provides an ‘auto response’ capability for some of the network applications, such as Net.exe. It is compressed into Apps.dat, which in turn is copied to floppy folders and images.
System.ini file
This configuration file is required during MS-DOS phases of Client Reset. It is compressed into Apps.dat, which in turn is copied to floppy folders and images.
WfwSys.cfg file
This is a network configuration file required during MS-DOS phases of Client Reset. This file is compressed into Apps.dat, which in turn is copied to floppy folders and images.
<Language>.lng files
Not to be confused with the MS-DOS AppText files, these files provide language-specific strings to Client Reset Templates. They provide translations of time zones and keywords. The existence of a language file permits a Template to select that language. For instance, if German.lng exists, then Templates can select German as the language for an OS install. WinINSTALL currently supports Brazilian Portuguese, Chinese (Simplified and Traditional), English, French, German, Italian, Japanese, Korean, and Spanish.
<OS>.ua files
These are the master Unattend files for supported operating systems. When a Template is saved, a copy of the applicable Unattend file is created in the Template’s floppy folder and modified to reflect the Template’s settings. During MS-DOS phases of Client Reset, this specialized file is referenced by the Windows OS installer (WinNT.exe). WinINSTALL currently supports Windows 98, Windows NT (Workstation and Server), Windows 2000 (Professional and Server), Windows XP Professional, and Windows 2003 servers.
Distrib FOLDER HidePart.exe file
This application is used by Windows 98 workstations to detect presence of a reset partition.
CC3250.dll file
ImgLoad.exe file
This application runs the first time a user logs onto a workstation that was reset via third- party image install. It prepares the workstation to run WinLoad.exe.
3
PQAccd.exe file
This application copies files to a workstation’s non-FAT16 partitions during MS-DOS phase of Client Reset.
PQAccd.rtc file
This is a configuration file used by PQAccd.exe. It specifies the features allowed.
PQFile.exe file
This application reboots a workstation during MS-DOS phase of creating a reset partition using WIRPAdd.exe (Create Reset Partition application).
PQMagic.exe file
This application re-partitions the hard drive during MS-DOS phase of Client Reset.
PQMagic.ovl file
PQMagic.bmp file
PQMagic.pqg file
PQPB.rtc file
This is a configuration file used by PQMagic.exe. It specifies the feature allowed.
RestrMBR.exe file
This application restores the Master Boot Record (MBR) to a default version. It is available for customer use, but not used by Client Reset itself.
SetOS.exe file
This application manages the reset of a workstation during Client Reset.
SetRP.exe file
This application manages the MS-DOS phase of creating a reset partition, when initiated from WIRPAdd.exe (Create Reset Partition application).
VFile.exe file
This application creates a floppy image file. This application is invoked in two situations:
. . .
• When the Console creates, at the administrator’s request, a floppy image from the Create Floppy Disk wizard.
VFInst9x.exe file
This application forces a Windows 98 workstation to boot from a floppy image file.
VFInstNT.exe file
This application forces a Windows NT-based workstation to boot from a floppy image file.
VFInstNT.dll file
VFloppy.sys file
VFlppyLd.sys file
PQVxd.vxd file
WinLoad.exe file
This application manages the post-OS install operations, such as maximizing the OS partition size and installing WinINSTALL packages.
WIRPAdd.exe file
This is the Create Reset Partition application. It initiates creation of a reset partition on a Windows workstation.
WIRPAdd.hlp file
This is the Help file for WIRPAdd.exe (Create Reset Partition application).
WIRPRmv.exe file
This is the Remove Reset Partition application. It initiates removal of a reset partition on a Windows workstation.
WIRPRmv.hlp file
This is the Help file for WIRPRmv.exe (Remove Reset Partition application).
WIRPWks.exe file
This is the Reset Workstation application, which initiates the reset of a Windows workstation.
3
This is the Help file for WIRPWks.exe (Reset Workstation application).
WIRPRes.dll file
UniCows.dll file
This application extension provides Unicode support for Windows 98 workstations.
WIShlApi.dll file
WIMBR.com file
This program replaces the Master Boot Record when a reset partition is created. It is also the application which starts a reset of the workstation if Ctrl-R is pressed during boot up.
WIRPRmv.lnk file
WIRPWks.lnk file
This shortcut file references WIRPWks.exe (Reset Workstation application). It is copied to the workstations user’s Start Menu.
Remove.ima file
This image file runs as a virtual floppy when the workstation is rebooted by the Remove Reset Partition application. It initiates the actual removal of a reset partition.
Reset.ima file
This image files runs as a virtual floppy when the workstation is rebooted by the Reset Workstation application. It initiates the actual reset of a workstation.
Resize<n>.ima files
Four versions of this Resize image file are included. When a workstation is rebooted after an OS install, the appropriate one is run as a virtual floppy, depending on template settings. The versions supplied differ from one another in the following ways:
. . .
• Resize2.ima is the same as Resize1.ima, except that it also patches the Master Boot Record with WIMBR.com.
• Resize3.ima is the same as Resize1.ima, except that it also converts the file system to FAT32.
• Resize4.ima is the same as Resize2.ima, except that it also converts the file system to FAT32.
Logs FOLDER <Log>.txt files
These files are the logs created by a Client Reset operation (when logging is enabled in the Template. The Logs folder is not created until the first Client Reset log is created.
DosFiles FOLDER NicDrvrs folder
This folder contains all the MS-DOS NIC driver files to be used by workstations to connect to the network during boot up. These are treated as language-independent; that is, the user isn’t required to locate versions for each OS language to be supported.
<Language> FOLDERS Each such folder contains files that are specific to a supported OS language. The supported languages are Brazilian Portuguese, Chinese (Simplified & Traditional), English, French, German, Italian, Japanese, Korean, and Spanish.
DosFiles F O L D E R
DOS F O L D E R This folder contains the basic MS-DOS boot-up files:
• Command.com
• Emm386.exe
• HiMem.sys
• IO.sys
• Keyb.com
• Keyboard.sys
• MSDOS.sys
• RamDrive.sys
3
• SmartDrv.exe
• Sys.com.
Extra F O L D E R This folder contains any additional MS-DOS files required by Templates.
Net F O L D E R Programs folder
This folder contains the MS-DOS network-connection files:
• EmsBfr.exe
• Hosts
• IfsHlp.sys
• LmHosts
• Nemm.dos
• Net.exe
• Net.msg
• NetBind.com
• Neth.msg
• Networks
• NmTsr.exe
• ProtMan.dos
• ProtMan.exe
• Protocol
• Services
• TcpDrv.dos
• TcpTsr.exe
• TcpUtils.ini
• TinyRfc.exe
• Umb.com
. . .
Img<OS> F O L D E R S This folder contains third-party image installers for a supported operating system. Such folders are created only when a template specifies that the operating system will be installed by means of a third party image, rather than Windows setup. The following Img<OS> folders reflect currently supported operating systems:
• Img98
• ImgNTw
• ImgNTs
• Img2kp
• Img2ks
• Img2kas
• ImgXPp
• Img2k3s
• Img2k3e
• Img2k3w.
Data folder
This sub-folder contains the third-party image files for the related operating system and language.
Win<OS> F O L D E R S These folders contain Windows install files (.CAB, etc.) for the relevant operating systems and languages. Such folders are created only when a template specifies that the operating system will be installed by means of Windows setup, rather than a third party image. The following Win<OS> folders reflect currently supported operating systems:
• Win98
• WinNTw
• WinNTs
• Win2Kp
• Win2Ks
• Win2Kas
• WinXPp\i386
3
MAC FOLDER <xx>.MAC files
In order to maintain a consistent machine name and WinINSTALL machine ID (GUID) across a Client Reset operation, WinINSTALL automatically links these items with a workstation’s MAC address in a text file, where they will be automatically retrieved and applied after the new operating system is installed.
This behavior is automatically built in to the WinINSTALL Client Reset process. These text files are written and maintained automatically by the server Publisher sub-agent. To avoid file contention issues, these files are named according to the last two hex digits of each workstation’s MAC address, plus a .mac extension (for example, 5F.MAC).
Each file is written in three tab-delimited columns, with the first column containing the machine name, the second the MAC address, and the last the WinINSTALL machine ID. A typical entry might look like this:
SILVER 00:0C:29:EC:39:5F {29A500AE-B5A5-4E5A-8A28- 5297A4111955}
In this example, the MAC address will result in the filename 5F.MAC. Note that it is possible for a single MAC file to contain entries for multiple machines. Such a situation, while unusual, is not an error condition and will cause no problems.
RPClient FOLDER
{GUID} F O L D E R S A unique GUID folder is created for each Client Reset Template. It contains the Unattend.txt file that will be used by the OS installer during reset of a workstation using that template. It may further contain, if reset partitioning is enabled, files required to create a reset partition on a workstation. The following files are found within GUID folders:
WIRPAdd.lnk file
This is a shortcut to the Create Reset Partition application (WIRPAdd.exe). This link may be provided to workstation users (via e-mail or network share) if they need to create reset partitions on their workstations. This file will exist only if the template supports reset partitions.
Unattend.txt file
. . .
This file drives the operating system setup, specifying the settings for the OS installer.
UDF.txt file
This text file specifies overrides of OS settings in Unattend.txt. This file is optional and is manually created and managed, entirely by the user.
Apps.dat file
This file contains compressed files used during the MS-DOS phase of a Client Reset. This file will exist only if the template supports reset partitions.
PackApp.exe application
This file extracts (decompresses) the files contained in the file Apps.dat. This file will exist only if the template supports reset partitions.
AutoExec.bat file
This file will exist only if the template supports reset partitions.
Command.com file
Config.sys file
FindRamD.exe file
IfsHlp.sys file
IO.sys file
MSDOS.sys file
DOS folder
This folder will exist under the GUID folder only if the template supports reset partitioning. The following MS-DOS files must be present in this folder:
• Emm386.exe
• HiMem.sys
W I N I N S TA L L D I R E C T O R Y ST R U C T U R E S PXE Client Reset Folder Structure
3
• Keyb.com
• Keyboard.sys
• RamDrive.sys
• SmartDrv.exe
• Sys.com
Net folder
This folder will exist under the GUID folder only if the template supports reset partitioning. The following files will appear in the Net folder:
• Network.txt file This file specifies which network cards are supported by this template for workstation reset.
• OStart.ini file This file specifies general reset startup information, such as the distribution share to connect to.
• TDATA.x file This file contains the logon account required to connect to a distribution share. The data are encrypted.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . P X E C L I E N T R E S E T F O L D E R S T R U C T U R E The PXE Client Reset feature is available only in the WinINSTALL Desktop Availability Suite. The \ClientReset folder is the root folder in the WinINSTALL share for all PXE Client Reset files, including operating system files, console files, drivers, and post-install utilities. It is located directly under the WinINSTALL share and contains the following subfolders:
\ClientReset\nnnn FOLDERS These folders contain language-specific operating system files, where nnnn represents the Microsoft-assigned language ID. The following list provides examples for some of the most common language IDs.
ID Language
1033 • English
1036 • French
1031 • German
. . .
. .W I N I N S TA L L D I R E C T O R Y ST R U C T U R E S PXE Client Reset Folder Structure
So, for example, English operating system files would be located within the \ClientReset\1033 folder, while French operating system files would be found beneath the \ClientReset\1036 folder.
Operating system files are added as part of the configuration of PXE Client Reset servers. For more information, see the PXE Client Reset chapter of the WinINSTALL Desktop Management Suite and Desktop Availability Suite Administrators Guide.
\ClientReset\data FOLDER This folder contains the files required for the PXE Client Reset console functionality.
\ClientReset\drivers FOLDER This folder contains all driver files added for PXE Client Reset operations.
Drivers are added as part of the configuration of PXE Client Reset servers. For more information, see the PXE Client Reset chapter of the WinINSTALL Desktop Management Suite and Desktop Availability Suite Administrators Guide.
\ClientReset\sif FOLDER This folder contains the master unattended files for all operating systems. When a machine is reset, these files are loaded, and then settings specific to the template are applied.
\ClientReset\utilities FOLDER This folder contains all added post-install utilities.
1034 • Spanish
1040 • Italian
1028 • Traditional Chinese
2052 • Simplified Chinese
TIP: For users knowledgeable in the settings and syntax of Windows unattended files, the files in the ClientReset\sif folder can be edited directly- but this is not recommended, because incorrect settings may result in failed resets.
W I N I N S TA L L D I R E C T O R Y ST R U C T U R E S PXE Client Reset Folder Structure
3
The post-install utilities are specified when configuring PXE Client Reset Servers. For more information, see the PXE Client Reset chapter of the WinINSTALL Desktop Management Suite and Desktop Availability Suite Administrators Guide.
. . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . THE WININSTALL AGENTS 4
inINSTALL uses a Master Agent, also known as the WinINSTALL agent, plus a number of sub-agents to manage WinINSTALL operational tasks such as inventory, software distribution, scheduling, migration, and replication. The
WinINSTALL Master Agent and sub-agents also synchronize information between the WinINSTALL database and the WinINSTALL workstations and servers. This agent infrastructure is deployed to machines in the network directly from the WinINSTALL Console, though deployment can also be accomplished manually from the workstation or through scripts executed on a server or workstation. Which infrastructure components, or sub-agents, are installed depends on the role of the machine to be deployed: whether the target machine will operate as a WinINSTALL server or workstation.
Workstation deployments include the master agent plus a collection of sub-agents used for different purposes, including software distribution, scheduling, and additional functions. Server deployments include everything deployed to workstations, plus additional sub-agents for server-specific tasks, such as merging information to the database, publishing configuration and job information to workstations, and (in WinINSTALL Desktop Management Suite and Desktop Availability Suite) replicating WinINSTALL data from server to server.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . W I N I N S T A L L S U B - A G E N T S The WinINSTALL Agent can perform a number of different tasks by means of the installed set of sub-agents. The WinINSTALL Agent, also known as the Master Agent, starts and controls each of the following sub-agents, as needed:
CONFIGURATION The Configuration sub-agent moves XML files between the workstation and the share, and it also manages share selection.
IPC The IPC sub-agent manages all interprocess communication between the machine on which it is running and the console. For certain purposes, the IPC sub-agent may also communicate between workstations and servers.
W
T H E W I N I N S TA L L A G E N T S WinINSTALL Sub-Agents
4
SCHEDULER The Scheduler sub-agent processes all scheduled jobs for the local machine, notifying the appropriate sub-agent at the appointed time.
WAKE On the server, the Wake sub-agent transmits Wake-On-LAN packets to target end nodes, as requested by the console, by the Scheduler sub-agent, or by a workstation. On WinINSTALL Desktop Management Suite (DMS) and Desktop Availability Suite (DAS) workstations, this sub-agent also submits requests to the server for future Wake-On-LAN calls.
INVENTORY On WinINSTALL DMS and DAS machines, the Inventory sub-agent performs hardware and software inventory jobs, whether scheduled or launched through the Console in real time.
DISTRIBUTION The Distribution sub-agent launches the WinINSTALL Automatic Installer to perform all software distribution jobs.
MIGRATION The Migration sub-agent performs extractions and/or injections for all backup, migration, and policy jobs on workstations. This sub-agent is available only with the WinINSTALL Desktop Availability Suite (DAS).
MERGE The Merge sub-agent, which runs only on servers, reads XML data uploaded to the share by workstations (and servers) and merges the information in these files into the WinINSTALL database.
. . .
. .T H E W I N I N S TA L L A G E N T S Agent Deployment
REPLICATION The WinINSTALL DMS and DAS Replication sub-agent moves packages, lists and patches, Client Reset templates, and Personality Transfer repositories from one server to another. This sub-agent is responsible for both the sending and receiving of replication data and can operate in unicast or multicast, as appropriate.
HOUSEKEEPER The Housekeeper sub-agent cleans up old XML files and, when running on servers, is also responsible for database cleanup operations.
CLIENT RESET The Client Reset sub-agent executes on WinINSTALL Desktop Availability Suite PXE reset servers, handling communication between the server where it is running and PXE client machines which are in the process of booting up or performing PXE resets.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A G E N T D E P L O Y M E N T The WinINSTALL Agent can be deployed directly from the Console, manually, or through a script or package, using Secure Manual Deployment (SMD).
For systems running NT 4 and above, the Agent is most easily deployed from within the WinINSTALL Console.
For Windows 9x systems, the Agent must be installed manually or through a script or a package. You can also use scripting along with some of the special features of SMD to automatically deploy the WinINSTALL agent to your entire network or to selected subsets of your network.
SECURE MANUAL DEPLOYMENT Deploying the WinINSTALL Agent manually using a Secure Manual Deployment (SMD) file involves two steps. First, you create the SMD file from the Console machine. Then, you deploy the agent on the machine using the SMD file you created and the WIDeploy.exe utility, located in the \bin directory of the WinINSTALL share.
WARNING: When you create a Secure Manual Deployment file, you specify the share to use for the initial connection. All machines which use a particular SMD file will connect to the specified share and will be assigned to the server which owns that share.
T H E W I N I N S TA L L A G E N T S Agent Deployment
4
The following switches are valid for command-line deployment with WIDeploy.exe:
TIP: To assign machines to different servers using Secure Manual Deployment, create separate SMD files to connect to different shares.
-c <string> • Supplies the database connection string instead of reading it from the WINSTALL.CFG file.
-d <mode> • Sets the database mode:
• 0 = Don't try to retrieve machine IDs (GUIDs) from the database.
• 1 <default> = Try to retrieve machine IDs (GUIDs) from the database. If unsuccessful, generate a machine ID (GUID).
• 2 = Only deploy to machines that have a machine ID (GUID) in the database.
-e • Stops deployment when errors occur (when deploying to multiple machines)
-f • Forces an automatic reboot, if required
-i • Ignores the Agent deployed flag in the database when selecting machines
-k <context> • Specifies an Active Directory search context (see Query Active Directory (“+”), below).
-l • Generates an installer log file in the Windows folder
-m MyMachine • -m MyMachine Deploys the Agent to a single machine named MyMachine.
-m @MyList.xml • -m @MyList.xml Deploys the Agent to a set of machines, as specified in the XML file MyList.xml located in the current directory. A full path can be used to point to an XML file located elsewhere. The XML file must be in a specific format. See Deploy to a List of Machines (“@”), below.
. . .
A U T O M A T I N G W I N I N S T A L L A G E N T D E P L O Y M E N T WIDeploy.exe can deploy to multiple specified machines, it can query the WinINSTALL database and deploy to all listed machines which do not have the WinINSTALL Agent deployed (or to a subset of such machines), and it can sweep the network, using Active Directory, for machines to be added and deployed automatically.
In a dynamic IT environment, regular scheduling of this type of automated deployment (for example, through system scheduling of a batch file or the desired command line) can help to significantly reduce administrator workload and assure that all new machines appear in the database promptly and automatically.
• -m “*MACHINEGROUP='MyGroup' “ Deploys the Agent to all machines that are in the MyGroup machine group to which the Agent has not already been deployed.
Anything after “* and before “ is part of a SQL WHERE clause. Technically speaking, the double-quotes are not necessary unless the WHERE clause contains a space (for example, if you use AND or OR). See Query the WinINSTALL Database (“*”), below.
• -m +[ad-search-filter][::column] Uses Active Directory to search for machines to which to deploy. See Query Active Directory (“+”), below for full details.
-n <count> • Limit the Active Directory search to <count> machines.
-p <password> • Supplies the password - if needed - for the database connection string
-q • Shows no progress messages (Quiet Mode)
-r • Suppresses automatic reboot if required
-s • Shows the contents of the SMD (Secure Manual Deployment) file
-t <threads> • Specifies the number of simultaneous remote deployments to perform.
-u • Monitor the progress of each remote deployment.
-w <seconds> • Waits the specified number of seconds between deploying the agent to machines (simple form of bandwidth throttling)
-x • Simulates deployment instead of actually deploying the Agent, to verify the machine selection.
-? • Shows help
T H E W I N I N S TA L L A G E N T S Agent Deployment
4
Three variations on the WIDeploy.exe -m switch facilitate this type of automated deployment operation:
Q U E R Y T H E W I N I N S T A L L D A T A B A S E ( “ * ” ) “*” indicates a SQL query of the WinINSTALL database. By default, this switch returns all machines in the database which are marked as not having the WinINSTALL agent deployed. SQL syntax can further limit the list of returned machines to a specific subset.
D E P L O Y T O A L I S T O F M A C H I N E S ( “ @ ” ) “@” indicates an XML file, which contains a list of machines to deploy to, in the following format:
<?xml version=”1.0” encoding=”utf-8”?>
<MachineList>
</MachineList>
Q U E R Y A C T I V E D I R E C T O R Y ( “ + ” ) “+” indicates an Active Directory query. Further details on AD deployment follow below.
The AD query option uses AD query syntax to search the directory.
In all of these cases, what is found is automatically filtered by whether the machines are already in the database and deployed. Machines already listed as deployed will not be included in the deployment.
In its simplest form, “-m +” would search AD for all computers, check the database to make sure they're not already deployed, and do the deployment as is done for SQL- and XML- selected machines automatically.
. . .
But the Active Directory option provides additional capabilities: “-m +” uses Active Directory to search for machines to which to deploy. The general syntax is:-m +[ad-search- filter][::column]
By default, the entire AD tree is searched for computers, and any that aren't already in the database are candidates for deployment. The “ad-search-filter” is an AD/LDAP filter in RFC2254 form that can be used to qualify the machines selected. The “column” can specify a column to be used for the hostname, and defaults to “dNSHostName.” Typically, the column would only be specified in cases where you don't want deployment to use the fully qualified DNS name for the machine, in which case “cn” would be specified.
If no filter is specified, “(&(objectCategory=computer))” is used to select any machines in the forest. If a filter is specified, it will be added to the default so that in no case will anything other than machines be selected. For instance, “-m +cn=a*” would select any machines that began with the letter “a” (resulting in a filter of “(&(objectCategory=computer)(cn=a*))”). The context of the search is determined by the login account, so that if the user is logged in to a sub-domain, o

WinINSTALL 8.70.03 Desktop Management Suite and Desktop

Text of WinINSTALL 8.70.03 Desktop Management Suite and Desktop

Wininstall Macromedia Flash

VERITAS WinINSTALL 7...know how to use WinINSTALL. Support for Transforms (.mst files) and Patches (.msp files) You can now create transforms through the Discover program, and you

Desktop Suite GuiXT Portal SuiteWeb UI Suite

WinINSTALL 8.7 Desktop Management Suite and Desktop

Service Information - Cisco Desktop Product Suite 4.5 (ICD) · cisco desktop product suite 4.5.5 (icd) customer order number: text part number: ol-4205-02. the specifications and

WAVE Desktop Communicator Data Sheet · WAVE COMMUNICATOR APPLICATION SUITE WAVE Mobile Communicator PTT on the Go WAVE Desktop Communicator Communication Console WAVE Advanced Desktop

CLOUD DESKTOP - 5G Networks€¦ · CLOUD DESKTOP Desktop as a Service. Parameter Details Microsoft Office 365 Plans Full Microsoft 365 Product Suite: Windows 10 Enterprise, Exchange,

WinINSTALL MASTER DOCUMENT - Eddieeddiejackson.net/web_documents/WinINSTALL_MASTER_DOCUME… · MSI Error Codes MSI Error Codes ... LANDesk, Manually . WinINSTALL ... 6/28/2011 WinINSTALL_MASTER_DOCUMENT.doc

SV8100 Desktop Suite Release 4 October 2011

Desktop Backup v7 Quick Start Guide for Windows Desktop ... › manuals › windows-desktop.pdf · AhsayACB is the name for our Desktop backup suite 7 Run Backup Jobs Login to AhsayACB

Web ADI: Extending the E-Business Suite with Desktop ...arunmudragada.weebly.com/uploads/1/6/4/1/1641261/webadi.pdf · Extending the E-Business Suite with Desktop Applications

UNIVERGE® SV8100 Desktop Suites. NEC Confidential What is Desktop Suite? The SV8000 Series Desktop Suite is for use on the SV8100 Communications Server

NEC Desktop Suite User Guide - ECI - Empire · PDF fileNEC Desktop Suite User Guide ... Dial their number or press their Presence Button to get them on the line. 2. Next, press the

Desktop Integration Suite (DIS) Master Note.pdf

Desktop Suite Manual(English)

NEC Desktop Suite

AI Suite 3 User Guide 200 Series - Asus · 4 ASUS 200 Series AI Suite 3 Launching AI Suite 3 Windows® 7 OS From the Desktop, click or tap Start > All Programs > ASUS > AI Suite 3

SL1000 - Sales Support Training - Desktop Suite 3 © NEC Nederland B.V. 2011 SL1000 Sales Support Training Overview Desktop Suite is an Intuitive, Desktop Application that will help

Desktop Suite GuiXT Portal SuiteWeb UI Suite · Desktop Suite GuiXT Portal Suite Web UI Suite Mobile Suite Offline Suite Developer Suite 950 Tower Lane, Suite 750 Foster City, CA

(GD)SL Desktop Suite

Desktop Integration Suite Installation Guide · Desktop Integration Suite Installation Guide ... Additional Steps for Domino Administrators ... Content Server version 6.2, 7.1.1,

Atelier 4 : Introduction au WebMapping Du code … à la Carte - Introduction au web... · ArcGis On Line * Intégration complète à la suite ArcGis * Suite mobile, desktop, tablette

Campus Wide Microsoft Agreement for Desktop Suite Education Enrolment Solutions (EES agreement)

Oracle® E-Business Suite...Oracle E-Business Suite Desktop Integration Framework Developer's Guide, Release 12.2 Part No. E22005-10 Oracle welcomes customers' comments and suggestions

Desktop Integration Suite User Guide€¦ · Desktop Integration Suite 10gR3 has the following new features and enhancements (compared to version 7.7): This version of Desktop Integration

SOLIDWORKS ELECTRICAL SUITE€¦ · SOLIDWORKS Systemanforderungen finden Sie auf der SOLIDWORKS Website. SOLIDWORKS ELECTRICAL SUITE * Enthalten in SOLIDWORKS Desktop Professional

SL1000 - Sales Support Training - 08 - Desktop Suite

Certified Desktop and Network Specialist (CDNS) Student_Package.pdf · 529 Hahn Ave. Suite 101 ¨ Glendale CA 91203-1052 ¨ Tel 818.550.0770 ¨ Fax 818.550.8293 ¨ Certified Desktop

LANDesk Management Suite Our Desktop Support System

OOW15 - Standards-Based Desktop Integration in Oracle E-Business Suite

Documents

WinINSTALL 8.70.03 Desktop Management Suite and Desktop

Text of WinINSTALL 8.70.03 Desktop Management Suite and Desktop