A few posts to get you started and provide backing for the need. http://blogs.technet.com/b/configurationmgr/archive/2015/04/15/support-tip-configmgr-2012-update-scan-fails-and-causes-incorrect-compliance-status.aspx http://blogs.technet.com/b/sus/archive/2015/06/09/a-few-notes-on-the-recent-fix-for-the-configuration-manager-update-scan-failure-issue.aspx
http://mnscug.org/blogs/brian-mason/361-how-to-melt-a-sup http://blog.coretech.dk/kea/house-of-cardsthe-configmgr-software-update-point-and-wsus/ Daniel Ratliff From: [email protected] [mailto:[email protected]] On Behalf Of Jeff Poling Sent: Monday, November 16, 2015 5:31 PM To: [email protected] Subject: RE: [MDT-OSD] ZTIWindowsUpdate.wsf Unfortunately, I do not have access to or insight into the WSUS environment. I will need to work with the customer's administrator. As for the WUA, I am going to validate the version in the image and update it if it I not the latest. Thanks, Jeff Sent from my Windows Phone ________________________________ From: Daniel Ratliff<mailto:[email protected]> Sent: 11/16/2015 3:11 PM To: [email protected]<mailto:[email protected]> Subject: RE: [MDT-OSD] ZTIWindowsUpdate.wsf Do you have the latest WUA installed? Is your WSUS server cleaned up (superceded/expired updates removed)? Daniel Ratliff From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Jeff Poling Sent: Monday, November 16, 2015 3:46 PM To: [email protected]<mailto:[email protected]> Subject: [MDT-OSD] ZTIWindowsUpdate.wsf We are running into a challenge with the ZTIWindowsUpdate.wsf script in a ConfigMgr/MDT-Integrated TS. The script runs and returns a 0 exit code; however, numerous updates are available via WSUS after the system is built. The smsts.log shows the exit code 0, but prior to that, it also shows the following error: Timeout Error WU_E_PT_EXCEEDED_MAX_SERVER_TRIPS : Retry! (-2145107952) It appears the script is not completing the scan for updates and just exits gracefully. I read this older article that might explain why this is occurring: http://blogs.technet.com/b/sus/archive/2008/09/18/wsus-clients-fail-with-warning-syncserverupdatesinternal-failed-0x80244010.aspx But I am wondering if anyone else has experienced this and has suggestions for how we might overcome this challenge? Thanks, Jeff The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information. The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
