updating Internet explorer on citrix

[ITR]

I just realized that some of our users are using citrix to surf the web(dont ask me why).

Anyway, when you go to windowsupdate to update IE, do you have to be in installer mode?

 

[Illuvatar]

When installing ANYTHING on a citrix server it is advisable to switch to installer mode. However, make sure that you enter a CHANGE USER /INSTALL in the usrlogn2.cmd file to make sure that the server gets into installer mode when you have to make a reboot. If you login after the reboot, the the server goes on with the setting up. This way you make sure the server is in install mode when you logon.

I actually don;t believe in upgrading. Best way is to remove the old explorer and install the new version. But this is a personal thought

 

[CitrixEngineer]

From IE 5.5 onwards it's quite safe to upgrade IE on a Terminal Server. There were all kinds of wierd issues on previous builds of IE, however - with 5.0 you had to ensure that your paging file was a certain size, if I remember rightly!

You don't want users to be able to install stuff via IE, though - and DEFINITELY not Windows updates. Sadly, the defaults allow WU to install stuff without the server going into install mode - which can create real headaches for everyone.

This should all have been thoroughly tested before rollout (see my FAQs on testing for why I think it's important). You can lock IE down by using the IE Res Kit and policies - but you may have to go back to the test lab and build a server from scratch. I would not like to do this kind of surgery in a production environment!

CitrixEngineer@yahoo.co.uk

 

[ITR]

Thanks for the help.

I've never heard of putting the change user command in the usrlogn2.cmd file. Actually, I've never messed around with the usrlogn2.cmd file before.

I tried searching the metaframexp admin guide, google, and this forum and couldn't find too much info on it. Could you give me a quick rundown on what the file does, etc.

Thanks

 

[Illuvatar]

When a user logs on a metaframe server, Usrlogon.cmd will be started. It's an alternative loginscript for a terminal server. Usrlogon will first start UsrLogn1.cmd. This script is used for situations where you do not have or need a rootdrive mapping (chkroot in application compat scripts). Next it will run usrlogn2. Here you can script special mappings and checks that you do not want to happen in the central logon script because you do not want to apply this to every domain user. Only users loging on on this server will get this script. This way you can script automatic profile creation (outlook), map special printers, map special drives etc. If you enter CHANGE USER /INSTALL the moment a user (admin) logs on the server will be in installation mode. Normally, when installation continues after reboot, you do not have the time to open a command prompt and type in the sequence manually.