Hutch Posted April 11, 2014 Report post Posted April 11, 2014 I just figured it out. They've separated the missing steps into their own wizard. Now you have to right click on the SUG and choose Download. Then you get this. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted April 12, 2014 Report post Posted April 12, 2014 Correct. Do the updates now also arrive on the clients? Quote Share this post Link to post Share on other sites More sharing options...
Hutch Posted April 14, 2014 Report post Posted April 14, 2014 Nope. I'm still missing something. Quote Share this post Link to post Share on other sites More sharing options...
Kazi Posted April 14, 2014 Report post Posted April 14, 2014 Clear your cache on the computers you are trying to deploy to. Recreate everything - your SUG's, Deployment Packages, etc. and make sure you are choosing full downloads of the updates you want to deploy. After you get everything downloaded, set your deployment time to As Soon As Possible or a date in the future. Also, are all of your clients updated to R2? Quote Share this post Link to post Share on other sites More sharing options...
Hutch Posted April 15, 2014 Report post Posted April 15, 2014 Hi Kazi. I've done everything you suggested and still no luck. Clients are all R2. Quote Share this post Link to post Share on other sites More sharing options...
Kazi Posted April 16, 2014 Report post Posted April 16, 2014 What does your deployment status show you under Monitoring - Deployments? Find your software deployment and check the status. Quote Share this post Link to post Share on other sites More sharing options...
Hutch Posted April 16, 2014 Report post Posted April 16, 2014 All Unknown Quote Share this post Link to post Share on other sites More sharing options...
Kazi Posted April 16, 2014 Report post Posted April 16, 2014 What operating system are your client computers and how many of them do you have? I had an issue with installing CU3 a while back so what I had to do was create a PowerShell script to copy the R2 client update to the computer that needed it and then kick off the R2 .msp file on that same computer. What I would try to do is go to a test computer and uninstall the client and then reinstall it manually just to rule out that something didn't happen when the R2 client was installed. Quote Share this post Link to post Share on other sites More sharing options...
Hutch Posted April 16, 2014 Report post Posted April 16, 2014 All clients are Windows 7 SP1 and there are many computers that have already had the client manually reinstalled when I was working on other issues so I don't think that's the problem. Besides, I can push out apps and software updates via ADR. It's just this one package that's giving me trouble. Quote Share this post Link to post Share on other sites More sharing options...
Peter van der Woude Posted April 17, 2014 Report post Posted April 17, 2014 Software update deployments are not related to a specific package.. Do you see anything about update locations in the CAS.log or the LocationServices.log? Quote Share this post Link to post Share on other sites More sharing options...
