FFS!!! Console only on the site server. Problem resolved. On Thu, Oct 16, 2014 at 1:07 AM, Paul Winstanley <[email protected]> wrote:
> Permissions on the disk are absolutely fine and I have compared these to > the Technet article. No matter what I am attempting to do I cannot get the > remote SUP to sync and download the EULA. > > So to recap the scenario is: > > Local SQL on site server. No SUP installed on site server and SUP > installed on role server. All updates sync except those with EULA. I have > exhausted all suggestions on blogs, technet forums and also the articles > suggested on this thread but cannot get the content to download at all. > > I have tried using local path and using a share for WSUSContent. I have > ensured network service has rights. Added read rights for this account at > root of drive as suggested elsewhere (I also added full control as a test). > > I have given the role server's sec object in SQL sysadmin and set user > mapping on the SUSDB to public and webservice. > > I see successful syncs within the WSUS console and these are not marked as > failures but ConfigMgr will mark as an unsuccessful sync. > > Nothing except an anonymousCheckFile.txt is written to the WSUSContent > folder. > > If I remove Service Packs from my classifications (i.e. all updates > requiring EULA acceptance) then ConfigMgr sync completes and the > WSUSContent folder is populated as expected. > > So if I reset my environment and remove SUP/WSUS/SUSDB etc and then set > all this up on my site server the EULA content does not error and I can > download and sync correctly. > > On a final note. I decided as a final test tonight that I would keep the > content downloaded by the sync on my site server. > > I reset my environment and set up my remote SUP again. EULA error's > started again. I then copied over the data within the WSUSContent folder > from my site server to the remote SUP. Re-ran a sync and hey presto sync is > a success and not EULA error. So basically if the content is there then > this is not a problem but if not there the sync process is unable to create > it. > > As I say I have checked and double checked the disk permissions, even > setting everyone full control to share and NTFS but I still cannot get this > to work as it should. > > Anyone out there installed remote SUP only (i.e. not using site server as > a SUP) and managed to get SP's (particularly Win 2k8) synching or willing > to run a test lab to check this out? > > Thanks for your assistance so far. > Paul > > > > > On Wed, Oct 15, 2014 at 4:40 PM, Russ Rimmerman < > [email protected]> wrote: > >> Have you gone through >> http://technet.microsoft.com/en-us/library/cc708545(v=ws.10).aspx to >> confirm all your permissions are correct, especially the WSUSContent items >> under the “Permissions/Disk” section? >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Paul Winstanley >> *Sent:* Wednesday, October 15, 2014 8:43 AM >> *To:* [email protected] >> *Subject:* Re: [mssms] WSUS Synch Issue >> >> >> >> Russ - followed the TechNet article and it still fails. EULA not >> downloaded. >> >> >> >> On Tue, Oct 14, 2014 at 4:12 PM, Russ Rimmerman < >> [email protected]> wrote: >> >> You’re sharing the same wsuscontent share on each SUP correct? You >> should follow pretty much the same process documented on the setting up a >> SUP for NLB TechNet article @ >> http://technet.microsoft.com/en-us/library/hh237369, ignoring the >> mentions of NLB. >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Paul Winstanley >> *Sent:* Tuesday, October 14, 2014 9:59 AM >> *To:* [email protected] >> *Subject:* Re: [mssms] WSUS Synch Issue >> >> >> >> Ok so this is interesting. >> >> >> >> My current lab set up is 3 x remote SUP's. I get the EULA error. >> >> >> >> I have installed a SUP on my primary site server and remove the remote >> SUPs. So only the 1 SUP left on the site server. Re ran the synch and the >> EULAs have come down. >> >> >> >> So there must be some permission error or something stopping the EULA's >> coming down to the 3 remote SUPs. I have added in network services to the >> C:\WSUS folder on each SUP and still a problem. >> >> >> >> Any one have any ideas on remote SUP config? Take a look at my remote SUP >> config guides. Have a missed out anything obvious here >> >> >> >> >> http://sccmentor.wordpress.com/2014/09/06/installing-a-remote-software-update-point-on-sccm-2012-r2/ >> >> >> >> >> http://sccmentor.wordpress.com/2014/09/11/installing-a-remote-sup-in-sccm-2012-r2-on-windows-server-2012-r2/ >> >> >> >> >> I'm having the same issue at a client who has remote SUP only. >> >> >> >> I will re-add the remote SUPs and remove the SUP on the primary as a next >> test to see if this all falls over again. >> >> >> >> Cheers >> >> Paul >> >> >> >> On Tue, Oct 14, 2014 at 2:59 PM, Paul Winstanley <[email protected]> >> wrote: >> >> Andrew, >> >> >> >> The updates haven't even hit the ConfigMgr All Software Updates list. All >> Licence Terms are set to 'not applicable'. I can search for the update in >> the WSUS console and find it. I take is since the EULA is not accepted it >> is not appearing in the list. >> >> >> >> I've noted this are all SP related updates btw. >> >> >> >> Cheers >> >> Paul >> >> >> >> On Tue, Oct 14, 2014 at 2:32 PM, Andrew Craig <[email protected]> >> wrote: >> >> In All Software Updates you can sort by License Terms (but not add as >> search criteria sadly) and then look for Required – these are awaiting >> acceptance. The other possible values are “not applicable”, “Accepted” and >> “Declined”. Only those that are not ”not applicable” have the Right-Click >> option to Review License. >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Paul Winstanley >> *Sent:* 14 October 2014 15:09 >> *To:* [email protected] >> *Subject:* Re: [mssms] WSUS Synch Issue >> >> >> >> Andrew, >> >> >> >> I'm not able to filter out as the updates are appearing in the update >> list, due to not accepting EULA I would assume. >> >> >> >> On Tue, Oct 14, 2014 at 1:31 PM, Paul Winstanley <[email protected]> >> wrote: >> >> Well I never knew that! Thanks Andrew I'll test this out shortly. >> >> >> On 14 Oct 2014, at 12:51, Andrew Craig <[email protected]> wrote: >> >> You can automatically accept licenses in configmgr. In the main updates >> view you can also filter for updates that have a license agreement >> attached. Then you can right-click and review/agree if required. >> >> >> >> You can also use wsusutil reset to force these to download again. >> >> >> >> *From:* [email protected] [ >> mailto:[email protected] <[email protected]>] *On >> Behalf Of *Paul Winstanley >> *Sent:* 14 October 2014 12:58 >> *To:* [email protected] >> *Subject:* Re: [mssms] WSUS Synch Issue >> >> >> >> Andrew, >> >> >> >> At which point were you prompted for licence agreement acceptance? Only >> time I have had to accept a EULA is when enabling SCEP. >> >> >> >> Cheer >> >> Paul >> >> >> >> On Tue, Oct 14, 2014 at 11:47 AM, Andrew Craig <[email protected]> >> wrote: >> >> I had a similar problem with multiple sites in 2007. I cleaned up all >> the wsus metadata from the downstream sites, re-accepted all the license >> agreement at top level and then scheduled a full resync. >> >> >> >> Did the trick. I was getting this exact message on a child site. >> >> >> >> *From:* [email protected] [mailto: >> [email protected]] *On Behalf Of *Brian McDonald >> *Sent:* 13 October 2014 15:43 >> *To:* [email protected] >> *Subject:* [mssms] WSUS Synch Issue >> >> >> >> Hey all, >> >> >> >> I am trying to get WSUS to synch and it continues to fail. Here is what >> the wsyncmgr.log file says: >> >> >> >> Failed to sync update 87e13ecb-c669-43be-9e2a-01e567285031. Error: The >> Microsoft Software License Terms have not been completely downloaded >> and~~cannot be accepted. Source: >> Microsoft.UpdateServices.Internal.BaseApi.LicenseAgreement.GetById >> >> >> >> Sync failed: Failed to sync some of the updates. Source: >> Microsoft.SystemsManagementServer.SoftwareUpdatesManagement.WsusSyncAction.WSyncAction.SyncUpdates >> >> >> >> I've researched this error and came across the following KB: >> http://support.microsoft.com/kb/922330 >> >> >> >> However, I do not see the ExecuteSQL.exe or OSQL.exe files in the >> directories mentioned. >> >> >> >> Has anyone seen this before? Not finding much in my research online. >> >> >> >> Thanks, >> >> >> Brian >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >
