Configuration Manager Package Preparation Guide for App Owners

While helping one of my customers recently, I provided some guidance for non-SCCM application owners to validate their app is ready to be deployed with ConfigMgr. I thought this might be useful to others.

To prepare a package for deployment with Configuration Manager, we'll need the following:

1. Unattended installation syntax
2. The ability to execute it under the system context

You can test these items using psexec.

Download PSExec from SysInternals here:

https://technet.microsoft.com/en-us/sysinternals/bb897553.aspx

From an *elevated* administrative CMD prompt, execute once downloaded:

PSEXEC -i -s -d CMD

Type "whoami" and validate that you see "nt authority\system"

This ensures that you are running under the system context

You can now test your unattended installation syntax under the system context. If it works properly here, it’ll work when executed via ConfigMgr.

Note:

• Execution syntax and/or batch files should be executed locally
  • Copy content local to test machine (do not run from a network location or specify UNC for installation files)
• Configuration Manager will handle getting the content distributed to the client

Validate proper installation of application

Deliver package content, install syntax, and clients to be targeted (or logic to detect them) for the deployment to ConfigMgr team.

Enjoy!

Comments

• Anonymous
  January 01, 2003
  thank you
• Anonymous
  March 03, 2015
  I had a customer ask for some guidance on deploying SQL 2014 via application management and thought that