Login AM Basics
”Make everything as simple as possible but not simpler” –Albert Einstein
Simplicity is one of the key design pillars of Login AM. Adapting this ideology throughout the complete Login AM suite resulted in a powerfull yet lightweight architecture. Apart from a simple file share, Login AM doesn’t have any back-end requirements like database servers or agents on the target machines.
Login AM is comprised from a set of cleverly built PowerShell modules and scripts, the configuration is stored in XML files and the Login AM User Interface (in short; UI) consolidates all functionality in a concise interface.
The file share, residing on the Login AM server, contains all configuration items in order to fully configure and maintain the target computers. When initializing a target computer from the Login AM UI, a subset of the Login AM file share will be replicated to the target machine, also named as Login AM client). The locally synchronized cache enables the Login AM client to autonomously run the deployments and maintenance scripts as defined in the Login AM UI. In other words the installation and maintenance of the target machines run independently from the Login AM UI.The Login AM Manager is not used to directly manage the target computers.
Within the Login AM file share all configurations are stored in text files, in XML format, making an environment extremely easy to backup, copy, replicate, synchronize and secure. All relevant configuration files and all scripts are copied from the Login AM file share by the target computers at boot time and processed locally on each individual computer.