Login AM Collections

From Login VSI Documentation
Jump to: navigation, search

Collections group computers logically and bind one or more layers to them. By adding a computer to a collection, Login AM will know which components to deploy and how to configure the computer. All computers which are a member of the same collection will be deployed using the identical layers. This ensures all computers that belong to the same role will react in a predictable and consistent manner. Inheritance of the collections works as follows: When a computer is added to a collection, all layers for that collection will be processed. If the collection has any parent collections, those parent collections' layers will be processed first, i.e.:

  • Testcomputer is a member of the collection Session Hosts
  • Session Hosts is a child of Remote Desktop Services
  • Remote Desktop Services has the layers: Desktop Silo and Office
  • Session Hosts has the layers: Adobe and AntiVirus

The order of execution for the layers on Testcomputer will then be:

  1. Desktop Silo
  2. Office
  3. Adobe
  4. AntiVirus

An example of a collection configuration is shown below.

LoginAM Basics Collections 01.png


Collection Types

A collection has a property called collection type. This collection type configures the behavior of AM on the target computers. As the needs and wants for platforms can largely differ, you can configure the type of the collection in AM. Currently, the following collection types are supported:

  • Generic Server
  • Golden Image
  • RDS 2012R2 Session Host
  • XenApp Session Host
  • Stateful VDI