MarvelClient allows you to precisely define when a particular action is supposed to run, whether it’s just once or a recurring event (e.g., to enforce configurations). You can even specify that actions run in realtime for true control over connectivity, traffic, and disk-space consumption.

One-time changes are best for migrations, server consolidations, and recertifications. Your clients can easily run hundreds of changes to flank your server-side changes (i.e., moving databases or directories, renaming servers, etc.) without negatively impacting your client base at all. Implementing one-time changes also ensures virtually unlimited freedom in performing migrations; for example, you can freely move a database from multiple old servers to one new server or from one old server to multiple new ones, and the clients are seamlessly synchronized with any server renames and database moves.

For help desk incidents, however, one-time actions are usually not the best solution. Most problems occur more than once, so you might just want to solve them for good through permanent enforcement. Also, recurring changes can be very handy when you want to run certain actions (e.g., compacting databases or performing a hardware or software inventory) once a week, once a month, or on certain days of the week or month.

Permanent changes come in three flavors: changes can either be applied