This content has been marked as final. Show 3 replies
The method of installation is determined by SCCM. It may have been the case that one of the updates required an immediate, post-deployment power-cycle.
The automatic updating is enabled by default, and is part of the vendors installation. There are a number of ways to 're-disable' automatic updating (such as via GPO, as you suggested). We utilize a Powershell script to accomplish this with our on-premise product (Protect). The script is available for review on our community site, as follows:
Please also see the following article in our product Knowledge Base:
http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=2019645&sliceId=1&docTypeID=DT_KB_1_1&dialogID=429578214&stateId=1 0 429582746
The issue we're having is that it is presented as three separate installs with reboots in between, not a singular streamlined install thru WSUS/Windows Update. Because the way the third party updates are presented, it appears that they are coming from the internet. Also, it then prompts the users for input to install, who then calls our service desk wondering why they're getting prompted for these installs. Aren't the third party updates re-packaged in a MSI format?
We do not repackage or redistribute the installers. The data added via SCUP includes both meta-data and file/installer related data. The process of evaluation and deployment is determined by SCCM. If you are experiencing an issue which you feel is related to our data, we would urge you to contact Support directly so that we may assist in fully identifying and assessing the issue.