Download the Flash player at www.macromedia.com.
Home
Solutions
Solution Archives
Software Products
Site Search

 

03-Apr-05, ZWDynaUser Article posted! (Pt. 1)

28-Mar-05, Windows Process Authority article posted!

28-Mar-05, ZWXPDrive article posted!

22-Mar-05, ZENworks Enhancement Software Posted!

22-Mar-05, Site Updated!

!SNAP TO IT!

A snapshot is a method used by ZENworks to capture all file, ini, text, and registry changes made to a workstation during the install of a software package. ZENworks is then able to duplicate those changes on client workstations which result in the package being fully installed and configured on the client machine. This allows programs to be installed with little or no user interaction and without requiring any special rights by the user. This is very useful for deploying software, which normally requires administrative rights to install to users who do not have administrative rights

I have broken the SNAPSHOT and APPLICATION CREATION two main parts. Part A describes the process of creating the AOT file, which defines all the changes that need to be made to the client workstation. Part B describes the process of converting the AOT file into an Application object to be delivered to the client workstations.

PART A

  1. Creating a Clean Machine
  2. Performing the Initial PC Scan
  3. Installing the Software
  4. Tweaking the Software
  5. Performing Final Scan of Software
  6. Common Snapshot Troubleshooting

PART B: Creating an Tweaking the Application Object

BONUS SECTION: Tips, Tricks, and Pitfalls to Avoid!

Creating a Clean Machine:

  1. This machine should have the oldest32-BIT OS possible. (Do Win3.x Separate)
  2. The machine This machine should have the minimum number of OS patches with the oldest Novell client that you may have on your network.
  3. This machine should not have ANY software currently or previously installed on the box.
  4. Use a product such as "Drive Image" or "Ghost" to restore your "Clean" machine to a pristine state before each snapshot.

My Personal clean machines are a "Windows 95A W/SP1 and Novell Client 2.5" installed and a "Windows NT 4 W/SP3 and Novell Client 4.11" installed. Avoid installing Workstation Manager on the PC to prevent accidental software pushes to the "Clean" PC.

I use the Windows NT box for any software that will be deployed only to NT workstations. I use the Windows 95 box for any software that will be deployed only to Windows 95 boxes or to both Win95 and WinNT boxes.

Performing the Initial PC Scan:

  1. Boot PC
  2. Login to PC – Do not run any login scripts (This prevents accidental software installs.)
  3. Manually Map any desired Network drives to be used for running snapshot or installing software and set them to permanent.
  4. Run file \\Server\Public\Snapshot\snapshot.exe"
  5. Select "Standard" Snapshot
  6. Enter an NDS Object Name. This is the name of the object in the NDS that will be created with the AOT is imported.
  7. Enter an Application icon title. This is what will appear under the Icon on users desktops. If this field is left blank, the value will default to the NDS Object Name. Select "Next" to continue.
  8. Enter the File location for the file updates to be placed. This can be either be a network location or a local location (Which means copying them to a server later.) Select "Next" to continue.
  9. Select Yes to create the "directory" for your snapshot.
  10. Select Next to accept the default name for the AOT object.
  11. Select drives snapshot needs to scan. These drives should be the "Boot Drive", the drive containing Windows, and the drive to which the software will be installed if it is a local drive. DO NOT ADD THE NETWORK DRIVE TO WHICH YOU INSTALL SOFTWARE. This will cause each person who installs the software to try and update the network copy of the software, which is clearly unnecessary.
  12. Select "Next" to proceed past the "Drive Scanning" options and the select "Next to begin the initial Scan of the PC."

Installing the Software

  1. Install the Software. Select the "Run Application Install" tab to run the setup program. You may also run the program from explorer or a command prompt.
  2. Reboot Now. (Select "Yes" to shutdown now when prompted by snapshot. Login once again without running any login scripts after the PC has rebooted. Select to complete the snapshot when prompted after logging back into the network. If snapshot does not auto-restart, just rerun snapshot.exe and then select the option to complete the previous snapshot.)

Tweaking the Software

  1. The Final step is to configure the software as you want it configured.
  2. Start the application and configure all the options you want configured
  3. Loading a couple files so they appear under the recent file list may also help in some cases.

Performing the Final Software Scan

  1. From the Snapshot window, select the next button to begin the capture all the changes.
  2. The Snapshot program will now run for a few minutes and capture all the changes made.
  3. Select Finish to Complete the Process

Common Snapshot Troubleshooting

  1. On occasion the snapshot process does not run or complete properly.  Though this is a very rare occurrence, and the  steps mentioned do not normally need to be taken
  2. The first tip is to save the comparison files to the local PC.  Once the snapshot is complete, they can be saved to the network.
  3. If the first tip does not help, snapshot can be started with the /SLOW parameter.  This usually resolves any other problems that occur with the snapshot program.  The /SLOW parameter does cause the snapshot to run quite slow and should only be used when necessary.  

(Note: I am note aware of any other switches than /SLOW for snapshot) 

PART B: Creating an Tweaking the Application Object