
(latest build on 10/05/2006)

trust to user

Looking how to make your business more efficient? Got tired of IT administrators installing tons of software here and there and wasting their valuable time? Give more freedom to your employees; let them install what they actually need with the Trust to User service!

AN EXAMPLE OF THE LISTING STRUCTURE 
ON THE SERVER FOR T2U 
Put the following listing structure on DFS or on a server in your 
enterprise. 
T2U 
Catalog - file place for safety catalogs (CAT files), which those 
Results of marking packages represent. 
Icons - file place for ICO files, those for linkages from that 
Shortcuts listing to be used.
Logs - file place for central log files 
Packages - file place for all packages 
PkgPerms - file place for T2UPerms.xml 
Release - file place for T2UClnt.exe, T2USvc.exe etc.. In Zap files and 
in the linkages from the Shortcuts listing becomes optional 
T2UClnt.exe from release listing uses. 
Self update - file place for INI files, those of the program OKsu.exe 
are used 
Shortcuts - file place for linkages for the start of packages 
Zap files - file place for Zap files 
Give T2U to listing freely with the following release authorizations: 
Administrators - execution reef 
User - vintages 
T2UService - changing 
For the listings Catalog, Packages, PkgPerms the NTFS authorization: 
Administrators - execution reef 
SYSTEM - execution reef 
T2UService - vintages 
For Logs listing 
Administrators - execution reef 
SYSTEM - execution reef 
T?Service - changing 
For the remaining listings (Icons, release, Self update, Shortcuts, Zap files) those 
NTFS authorization: 
Administrators - execution reef 
SYSTEM - execution reef 
User - vintages

Go to Help Contents

trust to user

T2U HELP