You can however directly type the EXE file name and SCCM will accept it. When you click the Browse button next to Installation Program, you will notice that you cannot select EXE as the file type. Click browse next to Content Location and specify the location of the System Center Library share where the Silverlight package is present. Fill out the relevant information and continue to Content. Keep the default option of Windows Installer (.msi) and choose “Manually specify the deployment type information” option. We will create the Deployment Type as MSI deployment but we will use the EXE setup file of Silverlight. Continue to Deployment Types and click Add. Be sure to specify a relevant icon as well. Proceed to Application Catalog and fill out the additional details as needed. An example for Silverlight is shown below: Note: Always dedicate a central share location to store all System Center files.Ĭhoose the “Manually specify the application information” option in the wizard that appears and proceed to the next step. Following that, go to Software Library, Applications and Create Application: We will start by placing the Silverlight setup file in the System Center Library. This can be applied to any EXE setup file. I will use the Silverlight setup as an example in this article. Fortunately, working around that limitation is easy. As any SCCM administrator will tell you, ConfigMgr does not offer the option to deploy EXE files in a direct manner like MSI files.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |