Summary:

Cloning software such as Symantec's GHOST and PowerQuest's DriveImage are excellent companion products to New Boundary Technologies’ packaging and deployment products. Use cloning software to quickly build a base Windows system. Then use Packages to easily and accurately install applications and customize the environment.

Recommendation:

Download and evaluate Prism Deploy from http://www.newboundary.com/. In addition to New Boundary Technologies’ award-winning packaging technology, Prism Deploy includes a deployment console that can be used to deploy packages to newly imaged machines that have been grouped to your specifications. For example, you could create functional groups such as Accounting or Human Resources, or geographic groups such as San Francisco Office and San Jose Office. Then deploy the appropriate packages through the Console to the groups you created.    

Alternate Solution:

This technical note simulates the environment where an administrator uses cloning software to install a base operating system and then uses Packages to install specific applications and customizations. In addition, it discusses using Pictures to backup user customizations such as new icons, screen savers, wallpaper, application preferences, etc. 

If the workstation needs to be rebuilt, the next time the user logs in the application Packages will be downloaded and the last backup Picture will be applied to restore the user’s preferences. 

This technical note assumes that users log in to a NetWare server and the System or Container login script is implemented.

Getting Started

The first step is to create your operating system image. Install a clean build of the operating system to standardized hardware. Configure the environment and install the base applications that every user needs to have. When you're satisfied with the build, create an image using your cloning software, and store the image on a server or CD for later use. 

Next, create your Packages and Pictures. Create Packages to install a specific environment. For example, create an Accounting suite of packages, or an Engineering suite, etc. Create Packages (using any of the New Boundary Technologies packaging products) for each application, printer and other customization you want to distribute to users. Store these files on your server where users have access. (Refer to your User’s Guide for information on creating Pictures and Packages.)

Rolling out Packages

We created NetWare groups for each Package we wish to distribute. For example, we created an Office2000 group for users who need access to the MS Office2000 suite. Then we edited the Container login script such that if a user is a member of a group, an environment variable is set. This variable is later referenced in a Prism or PictureTaker script. 

IF MEMBER OF "OFFICE2000" THEN
SET OFFICE2000="1"
END

IF MEMBER OF "VISIO" THEN
SET VISIO="1"
END

You may want to create groups based on the department to which each user belongs. For example, if all Accounting users get the MS Office Suite, a payroll program, and access to an HP5 printer, set up your login script as follows: 

IF MEMBER OF "ACCOUNTING" THEN
SET OFFICE2000 = "1"
SET PAYROLL = "1"
SET HP5ACCTING = "1"
END 

We then created a group called "PRISM" such that if the user is a member, a Prism (or PictureTaker) script runs that installs the above applications. Add the following to the login script after the environment variables are set: 

IF MEMBER OF "PRISM" THEN
MAP ROOT K:=\\NW5\SYS\PRISM
#K:\PACLIENT.EXE /PS K:\SCRIPTS\MASTER.PTS
END 

[NOTE:  If using Prism Deploy or PictureTaker, change PACLIENT.EXE references to PTCLIENT.EXE.] 

MASTER.PTS is the Prism Pack script that installs the applications by applying Packages. We created MASTER.PTS in a Prism Pack directory on the server. Refer to the Prism Pack User’s Guide for more information. 

REM Set the location of the Prism Pack log file to the user's home directory.
/DLF H:\PICTAKER.LOG

REM Install the appropriate Packages based on group membership.

IF X%OFFICE2000% == X1
REM User is a member of the Office2000 group
REM Install Office2000 Package
/IP K:\APPS\WIN2K\OFF2000.PWC /ONCE
END IF

IF X%VISIO% == X1
REM User is a member of the Visio group
REM Install Visio Package
/IP K:\APPS\WIN2K\VISIO.PWC /ONCE
ENDIF 

[NOTE:  If using PictureTaker, change /IP references to /AF.]

Making Backups of User Customizations

Users are bound to make customizations to their environment and they may even be storing files on the workstation. Use the New Boundary Technologies products to take Pictures to backup these customizations and store them on the server. If the workstation needs to be rebuilt, the Picture can be installed to restore the user’s changes. 

We created a batch file called BACKUP.BAT which runs from the login script on our server. The purpose of the file is to create up to two backup files and store them in the user’s home directory. Then cycle the files such that a new Picture is created at each login, but an older backup Picture remains as a precaution. The batch file is as follows: 

REM This file creates backup Picture files
REM Two Backup Pictures are created BACKUP1.PWF, BACKUP2.PWF. The files are cycled so

REM that BACKUP2 is the most recent Picture. If the workstation needs to be rebuilt
REM BACKUP2.PWF is automatically applied.

:BACKUP2
REM CHECK FOR EXISTENCE OF FILE BACKUP2.PWF
IF EXIST H:\BACKUP2.PWF GOTO COPYFILES

:BACKUP1
REM CHECK FOR EXISTENCE OF FILE BACKUP1.PWF
IF EXIST H:\BACKUP1.PWF GOTO CREATEFILE2 

:CREATEFILE1
REM CREATE FILE H:\BACKUP1.PWF FOR THE FIRST TIME
K:\PACLIENT.EXE /TP H:\BACKUP1.PWF K:\USERBACKUP.PWI
GOTO FLAG

:COPYFILES
DEL H:\BACKUP1.PWF
REN H:\BACKUP2.PWF BACKUP1.PWF
GOTO CREATEFILE2 

:CREATEFILE2
K:\PACLIENT.EXE /TP H:\BACKUP2.PWF K:\USERBACKUP.PWI
GOTO FLAG 

:FLAG
IF EXIST C:\FLAG.TXT GOTO END
COPY K:\FLAG.TXT C:\
:END 

This batch file references a USERBACKUP.PWI. This is a Prism Pack file that defines what information will be included in the Picture. We determined what needed to be included in the Picture to effectively backup these settings by setting up a workstation with the base OS and applications. We took a Picture using the "Baseline Picture" option. We then simulated actions of a typical user by changing the wallpaper, defining a screen saver, customizing application settings, saving documents, and performing other tasks a user may complete. Prism Pack was used to Find Changes. We then examined the Package and noted where the changes were located (in the registry, local directories, INI files, etc.).

We decided to include the following information in our backup Picture: Windows Desktop, Start Menu and Start Menu Programs, INI Files, Recent Documents, Registry (Current User), and we added two directories where users may save files. 

The PWI file is created by launching Prism Pack or PictureTaker and taking a Customized Picture. We then specified the information to store and selected Save.

Automating the Rebuild

The purpose of doing backups of user configurations is to be able to restore this information if the workstation ever needs to be rebuilt. To reduce administrative interaction we have designed a rebuild process that will happen automatically. The first time the Backup batch file runs for a user, a flag file is created on the workstation. (See BACKUP.BAT above.) We have added a section to the MASTER.PTS file that searches for the existence of the flag file. If the file doesn't exist (i.e., the workstation has been recently built and this is the first time the user has logged on from this workstation), the script will then search for the existence of BACKUP2.PWF. If found, the BACKUP2.PWF file will be applied. The logic is as follows: 

If c:\flag.txt exist = false
and
If h:\backup2.pwf = true
then
install h:\backup2.pwf

The following section was added to the bottom of the MASTER.PTS Prism (or PictureTaker) script. 

REM Check for existence of flag file. If it exists, the workstation does not need to be rebuilt.
IF NOT EXISTS C:\FLAG.TXT
REM check for the existence of H:\BACKUP2.PWF
IF EXISTS H:\BACKUP2.PWF
REM Apply most recent backup file
/IP H:\BACKUP2.PWF
ENDIF
ENDIF

Once all the scripts have been created, you are ready to implement. Please note that the scripts can be enhanced and modified to work with your environment. Feel free to contact the Support Center to share your ideas. We appreciate any feedback you may have.

New Boundary Technologies Support Center
support@newboundary.com
612-379-1851