I'm trying to figure out the best practices for installing software on session hosts while there are users logged in. I have someone arguing that it's not critical to get users logged out before proceeding with the installation. What do you all think?
5 Answers
I've installed programs while users were connected in the past, and it usually worked fine. Before installation, I'd run 'change user /install' to enable the install mode, and after installing, I'd switch back with 'change user /execute'. Not sure if that’s still necessary, but it’s what I always did.
It really depends on what you're installing. I try to get users out whenever possible, but sometimes I've sneaked in updates during the day. Just make sure you know exactly what the software does—like with browsers, never update those while users are logged in! But if it’s a minor update for a program not heavily used, you might get away with it.
Honestly, I only install new programs on the golden image and then re-image the session hosts. It's much simpler and avoids potential issues with users still being logged in.
He's right; installing software while users are on can lead to performance hiccups. It's best to perform installations during off-peak hours when maintenance mode is activated.
Lol, I've totally blamed performance issues on everything under the sun, from sun spots to line work outside. But seriously, it's better to get everyone off before you make changes.
One good way to approach it is to drain one session host at a time. This means you'd install the software on one host at a time, then re-enable it before moving on to the next one. This minimizes disruption for users.
I prefer to use the disconnect method whenever I install something too. I always forget about the drain switch!
You can also use 'change login /disable' to prevent new users from logging in while you install, then re-enable with 'change login /enable' after you're done.