General Fileset workflow

Distributing content with FileWave follows a basic workflow that can expand as needed. Related articles cover each area in more detail. 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 detailed deployment may include some or all of the following additional steps. Some options apply only to computer Filesets or only to mobile Filesets.

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.

Fileset deployment is flexible. You can make Filesets react to conditions on the client, deploy Filesets at staggered intervals, pre-stage Filesets on clients, and edit Filesets after deployment to add or remove content as needed. These options help control management at the file level, reduce network load, improve response time, and support self-healing for applications and content.