Look at it this way,
What is the risk? 1) Usually folks don't deploy technology without full testing it, putting in the proper change management and approval. 2) Access to the server console is highly restricted 3) Outbound access via 80/433 web traffic from the servers/organization is restricted ( either via Proxy etc etc) ( Again some might have processes that talk out port 80/433 to the internet for process transfer and will be constrained by this factor) Z Edward E. Ziots CISSP, Network +, Security + Network Engineer Lifespan Organization Email:[email protected] Cell:401-639-3505 From: Malcolm Reitz [mailto:[email protected]] Sent: Tuesday, March 15, 2011 5:02 PM To: NT System Admin Issues Subject: IE9 on servers? We are updating our Windows Server 2008 R2 build to include Service Pack 1. During this effort, the question of "why not include IE9 at the same time?" was brought up. We discourage browsing from servers anyway, so it may not matter much other than keeping the build more current (possibly more secure or requiring fewer patches). I like keeping current, but I typically have somewhat of an aversion to deploying brand new, just released apps on our servers. Thoughts from the list? Thanks, -Malcolm ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
