Export (0) Print
Expand All

Creating a Non-Microsoft Update Software Package in Windows Intune

Updated: November 1, 2013

Applies To: Windows Intune

You can upload non-Microsoft updates to be stored in the Windows Intune Cloud Storage space, and you can deploy non-Microsoft updates to client computers that are managed by using Windows Intune. This topic describes how to use the Upload Update wizard.

ImportantImportant
The Windows Intune Software Publisher can only deploy updates that do not require user interaction during the installation.

When you upload an update through the Windows Intune Software Publisher, you must specify any required command-line parameters (such as /q) to force the update to install silently (without user intervention) on the managed client computers. If you upload an update that requires user input, subsequent installations to the targeted client computers fail with a time-out error. To correct this problem, you can revise the update and specify the required command-line parameters.

If the update does not support silent installation, you cannot install the update by using Windows Intune.

The Upload Update wizard is interactive—the options and pages that are displayed vary depending on the selections that you make. As you proceed through the wizard, you can return to any previous page by selecting the page name in the left pane of the wizard.

  1. Open the Windows Intune administrator console.

  2. Open the Updates workspace.

  3. In the Uploads Overview pane, click Upload.

    noteNote
    When you start the Upload Update wizard for first time, a short delay occurs while the wizard application is installed.

  4. The Before you Begin page is displayed in the Upload Update wizard. This page describes the role of the wizard. You can remove this page from the wizard by selecting the Do not show this page again check box.

You must specify the setup files that are required to install the update. These files must exist on a disk that is available to Windows Intune by using a standard File Open dialog box—for example, in a folder on a local computer’s hard disk.

noteNote
If the update setup file is an executable program (exe) file, the wizard might not be able to extract this information.

  1. On the Update files page, click Browse to locate the setup files that are required to install the update package. By default, the browser opens in the Current User\Documents Library folder. Navigate to the appropriate folder and select the executable program file that installs the update. This can be a Windows Installer (.msi), Windows Installer patch (.msp) file, or .exe program file.

    ImportantImportant
    Please ensure that you have the appropriate licenses to upload, distribute and use this software.

  2. If additional files or folders are required to successfully install the update, select the Include additional files and subfolders from the same folder check box.

    The total size of the selected files to upload is displayed. Note that this size does not include the uncompressed or expanded sizes of installation files.

    ImportantImportant
    If your Cloud Storage space is nearing its limit, you receive a message that the upload might fail because you are close to your storage quota. After you have completed all the forms, the Upload Software – Upload Updates wizard tries to upload the software. If the compressed upload package exceeds your storage quota, the upload fails, and you receive a message that the size of the package exceeded the available storage quota.

    For more information about purchasing additional Cloud Storage space, see Purchasing Additional Storage for Windows Intune.

  3. Click Next.

  4. After you specify the setup files, the Update description page displays the name, description, and classification for software information that Windows Intune extracted from the software setup files. You can select a classification to label the type of update you are deploying (Updates, Critical Updates, Security Updates, Update Rollups, Service Packs). You can accept those values, or you can edit them.

    noteNote
    Windows Intune Software Publisher attempts to extract information to use in the name and description fields from the setup file you provided.

    If a required value (indicated with an asterisk) remains empty, the Next button will be disabled. Make sure to provide all required values.

The Specify requirements page lets you describe the targeted client computers on which the update can be installed. This information is used to ensure that the update is installed only on client computer platforms that are supported by the update publisher.

For each requirement, you can select a displayed option by selecting the check box next to that option. You can select multiple options. After you have made your selections, click Add. Your selections are displayed on the wizard page. To remove a selected option, click the X that is displayed to the right of the displayed option.

noteNote
The wizard displays options sequentially as you proceed. For example, the operating system options are displayed after you select the architecture.

  • On the Requirements page, click the Architecture is menu. Select one or more of the following options:

    • Any — Select this option to specify that the update can be installed on any architecture.

    • 32-bit — Select this option to specify that the update can be installed on 32-bit computers only.

    • 64-bit — Select this option to specify that the update can be installed on 64-bit computers only.

  1. On the Specify requirements page, click the Operating system is from menu. Select one or more of the following options:

    • Any — Select this option to specify that the update can be installed on any client operating system that is supported by Windows Intune.

    • From Windows XP — Select this option to specify that the earliest operating system that the targeted client computers can run is Windows XP.

      noteNote
      Windows Intune supports Windows XP Service Pack 3 only. Earlier versions of Windows XP are not supported.

    • From Windows Vista® — Select this option to specify that the earliest operating system that the targeted client computers can run is Windows Vista.

    • From Windows 7 — Select this option to specify that the earliest operating system that the targeted client computers can run is Windows 7.

    • From Windows 8 — Select this option to specify that the earliest operating system that the targeted client computers can run is Windows 8.

  2. After you identify the earliest supported operating systems, the wizard displays a new menu from which you can select the newest supported operating system. This is displayed as:

    Operating system is <selected operating systems> To [menu]

    where <selected operating systems> are the earliest supported operating systems that you selected in the previous step.

    Click the To menu to select the newest operating system that the update publisher supports for this update title. You can select All newer operating systems, or you can define specific operating systems. The displayed options vary depending on the previous selection.

    For example, if you select Windows Vista as the earliest supported operating system, the To menu displays Windows 7 and Windows 8. If you select Windows 7 as the earliest supported operating system, the To menu displays Windows 8.

    A completed selection looks something like this:

    Operating system is [from Windows Vista] To [All newer operating systems]

The Detection rules page lets you specify how Windows Intune determines whether the update already exists on targeted client computers.

noteNote
If the update setup file that you specified in To specify the update files is a Windows Installer or .msp file, the Detection rules page of the wizard does not appear. This is because Windows Installer and .msp files contain their own instructions for detecting previous update installations. In this case, you can continue directly to Specify the prerequisites.

ImportantImportant
The Use the default detection rules option is the first option that appears on the page, and it is preselected. If you proceed by using this option, Windows Intune always installs the update package on each targeted computer one time.

We highly recommend that you select the second option, Detect whether the update is installed by using the following rules (recommended) instead of using the default detection rules option. If you select the default detection rules and if the update is already installed on any targeted client computer, Windows Intune nevertheless installs the update on the targeted computer.

The detection rule types are as follows:

  • File exists

  • MSI product code exists

  • Registry key exists

You can select multiple detection rules. For example, you can create a File exists rule to search for an existing file in one file path, and then create another File exists rule to search for an existing file in a different file path. You can also select multiple detection rules of different types. For example, you can add a Registry key exists rule to the previous search criteria. In this case, Windows Intune first determines whether the file exists. If it does exist, the update is considered to be detected. If it does not exist, Windows Intune next examines whether the registry key exists.

  1. On the Detection rules page, select Detect whether the update is installed by using the following rules (recommended).

  2. Click the Add Rule menu. The following options display:

    • File exists

    • MSI product code exists

    • Registry key exists

  1. On the Add Rule menu, select the File exists check box, and then click Add.

  2. In the Specify file path text box, complete the file path including the file name that you want Windows Intune to find. To change the starting point, click the %ProgramFiles% menu.

    • If you select %ProgramFiles% as the file path starting point, Windows Intune searches for the file in both Program Files\

      <file path> and Program Files (x86)\ <file path>, where <file path> is the subfolder\file path that you type into the text box.



    • If you select %SystemDrive% as the file path starting point, Windows Intune searches for the file starting at the root of the client computer’s system drive (this is usually drive C).

    Examples:

     

    Specified path Search action

    Program Files\Adobe\Reader 10.0\Reader\AcroRd32.exe

    Searches for AcroRd32.exe in the Program Files\ Adobe\Reader 10.0\Reader\ and Program Files X86\ Adobe\Reader 10.0\Reader\ folders and subfolders.

    %SystemDrive%\AcroRd32.exe

    Searches for AcroRd32.exe throughout the whole system drive.

    %SystemDrive%\DevTools\AcroRd32.exe

    Searches for AcroRd32.exe on the system drive, in the \DevTools folder and subfolders.

  1. On the Add Rule menu, select the MSI product code exists check box, and then click Add.

  2. In the Choose an MSI file text box, click Browse to identify the name and location of a Windows Installer (.msi) file.

  1. On the Add Rule menu, select the MSI product code exists check box, and then click Add.

  2. In the Specify registry key path text box, complete the registry key name that starts with HKEY_LOCAL_MACHINE.

    noteNote
    Windows Intune checks both the 32-bit and 64-bit versions of the submitted registry path. If the registry key is found in either version, the update is considered to be detected.

You should always specify the software prerequisites on which the update depends, to prevent the update from being installed on computers that do not have the base software package.

noteNote
In this step, you are providing the name of a previous version of the software that is to be updated. For example, to update Adobe Acrobat Reader 9.4 to Acrobat Reader 10, you could specify File exists%ProgramFiles%\Adobe\Reader 9.0\Reader\AcroRd32.exe or Registry Key exists:HKEY_LOCAL_MACHINE\SOFTWARE\\Adobe\Acrobat Reader\9.0\.

  1. On the Prerequisites page, select from the following options:

    • None

    • It is managed software in Windows Intune.

      Click Browse to locate the software program.

    • The software is not managed by Windows Intune. I will add rules manually.

      Select from the following list:

      • File exists

      • MSI product code exists

      • Registry key exists

    For more information about selecting multiple detection rules, see Specify update detection rules.

You can add command-line arguments to the update deployment package. For more information about valid command-line arguments, see the update documentation.

ImportantImportant
Remember to use any required command-line parameter, such as /q, to force the update to install silently (without user intervention).

  1. On the Command line arguments page, click Yes.

  2. Type the command-line arguments in the Command line arguments text box.

By default, Windows Intune uses industry-standard return codes to report a failed or successful installation of an update package. The supplied return codes are:

 

Return code Interpretation

0

Success

3010

Success with restart

Any return code that is not listed is considered a failure.

Some updates use nonstandard interpretations for return codes. In this case, you can supply your own return code interpretations.

  1. On the Return codes page, click Yes.

  2. Click the Add return code menu.

  3. Select the return code type on the menu by selecting the check box next to the option. The options are Success and Success with restart. You can add both types. Click Add.

  4. Type the return code in the Return code text box.

    noteNote
    You can edit the default return codes in the provided Return code text boxes, instead of or in addition to adding new return codes.

After you enter all of the update information into the wizard, you can review your selections and optionally modify them before you start the upload.

  1. On the Summary page, review the update settings that you selected. You can scroll down to view the complete summary.

  2. You can change any parameter by clicking the appropriate page in the right pane and editing the selections.

  3. When you are satisfied with the update specifications, click Upload on the Summary page.

    The Upload page displays the status of the update as it uploads to Windows Intune.

    noteNote
    Uploaded update is stored in the Windows Intune Cloud Storage that your organization purchased. If you have insufficient free space to upload the update package, you are notified of this during the upload process. Windows Intune cannot determine sufficient free space until after the update upload has started, because compressed setup and installation files require more space when they are uncompressed.

    To manage your Cloud Storage space, see Purchasing Additional Storage for Windows Intune.

  4. The Summary page displays a message when the update is successfully loaded. You can exit the wizard.

After it is uploaded into Windows Intune, a non-Microsoft update is displayed in the Updates workspace in the All Updates pane. The final step is to approve and then deploy the non-Microsoft update. For more information, see Approving Updates in Windows Intune.

See Also

 
Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft