Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I've been asked by a client if it is possible to prepare our product for deployment via SSCM. Currently we produce an msi installer; is that what SCCM would need or do we need to do something to the msi package to make it SCCM friendly?

share|improve this question
up vote 2 down vote accepted

They're most likely asking you to make sure your product can be installed without any user interaction required. Since it's already an msi, you've got nothing to worry about unless you've done a very poor job at making the msi and included custom actions that popup separate dialogs that can't be turned off.

Basically, if you can install your msi with silent options like /qn or /qb and not be required to touch it before it's done installing, you're golden.

*Edit: I just thought of another caveat. If your application requires activation, ideally that activation should have the option of being included as part of the install process. At a worst case, it should at least be doable by limited-rights end-users. Essentially, everything that your application needs elevated access to do should have the ability to be automated during the install process.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.