Efficient client management approaches
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
- at every client start up,
- once a day,
- or in freely configurable intervals.
These options ensure enforcement of links and settings to
provide clients with a kind of self healing. For example, you can use MarvelClient to set the following permanent configurations:
- A user’s mail database is always on page one at the top left of his or her desktop and the Domino Directory is right underneath it.
- Desktop, laptop and Citrix users have, at the very least, a certain set of locations with specific settings.
- Local replicas are automatically created for certain databases with their correct replication settings.
Apart from HOW OFTEN and WHEN to execute actions, you can also easily specify WHO shall be affected by a particular action: Laptop or desktop users, Citrix/WTS users, users in certain IP ranges, or with clients certain notes.ini- or OS-settings - all without any programming. And you can naturally also target actions at Notes usernames, groups or certifiers(e.g. */panagenda), as well as exclude subgroups.
Last but not least you can also define predecessor and successor actions, as well as an action to depend on a certain result from another action - MarvelClient takes care of the correct execution sequence without you having to sort any actions yourself.
Click here for details on panagenda MarvelClient's real-time relocation and restriction engine >