There might be a way around these issues, but I would never allow a user to install their own application in an organization that's under my control. Doing so just raises too many legal questions. Another reason for not allowing users to install applications of their own is because doing so can greatly increase support costs. I once worked for an organization that allowed users to install anything that they wanted onto their PCs. One particularly arrogant user would install all kinds of crazy applications and then make angry phone calls to the Human Resources department when the IT staff refused to support them.
Granted, the Human Resources staff took our side in the issue, but the time that we wasted defending ourselves could have been better spent assisting users with legitimate problems. Even if your users don't expect you to support the software that they install, user installed applications can increase support costs in other ways. For example, imagine that a user installs a buggy application that causes the system to become instable.
If you don't know that the application exists, how much time will it take you to diagnose it as the cause of the problem? Even if you can make the diagnosis relatively quickly, how long will it take you to repair the damage? The whole incident could have been avoided if the user had not been allowed to install the application in the first place.
Another reason for not allowing users to install applications of their own is because of the threat of malicious software. There are two different types of threats that you have to worry about when it comes to malicious software. One threat is malicious software that is piggybacked onto legitimate software. The Internet is chock-full of freeware applications that are bundled with adware or spyware modules. Revisit the policy and be diligent in revising it A key failure of many policies is to let them become stale.
IT is fortunate that it can update a policy and push it out easily through technology. A policy needs to be a living document with core principles remaining the same through its period of enforcement.
However, the policy should be updated regularly to adapt to changes in the IT environment. Avenues to address updates to a policy You should adhere to a specific plan when implementing updates. Make provisions for changes in the policy and determine who will make them. Set a monthly reminder in your groupware package to ask you if there are any changes or new situations that need to be addressed in the policy.
E-mail the policy or possibly the changes to all users periodically or post the updates on your intranet and notify users when updates occur. IT should be proactive about the risk that is present with software installations on company computers. Simple tasks can allow IT to have the upper hand in dealing with these issues as they occur or even before they occur. There are tools to use, choices to make, and easy notification actions to take that will help you protect the company computer. Some examples include the following: Utilize security policies on Windows-based computers either as a native feature of Windows or by using a third-party package.
Use specific cloning procedures to immediately roll back to a known software environment using Norton Ghost, PowerQuest Drive Image, Sysprep, or a similar tool when the environment has changed outside IT. In a Windows environment, use a simple copy operation of all. In a login script, you could be crafty and make the login script resolve the computer name from the registry, make a directory of that name, place the shortcuts there, and review the contents, periodically looking for aberrations from the desktop standard.
The software policy assists the organization in achieving its objective Management of the client computer is a critical area for measuring the success of an IT group. Having the client computer in a controlled environment can allow you to be most responsive to changes in your organization. And an enforced software policy can be a key to reaching your client environment utopia.
We look forward to getting your input and hearing your experiences regarding this topic. Join the discussion below or send the editor an e-mail. Editor's Picks. Look around for the best deal, but make sure that the supplier you choose can deliver on its promises. Find out how to choose and manage your IT supplier. My New Business Northern Ireland business support finder Sample templates, forms, letters, policies and checklists Licence finder Find a case study Do it online.
Computer software for business Software installation and maintenance. Software upgrades Software upgrades are generally needed to ensure that your software continues to perform properly and securely. Software upgrades may become available because: new or improved functionality is added to the software current software has become incompatible with other, newer programs security 'fixes' or 'patches' are needed to address 'bugs' discovered in the software You can usually access upgrades online.
Software support An important factor in choosing software is the availability of technical support. When assessing support, you should consider: Location - Time differences can affect availability during particular times. Some providers may offer online or email support, or real-time messaging. Faculty and staff with systems that differ from the standard Floor Systems should expect to accept greater responsibility for the setup, configuration, and administration of their systems.
TSG can typically install and maintain software on systems that do not qualitative differ from the standard Floor Systems. For example, a system with more memory or with a larger hard drive compared to Floor Systems can be installed and maintained by TSG. Systems made by a different vendor or systems with devises e. The LSC is responsible for approving a list of insecure software and services.
All faculty members are allowed to have privileged access on their Personal Computers and Area Research Servers. Visiting faculty, students working with DSC faculty, and postdoctoral fellows can have privileged access on their Personal Computers and Area Research Servers.
The LSC is responsible for approving requests for privileged access.
0コメント