Do you have to re- sequence virtual application packages sequenced in version 4.1 before it will work on 4.6?
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
I'm not sure. Have tried opening and saving them again on a 4.6 sequencer? That used to work with the 4.5 sequencer, but haven't encountered any old sequences for some time now.
Answered 07/05/2010 by: Rheuvel
Brown Belt

Please log in to comment
0
Application which are sequnced in 4.1 will not support to 4.6 client you have to re-sequnce the application.

Thanks,
Sirish Kumar K
Answered 10/14/2010 by: Sirish727
Senior Yellow Belt

Please log in to comment
0
Has anyone tried updating the sequence with the AVE Professional? (Just considering another option, as this tool uses it's own engine...?)
Answered 10/15/2010 by: Rheuvel
Brown Belt

Please log in to comment
0
You may not need to resequnce the applications from scratch you did with 4.1 to work in 4.6. Try re-saving the application by opening it in 4.6 sequencer, that will update the files to be compatiable with 4.6 client. If that is not working, try to open the application in the Upgrade mode and save the application. If that is also not going to work which is less likely, you have to sequence the original application from scratch.
Answered 10/17/2010 by: lurims
Senior Yellow Belt

Please log in to comment
0
AVE or the sequencer are methods you can use but we are looking at a bulk conversion from 4.1 to 4.6 using SFTEncoder. Still haven't quite gone all the way just yet but throught I would share the approach.
Answered 10/18/2010 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
0
Application which are sequnced in 4.1 will not support to 4.6 client you have to re-sequnce the application.


Strictly speaking (in technical sense) this is not true as 4.5 Management Server is able to stream and 4.6 is able to run packages in 4.1 format, it's just that Microsoft recommends always re-saving the package in the latest format. Not to say there won't be any issues if you do do not upgrade them, but in general there's downward compatibility.

Only real structural changes between 4.1 and 4.6 (or 4.5) I'm aware of are addition of ACL information to the SFT (not a breaking change like history entries were, since there has been placeholder for ACLs from the beginning) and re-ordering of data blocks to better support differential streaming. Of course, there's few small changed implementation details for CP files etc. but nothing major.

/Kalle
Answered 10/20/2010 by: ksaunam
Orange Senior Belt

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