New Release of Swimage Encore ® Contains Amazing New Features

Swimage Encore New Features

The latest release of Swimage Encore (Build 5.0.7) contains many new optimizations and advancements in deployment. Native virtual application support as part of the deployment process is only the tip of the iceberg. This release offers a number of significant and, we feel, exciting new features. Here is a quick review of the most notable.

Dynamic Application Deployment
While most activities in Swimage Encore are explicit and deterministic (i.e., Roles and Templates are used to specify EXACTLY what will be installed on a new deployment or a redeployed machine), there are times when an administrator would like to be able to simply reset a machine to the existing configuration (hardware, location, domain, OU and application) status but on a clean installation of the operating system. With Swimage Encore’s new Dynamic Application Deployment, enabled by our new Discovery phase, deployment can now be just that simple. The Swimage Encore Conductor will scan the targeted machine for installed applications and compare them to a manifest that is stored on the Swimage Encore server. Administrators can create ‘matching rules’ on the server to dictate which applications should be installed based on easy to use wildcard definitions. Your corporate standard is Adobe Reader? Make sure all machines, when they are redeployed, receive your latest and greatest by creating a rule that stipulates “Any machine running Adobe Reader of any version NOW will be deployed with Adobe Reader 9.2.” By allowing administrators to create the rules on the server, when deployment is triggered, those rules can dictate migration activities through the use of a dynamic template reducing deployment configuration time dramatically while helping rationalize your environment at the same time! This feature allows the person deploying the machine to be blissfully ignorant as to what is on the machine and to simply state the Role a machine should be (which includes OS, core apps, etc…) and let Encore figure out all customizations that are necessary for each individual user. (This is real power!)
Hardware ‘Wildcarding’
Encore has always allowed an administrator to setup drivers and link them to specific hardware models. This method is great in that it allows the administrator to specify specific drivers for a model preventing driver version conflicts. There are times however when manufacturer’s will differentiate the same model (that uses the same drivers). Encore now allows hardware ‘Wildcarding’ to associate a set of drivers with multiple defined hardware objects.
Hardware Approval
We already know that Swimage Encore does an amazing job of populating your driver database rapidly through its implementation of the Driver Interrogator. In an effort to enable more granular control of the use of those drivers, now administrators can choose to approve hardware models for specific OS’s before they are considered active. This additional level of control and auditing will prevent accidental deployment to unsupported hardware and OS configurations. If a hardware model that is not approved for a given OS is attempted to be deployed with that OS, the process will abort gracefully with no modifications to the target system.
Discovery Phase
This new phase in the Swimage Encore deployment process is executed by the Conductor on the client. The Conductor will now scan the targeted machine for inventory data (fear not, we are not trying to supplant your current inventory toolset, just trying to improve deployment process) that is relevant to the deployment process. Currently scanned items include time zone, organization unit, domain and applications installed. That data is reported back to the Swimage Encore server and can be leveraged by all new features of the system to enable dynamic image deployment.