Automated Deployment

[Mark Brady]

Our Desktop team is having problems getting PD packaged for deployment
using LanDesk.

Has anyone else ever run into an issue packaging?

Just looking for generic feedback, not necessarily solving this one
issue.

[rkkier]

We deploy using packages but we have a field engineering group that
creates all of them for us so I can't be terribly specific on the
details. I just provide them the software and a list of
customizations. I haven't received any feedback that there are
particular issues when they do the work. We've been doing it that way
from version 11. We did occasionally end up with DLL files that
weren't linked properly (we used to have the same problem occasionally
deploying EBFs) which we fixed with a script but that was on version
11. I don't believe we've had any problems with version 15.

[Mark Brady]

Post by rkkier
We deploy using packages but we have a field engineering group that
creates all of them for us so I can't be terribly specific on the
details.  I just provide them the software and a list of
customizations.  I haven't received any feedback that there are
particular issues when they do the work.  We've been doing it that way
from version 11.  We did occasionally end up with DLL files that
weren't linked properly (we used to have the same problem occasionally
deploying EBFs) which we fixed with a script but that was on version
11.  I don't believe we've had any problems with version 15.

That's great feedback... I really appreciate it.

Same setup here, so I'm not clear on the precise issue.

[Mark Brady]

Post by Mark Brady

Post by rkkier
We deploy using packages but we have a field engineering group that
creates all of them for us so I can't be terribly specific on the
details.  I just provide them the software and a list of
customizations.  I haven't received any feedback that there are
particular issues when they do the work.  We've been doing it that way
from version 11.  We did occasionally end up with DLL files that
weren't linked properly (we used to have the same problem occasionally
deploying EBFs) which we fixed with a script but that was on version
11.  I don't believe we've had any problems with version 15.

That's great feedback... I really appreciate it.
Same setup here, so I'm not clear on the precise issue.

Didn't think about using the zip instead of the msi.

[Mark Brady]

Post by Mark Brady

Post by Mark Brady

Post by rkkier
We deploy using packages but we have a field engineering group that
creates all of them for us so I can't be terribly specific on the
details.  I just provide them the software and a list of
customizations.  I haven't received any feedback that there are
particular issues when they do the work.  We've been doing it that way
from version 11.  We did occasionally end up with DLL files that
weren't linked properly (we used to have the same problem occasionally
deploying EBFs) which we fixed with a script but that was on version
11.  I don't believe we've had any problems with version 15.

That's great feedback... I really appreciate it.
Same setup here, so I'm not clear on the precise issue.

Didn't think about using the zip instead of the msi.

I run this msi fine but when the packagers try to run it they get.

Error 1334. The file 'sybase.core.platform.net2.0.1' cannot be
installed because the file cannot be found in the cabinet file
'Data1.cab'. This could indicate a network error, an error reading
from the cd-rom, or a problem with this package.