Difference between revisions of "Related projects"

From WPKG | Open Source Software Deployment and Distribution
Jump to: navigation, search
m
Line 39: Line 39:
 
* Supports Windows 2000, Windows XP, Server 2003. Vista support can be integrated in the near future.
 
* Supports Windows 2000, Windows XP, Server 2003. Vista support can be integrated in the near future.
  
* Is based on two methods of accessing a client computer: First, a network boot with a Linux image, that e.g. can be used for preparing a OS installation, or saving and restoring a partition. Second, a boot of the installed OS, in which a service is implanted that then triggers the execution of install processes or other scripts. Theses processes are controlled by (https-) requests to the "opsi configuration service" which runs on the opsi server.
+
* Is based on two methods of accessing a client computer: First, a network boot with a Linux image, that can e.g. be used for preparing a OS installation, or saving and restoring a partition. Second, a boot of the installed OS, in which a service is implanted. This service triggers the execution of install processes or other scripts. These processes are controlled by SSL-requests to the "opsi configuration service" which runs on the opsi server.
  
 
* The software configuration of each client can be individually configured. For this purpose, there exists an easy to use graphical user interface.  
 
* The software configuration of each client can be individually configured. For this purpose, there exists an easy to use graphical user interface.  
  
 
* To prepare the software packages for deployment there is a scriptable environment that combines different approaches as Windows Installer packages, automated installs by AutoIt scripts, and specific command calls.
 
* To prepare the software packages for deployment there is a scriptable environment that combines different approaches as Windows Installer packages, automated installs by AutoIt scripts, and specific command calls.

Revision as of 10:48, 1 October 2007

Unattended - a system for fully automating the installation of Windows 2000, Windows XP, and Windows Server 2003.

Features include:

  • Automated install of OS, hotfixes, and applications
  • Full documentation and source code
  • Support for floppy, CD-ROM, and "nothing but net" installs
  • True unattended installation, not disk imaging
  • No Windows servers required; use your Unix servers instead
  • No Unix servers required; use your Windows servers after all
  • Completely free

When you are finished setting up Unattended, you will be able to boot any PC from a floppy, from a CD-ROM, or directly from the network, answer a few questions, and come back an hour or two later to a fully-installed Windows workstation.



Unattended GUI - This is the GUI to Unattended. Also a collection of scripts for inventory, deinstallation and other add-ons.


Diegostart - Unattended windows installs based on the use of the BartPE cd.

Features:

  • Detailed Howto for Windows XP installations.
  • Supports Windows 2000, 2003 and the corresponding server versions.
  • Based on answer files, batch scripts and free software.
  • Allows simultaneous installation of different classes of systems, e.g. Windows XP Pro for a Computing Lab, Windows XP pro for a laptop, Windows XP Pro for a Staff person.
  • Free as in beer



opsi or: Open PC Server Integration, a Linux server based system for automating OS deployment and software installation on Windows clients, now downloadable in version 3.1

Features:

  • A VMware machine with an ready to use opsi server can be downloaded (opsi3.1-depotserver.zip) - nothing but the original Windows installation cd contents must be added.
  • Supports Windows 2000, Windows XP, Server 2003. Vista support can be integrated in the near future.
  • Is based on two methods of accessing a client computer: First, a network boot with a Linux image, that can e.g. be used for preparing a OS installation, or saving and restoring a partition. Second, a boot of the installed OS, in which a service is implanted. This service triggers the execution of install processes or other scripts. These processes are controlled by SSL-requests to the "opsi configuration service" which runs on the opsi server.
  • The software configuration of each client can be individually configured. For this purpose, there exists an easy to use graphical user interface.
  • To prepare the software packages for deployment there is a scriptable environment that combines different approaches as Windows Installer packages, automated installs by AutoIt scripts, and specific command calls.