4 replies
what can and cannot be put on the system. The basic rule for most is that nothing goes on until AFTER it has been thoroughly checked out by a team or end users and tech staff - any costs involved to be met by the area wanting it on. If your organisation does not have any such policy I wonder what IT policies they do have as controlling extra software is usually on of the first. I suggest you may wish to look at this item from the TR sales area - it is a CD on IT policies. It should give you a good idea of what else you need.
by sysnetmgr
a book like that to make sure you cover all the important bases.
As I said before the general policy in organisations that I know the policies of (govt depts, govt agencies, big companies, govt schools, private schools) is that NOTHING is installed onto the network except by the IT people and then only AFTER the software has been thoroughly checked out in a test environment at the expense of the unit wanting it put in. Time to install and get it working is billed to the unit wanting the software, and all support is chargeable to the unit. In small organisations testing will often comprise of installation on a stand alone PC not on the network, and it is tested for user needs and then examined by IT for compatibility with existing network set up.
by drfez
This discussion is closed to new replies.
Trending Web Development posts
Sort by Trending