Swimage Future State


The Future State defines how a PC is to be imaged, what OS is installed, what settings are applied, what applications are installed, and how data is to be migrated.  Generally speaking, it defines everything about the “Future State” of the PC.

The Future State is created through a single Role in addition to any number of templates.   Minimally, a Future State could be assigned to a computer by adding a Role and nothing else.  This would be the simplest Future State configuration.  Conversely, a Future State can be created by adding any number of Templates, in addition to other provisioning components, such as automatic application matching or the individual PC’s Future State Template.

Only one Future State can be assigned to a PC at a time.   Once a Future State is created, the Future State is active until it’s either deleted manually or the PC completes the deployment.   Once the deployment is complete, the Future State is converted to the PC “Current State” in the database. 

A Future State is created in two ways.

  1. Through the Computer Import
  2. When a Deployment Job starts

When importing through the Computer Importer, the Future State is immediately generated.

When creating a Deployment Job, the Future State does not get created until the scheduled deployment time is reached.  

The Future State as well as all roles and templates include 8 tabs for the configuration of the entire system.

 Future State Tabs

> General

In most cases, this would be the only screen needing input. The only two required fields show up here, “Computer Name” and “Computer Role.” All other fields should have all the setting filled in for a successful deployment.
Available templates show up here on the left hand side. Any templates can be added at this time and the settings will change automatically.
Additionally, and settings can be changed manually on any of the tabs in order to override any of the settings assigned by the role or the templates.


> Advanced

The Advanced tab contains OS, Image, Domain, and other settings. The User ID field is optional, but can be used for tasks such as PC auto naming, assigning to local groups, or sending out e-mail communications.


> Migration Settings

The Migration Settings tab is where the data migration settings are defined. The data migration settings drop-down list the methods and settings for the USMT. The source USMT Computer is used for a “Computer Swap” scenario. This would be the PC that’s being migrated from. It assumes the old PC has already run the State Capture job and the data is waiting for the new PC to restore it. This is not used for the “Direct Data Transfer” process using a Swimage kit. In the DDT case, this field is left blank.


> Applications

The Applications tab is where applications are assigned to be installed. The top shows which applications are available and the bottom are the applications assigned. The check for Auto Detect will turn on the application matching function.


> Registry Punches

The Registry Punches tab shows which registry tweaks have been assigned to be added to the deployment.


> Custom Scripts

The Custom Scripts tab shows which scripts have been assigned to be executed during the customization phase of the deployment.


> Windows Features

The Windows Features tab shows which features will be turned on or off during the deployment. This tab will enable or disable windows features and packages. The best use of this tab would be in the WIM creation phase where limiting the extra windows features and packages can be done universally for all systems in the environment.


> Disk Configuration

The Disk Configuration tab defines how the disk will be treated during the deployment.

A Single Partition is the normal and recommended configuration for the disk. Even if Single Partition is selected, if the PC is configured to use UEFI, Swimage will automatically create the EFI and reserved partitions in addition to the Single OS partition. The default behavior is to keep the existing partition in-tact unless there is a requirement to repartition the drive. The check to “Force a repartition of the disk” will override the default behavior and repartition. Be aware that this may conflict with the data migration settings. If data migration is set to store locally and/or it’s set for Snapshot, checking the “Force repartition” could make you lose data. If you have conflicting settings such as this, Swimage will pop up a warning before it repartitions the drive.

Return to Swimage Training