sade055

Today I have reached the top contributor spot in ITNinja which was earlier famous as AppDeploy. I was too happy and just wanted to share this on my blog :D

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...

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...

Many times it is an issue with the Administrators to deploy Google Chrome enterprise wide as there are lots of issues like: 1) Many people would have already installed various other versions of Chrome either through MSI or through exe. 2) How to customize Google chrome for enterprise wide deployment. *Edited: The new version has a few differences, please see the end of post on how to tackle this.* First, I would like to mention here that Google Chrome Enterprise version can be downloaded from the following location: http://www.google.com/intl/en/chrome/business/browser/ This site contains an MSI, which is already customized for business as in there are no desktop/Taskbar shortcuts and the application automatically goes to Program files folder. If you need to customize this, it is best to capture this MSI as it runs a Setup.exe from within. I would say that, this MSI is good enough to go like this too so not recommended to waste your time in capturing the MSI unless specifically require...

I was facing this issue with Installshield 2012 SP1. I had installed this product with AdminStudio 11. When I converted the MSI to .ism project through Installshield and then tried to build it back to MSI, I always got this error code 0. I could not find any documentation for this online so wrote back to Installshield Customer Support and they came up with this work around. Hope this will help you if you are facing this similar issue with your product. Do let me know by commenting if this has helped you. Just want to know how many people are affected by this, Within the .ism project: Go to the Direct Editor under the Additional Tools section. Select the InstallShield table. Change the SchemaVersion property from 772 to 771. Save, close, and reopen the project. InstallShield will prompt asking if you want to upgrade the project. Click Yes to upgrade the project. You should now be able to build the project without error. Apprantly this is the issue with this release of th...

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 = ...

As per best practices we should not hard code the Root Drive in our package. If your package goes to multiple machines having different Root Drives, then you can use this simple VBScript in your package as Custom Action and it will set the Root Drive automatically for that machine. This script picks up the Root Drive from where Program Files folder is installed. Set oshell=CreateObject("Wscript.shell") prog=oshell.ExpandEnvironmentStrings("%ProgramFiles%") vletter=Split(prog,":") dletter=vletter(0) & ":\" session.property("ROOTDRIVE")=dletter