Problem in Repackaging Citrix Webclient
Dear All,
I'm in learning phase of repackaging using Install Shield. I have repackagaed Citrix webclient. The problem is when I install raw application I'm able to access citrix web applications. If I install repackaged MSI and trying to access application like Excel it giving error " access denied to the specified path " Can any one please tellme why I'm getting this problem.
With Many Thanks,
Satya.
I'm in learning phase of repackaging using Install Shield. I have repackagaed Citrix webclient. The problem is when I install raw application I'm able to access citrix web applications. If I install repackaged MSI and trying to access application like Excel it giving error " access denied to the specified path " Can any one please tellme why I'm getting this problem.
With Many Thanks,
Satya.
0 Comments
[ + ] Show comments
Answers (9)
Please log in to answer
Posted by:
brenthunter2005
19 years ago
Posted by:
brenthunter2005
19 years ago
Posted by:
msvkumar
19 years ago
Posted by:
plangton
19 years ago
Hi Msvkumar,
As you stated you are a new to repackaging then it might be wise to listen to BrentHunter - its generally accepted that its bad practice to repackage MSI's. I have deployed the MSI that Brent Hunter mentions for many clients with various network configurations, citrix configurations etc and have always found the MSI provided to be the easiest method of deployment. If you need to customise it create a MST file.
Also, if you do have errors repackaging anything, the first thing I usually do is obtain a log ("msiexec /i EXAMPLE.MSI /L*v c:\EXAMPLE.LOG") and look in there for what might be causing the error. Posting relevant sections can help figuring out what is going wrong. But in this case I'd say forget about repackaging it and use the vendor MSI, or give a pretty good reason why you have to repackage it.
Hope that helps
Rgds
Paul
As you stated you are a new to repackaging then it might be wise to listen to BrentHunter - its generally accepted that its bad practice to repackage MSI's. I have deployed the MSI that Brent Hunter mentions for many clients with various network configurations, citrix configurations etc and have always found the MSI provided to be the easiest method of deployment. If you need to customise it create a MST file.
Also, if you do have errors repackaging anything, the first thing I usually do is obtain a log ("msiexec /i EXAMPLE.MSI /L*v c:\EXAMPLE.LOG") and look in there for what might be causing the error. Posting relevant sections can help figuring out what is going wrong. But in this case I'd say forget about repackaging it and use the vendor MSI, or give a pretty good reason why you have to repackage it.
Hope that helps
Rgds
Paul
Posted by:
msvkumar
19 years ago
Dear Paul ,
Thanks for the reply. I'm working in as repackager and I'm still in learning mode for repackaging. My client requirement is to repackage ica32t.exe and access the webserver to access applications. The problem I'm facing is after repackaging the ica32t.exe and installing I'm not able to access the applications. I also want to know how to determine applications are (e.g., ica32t.exe) suitable for repackaging or not.
Many Thanks,
Msv
Thanks for the reply. I'm working in as repackager and I'm still in learning mode for repackaging. My client requirement is to repackage ica32t.exe and access the webserver to access applications. The problem I'm facing is after repackaging the ica32t.exe and installing I'm not able to access the applications. I also want to know how to determine applications are (e.g., ica32t.exe) suitable for repackaging or not.
Many Thanks,
Msv
Posted by:
plangton
19 years ago
Gday Msv,
Well, the general rule is where the vendor provides an MSI, use that instead of repackaging. Sometimes it doesn't always work that way and you have to repackage a vendor provided MSI, but its relatively rare in my experience (though I've just recently gone through the joy of having to do that).
In this case, I'm assuming the client is relying on your packaging experience to guide them - I'd tell them that repackaging the ica32t client is a bad idea when Citrix kindly provide an MSI file. I'm pretty sure Citrix also have comprehensive deployment documentation and their forums are a good source of information too. At least give the vendor provided MSI a try before resorting to repackaging would be my advice.
Feel free to ignore it as you see fit :)
Paul
Well, the general rule is where the vendor provides an MSI, use that instead of repackaging. Sometimes it doesn't always work that way and you have to repackage a vendor provided MSI, but its relatively rare in my experience (though I've just recently gone through the joy of having to do that).
In this case, I'm assuming the client is relying on your packaging experience to guide them - I'd tell them that repackaging the ica32t client is a bad idea when Citrix kindly provide an MSI file. I'm pretty sure Citrix also have comprehensive deployment documentation and their forums are a good source of information too. At least give the vendor provided MSI a try before resorting to repackaging would be my advice.
Feel free to ignore it as you see fit :)
Paul
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.