Skip to main content

General Fileset workflow

Distributing content with FileWave is done with a simple workflow that can add complexity as needed. All of the information below is discussed in much more detail later in this Chapter. The basic workflow runs as follows:

  • Select Fileset type – you choose the type of content (files / folders / profiles / scripts / etc.)
  • Configure Fileset or add content – provide settings or assign content to the Fileset
  • Associate Fileset to client(s) – you attach or associate a Fileset with a specific Client or Group
  • Update server model – you commit the changes to the Server and the Fileset actions are performed by the Client(s)

A more complex model may include some or all of the following additional steps (Some items are specific to computer or mobile Filesets only):

Post-creation

  • Specify Details – Settings can include forcing the Fileset to be redeployed if removed and/or causing the deployed application to be removed if the FileWave profile is removed.
  • Provide Kiosk information – You can provide information for the user concerning this item.
  • Edit Payload – You can open the Profile Editor and make changes to the settings.
  • Edit Settings – You can specify the OS and other defaults for this payload.
  • Add items – You can add more files / folders to this Fileset.
  • Edit files inside Fileset – You can edit files directly within a payload.

Post-Association

These settings are covered in detail in the next section on Associations.

  • Specify a download time – You can choose to deploy this Fileset at another time other than immediately after the model is updated.
  • Specify an activation time – You can choose to activate the payload at a later time rather than right after the download is complete.
  • Specify a deactivation time – You can choose a time to make this payload inactive (but have it remain on the Client), rendering it invisible to the user.
  • Specify a deletion time – You can choose a time to remove the payload completely from the client.
  • Designate Fileset as a Kiosk item – You can choose to make the Fileset self-installable by the end user; in other words, have it appear in the self-service Kiosk.
  • Specify Fileset dependencies – You can specify that a Fileset requires another Fileset in order to function properly.

You have great flexibility with all aspects of Fileset deployment. You can choose to make certain Filesets react to conditions at the Client, specify certain Filesets for deployment at staggered intervals, pre-stage Filesets on Clients, and you can edit Filesets after deployment to add or subtract content as needed. Actions like these, and many more, give you the freedom to control your management at the file level, resulting in lower network loads, faster response times, and built-in self-healing of applications and content for your end users.

Back to top