I used to use the Wise Packager long ago with the Altiris Deployement Console. I am looking to possibly use this to create custom packages for software rollouts that would be independent of not only the Altiris Delpoyement console but also the network/environment it would be created/maintained on.

I am seeing some new applications that require an SQL instance and use of the 'repository manager'. My question is, can I ignore these and simply create my packages and implemnent them anywhere and any way I see fit?

Also, the MSi's Wise packages are virual instances correct? Does it run in some virtualized instance once installed? Any additional overhead? Sorry if I seem uninformed, it's been a long while. Thanks.
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


The most recent implementations of WPS use SQL Server instead of Access as the database medium. It is a pre-requisite and WPS won't install unless it can "see" the Wise d/b. You can, of course, use MSDE/Express Edition/whatever-MS-is-calling-it-this-week instead of full-blown SQL Server. That instance can obviously also live as just another VM, along with your packaging and testing VMs. There is no obligation to use the repository, once WPS is installed, though.

Wise MSIs are no different to anyone else's. They're not tied to any deployment system or to any virtual environment at all. WPS can "talk" virtualisation but, TBH, I haven't spent any time with that, preferring a more...er, robust solution like SoftGrid/AppV. You'll know what I mean by "robust" once you spend some time reaquainting yourself with WPS and working around its "features" which are still present 2 major releases on. IS is no better, BTW, so don't think I'm singling Altiris out for criticism.
Answered 03/25/2009 by: VBScab
Red Belt

Please log in to comment