I have been asked to use Tivoli to distribute packages to DSL locations. The workstations at each location have a mapped Drive J: which maps to a server machine at each location. In doing the delta we found that drive mapping are not handled well. Our solution has been to send a pre-req package that, through VBS, maps the J: drive correctly (if, for instance, there isn't a user logged in.) Then in the primary package we re-route the J:\ files to a C:\temp\jfiles then proceed to do an xcopy to move the files from C:\temp\jfiles to the actual J: drive. Has anyone found an elegant way to handle network mapped data via Tivoli package files?

Also I noticed that wildcards on network drives (for INI file scanning for instance) don't work but specifiying individual INI files dose work on network drives, any ideas?

Also in the development of a package for the location I have found a glitch due to the imaged nature of the machines. When the Tivoli endpoint client was installed there was a generic user XXX on the machine. Tivoli's remote file endpoint tool granted XXX via a local policy the ability to run as the system (to pull packages off the local server). In the process of deploying locations XXX is deleted for security reasons and a new user acct. is created. When I went into local policies I noticed the SID from the old XXX user was still there (expected) but Administrator, the administrator group, and the Tivoli group was not present. Adding those two groups in alleviated the error message we were getting for the delpoyment. Two questions:

A: Does Tivoli in the installation of the remote distribution client pull those two groups out?

B:Is there a way, via a script to add groups or users to that policy of running as the system?
0 Comments   [ + ] Show Comments


Please log in to comment

There are no answers at this time
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


Answer this question or Comment on this question for clarity