Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.
Endpoint Management Community Blog
Showing posts tagged with Wise Packaging
Showing posts in English
WiseUser | 18 Feb 2010 | 2 comments

When you click on the service it throws the following error "The Specified device handle does not correspond to a presen device"

In order to fix that we need to check whether the following key is present for the specif service

HKLM\SYSTEM\Currentcontrolset\enum\root\
with the name LEGACY_xxxx

xxx - service name

Sidd | 10 Feb 2010 | 9 comments

I'm not able to open PDF documents directly from web browser/internet site directly with latest version of Adobe Acrobat 9.3,  instead when I Open *.PDF from web browser/internet site directly it is opening with adobe in new window.

I have added following registry entry  to my package

[HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\9.0\Originals]
'bBrowserIntegration'=dword:00000000

(also verified this which the otherway  to modify the registry EDIT -> PREFFERENCES -> INTERNET -> and Uncheck (UnTick) “Display PDF in Browser” Option.)

Your suggestion are much appreciated  

Thanks,
Siddram

rjemison | 03 Feb 2010 | 0 comments

Although there is no native support or (easy method) to install a file on the root of the C:\ drive, from time to time it is necessary in order for an application function properly.  However, I recently had to an application which required this to be done and thought it would be a good idea to repost for everyone....since I could not find the original post from the old Wise KB many years ago.

Here are the steps required to install files directly on the root of the C:\ drive.

1.)  In the Installation Expert create a directory under the destination computer for your files to be placed in....(the name is irrelevant from a functional perspective but I name mine Root)
 
2.)  Add the files that you want installed directly to the root drive to this newly created directory.
 
3.)  Change from the Installation Expert to the MSI Script and add a custom action.  Use the...
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...