Endpoint Protection

 View Only
  • 1.  SEP RU6 distribution via SCCM

    Posted Oct 28, 2010 08:57 AM

    Hi,

     

    We are currently attempting to deploy SEP RU6 via SCCM - this works in the most part unless...

    "The user has windows updates ready to install"

    or

    "The user has a message advising a reboot is needed to complete windows updates"

    The only way to fix this is to instal the update(s) and/or reboot the machine then repush out via SCCM.

    As this is mostly a manual task is there away to prevent the package from deploying until neither of the above situations is the case?

     

    Regards,

    Mike



  • 2.  RE: SEP RU6 distribution via SCCM

    Posted Oct 28, 2010 09:08 AM

     Try creating a set of multiple files that include the .msi setup file instead of an setup.exe file and then check whether we are able to successfully deploy it from SCCM.



  • 3.  RE: SEP RU6 distribution via SCCM

    Posted Oct 28, 2010 09:14 AM

    Unfortunately that is the method are using.

     

    (The single.exe method caused SCCM to report an error everytime regardless of whether it was successful or not).



  • 4.  RE: SEP RU6 distribution via SCCM

    Posted Oct 28, 2010 09:18 AM

     

    Is there away to prevent the package from deploying until neither of the above situations is the case?

     

    I will check this and get back to you



  • 5.  RE: SEP RU6 distribution via SCCM



  • 6.  RE: SEP RU6 distribution via SCCM

    Posted Oct 28, 2010 10:38 AM

    Rafeeq,

     

    We don't want to force a reboot of the users system, just stop SCCM from trying to deploy until they have..



  • 7.  RE: SEP RU6 distribution via SCCM

    Posted Oct 28, 2010 11:54 AM

    You can delete the "PendingFileRenameOperations" registry key then deploy SEP..if that can be done via SCCM