Description¶
The aim of this project is to provide a very easy way to deploy software across Windows networks.
The project centres around an application that 'deploys' software to computers.
The supported version of Windows clients are:¶
- Windows 2000
- Windows XP
Other versions have not been tested, so we'll presume it doesn't work until we can say it does ie. have actually tested it.
Software deployment¶
Sofware in the sense of being able to be deployed, will be typically represented as either a .msi windows installer file or a single .exe executable file. Perhaps in the future more options will be provided like deploying a folder or non executable files like documents/patches etc. In theory this could be facillitated in the future.
Deployment is very Windows focused as it depends on windows file sharing, which involves copying deployment files to the c$ share of the target machine and remotely executing it. With deploying .msi files - this'd include running msiexec /i against the copied installer file.
Computer Sources¶
Computer sources represent where to get our list of computers from. These computers are the targets of whatever deployment we perform against them. Computer sources include Active Direcory, WorkGroup, IP Address ranges,Novell eDirectory, Text File or potentially even an obscure place like a DHCP server lease table etc. Computers will be
represented by either a DNS name or IP address that we use to address them when we try to deploty software to them or perform actions one them.
Computer Actions¶
Computer actions represent the actions that we can perform against a computer, other than deploy software to it.
Perhaps functionality like remote reboot, services control or remote cmd connect could be function that can be performed for a computer.
Plugin archiecture¶
Computer Source and Computer Actions are written as plugins to facillitate the many diffirent potential computer sources.