Video Screencast Help
Scheduled Maintenance: Symantec Connect is scheduled to be down Saturday, April 19 from 10am to 2pm Pacific Standard Time (GMT: 5pm to 9pm) for server migration and upgrades.
Please accept our apologies in advance for any inconvenience this might cause.

Endpoint Management Community Blog

Showing posts tagged with Wise Packaging
Showing posts in English
jmetzger2 | 28 Jan 2010 | 3 comments

Thank you to all of those who have joined the Altiris Cincinnati User Group.  Please pass the information onto your team members and anyone else in the Cincinnati/Dayton/Northern Kentucky area.  We would love to see this group grow and be able to host an event here in Cincinnati.  Look forward to meeting all of those who use this fantastic product.

CableGuy41 | 04 Jan 2010 | 2 comments

Hi All,

Check out the following link to know about how to Migrate an existing Wise Package Studio Server to a new server.

http://www.linkedin.com/groupAnswers?viewQuestionAndAnswers=&discussionID=11593593&gid=56031&trk=EML_anet_qa_ttle-d7hOon0JumNFomgJt7dBpSBA

Please note: You will need to sign in to Linked in to view this article. If you aren't a member of Linked in you will need to signup (it's free).

Thanks,
Arun

WiseUser | 22 Dec 2009 | 0 comments

We can do that by running the following in command prompt

cscript.exe //h:cscript or
wscript.exe //h:wscript

Superfreak3 | 17 Dec 2009 | 0 comments
The biggest issue I've dealt with over the years is getting files to register properly via install.  I've used various authoring tools (mostly big name products) and I've had the same problem(s) with each - some more frequent than others.

For the most part, you add a file to your project/template and the information is scanned.  It never fails though, from release to release, I get one or two .dll's that just aren't getting registered.  I look in my project and it looks as though the registration stuff is there, but app errors so something not getting scanned/included properly.

I also noticed recently that when I pull an assembly into a template, it appears that registry information does get scanned for it.  However, I think its missing some 'stuff' that would be registered via RegAsm.  Being so busy since being called back from a layoff, I haven't been able to take registry snapshots to see what information is missing.

Then...

B_Raj | 10 Dec 2009 | 5 comments

AutoIt continues to be FREE !!

AutoIt v3 is a freeware BASIC-like scripting language designed for automating the Windows GUI and general scripting. It uses a combination of simulated keystrokes, mouse movement and window/control manipulation in order to automate tasks in a way not possible or reliable with other languages (e.g. VBScript and SendKeys). AutoIt is also very small, self-contained and will run on all versions of Windows out-of-the-box with no annoying “runtimes” required!

AutoIt was initially designed for PC “roll out” situations to reliably automate and configure thousands of PCs. Over time it has become a powerful language that supports complex expressions, user functions, loops and everything else that veteran scripters would expect.

 

Features:

  • Easy to learn BASIC-like syntax
  • Simulate keystrokes and mouse movements
  • Manipulate windows and processes
  • Interact with...
Pascal KOTTE | 20 Nov 2009 | 2 comments

Hello,
Are you already build some packages, and spend a few times to find the few tricks to get it works?
Does those packages are standard market packages?
Does those packages are in a MSI format?
Better: You already make it as a VSA format (SVS 2.1 and/or SWV 6.1) ?
Are you ready to sell services to provide such "well known packaging stuff" to others?

For sure, except for open source packages with fixed or standard "same for all" parameters, each of commercial application must be "repackaged" with at least the customer serial.
So, for well known packages should be not such a complicated to predefine "well known workload" to repackage it, providing a limited predefined list of questions for the custom,

Please, share this. I don't propose you do that for free, never "free lunch" !
I just suggest you propose a low cost service, which is sharing what you already...

B_Raj | 27 Oct 2009 | 1 comment

I’m here with 10 Questions & Answers to describe some of the basic things we need to take care while we approach to repackage an application.

 1.How do you Customize the vendor MSI?

 Vendor MSI’s should not be re-packaged or edited. Create a transform file to customize the vendor MSI. 

  • Some vendors supply utilities to customize their MSI behavior. Where this is the case, such utilities should be first considered as the appropriate method of customizing the MSI.  For example, use Microsoft’s Custom Installation Wizard  to customize the Office XP suite.  

2.When will you create a new MSI wrapper/ Wrapper Script?

This technique can be used in scenarios in which the installation program is not in MSI format and a setup capture is not appropriate.

Example:  Service packs and security patches

3.How do you treat INI files while repackage an...

B_Raj | 27 Oct 2009 | 0 comments

The table below lists some of  the language IDs for which the Windows Installer has

localized resource strings.

 

LangID           (Hex)              ACP                (Abbr)           Language (country)

 

 1025                 401                1256                ARA               Arabic (Saudi Arabia)

 1027         ...

B_Raj | 27 Oct 2009 | 3 comments

Greetings!!

My intention by publishing this post is to help the newbies to understand the basics about packaging and repackaging technologies.And ofcurse for those who prepare for interviews !! :-)

 1.What is Application Packaging?

Simply Application packaging means,the process of Creation of an Installation Program for a Software. Or we can say it as creation of a setup file. Setup.exe is an installation file, a program that puts all of the files and registry keys in the right places so that everything works correctly.

  2.What is Application Repackaging?

The process of creating a customized installation using an already packaged installation is termed as Re-packaging.

The setup routine can sometimes be very complex and open to user error especially when thousands of repeat installations are required in a corporate environment. In such environments reliability and repeatability are crucial.

Re-...

B_Raj | 26 Oct 2009 | 0 comments

While we deal with large windows installer packages, time required to install the package is one of the key factor in measuring the efficiency\quality of the package.

I’m briefing  here about some of the techniques that can be used to reduce the installation time of a MSI package.

Using MSIFASTINSTALL Property

The MSIFASTINSTALL property can be used to reduce the time required to install a large Windows Installer package. The property can be set on the command line or in the Property table to configure operations that the user or developer determines are non-essential for the installation.

How MSIFASTINSTALL Property will help to reduce the time?

1. This property helps to skip creating system restore point action in MSI install sequence.

2. This property helps to skip calculating the space requirements action in MSI install sequence. (Filecost)

Thus,if the developer is sure...