Configuring Applications and Packages with License File (SCCM 2012)

[MarshMan0331]

I am new to using SCCM 2012, need help adding licnece files and configruations to Applications and packages within SCCM 2012. This has to be zero user interaction.

Programs will be Project 2010, Visio 2012, Adobe Pro, Photoshop, and some other programs.

Also is thier a way to create applications with .exe files.

 

Garrett

[Peter van der Woude]

By creating a new Application, selecting Manual specify the application information and following the wizard you can create an Application (and Deployment Type) for an executable.

[Rocket Man]

 

Programs will be Project 2010, Visio 2012, Adobe Pro, Photoshop, and some other programs.

 

For the MS software use the OCT tool that will allow you to embed your key into the MSP/config files.

For adobe they also have a application management piece of software that will allow you to run your adobe packages seemlessly without user interaction!

[Jorgen Nilsson]

Hi,

To create a an application with a deployment type "Script Installer" you have to select "Manually specify the application information", then you can select the "Script Installer" deployment type.

For office Products you can use the setup.exe /admin to create a .msp file which can be used for deployment. http://www.migee.com/2010/12/08/office-2010-completely-silent-install-a-really-really-quick-rundown/

For Adobe Product I would check for information att for instance ITNinja.com on how to deploy them.

Regards,
Jörgen

[MarshMan0331]

By creating a new Application, selecting Manual specify the application information and following the wizard you can create an Application (and Deployment Type) for an executable.

I have seen a few forums in here where you state this. But do you have a guide on how to do it. I tried yesterday but it was failing for me.

[Peter33]

Here you go ...

 

Create a new application and chose the manual option

 

Fill the application informations with something useful

 

Make sure the localized app name is filled properly. That's what's shown to the use in the software center

 

Here click "add", to create a new deployment type

 

As type chose "script installer"

 

Add the source location and the installation command. It's recommended also to add a working uninstall command to support a later supersedence.

 

This is most important. Create a proper detection methode. The most practicable way is to use the Product ID of the program. Some do not supply one though, like 7zip 32 Bit. There you can go for the registry entry of the uninstall section.

 

In the next step you can define some requirements. I am always defining the supported operating systems here.

[MarshMan0331]

Awesome, Thank you Guys.

[mkhan]

Can anyone tell me please- what will be the format of GUID, if I have MAK product key abcd-1234-abcd-1234-abcd-1234

I try {abcd1234abcd1234abcd1234} but it is saying "Specify a valid GUID".

 

Thanks in advance.

[narcoticmind]

Can anyone tell me please- what will be the format of GUID, if I have MAK product key abcd-1234-abcd-1234-abcd-1234

I try {abcd1234abcd1234abcd1234} but it is saying "Specify a valid GUID".

 

Thanks in advance.

 

MAK/KMS product keys don't have anything to do with MSI packages GUIDs...

 

The easiest way for me to find the MSI GUID to be used in the application properties, is to introduce the actual .MSI for the GUI as shown above this thread (just click browse).

Another way is to install the application and check for HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall and try to find the Key pointing to the installed application, there should

be msiexec.exe /x {guid} command shown...