locked
How to Distribute a Software Package without Prompting in Client End RRS feed

  • Question

  • Hi ,

    I've created a Software Package for Distribute from SCCM. i monitored this thing . After around 60 minutes it is starting to install in Client's End.

    But it is prompt for Install. Then Client should Click INSTALL button. ( I tried with Distributing Microsoft SliverLight 4.0 ) .

    I think that i've missed some thing. but can't find it. my requirement is install a package without asking from User.

    what should I do for this ?


    Regards, COMDINI
    Saturday, June 18, 2011 6:47 AM

Answers

  • You need to specify this in the actual package and in the commandline properties. The package must support a silent install, in ConfigMgr. you can configure the program to run with no user interaction.
    Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund
    • Proposed as answer by Garth JonesMVP Saturday, June 18, 2011 2:47 PM
    • Marked as answer by Sabrina Shen Tuesday, June 21, 2011 6:38 AM
    Saturday, June 18, 2011 7:08 AM
  • Hello - As mentioned by Kent the MSI should support silent install.
    Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Sabrina Shen Tuesday, June 21, 2011 6:38 AM
    Saturday, June 18, 2011 8:34 AM
  • Correct. ConfigMgr has no way of forcing an installtion to do something, all it (or any other deployment method) can really do is run a command-line: specifically whatever command-line you give it. Thus, the onus is on you to discover and test the command-line so that it behaves the way you want it to including making it silent.

    In the case of MSIs (that are well-written and don't include uncontrollable custom actions or other embedded installations) this is an easy task because /q always tells Windows Installer to perform a silent install: http://msdn.microsoft.com/en-us/library/aa367988(v=VS.85).aspx.

    However, in the case of .exe (or other types of) installers, you have to consult the vendor on what to do because there is no absolute or enforced standard. Many setup.exe programs were created by InstallShield so follow their standards, but that is no guarentee. You can often discover the possible command-line switches by running setup.exe /?.

    For silverlight specifically, it is a setup.exe created by the silverlight team and simply running silverlight.exe /? will inform you that /q is the proper command-line argument to make the install silent.


    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    • Proposed as answer by Garth JonesMVP Saturday, June 18, 2011 2:47 PM
    • Marked as answer by Sabrina Shen Tuesday, June 21, 2011 6:38 AM
    Saturday, June 18, 2011 1:14 PM

All replies

  • You need to specify this in the actual package and in the commandline properties. The package must support a silent install, in ConfigMgr. you can configure the program to run with no user interaction.
    Kent Agerlund | My blogs: http://blog.coretech.dk/author/kea/ and http://scug.dk/ | Twitter @Agerlund | Linkedin: /kentagerlund
    • Proposed as answer by Garth JonesMVP Saturday, June 18, 2011 2:47 PM
    • Marked as answer by Sabrina Shen Tuesday, June 21, 2011 6:38 AM
    Saturday, June 18, 2011 7:08 AM
  • Hi Kent.

     

    thanks for your reply . that mean we can't configure it from Silent Mode from SCCM. it should shupport Silent Mode ?


    Regards, COMDINI
    Saturday, June 18, 2011 7:52 AM
  • Hello - As mentioned by Kent the MSI should support silent install.
    Anoop C Nair - This posting is provided "AS IS" with no warranties or guarantees, and confers no rights. |Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Marked as answer by Sabrina Shen Tuesday, June 21, 2011 6:38 AM
    Saturday, June 18, 2011 8:34 AM
  • Correct. ConfigMgr has no way of forcing an installtion to do something, all it (or any other deployment method) can really do is run a command-line: specifically whatever command-line you give it. Thus, the onus is on you to discover and test the command-line so that it behaves the way you want it to including making it silent.

    In the case of MSIs (that are well-written and don't include uncontrollable custom actions or other embedded installations) this is an easy task because /q always tells Windows Installer to perform a silent install: http://msdn.microsoft.com/en-us/library/aa367988(v=VS.85).aspx.

    However, in the case of .exe (or other types of) installers, you have to consult the vendor on what to do because there is no absolute or enforced standard. Many setup.exe programs were created by InstallShield so follow their standards, but that is no guarentee. You can often discover the possible command-line switches by running setup.exe /?.

    For silverlight specifically, it is a setup.exe created by the silverlight team and simply running silverlight.exe /? will inform you that /q is the proper command-line argument to make the install silent.


    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    • Proposed as answer by Garth JonesMVP Saturday, June 18, 2011 2:47 PM
    • Marked as answer by Sabrina Shen Tuesday, June 21, 2011 6:38 AM
    Saturday, June 18, 2011 1:14 PM