locked
ccmsetup.msi Behaviour RRS feed

  • Question

  • We are currently using GPO to deploy the CM agent using the ccmsetup.msi and it's having some mixed result so I wanted to try using another method using a logon script but when I attempt to run the ccmsetup.msi from the command line it fails.

    When I look in the ccmsetup.log I see this

    When using group policy we don't get this error and the agent installs successfully (mostly). Group policy is just calling the .msi from a share so why is there differing behaviour and how can I get ccmsetup.msi to work from the command line?


    Hibs Ya Bass!

    Thursday, October 24, 2013 9:49 PM

Answers

  • You can't use the MSI from a command lien you need to use ccmsetup.exe from a command line.

    http://www.enhansoft.com/

    Thursday, October 24, 2013 10:02 PM
  • Also, don't use a login script, use a startup script. Logon scripts run in the user's context which is not good enough unless you users are actually local admins (God help you if they are).

    Jason | http://blog.configmgrftw.com

    Friday, October 25, 2013 12:54 AM

All replies

  • You can't use the MSI from a command lien you need to use ccmsetup.exe from a command line.

    http://www.enhansoft.com/

    Thursday, October 24, 2013 10:02 PM
  • Ah, ok. Thanks.

    Hibs Ya Bass!

    Thursday, October 24, 2013 11:49 PM
  • Also, don't use a login script, use a startup script. Logon scripts run in the user's context which is not good enough unless you users are actually local admins (God help you if they are).

    Jason | http://blog.configmgrftw.com

    Friday, October 25, 2013 12:54 AM
  • Hi,

    Jason has written a great startup script which I Always use: http://blog.configmgrftw.com/?page_id=349 instead of using ccmsetup.msi.

    Check it out!

    Regards,
    Jörgen


    -- My System Center blog ccmexec.com -- Twitter @ccmexec

    Friday, October 25, 2013 6:00 AM
  • That looks very good. Way better than my basic logic.

    Hibs Ya Bass!

    Monday, October 28, 2013 11:39 PM