Replacing Complex Logon Scripts For Faster Logon Times & Simplified Management

July 2, 2009

The traditional logon script has been the de-facto method to configure enterprise options for a user.  As its name suggests, the logon scripts executes during logon. This makes it a one stop ‘set and forget’ solution in that once the value has been applied the script has performed its job.

A typical logon script will connect network drive mappings, printers and perform other tasks such as ensuring corporate email clients are correctly configured as well as copying necessary files and / or folders into place within the user’s home directory or profile.

Logon scripts by their very design are synchronous in their approach, which can mean that while some of the actions required to be part of the script are completely unrelated, they are addressed in line with each other. This shows itself as a user logon taking an unacceptable length of time due to the number of actions, all of which are fed into the operating system line by line.

Furthermore, at the same time, because the script is an interpreted language, they are constructed differently from one person to the next!  This leaves the script subject to the administrator’s style and ability, meaning there is no standardization across the enterprise. The variations in styles of different authors can rapidly make the scripts difficult to read and follow, making debugging or alterations a very time consuming and costly task.

The above variables and computing conditions can often lead to scripts which take a long time to execute, even hanging or failing to complete. When this happens, the user is left disconnected from the system and the IT department plagued with support calls. Troubleshooting is often difficult as the support desk operator is unlikely to be the person who created the script, and as covered, has to learn the script before he can troubleshoot the issue or in some cases pass the call up to a higher level of support, either of which increases the time and cost spent on remedying the issue.

AppSense Environment Manager resolves the above issues, reducing complexity and saving on time and cost by completely replacing the troublesome scripting process with an easy to use graphical user interface, complete with wizard based actions. Actions can be selected and then applied at a user or device level, based on environment variables, without the need for any complex scripts. Furthermore, the GUI ensures consistency between Administrators, meaning any other support worker can quickly troubleshoot and amend any existing configuration..

AppSense Environment Manager is used by thousands of enterprise customers around the world to provide the flexibitily a logon script cannot give, reduce operational costs, and ensure users can log onto their system in the quickest time possible..

Managing Roaming Users & Printers Across Desktop, Citrix & VMware

June 28, 2009

Managing user printers and printer policies across Desktop, Server Based Computing ( SBC – Microsoft Terminal Server & Citrix XenApp) and Virtual Desktop Infrastructure (VDI – Citrix XenDesktop & VMware View) environments is becoming increasingly complex.

Administrators are spending huge effort (meaning they are also missing on investigating other projects) managing complex logon scripts to perform printer mappings, and, when printers are not available, for example if the user has roamed or changed desk or location or changed desktop delivery mechanism, IT must answer a support call and manually map the printer for the user.

AppSense Environment Manager solves this issue by automatically mapping the local or closest printer to the user and thier device (no matter how their desktop is being delivered to them), without the need for any complex logon scripts.  This not only reduces the time and costs associated with ongoing IT operations, but also improves the user experience and ensures all printed documents, including confidential data, is printed to the correct printer.

Using a combination of conditions (when an action is to apply) and actions (the application of a specific policy, in this case, mapping a printer) AppSense Environment Manager will dynamically map any pre-determined printer based on Client IP or MAC address conditions.  As an enterprise focused product, this all achieved and configured in a very simple and intuative management console as opposed to traditional complex logon scripts and policy actions.

Further more, it is common practice for many enterprise environments to have dedicated printers mapped and used exclusivly by specific applications, such as ERP or Finance applications.  AppSense Environment Manager is again used by thousands of organzations around the world to help provide a logical and cost effective solution to ensuring certain applications always print to the same secure printers. Please see the screenshot below showing that when the JD Edwards application is launched, and the user is running the application on a client within a set IP address range, then a specific printer is automatically mapped as the only printer available for the application.App_Printer

In this scenario, printers can be enforced as the only printer available for a specific application, based on either application name or, application IP address if it is delivered from a silo via streaming or publishing technology.   With that said, AppSense Environment Manager can also provide security in that the user can not change the printer, yet requried flexibility of allowing the user to change specific settings such as paper trays, paper sizes, formats & finishing etc..

In conclusion, printing can be a troublesome, time consuming issue, but it needent be.  AppSense Environment Manager is not only proven to resolve these issues, but also reduce opertional costs and provide a strong ROI.

For more information, please visit