HI all,
What changes are made when packaging msis for a Citrix server rather than a regular client desktop. Using installshield 5.x. Any suggestions appreciated.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Not much. In fact, I make a point of using the exact same MSIs across both. You worry more about where things get saved to on Citrix because of the concept behind Citrix but that's about it.
Answered 10/28/2004 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
Hi Oreillyr, VikingLoki,

I think this actually depends on the server setup more so than the fact you are using citrix. Say for instance you have an app packaged for normal desktops and you want to put it on a citrix server. If, as is common in server setups, the C drive is quite lean then you'll need to install it to another drive. This might not require a new MSI/MST, but in some cases it does.

Also, some utilities (like RelfectionX) for example, have utilities that test things like graphics speed and capabilities on first launch. These should be disabled for Citrix server installations (relfectionx is good because their website details which to leave out in a thin server environment).

It does need to be looked at carefully, also from the front that its a different OS you are installing on (Windows 200 Server vs Windows 2000 desktop, or Windows 2003 Server vs XP desktops, or whatever the case may be).

Hope this helps

Rgds

Paul
Answered 10/28/2004 by: plangton
Second Degree Blue Belt

Please log in to comment
0
There isn't any major difference in the MSI you create.

However, I do prefer to use the Citrix Packager and create WSF when I intend deploying to Citrix Server. There is no major reason for my decision with the exception that I Citrix Packager is made by Citrix.

Are u deploying with Citrix Installation Manager or some other 3rd party deployment tools?
Answered 10/29/2004 by: oofemioo
Blue Belt

Please log in to comment
0
Thanks guys,
I do not yet know what deployment tools i will be using as i have not started with company yet, but thanks for the heads up.
Answered 11/01/2004 by: oreillyr
Fifth Degree Brown Belt

Please log in to comment
0
Skip packaging, there are many ways to package Citrix, however pay attention to the ini files and registry because if you want a configured client, you need to make sure the configurations in the ini files are copied over.

Or you can create basic Citrix packages and publish *.ica files with all the configurations built in.
Answered 11/02/2004 by: Vision33r
Senior Yellow Belt

Please log in to comment
0
Most importantly is to get a clear understanding on how the user profiles are going to be handled.

If the user has a roaming profile then you have to package the apps differently in order to use that profile under Citrix.

Other than that Citrix will take care of itself......you gotta love it.
Answered 11/05/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
0
A quick question for MSIMaker.

Do you have to be bothered about roaming profiles if you are creating WSFs using Citrix Packager?

There shldn't be any problem with that as you will be installing on to Citrix Servers in the farm and then publishing to the clients!
Answered 11/05/2004 by: oofemioo
Blue Belt

Please log in to comment
0
What do you do with the current user keys if you are not allowed any under HKCU.
Answered 11/05/2004 by: oreillyr
Fifth Degree Brown Belt

Please log in to comment
0
oofemioo,

No you should be ok.....WSF's arent a worry.

oreillyr,

You can place them in a custom action to run when the app is launched. Just make a wisescript that inserts the keys and then calls the exe file.
Answered 11/05/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity