This can be both a blessing and a curse for users and administrators alike while it is now much easier to find tools that you may not have even known were available, it is also easier to stumble upon features that may not be appropriate for all users or simply to become overwhelmed with all of the options presented. Where Client Access simply relied on your PC operating system to present its components in whatever form (Start Menu, Applications folder, etc.) was available, ACS now provides easy and convenient links to all of its features from a single panel with tooltips and explanations for each. Unless launched from a shortcut directly to one of its components, Client Solutions opens by default to a unified main menu that is drastically different from the experience found in the previous generation. The ACS Main Menu, a buffet of fun and foibles for your users. To address this, I’d like to discuss a bit about how ACS does configuration under the hood and how administrators can have some control over what can be accessed within the application. One of the recurring questions we get from clients who are planning the switch relates to controlling what the end-user can see and use within the application. ACS is as flexible as the old application was rigid, and there are many different ways to configure it on a PC. With Client Solutions now being the only IBM-supported client software for IBM i, quite a few organizations have made the switch from the old iAccess products or are in the process of doing so.
0 Comments
Leave a Reply. |