The installation of LOGINstall is structured in two phases: the administrative setup for the LOGINstall configuration and the client setup.
The administrative setup
- copies the client installation packages to an Administrative Installation Point (AIP) on a network share
- creates the file LOGINstall.ini
- creates the configuration file LOGINstallCfg.ini.
To execute the installation, you must login as a user with local administrator privileges.
By ticking the box "Use command 'KISClnt' also …" you can ensure compatibilty to the previous version "KIS 2.5". The KIS client was started with the command "KISClnt". In new LOGINstall the command "KIS" will do.
The configuration program copies the client installation packages (LOGINstallClient.msi) to the AIP. Additionally, it creates a LOGINstallCfg.ini file, defining the parameters that are necessary for the final installation. As all of the required settings now have been made, the client installation can be performed "unattended".
In the second phase the
- LOGINstall Service (KISVC),
- LOGINstall Client (KIS) and
- LOGINstall Menu (if desired)
must be distributed to the clients, e.g. by creating a Group Policy Object (GPO) and placing a new package 'loginstallclient.msi' from the above created AIP under Computer Configuration / Policies / Software Settings / Software installation.
Flexible Rights Assignment
It is possible to centrally block the execution of special commands for users or user groups. In Windows this is realized by using access rights to files, making it reliable and easy to use.
Optionally, the administrator can specify the name of a file to which the user must have access rights to, so he can run the command. This way it is feasible to take account of individual user rights and group memberships.
Every command is performed with local administrative rights in the computer context. For example, if the command releases a program installation, the program will be installed in a way how the administrator would have done it in person.
The service KISVC allows e.g. the automated program installation in the NETLOGON script. An integrated version management prevents the double command execution. This may be useful for a service pack installation that needs to be performed only once on every computer.
The service KISVC is a central element of our standard client-concept and is already used by several thousands of our customers.
LOGINstall demands the following hardware and software minimum requirements:
- Compatible hardware for Windows XP, Windows Vista, Windows 7
- x86/AMD64 compatible processor
- RAM: 512 MB
- free hard disk capacity: 50 MB
- Windows XP-SP3, Vista-SP2, Windows 7 and even Windows Server 2003/8
- .NET Framework 2 or later
- Windows Domain
- Workgroup (with some limitations)