For Microsoft System Center Configuration Manager (SCCM). If the HP Printer Security Plug-in is already installed on the MS SCCM server, and it. FTP print and download (for firmware updates) were introduced into JetDirect. Each report allows for saving the report as PDF by choosing the icon on the far right.
This article guides you through the process of creating an SCCM package to deploy an Adobe deployment package. Because both Adobe and Microsoft use the term package and because there are currently two versions of the Microsoft software in use, we use the following naming conventions for clarity in this article:
SCCM is designed for a great variety of network configurations. The best choice of deployment configuration for the Adobe package and its product install folder is the TS option, where the Adobe package and its product install folder are placed together on the same distribution server or servers.
When you create a package for deployment in Windows, Creative Cloud Packager creates two folders in your specified Save to location, Exceptions and Build.
The Exceptions folder contains folders with installers of various kinds (EXE, AIR, MSI) that cannot be deployed using the main MSI installer (because it cannot contain an embedded installer). You must create separate SCCM installers for each of these, using instructions in the ExceptionInfo.txt file at the top level of the Exceptions folder. The folder can be empty if your package has no dependencies on other installers.
The Build folder contains an MSI file whose filename uses the Package Name that you specified, and a subfolder named Setup. The subfolders are required to run the MSI file and install the product successfully.
Note: The packages created by Creative Cloud Packager silently use the Adobe installer subsystem, which in turn uses the native Windows installer, MSI. Therefore, you cannot wrap an Adobe install package inside of a Windows package for use with MSI because Windows prohibits such a recursive use of MSI.
Creating an SCCM package is a two-step process. First create a new SCCM package, then create install and uninstall programs.
Create install and uninstall programs for the SCCM package
Creative Cloud Packager generates a single MSI file in the Build folder, which you use for both installation and uninstallation of the product or suite. (Uninstall is not available for update packages, only for installation packages.)
If you want, you can create two separate SCCM programs for an installation package: one for installation and another for uninstallation. Name these programs to make it obvious to the users on the target systems who choose what the commands will do.
![]() Creating installers and uninstallers for Exceptions components
To create install and uninstall programs for the MSI, EXE, or AIR installers that are present in the Exceptions folder, use the commands described in the ExceptionInfo.txt file at the top level of the Exceptions folder.
For example, to create an SCCM install package for an MSI installer such as Adobe Flash Player 10, use this command:
msiexec.exe /i AdobeFlashPlayer10_plRel_mul.msi /qn
To create the uninstaller, use /uninstall instead of /i
msiexec.exe /uninstall AdobeFlashPlayer10_plRel_mul.msi /qn
Warning: For AIR-based installers, you can create a silent installer the same way, using the command listed in the ExceptionInfo.txt file. For these components, however, you cannot create a silent uninstaller. When uninstalling, you may need to uninstall AIR applications manually.
Follow the directions in this section once for each SCCM package program you want to advertise.
These directions assume you already have a collection with target systems where you will advertise the SCCM package programs.
When the SCCM package is advertised, the Windows toolbar of the target machines displays a notification that a program is scheduled to run.
Twitter™ and Facebook posts are not covered under the terms of Creative Commons.
Legal Notices | Online Privacy Policy
What is a software package in Configuration Manager?
One of the primary features of System Center Configuration Manager is its ability to distribute software packages to client computers.
A software package gives an administrator the ability to systematically distribute updates to clients. The updates can be new software, command lines, registry modifications, scripts etc. This gives you the ability to centrally manage and standardise an entire network of client computers.
There are three components involved in a software distribution-
The package
This is the ‘what’ of the distribution and can be anything from a software package to a command line.
The package consists of four parts, the source files, the package definition, the program and the distribution points. The collection
This is the ‘who’ of the distribution and is where you specify who receives the update. Normally we would target workstation computers, but you can also target groups or particular users. These are defined by “membership criteria” within the collection and for the update to be received the client must meet one or more of the criteria.
The advertisement
This is the ‘when’ of the distribution and is how you specify when the update runs. The advertisement is a process of applying a specific package to a specific collection. Advertisements can be set to start as soon as possible or at some point in the future and can be set to expire at a specific time.
Note:
The following steps will detail how to create a software package. It will add the software to the ‘Run Advertised Programs’ list in control panel of each of the targeted client computers.
If you want the software to install automatically on the client computer, continue through to ‘How to set a mandatory assignment’
Step1: Creating the PackageSource Files:
Source files are the installation files for the package. You will need to save these files to a shared folder which can be access by the Configuration Manager computer account.
In this example our source files will be saved to SCCMSEVERSMS_Source
Before you can create the package, you will need to obtain the required .exe or .msi files for the installation. You will also need to know the installation switches to use to make the installation automated. If you are unsure where to get the files or how to do a silent install see http://itsupportguides.com/configmgr-sccm.html or http://www.appdeploy.com
In this example we will be creating a software package for Mozilla Firefox 3.6
The source file has already been downloaded and saved the source folder, which will be SCCMSERVERSMS_SOURCEMozillaFirefox3.6
Step 2: Create the program
Step 3: Distribute the software
Step 4: Create advertisement
Step 5 (optional): How to set a mandatory assignment
Mandatory assignments are used to force the package to install automatically at a selected time.
With a mandatory assignment the package will start to run at the indicated time, which can be As Soon As Possible or a given time.
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |