Posts

Showing posts with the label install

Packaging Skype with Auto Update disabled

EDITED: I have edited this post on 30-Aug-2013 after some users comments that the given solution is not working. I have studied in depth the skype update process and created this solution for all. Please check below (Edited Section) for more information. Recently while packaging Skype for enterprise version, I could not disable the Auto Updates and finally found a way to get rid of it. You can get the latest version of Skype setup in MSI format from the following URL: http://download.skype.com/msi/SkypeSetup.msi  or http://www.skype.com/go/getskype-msi There is no registry, file which can disable the Auto Update functionality of Skype. I searched in lots of forums and all said that it automatically prompts for update. So finally I decided to look in the MSI and find why and how it is doing it. What I found was that Skype has an Updater.exe in the installation folder and it also creates a Skype Update service which points to this exe. I just removed this service and updater.exe file...

Error installing MSI from USB/DVD

Image
I faced an issue installing Flash player from USB drive though it was installing fine when installed from local or network drive. I found out the issue and resolution and want to document here for all of you. While installing the package, I got this error in the log files:   MSI (s) (44:C4) [14:06:35:318]: Source is incorrect. Volume label should be   but is SMSBOOT. MSI (s) (44:C4) [14:06:46:956]: Source is incorrect. Volume label should be   but is SMSBOOT.   While analysing this, I realized that the disk label for my USB is SMSBOOT and this could be anything else for you on your USB or DVD. I had added a file in my MSI through MST and it had created an entry in the Media table. This entry looked like this and this is the default entry which you get with the tool.     Behind the scene it was looking for a Blank labelled disk where this media is located but could not find it and it gave an error “Insert Disk”. I removed the label from my USB drive and kept...

Re-Packaging Apple Quicktime 7.72.80.56 and later versions

Quicktime comes as an EXE file which can be extracted easily with 7Zip. The three MSI I received were AppleApplicationSupport, AppleSoftwareUpdate and Quicktime. The Apple Update MSI can be discarded if you do not want to AutoUpdate your Quicktime. Apple Application Support MSI can be directly installed with /qb! switch. iTunes can be packaged separately and I have created a separate post for its customization: http://msiworld.blogspot.com.au/2012/06/re-packaging-apple-itunes-10617-and.html Quicktime should be modified through Transform as follows: 1) Change the following properties in your MST:  SCHEDULE_ASUW =0   REGSRCH_DESKTOP_SHORTCUTS =0  REBOOT=ReallySuppress 2) Install Quicktime on a test machine and do all the customizations you want with preferences. Once all customizations are complete, copy the quicktime.qtp file from "%userprofile%\AppData\LocalLow\Apple Computer\QuickTime\QuickTime.qtp" Add this file to Transform in C:\ProgramData\Apple Computer\QuickTi...

Re-Packaging Apple iTunes 10.6.1.7 and later

iTunes comes as an EXE file which can be extracted easily with 7Zip. The five MSI I received were AppleApplicationSupport, AppleMobileDeviceSupport64, AppleSoftwareUpdate, Bonjour64 and iTunes64. The Apple Software Update MSI and Bonjour MSI can be discarded if you do not want to AutoUpdate your iTunes. Bonjour can be kept if you want to allow file sharing on your desktop fleet. We did not want this so we removed this MSI. If you want to install Bonjour then it can be installed silently with /qb! switch. From this Version QuickTime is not part of iTunes. QuickTime can be packaged separately. more details for packaging this is in this post: http://msiworld.blogspot.com.au/2012/06/re-packaging-apple-quicktime-7728056.html Apple Application Support and Apple Mobile Device Support MSI can be installed silently with /qb! switch. You will have to customize iTunes by creating an MST file. 1) Change the following Public Properties in the MST: DESKTOP_SHORTCUTS = 0 DISABLEADVTSHORTCUTS = 0 SCHE...

VBScript to Determine 32-bit or 64-bit machine

Often we come across a situation where we need to see the Operating system bit information and then install application or do any customization. Here is a script which I use for this purpose: '=============================================================== Const HKEY_LOCAL_MACHINE = &H80000002 'Lines to get the computer Name Set wshShell = WScript.CreateObject( "WScript.Shell" ) strComputerName = wshShell.ExpandEnvironmentStrings( "%COMPUTERNAME%" )   '=============================================================== 'To check whether the OS is 32 bit or 64 bit of Windows 7 '=============================================================== 'Lines to detect whether the OS is 32 bit or 64 bit of Windows 7 Set oReg=GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputerName & "\root\default:StdRegProv")   strKeyPath = "HARDWARE\DESCRIPTION\System\CentralProcessor\0"   strValueName = ...

Installation and Uninstallation of MSU in silent mode

MSU are the Microsoft Update files. You can easily install the MSU file silently without reboot with the following command line: wusa.exe Windows6.1-KB123456-x86.msu /quiet /norestart To Uninstall it Silently you need to follow this simple procedure: 1) Run this command: expand c:\temp\Windows6.0-KB123456-x86.msu –F:Windows6.0-KB123456-x86.xml c:\temp 2) This will create an XML file in temp folder as per the name above. Edit this xml in notepad. 3)Find the assemblyidentity tag. Then, note the values of the following attributes: The name attribute The publickeytoken attribute The processArchitecture attribute The version attribute 4) Use the below command to uninstall the MSU from your machine. start /w pkgmgr /up: name ~ publickeytoken ~ processArchitecture ~~ version Note: The variables above need to be replaced by the vaules you have copied in step 3.

Packaging Mozilla Firefox

Most people dread while packaging Mozilla Firefox application and mostly try to make a silent installation of it. I was recently given task to package the latest Mozilla Firefox application. The same procedure can be used for version 10.0.1, 11, 12 and 13, 14 and 15 as well as I have tried and it works fine for all of these. I would like to share here how I could easily package it. Also by this method you will be able to do Proxy server settings. First step is to do a Setup capture of the source exe which can be downloaded from Mozilla’s website. Take care that you do not have to launch the application after the installation is completed. Second Step is to copy 3 files as stated below. You can add these files in your .wsi directly after the setup capture. These 3 files will solve all your issues. 1. Mozilla.cfg : This file needs to be added to "%programfiles%\Mozilla Firefox\" folder and should have this content: //Firefox Default Settings // set Firefox Default homepage pref...

Repackaging Microsoft Visual Studio 2010 Pro (Or any other version)

There are a lot of sites referring the installation of Microsoft Visual Studio 2010 in silent mode, but if you have a closer look, no one gives the complete information on the installation and Un-installation of the package. Here are the steps which I followed to install Visual Studio on 32 bit as well as 64 bit machines. I assure you that you can save atleast 1 to 2 man days by taking information from here before proceeding with your packaging. Copy the compete source to a directory and name this directory as per your standard naming convention. Copy these files to this main directory (Explanation and details also provided later) VS2010_Uninstall-RTM.ENU.exe Dfusrprf.xml User.vbs Arpsuppress64.reg Arpsuppress32.reg Arpsuppresswow64.reg ConfigurationFile.ini Setup.vbs Uninstall.vbs Uninstall.bat These files are the complete list of files which will do the trick to install and un-install the MS Visual Studio 2010 package. You can use WISE Script Editor to create an exe for most of the p...

Different Ways of Giving Permissions in Your Windows Installer

Image
Windows XP/Windows 7 works under a locked down environment in most organisations. The MSI authors generally have to provide permissions to the installation directory, so that the users without admin rights are able to access and write data into the installation directory. When you set permissions, you are specifying what level of access the user has to the folder and its files and what users can do within that folder such as save, delete, or read files. If you would like to know how to set permissions through Powershell Script, then I would recommend you to read my new blog entry here: http://msiworld.blogspot.com/2012/01/my-first-powershell-script.html There are six standard permission types which apply to files and folders in Windows XP/Windows 7: Full Control Modify Read & Execute List Folder Contents Read Write Each level represents a different set of actions users can perform. See the table below for more information. For folders you can also set your own unique permission...

Using SOURCEDIR Property in Package

SOURCEDIR property in MSI package refers to the location from where the MSI is installed in the machine. How do we use this property in our package. If you want to use a file which is kept in the source folder (next to where your MSI is placed), through Custom Action then you need to follow this procedure. The SOURCEDIR cannot be directly used in the package. If you read the logs then SOURCEDIR property is created and correctly pointed to the directory. But later the log shows that: Deleting SOURCEDIR... So the value of this property is deleted and the MSI does not get access to it. If you display message with [SOURCEDIR] property then it will be empty. The work around for this is that we can put an Action in the sequence called: "ResolveSource" after CostFinalize action. Then if you place your Custom Action after this action which refers to SOURCEDIR property then you will get the correct value of SOURCEDIR. Acknowledgement: I would like to thank my friend, Anurag, here who ...

Installation of MSP File in Silent Mode

The best way to install an MSP file in silent installation is with the following command line: msiexec /p patchfile.msp REINSTALL=ALL REINSTALLMODE=omus But if you do not give the command line options of REINSTALL and REINSTALLMODE then it will not patch the existing installation package. What it will do is update the locally cached copy of the MSI database. You can also use following command line to install patches like for Adobe etc.: msiexec /update patchfile.msp /qb! If you run the MSP in UI mode then it will patch the installation and will also update the locally cached copy of the installation, because when the dialogs are run they in turn set REINSTALL and REINSTALLMODE. For installation of MSU, which is used as update in Windows Vista and above, please follow this new post on my blog: http://msiworld.blogspot.com.au/2012/04/silent-install-and-uninstall-of-msu.html