install appliacations with users still on server.

[DrPink]

Sorry if this is to "newbie", but I'm still very green at this Citrix stuff.
To install applications on a citrix server, you have to set it to install mode after which it will "record" all the changes made to the registry and so forth, right?
So in theory, it's bad practice to install applications with users on the server, right?
In our company we have an experienced citrix guy who just install application and update whenever. What is your take on this, is this a no no, or general practice?

-the new guy

Real life needs a mucical score.
------------------------------------
Dr. Pink isn't in today, he's gone insane!

 

[KaronW]

It really depends on the app being installed. If it doesn't take long or require a reboot, I will do it. However - I am using Installation Manager so the install time is as short as possible. Also, if you are updating an app that users are on, it is not going to work usually.

Users that are on the system when it goes into install mode will be fine. New connections will be denied (logon is turned off).

Hope this helps!

 

[Dublin73]

So in theory, it's bad practice to install applications with users on the server, right?"

Right. Very bad practice.

Do not under any circumstances install so much as even a hotfix with users logged into a Citrix server.

 

[DrPink]

wow, totally different replies here. What I get from all this is, that allthough it's not recommended to install with users still on the server, it's obvious being practised.

Let me hear from some more of you guys. Any examples of installation gone bad due to users still being logged on?

Or are you a citrix guru, that's been doing this for YEARS without ever having problems?

Looking forward to your replies.


-The Doctor

Real life needs a mucical score.
------------------------------------
Dr. Pink isn't in today, he's gone insane!

 

[KaronW]

Sample of when I will install with users on-
This morning we had a "thinstall" application that needed to be updated.
I disable the app, removed the old, installed the new and enabled the app.
This was not an optional "wait til tonight". This was a critical application.
I would NOT do an install with users in the app itself, or if a reboot is required.
I have several apps that are called from a software server and these I do after hours as well, since it is used by many all day long.
System updates, hotfixes etc - I would wait til off hours so that it goes smoothly.
Hope this gives you an idea of when you can, and when you should not do changes with users on.

 

[enigma99]

DrPink,
I wouldn't recommend installing an update for either an Application or System specific issue while users are on the server...............BUT..in some cases you can =)
Lets take this example:
You have an update for Java and you have a server that has 30 users on it but none of them are running Java. I would disable the logins on the server and run the update. Everything should be cool.

BUT...say you have an update for Office or SAP or Windows! My recommendation would be to disable the server from logins and allow the users to log off gracefully (or kick them all off if you want too..lol). This will ensure that you don't have any files open on the application you are trying to update (which could cause an error during ur install).

Hope that helps.

 

[oisnds]

I'm not sure what you mean by "installing". If you are installing via the Citrix console using a package, I don't see a problem. If you are at the server, putting it into install mode then there is a problem.

 

[snootalope]

wow, not sure about others, but I install some things with a fully loaded server. Sure, I'm not going to do anything major, or anything that would require a reboot, but I've installed many of small things over the years with users on, never had a problem.