To set up a software package for distribution, perform the following tasks in order:
If you want to manage your software packages from multiple workstations, do the following in order to set up managing the replication of a master copy of the snapinprefs.ser file to multiple workstations; otherwise, continue with Section 5.4.2, Creating a Server Software Package.
For the following instructions, select any workstation that you use for managing software packages. If you have already created software packages using a workstation, select that workstation so you do not lose any software package information stored in the workstation’s snapinprefs.ser file.
Map a drive to the server where you want to store your .spk and related .cpk files.
This drive letter should be one that can be used by all of the other workstations you use to manage software packages. This drive letter is written to the snapinprefs.ser file as part of the path information for each listed .spk file, so it should be a fixed drive letter that all workstations use.
The drive letter is also used in the batch file that you use to start ConsoleOne, which provides each workstation access to the same .spk file locations.
If you already have Server Software Package objects created by this workstation, skip to Step 5.
or
If you have not yet created any Server Software Package objects using this workstation, start ConsoleOne.
This version of ConsoleOne must have the Policy and Distribution Services snap-ins installed.
In the Server Software Package namespace, create a Server Software Package object.
You do not need to fully configure the Server Software Package object at this time. Just give the package a name and provide a location and filename for the .spk file. Make sure you use the drive mapping you used in Step 1.
For information on creating software packages, see Section 5.4, Setting Up Server Software Packages.
Exit ConsoleOne.
This step is important to make sure that the snapinprefs.ser file is created for this workstation.
On the network server you use to store the master copy of the snapinprefs.ser file, create a directory named \C1 at the root of the drive.
You can select any safe location on the server for the master snapinprefs.ser file.
The batch file sample provided below uses a directory named \C1. You can modify the batch file if you want to use a different directory name, and you can include path information; however, do not use variables for the root location.
For example,
\zenworks\clssp
could be used to replace the \C1 directory name.
Copy the workstation’s snapinprefs.ser file from:
c:\documents and settings\user_ID\.consoleone (Windows 2000)
to the \C1 directory on the network server.
This becomes the master snapinprefs.ser file that is updated with new .spk paths, provided you are using the batch file documented in Creating and Using the ConsoleOne Batch File.
Continue with Creating and Using the ConsoleOne Batch File.
Review the following sections to understand, create, and use the batch file:
@echo off REM map a network drive net use m: \\server1.servers.novell.com\vol1 REM create a backup copy of the workstation’s .ser file copy "%USERPROFILE%\.consoleone\snapinprefs.ser" "%USERPROFILE%\.consoleone\snapinprefs.tmp" REM copy the master .ser to the workstation copy m:\c1\snapinprefs.ser "%USERPROFILE%\.consoleone\snapinprefs.ser" REM start ConsoleOne c:\Novell\ConsoleOne\1.2\bin\ConsoleOne.exe REM batch file control returns after exiting ConsoleOne REM copy the updated .ser to server copy "%USERPROFILE%\.consoleone\snapinprefs.ser" m:\C1\snapinprefs.ser REM restore the backup copy of the workstation’s .ser file copy "%USERPROFILE%\.consoleone\snapinprefs.tmp" "%USERPROFILE%\.consoleone\snapinprefs.ser" REM delete the mapped network drive net use m: /delete @echo on
It maps a network drive for accessing the server where you are storing .spk and .cpk files.
It uses the %USERPROFILE% Windows variable to locate the Server Management \consoleone directory. This variable is also used by Server Management to determine where it creates the \consoleone directory and writes the snapinprefs.ser file.
It creates a backup .tmp copy of the snapinprefs.ser file.
It copies the master snapinprefs.ser file from the \C1 directory on the server to the workstation’s \consoleone directory.
It starts ConsoleOne.
After you have exited ConsoleOne, the batch file copies the updated snapinprefs.ser file from the workstation’s \consoleone directory to replace the version in the \C1 directory on the server. This becomes the new master snapinprefs.ser file.
It restores the backed-up copy of the snapinprefs.ser file from the .tmp file.
It unmaps the drive letter to the server.
Copy the text from the above sample batch file into a text editor.
Replace the m: drive letter with one that each of your workstations has free. Make sure you do this wherever m: exists in the batch file.
Edit the net use m: \\server1.servers.novell.com\vol1 line by replacing it with the path to the server volume or shared folder of the server where you are storing the .spk and .cpk files.
Save the batch file on your workstation and give it a name, such as:
C1SSP.BAT
Copy this batch file to each workstation that you use to manage software packages.
If you installed ConsoleOne to a different location on the workstation than the one indicated in the batch file sample, modify the c:\novell\consoleone\1.2\bin\consoleone.exe line to reflect the location of the consoleone.exe file on the workstation.
You should make this modification in each individual batch file copy on a workstation where the default ConsoleOne path was not used.
This batch file can also be used by a workstation to start an instance of ConsoleOne that is installed on a server. Modify the c:\novell\consoleone\1.2\bin\consoleone.exe line to reflect the location of the consoleone.exe file on the server. Make sure the drive letter is the one being used for accessing the server (see Step 1).
If the \consoleone directory path is different between workstations because the %USERPROFILE% variable was not used, you need to edit any lines containing the variable, as necessary. Open the copy of the batch file on a workstation where the %USERPROFILE% variable was not used and edit the lines containing the variable to reflect the correct path to the \consoleone directory.
If you created a directory other than \C1 on the server, replace \C1 wherever it exists in the batch file with the directory that you specified in Step 5.
The batch file creates a .tmp version of the snapinprefs.ser file. This allows you to maintain the version of the .ser file on the workstation that existed before you used the batch file. However, if you want the workstation’s version to always match the master version it copied to the server, remove the following two lines from the batch file:
copy "%USERPROFILE%\.consoleone\snapinprefs.ser" "%USERPROFILE%\.consoleone\snapinprefs.tmp" copy "%USERPROFILE%\.consoleone\snapinprefs.tmp" "%USERPROFILE%\.consoleone\snapinprefs.ser"
If you cannot use the same drive letter for all workstations, you can use the %1 argument in the batch file, but only if you are using UNC paths for all of your .spk files. To do this, replace all occurrences of m: with %1. Then, when you execute the batch file from a command line, add the drive letter after the batch file’s name. For example,
C1SSP R:
causes the batch file to use R: as the drive for locating the master copy of the snapinprefs.ser file.
Before running this batch file, place a snapinprefs.ser file in the \consoleone directory of each workstation you use to manage software packages. The batch file assumes that the .ser file exists for copying and replacing.
Before running this batch file, place your master copy of the snapinprefs.ser file in the \C1 directory of the server where you have stored the software package files. The batch file assumes that this .ser file exists for copying and replacing.
Run this batch file any time you plan to add, delete, or compile software packages.
You do not need to use the batch file when you view or edit the properties of software packages. The add, delete, and compile functions are the only actions that causes the snapinprefs.ser file to be updated.
Continue with Section 5.4.2, Creating a Server Software Package.
In ConsoleOne, right-click the Server Software Packages namespace, then click .
The Create New Server Software Package Wizard opens.
Read the information on the first dialog box, then click .
Provide a name for the software package.
Make this a descriptive name. It is displayed in ConsoleOne under the Server Software Packages object.
IMPORTANT:Do not use double-byte characters in the software package name. This causes an error in any report you run on the software package.
Because software packages are file-based, provide the full path and filename, including the .spk extension.
If you don’t enter the extension, you are prompted to add it.
You can also use UNC paths.
You can store the .spk files on a workstation or server. The .spk files is typically below 100 KB in size. However, compiled software packages (.cpk files) can be in the hundreds of megabytes. For information on storing .spk and .cpk files, see Section 5.2.9, Managing Server Software Packages.
WARNING:Software package full paths and filenames are drive-dependent. A software package can become unusable if you change drive mappings after creating the package. Make sure your entry in this field is not changed. However, if you used a UNC path, this is not an issue.
Click .
Continue with Section 5.4.3, Configuring the Server Software Package.
After a software package has been created, you need to configure it by setting the prerequisites for installation of the files and applications contained in the package.
To configure a package:
In ConsoleOne, right-click a software package, then click .
The tab should be displayed. If not, select it.
The field should display the name you gave the package when you created it.
Provide a useful description for the software package.
If you don’t want to be able to roll back to the older version of the server file or application after installing the newer version, click . However, this is not recommended.
For information on rolling back software package installations, see Section 5.2.11, Rolling Back Software Package Installations.
Select the tab.
Click , then select a requirement:
Repeat Step 5 for each requirement.
If you want to use variables to customize the installation, select the tab, then click .
Provide the variable name and value.
For information on variables, see Section 9.6, Using Variables to Control File Extraction.
Click when you have finished configuring.
If you click , none of the configuration changes on any of the tabs are saved.
Continue with Section 5.4.4, Creating the Software Package Components.
After you have created and configured a software package, you need to create the components of the package, including the individual files or applications for the package.
To create the software package components:
In ConsoleOne, right-click a software package (in the left pane), then select .
Provide the name of the component as you want it to be displayed in ConsoleOne, then click .
The component is displayed as named under the Software Package object.
Repeat these steps for each component needed.
Continue with Section 5.4.5, Configuring the Software Package Components.
After you have created the software package components, you need to configure the prerequisites for each, including identifying the files or applications for the component.
Package components can each have the same prerequisites, which can save time and minimize user error.
To configure a component:
In ConsoleOne, right-click a component, then click .
The tab should be displayed. If not, select it.
Provide a useful description for the component.
Select a further action for the software package to perform after the installation process has finished from the drop-down list.
To continue configuring the component, see each of the following that you might need to configure:
Do not click on this component’s property page until you have finished configuring all of the above items, as needed.
Click .
If you click , none of the configuration changes on any of the tabs are saved.
Continue with Section 5.4.6, Compiling a Software Package to ready your software package for distribution.
To specify requirements for installing the server files or applications:
While displaying the properties of the software package component, select the tab, then click .
Select any of the following requirement items:
For further instructions on configuring an item, see one of the above items.
Continue with the next item to configure before clicking .
To configure certain NLM files or processes to load or unload before installing the software package on a server:
While displaying the properties of the software package component, select the tab, then click .
Click .
Select one of the following:
For further instructions on configuring an item, see one of the above items.
IMPORTANT:If you select a process to be loaded by the software package, and it is already running on the target server, the package installation fails and is rolled back (if rollback is enabled). If the process requires intervention to unload, you must remember to unload it manually before installing the software package.
To make sure that a process is not already loaded when you are including it in the software package, add an unload option for that process before adding the load option—but only if the process does not require user input from the keyboard to unload it.
Repeat Step 1 through Step 3 for each NLM or process to be included.
Use the arrow keys to arrange the order to execute the NLM files and the processes.
Continue with the next item to configure before clicking .
To configure running server scripts before installing the software package on a server:
While displaying the properties of the software package component, select the tab, then click .
Click .
Provide the script name.
Select the script type (NCF, NetBasic, PERL).
IMPORTANT:NetBasic is not supported on NetWare 6.5 servers.
Enter the script text.
WARNING:If a software package passes all requirements and executes the script, processing done by the script cannot be undone by rollback.
Use the arrow keys to arrange the order to execute the scripts.
Continue with the next item to configure before clicking .
The Local File Copy component enables copying of files on a server from one location to another using a software package. You can either copy or move the files.
To configure the Local File Copy component:
While displaying the properties of the software package component, select the tab.
Click .
Local File Copy #1 is the default name. You can edit that name.
Fill in the fields:
Source path: Provide the full path where the files to be copied are located.
You can use wildcards in the path:
Target path: Provide the full path where the copied files are to be placed.
You can use wildcards in this path. This path does not need to mirror the source path. However, you could mirror an existing target path.
Include subdirectories: Includes all subdirectories and their files beginning from the directory at the end of the path; otherwise, only the files in the directory at the end of the path are copied.
Maintain attributes: Maintains the file attributes in the target’s file system that exist in the source’s file system.
Overwrite Destination Files: Overwrites files of the same name in the destination directories, regardless of differences in file dates. If you do not select this option, files of the same name are not replaced.
Maintain trustees: Maintains the file’s trustee attributes.
When a file is locked: Select one or both:
Retry __ times: Retries overwriting a locked file the number of times you select before failing to replace the file. Leave this check box deselected to not replace locked files on the target file system.
Kill connection of open files: (NetWare only) Attempts to kill the connection of locked files so that they can be overwritten. This applies only to files being extracted, not to files being accessed to build the Distribution. If a file belonging to a Distribution is locked when the Distribution is being built, the build fails. Server and NLM connections cannot be killed.
Error processing: is selected by default. This stops the file copying process when an error is encountered in copying. To continue file copying when an error is encountered, select .
Operation: Sets whether to copy or move the files identified in the field.
Continue with the next item to configure before clicking .
You can configure the Copy File component to control how files are copied during installation of a software package. This includes adding files to existing directories, creating new directories, adding files and subdirectories to the new directories, and deleting existing files and directories.
A file group is a root item for the component’s expandable tree structure. You can have multiple file groups for the Copy File component. A file group is a set of related directories and files. File groups are top-level items and cannot contain other file groups.
The other structure items are directory and file, which are contained within a file group. Directories can contain other directories or files, but not file groups.
IMPORTANT:When you add a file group or directory, you are creating the target paths where the files are to be copied, not the source paths of the files. The source paths are automatically accounted for as you select your source files or directories.
To configure copying files during installation of the software package:
While displaying the properties of the software package component, select the tab.
To create your first file group, do the following:
Click the down-arrow on the drop-down list next to the button, select , then click .
Because files and directories must be contained within file groups, you are prompted to create a file group the first time you click , regardless of the type you are attempting to add.
You should create one file group for each specific target location. For example, c:\files, c:\data\accounting, and c:\data\personnel could be different locations on a C: drive where you want to copy different groups of unrelated files.
Name the file group, then provide its target path.
The file group’s target path specifies the base path from where all directories and files within the group are installed.
To specify what to do when a file group location is locked, select the check box for one of the following:
1. Retry (enter the number of retry times) 2. Kill Connection of Open Files (NetWare only) 3. Fail With Error
Retries are about 5 seconds apart. Therefore, 12 retries would take about one minute.
To create a target directory under a file group or another directory, select the file group or directory, in the drop-down box select , click , then do the following:
Because Directory is the default directory name, to rename the directory, right-click , click , type the desired directory name, then press Enter.
When entering information into this field, you must press Enter for the change to be saved.
To match an existing target directory for deleting or copying files, you must enter the exact name.
IMPORTANT:If you provide an existing directory name and that directory is marked as Read Only on the destination server’s file system, the Software Package Distribution fails when the Subscriber tries to extract the Distribution, because it cannot write to that directory. Therefore, you must know the attributes of existing target directories and remove their Read Only directory attributes.
You must create the same directory structure in the File Copy component as exists in the target location so that the directory name you provide here is in the same sequence in the path.
To determine whether to create or delete the directory, select the mode from the drop-down list.
Create: If you select and the directory does not exist, the directory is created. If you select and the directory does exist, the directory is not created, and no error is encountered.
Delete: If you select and the directory exists, the directory is deleted, including any subdirectories and files under it. If you select and the directory does not exist, the directory is not deleted, and no error is encountered.
WARNING:If you plan to set the as Delete for any directories you add, and you do not want any parent directories that you have added to also be deleted, place those parent directories in the field of the file group. For example, if you want to delete c:\winnt\cookies, but do not want to delete the \winnt directory, enter c:\winnt in the field, click to enter the \cookies directory in the tree structure, then click for the field. For example:
Target = c:\winnt
Tree structure = cookies
causes only cookies and all of its files and subdirectories to be deleted.
Conversely, both the \winnt and \cookies directories are deleted if you enter c:\ in the field, click to enter the \winnt directory in the tree structure, click to enter the \cookies directory under \winnt in the tree structure, then click for the field.
For example:
Target = c:\
Tree structure = winnt\cookies
causes winnt and all of its files and subdirectories to be deleted.
To add files or source directories under a file group or directory in the tree structure, select a file group or directory, in the drop-down box select , click , then do the following:
Select the files or directories using the Open dialog box.
These directories and files are displayed directly under the file group or directory you selected in Step 3.
For the destination server’s file system, attributes of the copied files and directories are not maintained. For more information, see Step 4.c.
If you selected a directory on the Open dialog box, it is not displayed expanded. Click the plus signs to expand the existing structure under the directory that you added.
In the Open dialog box, the Recurse Directories option is selected by default. To only select files in this directory, select the Recurse Directories check box to disable it and none of the subdirectories are selected.
To exclude files or subdirectories from being selected, select the Exclude Selected Subdirectory option, select the files or directories to be excluded (use Shift and Ctrl for multiple select), then click Open.
If you exclude files or subdirectories, it does not remove them from the file system. It only prevents them from being selected.
For information on removing files or subdirectories from the tree structure after adding files and directories, see Step 8.
To configure a subdirectory that was added, do the following:
Select the subdirectory, then select the (whether to Create or Delete the directory).
WARNING:When you set the to Delete, it causes deletion of the target directory and all of its files and subdirectories.
To rename a subdirectory that was added, right-click the subdirectory, click , type a new directory name, then press Enter.
When entering information into this field, you must press Enter for the change to be saved.
If you rename a directory that was selected through the Open dialog box, make sure that the new name meets your expectations for the target location.
Because only selected files have their path remembered for copying, renaming a directory does not affect file selection. In other words, you can give a target directory a different name than its source, and still have the same files copied under it.
To configure an added file, select the file, then do the following:
To determine the file’s copy mode, select a mode from the drop-down list.
You must select an option for every file. You can select multiple files where you want the mode to be the same.
The options are: Copy Always, Copy If Exists, Copy If Does Not Exist, Copy If Newer, Copy If Newer and Exists, and Delete.
WARNING:When you set the to Delete, it causes deletion of the selected file from the target server.
Select the check box for each attribute that should apply to the selected files.
Attributes do not default. You must set them for the destination server. They are not carried over from where you obtained the file.
IMPORTANT:Do not select all of the attributes for a file, or an exception is thrown on the server.
When setting the attribute of an executable file, set it to Read Only. Do not set it to Execute. If you mark a file as Execute, the NetWare® CLIB API does not allow you to change it to a different attribute. To change the attribute from Execute to Read Only after the software package has been installed, you need to manually delete the file, replace it, then set its attribute again.
To create another file group, do the following:
Click the down-arrow on the drop-down list next to the button, select , then click .
It doesn’t matter what you have selected in the tree structure; the file group is automatically placed at the first tree level, equal to any other file groups that are displayed.
Name the group.
Provide its target base path.
To indicate what to do when a group location is locked, select the check box for one of the following:
1. Retry (enter the number of retry times) 2. Kill Connection of Open Files (NetWare only) 3. Fail With Error
Repeat Step 5 or each additional file, directory, or file group to be added.
If you want the file groups to be copied in a particular order, use the arrow keys to arrange the order of the file groups.
The arrows are dimmed if the file group you have selected has no valid up or down movement available to it.
To remove a file group, directory, or file, select it, then click .
You can use the button to prune the tree structure of unwanted files or directories.
You can use the Shift and Ctrl keys to select multiple items for removal.
IMPORTANT:If you remove a file group or directory, all files and directories displayed below it are also removed, but only from this tree structure, not from the source file system.
Continue with the next item to configure before clicking .
To configure making changes to text files during installation of the software package:
While displaying the properties of the software package component, select the tab.
Click .
After one text file has been added, you are given the opportunity to select whether you are adding another text file or adding another change item for the selected text file.
To add another text file: Select . It does not matter which text file or change item is selected in the left pane—the text file is added to the far left level.
To add another change to a text file: In the left pane select the text file for the change, click , then select . The change item is added under the selected text file.
If you are adding a text file, provide the name of the text file.
Accept the default name (such as Change #1) or rename it.
If you are adding a text file, click .
Click the down-arrow for the field, then select the change mode from the drop-down list.
Click the down-arrow for the field, then select the search type from the drop-down list.
Enter the exact search string.
Select the check box if you want the string search to be case sensitive.
To find all occurrences of the search string, select the check box (default); otherwise, deselect the check box to find only the first occurrence.
Click the down-arrow for the field, then from the drop-down list, select the action that should result if a string is matched.
If you are replacing a string or entering a new one, enter the text in the text box.
Repeat Step 2 through Step 11 for each text file to add or each change to be made.
To reorder the text files and change items, use the arrow keys.
Continue with the next item to configure before clicking .
For NetWare only.
To configure the target server’s SET commands:
While displaying the properties of the software package component, select the tab.
Click to open the NetWare Server SET Commands Wizard.
Select the server containing the SET commands, then click .
IMPORTANT:The Server Management and Java must be running on the server where you want to obtain the SET commands.
Select all of the SET commands you want to configure for the target server.
You can select whole categories by selecting the check box for the category, or click the plus sign to expand a SET command category and select the check boxes for individual SET commands to be included.
WARNING:Do not select the Set Developer Option SET command and change Off to On. This parameter is meant to help developers debug server abends. It disables some operating system checking to prevent certain abends from occurring. Also, if the Set Developer Option is enabled, running NCP™ scripts that require keyboard entry could abend the server.
Click when you have completed selecting SET commands.
The selected SET commands are now displayed in the tab for the file or application component.
To edit a SET command, click its plus sign to expand its attributes.
To edit an attribute, select the attribute, then click .
A dialog box is displayed where you can make changes to the attribute.
Repeat Step 7 for each attribute to edit for a given SET command.
Repeat Step 6 through Step 8 to edit another SET command’s attributes.
Continue with the next item to configure before clicking .
To configure registry changes for either NetWare or Windows servers:
While displaying the properties of the software package component, select the tab, then click HKEY_LOCAL_MACHINE.
HKEY_LOCAL_MACHINE is a Windows registry key. For NetWare, HKEY_LOCAL_MACHINE is also recognized by Server Management as the equivalent to My Server. Therefore, you can use this key for editing both NetWare and Windows registries.
Click .
Select from the following:
For further instructions on configuring an item, see one of the above items.
Repeat Step 2 and Step 3 for each registry entry to be made.
Use the arrow keys to arrange the order in making registry entries.
Continue with the next item to configure before clicking .
For NetWare only.
The products.dat file can be updated by your software package so that future updates can identify the most recently installed version of the file or application.
WARNING:Modifying products.dat could prevent something from running or being installed on the NetWare server. Never modify any entries supplied by Novell.
To determine which action to take for products.dat:
While displaying the properties of the software package component, select the tab.
Select one of the following:
If you selected :
Provide the ID of the item to add.
This is case sensitive. The item is the ID of the new product for the .dat file.
Provide the exact version number to add.
Provide the description to add.
If you selected :
Provide the ID of the item to search for (case sensitive).
Provide the new version number.
Provide the new description.
If you selected :
Provide the ID of the item to search for (case sensitive).
Provide the exact version number to match.
Provide the new ID.
Provide the new version.
Provide the new description.
Continue with the next item to configure before clicking .
To configure certain NLM files and processes to load or unload after installing the software package on a server:
While displaying the properties of the software package component, select the tab, then click .
Click .
Select one of the following:
Select an item for further instructions on configuring it.
Repeat Step 2 and Step 3 for each NLM or process to be included.
Continue with the next item to configure before clicking .
To configure running NetWare server scripts after installing the software package on a server:
While displaying the properties of the software package component, select the tab, then click .
Click .
Provide the script name.
Select the script type (NCF, NetBasic, PERL).
IMPORTANT:NetBasic is not supported on NetWare 6.5 servers.
Enter the script text.
WARNING:If a software package passes all requirements and executes the script, processing done by the script cannot be undone by rollback.
Use the arrow keys to arrange the order to execute the scripts.
Continue with the next item to configure before clicking .
Your software packages (.spk files) cannot be installed by Policy and Distribution Services until they have been compiled and have the .cpk extension.
To compile a software package:
In ConsoleOne, right-click a software package, then click .
The Compile Server Software Package Wizard opens.
Read the information on the first dialog box, then click .
Provide a name and path for the compiled software package (using the .cpk extension), then click .
Select a location where free disk space is adequate for the .cpk file. Compiled software packages (.cpk files) are generally much larger than the uncompiled (.spk) counterparts.
IMPORTANT:If you provide the path and filename of the .spk when prompted for the compiled (.cpk) filename, the .spk is overwritten and can no longer be edited. Therefore, be sure to use the .cpk extension when naming the compiled version.
The compiling process could take some time, depending on how many files are involved.
When compiling has completed, click .
Continue with Section 5.4.7, Distributing the Software Package to distribute your software package (.cpk).
After a software package is ready for distribution, you can distribute it in the following ways:
Use Tiered Electronic Distribution (see Section 3.0, Tiered Electronic Distribution for instructions on distributing through Tiered Electronic Distribution)
Manually copy the software package file (.cpk) to the server and run it from the server’s console prompt using the PACKAGE command (see Section C.0, Server Console Commands for instructions on using the command)
After a software package is installed on a target server, you might need to reboot the server. For example, if ted.cfg is modified by the package, it cannot be downed—you must reboot the server to run that NLM again. However, you could have the software package cause the server to come down and restart automatically.