Difference between revisions of "WPKG with Samba"
From WPKG | Open Source Software Deployment and Distribution
m |
m |
||
Line 1: | Line 1: | ||
− | WPKG | + | = WPKG overview = |
− | + | WPKG can add great value to your Samba setup, as it allows to perform software installation, updates, removal etc. on your workstations. | |
− | + | It is also possible to execute custom scripts on your workstations, like synchronizing time, setting printers, changing permissions or adding registry entries (basically, some of the things you would do with Active Directory and Group Policy / GPO). | |
− | + | This is a list that summarizes what WPKG can do for you: | |
+ | |||
+ | * deploy software in any format - MSI, EXE, etc. | ||
+ | * deploy software to different groups of computers or single workstations | ||
+ | * easily install, upgrade or remove software | ||
+ | * run custom scripts to set printers, synchronize time, change permissions, add registry entries etc. | ||
+ | * work in a domain, in a workgroup, or even over internet or VPN (no domain controller needed) | ||
+ | * work with Windows 2000, XP and 2003 clients | ||
+ | * extremely small footprint on the client: no additional service is started | ||
+ | * extremely small footprint on the server: no additional service/daemon is started | ||
+ | * keep inventory of software installed on your Windows workstations | ||
+ | |||
+ | |||
+ | |||
+ | To use WPKG, you have to setup two things: | ||
+ | |||
+ | * '''Server side''' - configure a share on a Samba server with your software, scripts and WPKG files | ||
+ | |||
+ | |||
+ | * '''Client side''' - configure your workstations to run WPKG off a share you configured earlier | ||
+ | |||
+ | = Server side configuration = | ||
+ | |||
+ | * configure a share for software, scripts, and WPKG files | ||
+ | |||
+ | |||
+ | = Client side configuration = | ||
+ | |||
+ | * using Task Scheduler | ||
+ | * using srvany | ||
To be continued... | To be continued... |
Revision as of 20:05, 11 October 2005
WPKG overview
WPKG can add great value to your Samba setup, as it allows to perform software installation, updates, removal etc. on your workstations.
It is also possible to execute custom scripts on your workstations, like synchronizing time, setting printers, changing permissions or adding registry entries (basically, some of the things you would do with Active Directory and Group Policy / GPO).
This is a list that summarizes what WPKG can do for you:
- deploy software in any format - MSI, EXE, etc.
- deploy software to different groups of computers or single workstations
- easily install, upgrade or remove software
- run custom scripts to set printers, synchronize time, change permissions, add registry entries etc.
- work in a domain, in a workgroup, or even over internet or VPN (no domain controller needed)
- work with Windows 2000, XP and 2003 clients
- extremely small footprint on the client: no additional service is started
- extremely small footprint on the server: no additional service/daemon is started
- keep inventory of software installed on your Windows workstations
To use WPKG, you have to setup two things:
- Server side - configure a share on a Samba server with your software, scripts and WPKG files
- Client side - configure your workstations to run WPKG off a share you configured earlier
Server side configuration
- configure a share for software, scripts, and WPKG files
Client side configuration
- using Task Scheduler
- using srvany
To be continued...