Video Screencast Help
Search Video Help Close Back
to help

Endpoint Management Community Blog

Showing posts tagged with Wise Packaging
Showing posts in English
EdT | 25 Aug 2009 | 3 comments

The following changes should be made via an existing transform - eg: sp1033.mst for English installs.

Step 1 - Create a custom action in the CustomAction Table

Action: PolicyFix
Type: 3110
Source: (leave empty)
Target: Set S = CreateObject("WScript.Shell"):X="HKLM\Software\JavaSoft\Java Update\Policy\":Y="REG_DWORD":S.RegWrite x&"EnableJavaUpdate",0,Y:S.RegWrite x&"EnableAutoUpdateCheck",0,Y:S.RegWrite x&"NotifyDownload",0,Y:S.RegWrite x&"NotifyInstall",0,Y:S.RegWrite x&"Frequency",0,Y:S.RegWrite x&"UpdateSchedule",0,Y

Step 2: - Add a custom action to the InstallExecute Sequence:

Action: PolicyFix
Condition: NOT Installed
Sequence - Just before InstallFinalize - eg: Sequence: 3183

Step 3: In the Property Table, ensure the following properties have the stated values:

AUTOUPDATECHECK 0...
WiseUser | 20 Jul 2009 | 0 comments

Microsoft Best Practices on Component Rules

We need to keep the following points when we create components in Wise package Studio

We Can cusomise the rules by going into Component rules -> modify

  • Match components in previous versions of the .MSI
  • Add all executable files to their own components
  • Add all .TLB files to their own components
  • Group Matching .HLP and .CNT files together
  • Group matching .CHM and .CHI files together
  • Put registry keys associated with files or components in matching component
  • Put Current User registry keys in their own component
  • Put non-Current User registry keys in their own component
  • Group all non-executable files to their own component
  • Name new non-advertised shortcuts by destination directory
  • Group non-keypath resources by resource type
  • Create new components for resources not matching other criteria
WiseUser | 20 Jul 2009 | 0 comments

How to Package and deploy Visual Studio Team Explorer Application

1. Recording the installation

..\Setup\Setup.exe /CreateUnattend C:\temp\Install.ini

This Will create a unattend file named install.ini

2. Installing it silently

..\Setup\setup.exe /UnattendFile c:\temp\install.ini

This Will run the installation silently with settings in install.ini

R-Vijay | 25 Apr 2010 | 0 comments

This is just a Heads-up..!!

Hey Folks, I am writing a series of posts on Windows Installer FAQs. Do let me know your thoughts and feedback.
http://www.msigeek.com/615/windows-installer-faq-part-4

Also, it.. would be great, if you write questions tooo..!!

Cheers'
Vj

WiseUser | 09 Jul 2009 | 0 comments

Windows Installer is a powerful tool for managing application installations. Applications that are installed through the Windows Installer service gain the automatic benefit of self-repair and configuration of user data for new users. Additionally, applications written specifically to work with Windows Installer can install individual product features to run from source (server) and install on first use.

There is a registry key to look at for finding the sourcelist

HKEY_CLASSES_ROOT\Installer\Products\{Product guid}\Sourcelist
Media - > Might have 1, 2, 3 so one depending on the sourcelitst

We can set the Sourcelist during the installation itself
“msiexec.exe /I \\Test.msi SOURCELIST=”\\SMS02\Test\sourcefiles;\\SMS04\Test\sourcefiles;\\distsvr3\myfile\sourcefiles”

About SOURCELIST Property :

The SOURCELIST property is a semicolon-delimited list of network or URL source paths to the...

WiseUser | 01 Jul 2009 | 0 comments

To uninstall Media Player 11 , we need to execute the following command lines in the following sequence .

"C:\WINDOWS\$NtUninstallMSCompPackV1$\spuninst\spuninst.exe" /quiet /norestart
"C:\WINDOWS\$NtUninstallWudf01000$\spuninst\spuninst.exe" /quiet /norestart
C:\\WINDOWS\\$NtUninstallwmp11$\\spuninst\\spuninst.exe /quiet /norestart
C:\\WINDOWS\\$NtUninstallWMFDist11$\\spuninst\\spuninst.exe /quiet /norestart

WiseUser | 01 Jul 2009 | 0 comments

To uninstall the real player enterprise editon silently...

we can try
"C:\Program Files\Common Files\Real\Update_OB\rnuninst.exe" "RealNetworks|RealOneEnt|6.0" –s

WiseUser | 22 Jun 2009 | 0 comments

Some of the vendor executables are wrapped \ Created with the help of Wise Scripts. To deploy these executabales silently in enterprise environment we need to know the silent parameters used by the executables..

Most of the silent parameters are common and not necessarily to be same as it depends on the developer of the Wise script .

Most often used parameters are :

Setup.exe [/s] [/dir=destination] [/components=[a][b][c][d]] [/icons=[a][b]]

/s Silent install (you may receive a prompt to reboot)

/dir=destination Places the installation in the directory 'destination' (e.g. /dir=c:\style)

/components=[a][b][c][d] Installs Eg : [Program Files][Workstation .DLL's][Data][Newsletters] all these 4 are names of the components

/icons=[a][b] Creates desktop icons for [a][b] where a \ b are two shortcuts

/norestart PDF Exchange reboot command will be ignored (the computer will need to be manually rebooted at sometime for PDF Exchange to...

Screenbert | 16 Jun 2009 | 0 comments

To install a MUI Language for XP we folow these steps:

1 ) Download the the MUI Pack with the language(s) you need.
2 ) Get the latest MUIsetup.exe from SP3 and replace the one included in the MUI pack download.
3 ) Execute it using this command line where "0416" is your language code, in this case Portugese.
 
muisetup.exe /i 0416 /d 0416 /r /s

4 ) Then we execute another command that changes Regional Settings for all users that log onto that machine again using the language code in the BR.TXT file.

rundll32.exeshell32,Control_RunDLL intl.cpl,,/F:"BR.TXT"

The BR.TXT file has the following information:
[RegionalSettings]
LanguageGroup = 1
UserLocale = 00000416
SystemLocale = 00000416
InputLocale = 0416:00000416
MUILanguage = 0416
UserLocale_DefaultUser = 00000416
InputLocale_DefaultUser = 0416:00000416
MUILanguage_DefaultUser =...

WiseUser | 16 Jun 2009 | 0 comments

If an Msi has conditional features and the components have certain conditions , we need to make sure that the components are marked as Transitive components meaning the conditon is evaluated even during repair of an msi as well.

If the components are not set to transitive then we may experice a problem during repair of an msi as the installer will try to install without evaluating the conditon during repair.

Transitive Components :
https://www-secure.symantec.com/connect/blogs/transitive-components-wise-package-studio

Cheers
Wiseuser