> Device Based Collections
> Device Based collections allow you to assign Pano devices, rather than users, to specified DVMs. This model is useful if you want to implement special usage scenarios, such as a kiosk or shared computer.
> A kiosk is commonly defined as a limited purpose computer that supports multiple users. Kiosks are often placed in open locations where users can simply walk up and start using the device, perhaps without providing any credentials.
> Access without user-supplied credentials is implemented by having the system automatically log on to Windows using credentials that are specified in the collection properties. The user experience is such that the user only sees the Windows desktop—not the Pano client login screen or the Windows login screen.
> The operating system in a kiosk is generally locked down so that users cannot gain access to applications or networks that are restricted. You can find kiosks in public places such as libraries, company break rooms or corporate lobbies.
> Creating a Device Based collection is similar to creating a User Based collection. Device Based collections take advantage of the automated provisioning features of the Pano Manager, allowing you to create and specify a template, while automating the cloning of new DVMs.
> Once DVMs have been created, the next step is to assign a device. Device assignment can be performed through the Management User Interface (MUI) or by logging on for the first time from a device through the Pano client login screen.
> Once assigned, the Pano Manager allows a device to connect to the designated DVM only. If you later want to use that device with a User Based collection, you must first unassign the device from the designated DVM.
> There are three types of Device Based collections, and they are very similar and only differ in their process of logging on to Windows:

> • | Automatic Login

> Use this collection if you want the Pano device to automatically log on to the DVMs using the same credentials throughout the collection.
> DVMs are automatically created from a specified template. Pano devices are assigned to specific DVMs either through the Management Console or by logging in through the device for the first time. As soon as the Pano device comes up on the network and connects with the Pano Manager, the device automatically connects and logs in to the assigned DVM. The login credentials for the automatic logon into Windows are identical for each and every DVM in the collection. The account can be a local account or a domain account.

> • | Different Accounts w/ Automatic Login

> Use the collection if you want the Pano device to automatically log on to the DVMs using unique credentials for each login device.
> DVMs are automatically created from a specified template. Pano devices are assigned to specific DVMs either through the Management Console or by logging in through the device for the first time. As soon as the Pano device comes up on the network and connects with the Pano Manager, the device automatically connects and logs in to the assigned DVM. Upon automatically logging in to Windows, a unique account name and password will be used for each DVM in the collection. The accounts must be domain accounts and they must be members of the same security group.

> • | Windows Login

> Use this collection if you only want the Pano device to connect to a DVM, but not log on to the actual DVM (i.e. display the Windows Login prompt).
> DVMs are automatically created from a specified template. Pano devices are assigned to specific DVMs either through the Management Console or by logging in through the device for the first time.
> As soon as the Pano device comes up on the network and connects with the Pano Manager, the Pano device automatically connects to the assigned DVM. Users must type their credentials at the Windows login prompt (also known as the Windows GINA).
> Windows allows a Windows login screen to be displayed for only 2 minutes. If a user has not signed into Windows within 2 minutes, the Pano Manager re-establishes a connection with the DVM. This cycle repeats until a user logs in. Once logged in, the session remains active until the user logs out or disconnects.

Did you find what you're looking for?
v2.5.1