Tivoli Software Distribution Installation and Configuration

Goto the Tivoli Home Page
This page details problems and issues relating to the Installation and Configuration of Tivoli Software Distribution.

"'/lcf_bundle//bin/w32-ix86/TME/SWDIS/SPDE/spd_eng' not found" error when distributing software

I've installed a Managed Node/Gateway, but whenever I try to distribute software to any of the Endpoints logging in through the Gateway I'm seeing the following error message at the end of the package log file:

FRW:TASX:0004
05/24/02 02:43:19 PM (4): resource `c:/progra~1/Tivoli/bin/lcf_bundle//bin/w32-ix86/TME/SWDIS/SPDE/spd_eng' not found

Contributed By: Cliff Hobbs [MVP SMS], Dave Remkus
 This problem is down to the fact you don't have the Software Distribution Gateway component installed on the Managed Node.  You can use the "wlsinst -ah" command to check which Tivoli components are installed where. If the Software Distribution Gateway isn't installed on the Managed Node in question then install it and any necessary Gateway patches for the version of Software Distribution you are using (such as 4_0-COU-0017, 21, 27 and 29).

 You then need to verify that the Endpoint version is version 80 or later (load a browser on the Endpoint then type "http://127.0.0.1:9495" in the "Address" field and press [RETURN] to display the "TMA Daemon Status Page").  As Software Distribution 4.x uses the dependencies in the "lcf_bundle.40" directory, if the Endpoint isn't running at least version 80 then the Gateway attempts to load the dependencies from the "lcf_bundle" directory which aren't populated for Software Distribution 4.x.
 

"An instance named "SwdistCMSTATUSupport" of resource "distinguished" was not found" message in the Package log

I'm seeing the following message in the log file of my packages:

DIS:SENG:0175
The following warning messages occurred before the distribution was submitted:
-> FRWTT0003E An instance named "SwdistCMSTATUSupport" of resource "distinguished" was not found.

Contributed By: Cliff Hobbs [MVP SMS]
 You will see this error message if you don't have the Software Distribution Historical Database component installed or it is installed but disabled.  By default, Software Distribution works in Distributive mode which means each time you ask Software Distribution to perform an action an entry is made in the log file before the action is submitted to Tivoli and again when the operation is completed.

 Further information on Software Package Log files and how Tivoli uses them can be found in the "Software Package Log" section of the Software Distribution 4.1 (April 20, 2001) Release Notes.
 

Can I Use Wake-On-LAN for Software Distribution?

I've seen various discussions on the list about using Wake-on-LAN for Software Distribution. It seems that waking the machine up works quite well but I was wondering (apart from the obvious), how you shut a machine down once you've woken it up?

For example, if I set my software distributions to run at say midnight and I wake a whole bunch of machines up, how do I shut them down once the distribution has completed or can't I?

Contributed By: Jason Cordell, Cliff Hobbs [MVP SMS]
 Tivoli doesn't provide functionality to shut a machine down once it's woken it up.

 You can use SHUTDOWN.EXE from the NT Resource Kit - usage:

shutdown.exe \\%computername% /c /y /l /t:00

c - forces all running applications to close. NT will not save data in any open application.
y - answers all questions with "yes".
l - specifies a local shutdown
t:00 - specifies a time of :00 before shutting down.

I have never tried this on Windows 95/98 workstations, but I use this all the time on NT4/Windows 2000 systems.
 

"Cannot reserve <value> KB in the depot. The segment file is too large" Error when trying to Distribute Software

I'm trying to distribute software to my Endpoints but it doesn't arrive.  If I look in the package log file I'm seeing the following error:

Cannot reserve 66452 KB in the depot. The segment file is too large

Does anyone have any ideas why I'm seeing this?  I've checked for free disk space on both my TMR and the Gateway and both have plenty of space.

Contributed By: Cliff Hobbs [MVP SMS]
 This error is caused by the fact that there is insufficient space in your Repeater Depot for Tivoli to send the package.  You either need to purge the Depot to clear some space or if you don't want to purge what's already in the Depot you need to make it bigger.

From the Tivoli Command Line interface (CLI) issue the "wrpt" command to display the list of Repeaters that have been setup in your environment.  By default Endpoint Gateways are automatically configured to act as MDist 2 Repeaters in Software Distribution 4.x to allow them to distribute information to the Endpoints that login through them.

By default a Repeater also acts a Depot which is used to store distributions and helps reduce network traffic (you send the data once to the Depot and the Endpoints then retrieve the data).  Another key benefit of Depots is that if a distribution is interrupted for any reason, it can be resumed from the Depot rather than being resent from the Source Host.

Once you have a list of Repeaters you can use the "wdepot <repeater_name> describe" command to see the settings of a particular Repeater.  For example to see the settings for a Repeater named "thinkpad" you'd use the following command:

wdepot thinkpad describe

The output of this command lists the Depot Location, Size, Temporary Storage, Permanent Storage, Total Storage and Free Space.

The Depot seems to default to a size of 512000 KB or (512 MB to keep things simple).

The 'Total Storage' figure is a combination of the 'Temporary Storage' and 'Permanent Storage' figures and the 'Free Space' figure is the 'Depot Size' less the 'Total Storage' figure.

There are various settings you can configure for each Depot such as the size of the Depot, which drive it's stored on, whether copies of all distributions are stored in the Depot permanently, etc.  Listed below are the more common one's.

Moving a Depot
If you need to move a Depot use the "wmdist" command as follows:

wmdist -s <repeater_name> rpt_dir=new_dir_name

For example to move the Depot on a Repeater called "Repeater1" from the C: drive to the 'E:\Tivoli' directory, you first need to create the 'Tivoli' directory on the E: drive (if it doesn't already exist), and then use the command:

wmdist -s Repeater1 rpt_dir=e:\Tivoli

(You don't need to create the 'depot' directory under the directory you create as Tivoli populates this automatically for you).

You then need to stop/start the oserv service on the Repeater to make the changes take effect.

Increasing the Size of a Depot
If you need to increase the size of a Depot use the "wmdist" command as follows:

wmdist -s <repeater_name> disk_max=new_size_in_MB

So if I wanted to increase the size of the Depot to 2GB on a Repeater called "Repeater1" I'd use the following command:

wmdist -s Repeater1 disk_max=2048

Again, you will need to stop/start the oserv service on the Repeater to make the changes take effect.  Setting this value to "0"  will also the Depot to grow in size until the disk fills up.

Setting the Depot to not Permanently Store Copies of Distributions
If you don't want the Depot to store copies of any segments marked for permanent storage by applications once their distribution finishes, then use the "wmdist" command as follows:

wmdist -s <repeater_name> permanent_storage=FALSE

So if I wanted to change the Depot on a Repeater called "Repeater1" to not permanently store any segments marked for permanent storage I'd use the following command:

wmdist -s Repeater1 permanent_storage=FALSE

Again, you will need to stop/start the oserv service on the Repeater to make the changes take effect.

Note: Changing this setting to "FALSE" doesn't delete anything that's already stored in permanent storage. In order to delete the contents of permanent storage you'll need to use the "wdepot <depot_name> purge" command as detailed below.

Purging a Depot
If you want to purge a Depot to free up the Permanent space, you use the "wdepot" command as follows:

wdepot <depot_name> purge

So if I wanted to purge the Depot on a Repeater called "Repeater1" I'd use the following command:

wdepot Repeater1 purge

You will need confirm that you want to purge the Depot.
 

"Could not find an object's method implementation: o_errs:0030 method not found"

After installing my NT Managed Node, then installing a Software Distribution Gateway and patching it the next thing was for me to move the depot using the wdepot command to a drive with plenty of free space.

The 'wmdist -s <repeater_name> rpt_dir=new_dir_name' command seemed to work to move the depot to the drive/ directory that I'd already created. I then cycled the oserv on the Managed Node to get the changes to take effect.

The problem I've got now though is that when I use 'wdepot <repeater_name> describe' to make sure the changes have taken effect I get the following error:

 FRW:STEX:0011
Could not find an object's method implementation: o_errs:0030 method not found
Make sure that the TME method binaries are available for all installed platforms

Software Distribution still works but it puts the data in the default location on the C: drive rather than the D: drive.

Has anyone got suggestions as it now looks like I'm backed into a corner?

The oserv is started on the MN. I've tried using the odadmin shutdown all | start all and reexec MN_OID based on previous messages posted to the tme10list but this has made no difference.

Contributed By: Cliff Hobbs [MVP SMS]
 De-installing/ re-installing the Managed Node resolved this problem.
 

Endpoint Log Just Shows "spawning C:\Program Files\Tivoli\lcf\dat\1\cache\bin\w32-ix86\TME\swdis\spde\spd_eng.exe

I've got a problem where I'm trying to send the Software Package Editor to some NT Endpoints to prove Software Distribution 4.1 works. I've sent it to the TMR itself fine, yet when I send it to Endpoints all the log file on the Endpoint says is:

lcfd Spawning: C:\Program Files\Tivoli\lcf\dat\1\cache\bin\w32-ix86\endpoint\admin.exe, ses: 20ad77e9

I've tried deleting/re-installing the Endpoint, bouncing machines, etc. all with no joy. The log file on TMR says the job was submitted okay. If I resend the package it just spawns another copy of spd_eng.exe.

Anyone else ever seen this?

Contributed By: Cliff Hobbs [MVP SMS]
 Make sure that a copy of "KBDUS.DLL" is on the Endpoint in the "C:\WINNT\System32" directory.  In this particular case this file wasn't present.  By making a copy of the "KBDUK.DLL" file and starting and stopping the Endpoint service the Software Package Editor appeared instantly on the Endpoints.
 

Is it Possible to Display a Message Telling the User Software is being Deployed?

Is it possible to display a message on the Endpoint along the lines of 'Software package xyz is currently being installed. Please do not logout/disconnect your machine until this completes.' for mandatory installations and then display another message 'Package xyz has been successfully installed - you may now logout/disconnect'?

The prime reason for this is that I can see the scenario where a laptop connects in and I'm pushing out anti-virus updates, which would be a mandatory install and wouldn't appear in the mobile client. As nothing appears in the mobile client the user disconnects without the installation completing. I appreciate the next time they connect checkpoint restart will kick in and the package will continue installing where it left off, but I might be in the situation where I must ensure the software gets to the Endpoint at next login (e.g. urgent AV updates).

I know I can't stop people disconnecting/logging out (life would be easy if users did what we told them :-)), but it would at least be nice to be able to tell people what's going on so they've not got the excuse they didn't know.

Contributed By: Martin Carnegie, Brian Duffy
 You might want to embed a script in the package that pops up a window informing the user that a critical update is taking place and that they should remain logged in until it completes. That way, users cannot delay or cancel the distribution in the mobile console and they know that they are receiving something.

If the distribution is hidden then you cannot send this message via the mobile console. If it is mandatory then you can add a description to it so that it would say whatever you want. Another nice feature of the mobile console when using mandatory is the escalation dates.

One way I can think of to send a message would be to utilize the wrunuiep command. This allows you to execute a program on the workstation that would be displayed on the users desktop (notepad, IE).
 
© FAQShop.com 2003 - 2005

Goto the Tivoli Home Page

 Email the Author