Video Screencast Help

SEP RU6 distribution via SCCM

Created: 28 Oct 2010 | 6 comments

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

Comments 6 CommentsJump to latest comment

sandeep_sali's picture

 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.

Thanks & Regards

Sandeep C Sali

mthorpe's picture

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).

sandeep_sali's picture

 

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

Thanks & Regards

Sandeep C Sali

mthorpe's picture

Rafeeq,

 

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

Vikram Kumar-SAV to SEP's picture

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

Vikram Kumar

Symantec Consultant

The most helpful part of entire Symantec connect is the Search button..do use it.