msi packaging in a citrix environment
Hi,
Can anyone tell me what are the major differences between creating packages for deployment through a Citrix environment other than through the more standard AD or SMS.
For instance, do you need to make any changes to the way you create the package or is all the config carried out on the Citrix server.
Any help will be most appreciated.
Can anyone tell me what are the major differences between creating packages for deployment through a Citrix environment other than through the more standard AD or SMS.
For instance, do you need to make any changes to the way you create the package or is all the config carried out on the Citrix server.
Any help will be most appreciated.
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
ankur12sharma
12 years ago
Posted by:
The Packeteer
18 years ago
Dear Kingici,
I have been installing and maintaining Citrix Farms for 6 years now and i am very happy with the currect Metaframe 4.0 Software Installation Manager.
The Citrix Deployment Software Manager is a fairly simple tool and does not have any wierd Bugs or problems as i know of in the Current version of Metaframe XP.
The main problem with Packaging for Citrix Farms is that some applications create " shadowkeys" this is often in combination with Current User Settings.
Some extra attention is required for the Current user settings within applications. this also in combination the usage with profiles within Citrix itself.
The Software manager has limited characters in the names and especialy the MST files you might be using in the Software manager. For example, the spaces and the long filenames can and wil stop your deployment with a MSI of MST. so keeps the names short and preferbly no spaces of other wierd stuff from your keyboard besides letters and numbers :-)
furthermore when creating a MSI or MST for a Citrix Farm it needs to be more perfect to perfect, because your MSI Impacts the entire server and not a single workstation when you deploy your application.
Also deployment on a Citrix Farm comes with a " big bang" , and this you dont want to mess up.
So testing testing testing testing testing.
When removing an Application dont forget to Uninstall if through the Software Installation Manager before Deleting it from the Manager.
Regards,
The Packeteer.
I have been installing and maintaining Citrix Farms for 6 years now and i am very happy with the currect Metaframe 4.0 Software Installation Manager.
The Citrix Deployment Software Manager is a fairly simple tool and does not have any wierd Bugs or problems as i know of in the Current version of Metaframe XP.
The main problem with Packaging for Citrix Farms is that some applications create " shadowkeys" this is often in combination with Current User Settings.
Some extra attention is required for the Current user settings within applications. this also in combination the usage with profiles within Citrix itself.
The Software manager has limited characters in the names and especialy the MST files you might be using in the Software manager. For example, the spaces and the long filenames can and wil stop your deployment with a MSI of MST. so keeps the names short and preferbly no spaces of other wierd stuff from your keyboard besides letters and numbers :-)
furthermore when creating a MSI or MST for a Citrix Farm it needs to be more perfect to perfect, because your MSI Impacts the entire server and not a single workstation when you deploy your application.
Also deployment on a Citrix Farm comes with a " big bang" , and this you dont want to mess up.
So testing testing testing testing testing.
When removing an Application dont forget to Uninstall if through the Software Installation Manager before Deleting it from the Manager.
Regards,
The Packeteer.
Posted by:
YatesAG
18 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.