Friday, April 16, 2010

Deploy Office 2007 with SCCM

Office 2007 Dump Looks Like this….


Go to command prompt and change the working directory to office dump folder and type "setup.exe" /admin image

then you will see similar to below wizard


enter the values or choose the option that you want to customized then click on file and save now it will save as a FILE.MSP

Now lets try out our saved .MSP file and see if it works correctly before proceeding further

Now let's open CMD.
browse to your install and enter the following switch: "setup.exe" /adminfile file.msp

If this works create an Package and advertisement and push to the systems

Photos: Inside a Microsoft Data Center

Dublin Server Pod

Dublin Data Center















Dublin Data Center AerialChicago

Dublin Data Center Rooftop Air Unitsimage

Chicago data centerChill out

Highly automated


Inside a containerAir skates

Second floor server roomA lot to power

Keeping cool

Restoring Deleted All Systems Collection

Sometimes things just happen, sometimes you accidentally delete the All Systems collection because you were trying to do too many things at once.  I’ll fess up, I did it. 

Here’s how to restore the collection with the appropriate ID.  This solution was given to me by Microsoft Support.

Here is the VBS script that will do the restore:

####begin script

strSMSServer = "."
strParentCollID = "COLLROOT"
'This example creates the collection in the collection root.
'Replace COLLROOT with the CollectionID of an existing collection to make the new collection a child.

strCollectionName = "All Systems"
strCollectionComment = "This is the All Systems Collection."
Set objLoc = CreateObject("WbemScripting.SWbemLocator")
Set objSMS = objloc.ConnectServer(strSMSServer, "root\sms")
Set Results = objSMS.ExecQuery ("SELECT * From SMS_ProviderLocation WHERE ProviderForLocalSite = true")

For each Loc in Results
If Loc.ProviderForLocalSite = True Then
  Set objSMS = objLoc.ConnectServer(Loc.Machine, "root\sms\site_" & Loc.SiteCode)
End if

Set newCollection = objSMS.Get("SMS_Collection").SpawnInstance_()

'Create new "All Systems" collection
newCollection.Name = "All Systems"
newCollection.OwnedByThisSite = True
newCollection.Comment = strCollectionComment
newCollection.CollectionID = "SMS00001"
path = newCollection.Put_

'Set the Relationship
Set newCollectionRelation = objSMS.Get("SMS_CollectToSubCollect").SpawnInstance_()
newCollectionRelation.parentCollectionID = strParentCollID
newCollectionRelation.subCollectionID = ("SMS00001")

####end script

Once you’ve recreated the collection with the appropriate ID, then you’ll have to import the All Systems query for your membership rules.

Preload Package Tool for Configuration Manager 2007 


The Preload Package Tool (PreloadPkgOnSite.exe) is used to manually install compressed copies of software distribution package source files on Configuration Manager 2007 sites. After package source files are installed, a status message is sent up the site hierarchy indicating the presence of the new package source files. This avoids sites higher in the hierarchy from copying package source files over the network when distribution points at child site are selected to host software distribution package content that has already been preloaded on them.
The following feature enhancements have been made to the tool since it was released in the SMS 2003 Toolkit:

  • SQL Server named instance support
  • Administrator specified StoredPkgVersion value support


Problem Scenarios:

  1. When software distribution packages are created, information about them is sent to child sites in the hierarchy. If a child site has a distribution point installed that is listed in the package properties to host the content, the content is transferred over the network and uses available network bandwidth sending compressed copies of all required package source files. To avoid using network bandwidth, the Preload Package Tool can be used to copy compressed software distribution package source files to the remote child site before assigning the child site distribution point to host the package source files.
  2. If a child site fails that has a distribution point that is assigned to host software distribution package source files for a package created at a site higher in the hierarchy, all package source files will be resent over the network when the site is rebuilt and rejoined to the site hierarchy. To avoid this, the Preload Package Tool can be used to restore backed up compressed software distribution package source (.pck) files to the distribution point before rejoining the site to the hierarchy so they will already be present.
  1. Copy PreloadPkgOnSite.exe file to the .\program files installation directory\bin\i386 directory on the child site that you wish to preload compressed software distribution package source (.pck) files.
  2. Copy the applicable .pck files from the parent site or from a backup location to the distribution point share on the child site manually. After manually copying the files, ensure that the read-only NTFS file attribute for the .pck file is set.
  3. From a command prompt, run the tool using the following syntax: PreloadPkgOnSite.exe PkgID StoredPkgVersion.
  4. Running this command will update necessary software distribution package source location information for the site and forward this information up the hierarchy.
  5. After the package source file location information is sent up the hierarchy, the distribution point hosting the manually copied .pck files can be added to software distribution package source locations at without the need to transfer package source files over the network.
  1. The command line usage is: PreloadPkgOnSite.exe PkgID StoredPkgVersion
  2. If software package information already exists for a package at the site where the tool is used, the tool cannot be used.
  3. This tool is meant only for child sites and cannot be used to preload packages that were created at the child site where the tool is run.
  4. The PkgID.pck file must exist at the child site before the tool is run.
  • When run, this tool modifies site database information at all sites higher in the hierarchy. This tool should only be run on fully functioning child sites and only when necessary.
  • If the Configuration Manager 2007 distribution manager process has already started processing software distribution package information to be preloaded, there is no need to run the tool

How To Check If A BITS Enabled Distribution Point Is Up And Running like how we check MP

To check if a Management Point is up and running we have the mplist and mpcert http URLs that we can open in Internet Explorer.  We don’t have such URLs to test if a Distribution Point (DP) is up. Management Point and Distribution Point servers are very different roles.  The Management Point is a conduit for the clients to get information from the SQL database i.e. their cert, their machine policy, etc.  That is why there is a way to use an http link to get that information from SQL through the MP.  A DP is nothing but a server share.  To use BITS for downloads, we expose that share through a virtual IIS directory.


There is no http link with a cert on a DP that we can query on, but you can create a package just to test the DP health.  Here is how:

1. Create a text file and write in it whatever you want to see when you use the http URL to test the DP.

2. Rename that file and change the txt extension to html.

3. Create a package that only contains that file and add your distribution points to the package.

4. Get the package ID and then go to the IIS Manager console and find the name of the DP virtual directory and make sure there is a folder for your DP health package.

5. Use IE and type the URL for the server, the virtual IIS directory, the package ID folder, and then your html file.  In my case it looks like this:


6. You should get back the content of the text file you created on step one:


If you get the content of your html file back, your BITS enabled DP is up.

During OSD, format first partition only

Our helpdesk asked me to make a task sequence that can be used on computers with more than one partition. In this case, I had to make sure that the operating system will install only on first partition and will not touch the data on other partitions.

To achieve this, I copied another TS and modified the following 2 steps:

  • removed any “Format and Partition Disk” step
  • in the “Apply Operating System Image” step, under “Select the location where you want to apply this operating system” made the following modifications:
    • Destination: Specific disk and partition
    • Disk: 0 (if all computers are installed on first hard disk)
    • Partition: 1 (if all computers have OS installed on first partition)

This way, when TS runs, it automatically wipes partition 1 from disk 0 and will not touch any other partition or disk.

Wiping volume C:\




Detailed steps are below…for dummies
Format and Partition Disk:

In SCCM console navigate to Computer Management, Operating System Deployment, Task Sequences. Suppose you already created or imported a new Microsoft Deployment Task Sequence. If not, do it now.

  • Select the desired Task Sequence and click Edit in the Actions pane

  • In the <Name> Task Sequence Editor window, in the left pane select Format and Partition Disk


  • Click the yellow star to add a new partition
  • In the Partition name type the name of your system partition, this will be you disk C:
  • Under Partition options, select the Partition type as Primary
  • Choose how you want to set partition size, use a percentage of all hard disk drive or a fixed value. I use 50% of the HDD size, because not every time I know what HDD size new laptops/PCs will have but for sure it will be more than 80GB
  • Check the box to make this partition bootable
  • Under Formatting options, choose the file system you want and check the Quick format checkbox (optional) to save time during installation
  • Under Advanced options write a Variable name
  • Click OK when you’re done making your changes

TS 1st Partition properties

Now you’ll see this volume in the task sequence editor.

TS Properties

To add another partition click the yellow star again and fill in the following details:

  • In the Partition name type the name of your partition, this will be you disk D:

  • Under Partition options, select the Partition type as Primary

  • To use all the remaining disk space, select “Use a percentage of remaining free space” and set the Size(%) to 100

  • Under Formatting options, choose the file system you want and check the Quick format checkbox (optional)

  • Under Advanced options write a Variable name

  • Click OK when you’re done making your changes


Now you’ll see both volumes in your task sequence editor window. Next time you will deploy an operating system, the hard disk will format and create 2 partitions (C: and D:) and your computer will boot from the first partition (C:).

TS 2nd Partition properties

How does SCCM know that it needs to apply the OS image on the first partition and not the second? Well, it doesn’t, we will set this up in the “Apply Operating System Image” task.

Apply Operating System Image:

In SCCM console navigate to Computer Management, Operating System Deployment, Task Sequences.

  • Select the desired Task Sequence and click Edit in the Actions pane

  • In the <Name> Task Sequence Editor window, in the left pane select Apply Operating System Image

  • If you are installing the OS using the source media, then choose “Apply operating system from an original installation source” option using Browse choose one of the installation packages you have created when making the task sequence

  • If you have captured and OS image previously as a .wim file, you can select “Apply operating system from a captured image” option and select the image you want

  • Check to use a sysprep answer file and select the package using the Browse button

    • Now is the time to tell SCCM where you want your image to be applied.

              - To apply the image on a specific partition, under Destination select “Specific disk and partition”. Under Disk select 0 (zero) and under Partition select 1 (first partition). This is the option I use every time
              - To apply the image on the C: partition, under Destination select “Specific logical drive letter”. Under Disk letter select C:

    Format and Partition Disk

    This is it about these two tasks. Of course these tasks can be further customized using the Option tab of each task.

  • to find out linked report ID in all reports

    SELECT     TOP (100) PERCENT ReportID, Name, Category, DrillThroughReportID
    FROM       dbo.v_Report
    WHERE      (NOT (DrillThroughReportID IS NULL))
    ORDER BY   ReportID

    Upgrade Configuration Manager client from SMS 2003

    • Create a report that counts all client versions. (This is optional, just for information purposes).
      Report query is:

      SELECT TOP (100) PERCENT Client_Version0 AS [ConfigMgr client version], COUNT(Client_Version0) AS Total
      FROM dbo.v_R_System GROUP BY Client_Version0, Client0 HAVING (Client0 = 1)
      ORDER BY Total DESC, [ConfigMgr client version]

    • Create a collection (“Older Clients” for example) with all system resources with a client version not 4.00.6487.2000.
      Collection query is:

      SELECT SMS_R_SYSTEM.ResourceID, SMS_R_SYSTEM.ResourceType, SMS_R_SYSTEM.Name, SMS_R_SYSTEM.SMSUniqueIdentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup, SMS_R_SYSTEM.Client
      FROM SMS_R_System
      WHERE SMS_R_System.ClientVersion != "4.00.6487.2000"

      This way, system resources with older client version will be members of this collection.

    • Created a package and program with ConfigMgr client upgrade with custom command line parameters.
      Program command line is:


    • Advertised it to “Older Clients” collection.

    Now, as system resources with older client version are members of this collection they will receive the advertisement and will silently install the latest ConfigMgr client.

    When the collection will have no system resources, I will know that all clients are upgraded. Also, I can check this by opening the same report from any browser on any computer.

    How to create a Windows Image (.wim) file

    Method one:- With SCCM build and capture

    Method two : WDS capture Wizard

    method three: details steps are below

    Depending on what you need the .wim file for, you can create it manually or automatically.

    - To manually create a .wim file (capture image) you need a bootable CD with Windows PE (with ImageX.exe included) that you can create using Windows Automated Installation Kit.

    The basics steps are:

    1. Boot your computer using Windows PE disk.
    2. In the Windows PE command prompt navigate to the folder with ImageX.
    3. To capture the C: partition, use the following example:
      imagex.exe /capture C: D:\CapturedImage.wim “My captured image”

      Where: C: is the partition to be captured; D:\CapturedImage.wim is the place of the captured file; “My captured image” is the name of the file.
      More switches can be found on the ImageX Command-Line Options page.

    If you need the image for deployment, do not forget to run sysprep before capturing the image!

    - To automatically create a .wim file you can use a capture media created using Configuration Manager.

    If you want to capture a Windows XP OS, copy sysprep files to C:\sysprep. Newer operating systems have sysprep files installed by default.

    To use capture media:

    1. Insert the CD into your CD/DVD drive and shortly autoplay will open Image Capture Wizard.
    2. Clicking Next will show you Image Destination page. Select where to save the wim file.
    3. On the next page enter some information about the image.
    4. On the Summary page click Finish. The task sequence will start sysprep and restart the computer. After restart, the computer will boot to Windows PE and will capture a image of the machine.

    Deploy Office 2007 SP2 with ConfigMgr 2007

    As Microsoft recently released Service Pack 2 for Office 2007 suite, it is a good idea to add the update files to the package so it it can be deploy during the installation.

    So, first of all we have to download the SP2 executable file from here: (see additional information bellow).

    Then, using a command prompt window, extract the content of the package to a folder you can browse to.

    Extract (Click the image for a larger view)

    Accept EULA and click Continue.


    Select a folder to extract the files to.

    Browse For File

    When the extraction is complete, you should have the following files:

    Folder Structure

    At this point, you can delete the office2007sp2-kb953195-fullfile-en-us.exe file. Copy the other 9 files to “Updates” folder from your Office 2007 source folder.

    Updates folder

    Now you only have to update the distribution point/s and the next time Office 2007 will install, it will apply the SP2 update during Office 2007 installation.

    Applying Updates

    The same steps are valid for Visio and Project 2007.

    Microsoft Office Visio 2007 Service Pack 2 (SP2) can be downloaded from here:
    Microsoft Office Project 2007 Service Pack 2 (SP2) can be downloaded from here:

    Install drivers by computer model using WMI query

    When using task sequence, you might want to install different driver packages for different computer models. This can be accomplished by using a WMI query.

    First of all you need to have driver packages for all your computer models and know the exact model name for every computer.

    To find this, open a command prompt and type WMIC ComputerSystem GET Model (use this command on every computer to find it’s model).

    Then, Edit your task sequence. Add how many steps you need with “Apply Driver Package”. Select the driver package you have created for a certain computer model (HP dc5700 in my case).

    Apply Driver Package

    In the Options tab, click Add Condition and select Query WMI. In the WMI Query Properties window, make you sure you have root\cimv2 as WMI Namespace and write the following query in the WMI Query input box:

    SELECT * FROM Win32_ComputerSystem WHERE Model LIKE “%dc5700%” for HP Compaq dc5700 computer models.

    WMI Query

    Now, for every driver package, replace the model name with the computer model name the driver package is for. This way, the task sequence will install the correct drivers on every computer that will match the model specified in the query and will skip other steps sending the following status message: “The task sequence execution engine skipped the action (HP Compaq dc5700) in the group (Apply driver packages) because the condition was evaluated to be false”.

    Create a collection with systems without Adobe Reader 9

    select SMS_R_SYSTEM.ResourceID, SMS_R_SYSTEM.ResourceType, SMS_R_SYSTEM.Name, SMS_R_SYSTEM.SMSUniqueIdentifier, SMS_R_SYSTEM.ResourceDomainORWorkgroup, SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId where SMS_R_System.OperatingSystemNameandVersion not like "%Server%" and SMS_G_System_COMPUTER_SYSTEM.Name not in (select distinct SMS_G_System_COMPUTER_SYSTEM.Name from SMS_R_System inner join SMS_G_System_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName like "%Adobe Reader 9%")

    Install software using Task Sequence

    The TS Looks like this… to install software using a TS, is to have only Install Software steps. This way, you can install multiple software products using one advertisement instead of advertising every package. I use this only when I have an OS installed and I want to install software on it.

    This is how such a TS looks like:
    Install Software only

    Windows Installer : MSIEXEC Silent Install End to END

    The Windows Installer technology uses Msiexec.exe for installing MSI and MSP packages. This tool gives you full control over the installation process, allowing you to set:

    • install options (install, uninstall, administrative install, advertise a product)
    • display options (full, basic or no UI during the installation)
    • restart options (if the machine will be restarted after the installation)
    • logging options
    • update options (apply or remove updates)
    • repair options (only for an installed package)
    • public properties which are used by the installation

    The usual form of the msiexec command line is this:

    msiexec.exe <install_option> <path_to_package> [package_parameters]

    Install Options

    When launching an installation package, you can set the install type through these options:

    msiexec.exe [/i][/a][/j{u|m|/g|/t}][/x] <path_to_package>

    • /i - normal installation
    • /a - administrative install
    • /j - advertise the product

      • u - advertise to the current user
      • m - advertise to all users
      • /g - the language identifier used by the advertised package
      • /t - apply transform to advertise package

    • /x - uninstall the package

    Sample command line:

    msiexec.exe /i "C:\Example.msi"

    Display Options

    The user interface level of the installation can be configured according to the target environment. For example, a package distributed to clients should have a full UI, while a package deployed through Group Policy should have no user interface. Msiexec.exe sets the UI level of the installation through these options:

    msiexec.exe /i <path_to_package> [/quiet][/passive][/q{n|b|r|f}]

    • /quiet - quiet mode (there is no user interaction)
    • /passive - unattended mode (the installation shown only a progress bar)
    • /q - set the UI level:

      • n - no UI
      • b - basic UI
      • r - reduced UI
      • f - full UI

    Sample command line:

    msiexec.exe /i "C:\Example.msi" /qn

    Restart Options

    Sometimes an installation overwrites files which are in use or it needs to reboot the machine in order to finish. The reboot policy used by the installation can be set through these options:

    msiexec.exe /i <path_to_package> [/norestart][/promptrestart][/forcerestart]

    • /norestart - the machine will not be restarted after the installation is complete
    • /promptrestart - the user will be prompted if a reboot is required
    • /forcerestart - the machine will be restarted after the installation is complete

    Sample command line:

    msiexec.exe /i "C:\Example.msi" /norestart

    Logging Options

    When debugging an installation package you can use multiple logging parameters in order to create a log. This log will contain different information for each parameter you use:

    msiexec.exe [/i][/x] <path_to_package> [/L{i|w|e|a|r|u|c|m|o|p|v|x+|!|*}][/log] <path_to_log>

    • /L - enable logging

      • i - include status messages
      • w - include non-fatal warnings
      • e - include all error messages
      • a - mention when an action is started
      • r - include action-specific records
      • u - include user requests
      • c - include the initial UI parameters
      • m - include out-of-memory or fatal exit information
      • o - include out-of-disk-space messages
      • p - include terminal properties
      • v - verbose output
      • x - include extra debugging information
      • + - append to an existing log file
      • ! - flush each line to the log
      • * - log all information, except for v and x options

    • /log - the equivalent of /l*

    Sample command line:

    msiexec.exe /i "C:\Example.msi" /L*V "C:\package.log"

    Update Options

    The Windows Installer command line can apply or remove updates (patches for example) through these options:

    msiexec.exe [/update][/uninstall[/package<product_code_of_package>]] <path_to_package>

    • /update - apply updates (if there are multiple updates, you can separate them through the ";" character)
    • /uninstall - remove an update for a product (if there are multiple updates, you can separate them through the ";" character)

      • /package - specifies the package for which the update is removed

    Sample command lines:

    msiexec.exe /update "C:\MyPatch.msp"
    msiexec.exe /uninstall {1BCBF52C-CD1B-454D-AEF7-852F73967318} /package {AAD3D77A-7476-469F-ADF4-04424124E91D}

    TipNoteIn the above command line the first GUID is the Patch identifier GUID and the second one is the Product Code of the MSI for which the patch was applied.

    Repair Options

    If you have an installed package, you can use the Windows Installer command line for repairing it:

    msiexec.exe [/f{p|o|e|d|c|a|u|m|s|v}] <product_code>

    • /f - repair a package

      • p - repair only if a file is missing
      • o - repair if a file is missing or an older version is installed
      • e - repair if file is missing or an equal or older version is installed
      • d - repair if a file is missing or a different version is installed
      • c - repair if a file is missing or the checksum does not match the calculated value
      • a - forces all files to be reinstalled
      • u - repair all the required user-specific registry entries
      • m - repair all the required computer-specific registry entries
      • s - repair all existing shortcuts
      • v - run from source and recache the local package

    Sample command line:

    msiexec.exe /fa {AAD3D77A-7476-469F-ADF4-04424124E91D}

    NoteIn the above command line the GUID is the Product Code of the MSI which will be repaired.

    Set public properties

    The name of a public property contains only uppercase letters (for example PROPERTY). This type of properties can be set through the command line like this: PROPERTY="value".

    Sample command line:

    msiexec.exe /i "C:\Example.msi" MY_PROP="myValue"

  • MSIEXEC.EXE - the MSI executable, the program that performs the actual installation of the application.
  • /I - this switch informs the Windows Installer to install the specified application (as opposed to removing, reinstalling or repairing the application)
  • /QB-  - this switch instructs the Windows Installer to perform the installation with a basic user interface requiring no dialog boxes to be displayed. You might also use /QN to perform the installation with no user interface at all.

  • Correct syntax:

    msiexec /i A:\Example.msi PROPERTY=VALUE

    Incorrect syntax:

    msiexec /i PROPERTY=VALUE A:\Example.msi

    Property values that are literal strings must be enclosed in quotation marks. Include any white spaces in the string between the marks.

    msiexec /i A:\Example.msi PROPERTY="Embedded White Space"

    To clear a public property by using the command line, set its value to an empty string.

    msiexec /i A:\Example.msi PROPERTY=""

    For sections of text set apart by literal quotation marks, enclose the section with a second pair of quotation marks.

    msiexec /i A:\Example.msi PROPERTY="Embedded ""Quotes"" White Space"

    The following example shows a complicated command line.

    msiexec /i testdb.msi INSTALLLEVEL=3 /l* msi.log COMPANYNAME="Acme ""Widgets"" and ""Gizmos."""

    The following example shows advertisement options. Note that switches are not case-sensitive.

    msiexec /JM msisample.msi /T transform.mst /LIME logfile.txt

    The following example shows you how to install a new instance of a product to be advertised. This product is authored to support multiple instance transforms.

    msiexec /JM msisample.msi /T :instance1.mst;customization.mst /c /LIME logfile.txt

    The following example shows how to patch an instance of a product that is installed using multiple instance transforms.

    msiexec /p msipatch.msp;msipatch2.msp /n {00000001-0002-0000-0000-624474736554} /qb

    When you apply patches to a specific product, the /i and /p options cannot be specified together in a command line. In this case, you can apply patches to a product as follows.

    msiexec /i A:\Example.msi PATCH=msipatch.msp;msipatch2.msp /qb

    Some Sample Commands for EXE files:--

  • setup.exe /q
  • setup.exe /qn
  • setup.exe /silent
  • setup.exe /s
  • setup.exe /NoUserInput
  • setup.exe /unattended
  • setup.exe /CreateAnswerFile
  • setup.exe /quiet


  • MsiExec.exe /norestart /q/x{BA4B71D1-898E-4306-AE87-8BA7A596F0ED} REMOVE=ALL

    psexec \\computer_name MsiExec.exe /norestart /q/x{BA4B71D1-898E-4306-AE87-8BA7A596F0ED} REMOVE=ALL
    cmd='msiexec /qn /i %SOFTWARE%\adobereader93\AdbeRdr930_en_US.msi TRANSFORMS=%SOFTWARE%\adobereader93\AdbeRdr930_en_US.mst'
    'msiexec /qn /update %SOFTWARE%\AdobeReader93\AdbeRdrUpd932_all_incr.msp'

    'MsiExec.exe /x{AC76BA86-7AD7-1033-7B44-A80000000002} /qn '

    msiexec /qn /x{AC76BA86-7AD7-1033-7B44-A93000000001}

    msiexec.exe /qn /update "%SOFTWARE%\AdobeReader93\AdbeRdrUpd932_all_incr.msp"'
    'msiexec /qb /uninstall "%SOFTWARE%\adobe-reader\AcroRead.msi'
    siexec /i "UNCPath\filename.msi" /qn

    With the Product key

    msiexec /i "UNCPath\filename.msi" /qn PIDKEY="Key value without dashes


    jre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s ADDLOCAL=jrecore,extra MOZILLA=1

    jre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s /v"/qn ADDLOCAL=ALL IEXPLORER=1 INSTALLDIR=D:\java\jre"

    start /w jre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s ADDLOCAL=jrecore,extra MOZILLA=1

    msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0n1n2n3n4n50}

    msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150000}
    msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0151020}

    Creating a Log File
    If you want to create a log file describing the installation/uninstallation, append /L C:\<path>setup.log to the install/uninstall command. The following is an example for installation:
    Installation Example
    jre-1_5_0-bin-b99-windows-i586-12_aug_2003.exe /s /L C:\<path>setup.log
    The following is an example for uninstalling:

    Uninstalling Example
    msiexec.exe /qn /x {3248F0A8-6813-11D6-A77B-00B0D0150000} /L C:\<path>setup.log

    Note:- Adobe Customization Wizard 9 will help you to create MST file for silent installation


    Below is available WINZIP MSI File
    ymsgrie.exe /s /v/passive - install Yahoo! Messenger silent, with progress bar

    Team Viewer :--

    The /S switch for silent install of TEAMVIEWER WORKS!
    but you must do the following :
    download the program (preferably the latest version) ..or ..if you have it on your hard drive , open it... (AND LET IT OPEN! DO NOT CLOSE OR INSTALL THE APLICATION. JUST DUBLE-CLICK IT!!)
    Then , go to C:\Documents and Settings\Administrator\Local Settings\Temp. There you'll see a folder called TeamViewer. Open that folder. Inside you'll have 2 files. Teamviewer.exe and tvinfo.ini
    Copy the Teamviewer from that folder and paste wherever you want. After this you can close the other application.
    With the new teamviewer.exew which you copyed from the temp folder , u can run it sillently. Use the /S Switch. Works with WPI also.


    If you find MSiexec has problem then you can run below two commands

    msiexec /unregister  ---> for unregistering the windows installer


    msiexec /regserver---> for registering the windows installer

    Released Versions of Windows Installer

    The table in this topic identifies the released versions of the Windows Installer.


    Windows Installer 2.0
    Released with Windows XP.

    Windows Installer 2.0
    Released with Windows 2000 Server with Service Pack 3 (SP3).

    Windows Installer 2.0
    Released with Windows 2000 Server with Service Pack 4 (SP4).

    Windows Installer 2.0
    Released as a redistributable.

    Windows Installer 2.0
    Released with Windows XP with Service Pack 1 (SP1).

    Windows Installer 2.0
    Released with Windows Server 2003.

    Windows Installer 3.0
    Released with Windows XP with Service Pack 2 (SP2). Released as a redistributable.

    Windows Installer 3.1
    Released as a redistributable. This version is has the same functionality as version 3.1.4000.2435.

    Windows Installer 3.1
    Released with Windows Server 2003 with Service Pack 1 (SP1) and Windows XP Professional x64 Edition. Update this version to version 3.1.4000.2435 to address the issue discussed in KB898628.

    Windows Installer 3.1
    Released with Windows Server 2003 with Service Pack 2 (SP2).

    Windows Installer 3.1
    Released with a fix to address the issue discussed in KB898628. This is the latest version of Windows Installer 3.1.

    Windows Installer 3.1
    Released with Windows XP with Service Pack 3 (SP3).

    Windows Installer 4.0
    Released with Windows Vista.

    Windows Installer 4.0
    Released with Windows Vista with Service Pack 1 (SP1) and Windows Server 2008.

    Windows Installer 4.5
    Released with Windows Vista with Service Pack 2 (SP2) and Windows Server 2008 with Service Pack (SP2.)

    Windows Installer 4.5
    Released as a redistributable for Windows Vista.

    Windows Installer 4.5
    Released as a redistributable for Windows Server 2008 and Windows Vista with SP1.

    Windows Installer 4.5
    Released as a redistributable for Windows XP with Service Pack 2 (SP2) and later, and Windows Server 2003 with SP1 and later.

    Windows Installer 5.0 is released with Windows Server 2008 R2 and Windows 7.


    To create exe file by using winrar for silent installation / Self Extractor


    create SFX archive”. Change the archive name if you like but it must have the .exe extension.
    Posted Image
    Switch to the Advanced tab and select “SFX options” to open Advanced SFX options window.
    Posted Image
    On the General tab in the “Path to extract” box type the path you want to extract the installer to. Make sure it is the same path you have in the antivir.cmd file. Then in the “Run after extraction” box type in the path to the antivir.cmd file.
    Posted Image
    Change to the Modes tab and select the “hide all” and “overwrite existing files” radio buttons.
    Posted Image
    Close the “Advanced SFX Options” window by clicking OK, then click OK on the “Archive name and parameters” window to start creating the installer. The finished installer is created in the antivirpec folder.


    Also you can do with 7zip  where you will have more options compare to winrar or winzipself extractor.

    Office 2007 silent install with SCCM 2007

    So here is his tip on how to create a customized MSP file with OCT:

    1. Go to the original package source that contains the Office 2007 setup files
    2. From the directory that contains the Office 2007 setup files, run setup.exe /admin. This should open the Office Customization Toolkit (OCT)
    3. Select to Create a new Setup customization file
    4. In the “Install location and organization name”, set the default installation location and organization name.
    5. Click on Licensing and user interface. Make sure you enter a valid product key, check the EULA checkbox and set Display level to None. Completion notice checkbox should not be checked and Suppress modal should be checked.
    6. Save the MSP file by going to File --> Save. Give the file a name and save it to the Updates folder located in the Office 2007 installation source folder. By saving it to the Updates folder, the /adminfile switch will not need to be used as part of setup.exe. If the file is not saved to the Updates folder, make sure that the /adminfile switch is used as part of setup.exe and that it points to the MSP file just created.

    Further more, with OCT you can customize almost everything regarding how your Word/Excel etc. applications will run. What I liked most is the possibility to create the default profile in Outlook if you are using an Exchange server in your organization.

    Don’t forget to save the MSP file and to put the file in Updates folder or to use /adminfile <path to MST file> switch .


    Hope I will try to post when i get some time

    Thursday, April 15, 2010

    Before You Begin patching the

    Before You Begin/ready for patching

    Always read the Release Notes for the patch you are about to install. The Release Notes usually contain information on known issues with the patch and specific procedures on how to install them.

    Online resources for SCCM training

    Online hosted virtual machines :

    Downloadable VHD of with sccm 2007 R2 installed.

    Wednesday, April 14, 2010

    List of all predefined SMS/SCCM Exit-Codes:



    2250*) A retry exit code will force SMS/SCCM to rerun the advertisement after a timeout of 10 minutes.