I know, if I posted this on Altiris's website it will get locked...

I'm a WPS5.5 user and try to upgrade to 6.0 and noticed that MSDE or SQL database engine is required to install the software.

I'm wondering if anyone here has any feedback about 6.0, if the new version doesn't offer anything newer to speed up repackaging apps, then I'm not going to upgrade.

I felt it's not a good thing to make packaging software bulkier and require more components to run, it really burdens the clean machines that you need for snapshots and creates more fat to watch and remove.

Because of this new database engine requirement, I no longer can run my clean machine without a network unless I install the MSDE component and have it running on my host PC everytime.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


Both Wise and InstallShield recommend running the repackager tools remotely from a share. For Wise, this means a "client" installation which makes minimal changes to the system. I have not honestly taken a very close look at it yet, but one new feature that interests me is the new Wise Web Capture which is supposed to allow repackaging via an intranet URL.
Answered 11/15/2005 by: bkelly
Red Belt

Please log in to comment
I am waiting to get some free time to try the upgrade over at my primary client site but if I need MSDE or SQL in place it looks like I am going to have to beg for some access to set up a SQL database which means I'd better start asking now if I want a SQL database for christmas. I was using a rather large shared file server attached to a NAS but I highly doubt anybody will want MSDE on a file cluster server.

You could run two Virtual Machines on one machine with VMWare then you could still have the sharepoint without the physical box being networked. Still that is not a very nice solution. I know of some shops that run the sharepoint on a second partition so that they can just install the client and pump the data over to the second partition but I guess MSDE would blow this solution out of the water. Looks like that change in architecture is going to impact some people.
Answered 11/15/2005 by: kkaminsk
Ninth Degree Black Belt

Please log in to comment
I’ve spent a couple of days getting Wise 6 up and running. It is definitely an improvement in some ways, but still far from perfect.

The web capture feature (requires nothing on the clean build at all - capture from a web page) would be really cool, if only I could get it to actually function. The Wise Web server is a subject that Wise support was clueless about, so I will have to get some expert help for the Web Server.

The SQL database is funky on VM workstations that are not on the domain. I'm sure that with help from a SQL expert I could resolve the SQL Trust issues with VMWare. I have to get our SQL guy to figure out what I did wrong. (other than follow the Wise installation guide ... heh heh).

The "Legacy upgrade" function for InstallShield installations would be great, but I have yet to get a functioning MSI with it. It does actually do something, which is an improvement from the ISScript module in InstallShield’s admin suite, which did nothing.

The Wise server requires the "WiseSharePoint share" to be physically located on the server. I had to use up a LUN to get it to work with the SAN. The documentation said that you could use a UNC address, but support told me the documentation is wrong.

Wise support is still laughable, but I haven't given up on Wise 6 yet, because of the new features.
Answered 11/22/2005 by: BobTheBuilder
Purple Belt

Please log in to comment