Hi Jesse, We currently deploy SAS 9.4 successfully to thousands of machines via SCCM. Although it wasn't myself who packaged it, the person who did looks to have just made a package (not application) for it linking to a batch file.
Command from the batch file for the install bit excluding any licensing etc is below, looks to just do a quite install calling a pre made response file. "\\*PathHere*\SAS 9.4\setup.exe" -quiet -wait -responsefile \\*PathHere*\SAS 9.4\uos.properties Hope that helps. Rich From: [email protected] [mailto:[email protected]] On Behalf Of Schauer, Jesse ([email protected]) Sent: 16 January 2015 17:03 To: '[email protected]' Subject: [mssms] "IsCacheCopyNeeded returned 'true' by {5777363A-FB22-4a42-ABB0-522DD42711DC}" during software deployment I am trying to deploy a rather huge piece of software (SAS 9.4, ~19G) and am running into some issues with clients not being able to download the content. The software is being deployed as an application. When I set up a required deployment for a machine, the machine will see it, see it needs to download content, and try to start downloading. Around this time, CAS.log will start to go crazy spamming "IsCacheCopyNeeded returned 'true' by {5777363A-FB22-4a42-ABB0-522DD42711DC}". It write about 3-5M of this per minute. While googling around I found this thread: https://social.technet.microsoft.com/Forums/en-US/ce763dc6-c184-47bf-85a8-463501206000/2012-client-stuck-problem?forum=configmanagergeneral. There is not much detail but they do reference the "dodgy registry key IsCacheCopyNeededCallBack" (which is actually a value under HKLM\SOFTWARE\Microsoft\SMS\Mobile Client\ Software Distribution). Deleting this value causes the callback to fail, after which the content immediately starts downloading. It should be noted that machines that are not having these issues also have this registry value. Anyone else run into this before? We've pushed a ton of software out with this site (though this is the largest) and have never run into this until now. I'm not sure what deleting the registry value does and while it seems to alleviate the issue, I don't want to cause unexpected issues down the road. For reference, site and client version are ConfigMgr 2012 R2 CU1. The client cache size is currently set at 30G. Jesse Schauer Windows Server Administrator II Endpoint Manangement Services University of Idaho ITS
