Verify that the update still exists and is applicable to this computer from your WSUS server or Windows Update.To give your server a chance at receiving updates—including Windows Server Update Services 3.0 SP2 Dynamic Installer for Server Manager [x64 Edition] (KB972493)—through Microsoft’s website, temporarily disable intranet Microsoft update service location: Edit the Default Domain Policy in Group Policy Management, open , pick a single product with fewest updates possible (e.g., Silverlight).
Updating to sp2
So, when it tries Installation failed The update could not be found.
Either the update is not applicable to this computer or the update no longer exists.
(it 39) W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs.
(it 145) W: DYNDNS: Error 'RC_IP_CONNECT_FAILED' (0x13) when talking to IP server W:'RC_IP_CONNECT_FAILED' (0x13) updating the IPs.
Windows Update now recommends the installation of Update for Windows Server Update Services 3.0 SP2 [for x64-based Systems] (KB2720211).
It’s a 28 MB download from Microsoft servers if you’re curious.An update to WSUS 3.0 SP2 on Windows Server 2008 R2 and Windows Server 2008 (both x64 and x86) seems to break Windows Server Update Services (WSUS) and/or Internet Information Services (IIS) making clients unable to update via WSUS showing error 0x80072EE2.To me, the subversive update number is not clear yet.RBAC tool is written in C# and using Powershell behind the scenes For Release Notes please check Downloads section Tested on Windows 7, Windows 8 and Server 2008 R2 against Exchange Server 2010 SP2, Exchange Server 2013 Preview and Office 365 Pre-Requirement: 1.Reload, it will ask you if the "links to other files should be updated". The same will happen if you close and re-open the spreadsheet.Please check "Downloads" section for new binary (18.104.22.168) RBAC Manager puts all efforts to simplify the RBAC administration.