Slightly odd and very annoying problem.

Breif background.

For all sorts of policy reasons, we have a WSUS setup that allows us to "TRIAL" updates before going live, so we approve updates for a set of specially picked machines that give us a good cross section and check for issues, although we have only ever once found an issue with a patch. Once this is done and we are happy we approve for our entire estate.

For this reason we cannot allow any machines to go direct to Windows Update, and therefore we have things in place to allow access to our WSUS server for Laptops that are off WAN.

The problem?

Some retard office manager half the planet away has decided that a few people who have left the company in that office can take their laptops with them when they left. We did not discover this until way too late and there is nothing we can do to stop it. While the local Office manager did ensure data and licensable software was removed before they left, that's all he did.

I now have a bunch of rogue XP and Vista machines out there on the internet reporting in to my WSUS servers that are not my concern any more. I need a method, using nothing but WSUS itself, to get them off and stop them reporting in.

Help, anyone know of a way I can perhaps write a tiny custom patch I can approve just for these machines that will just reset the WU client back to defaults? I obviously cant rename or change DNS entries for my WSUS setup as it will be a reasonably big job.

Thanks All

Hello,

I patched a 2012 R2 server and it reverted the updates and did not install any of them (there were 14).  I now have 17 updates (total) to install on this server but the server will not install them and it says "No Updates are Available".  I tried to stop the windows update service on the server, renamed the SoftwareDistribution folder and restarted the windows update service,  then tried to check for updates on the server again and there is no change.  

I saw a post to do this: 

The easiest way to clear out the WSUS configuration information is to wipe out this registry key:  <tt>HKLM\Software\Policies\Microsoft\Windows\WindowsUpdate</tt>

<tt>I'm a newbie .. is this a valid option to try?  Please advise.  </tt>

<tt>Thanks for any help!  </tt>

Hello everyone,
I got the problem on my Windows Server 2012 R2 that I'm not able to install windows updates anymore. I searched for the error I got and found many different ways to solve this issue and I tried all of them. I tried to:

-Correct the date and time in the control panel
-Sync with an internet time server (time.windows.com) but got an error that it's not able to synchronize cause the time period expired
-run SFC scannow and solve all problems shown
-do most things written on this side (http://www.techsupportforum.com/forums/f320/solved-windows-update-error-80072f8f-885129-2.html)
-Restart the Windows Time Service
-Check all the needed Certificates if there are any errors
-Use the problem control from Microsoft
-Check if it had anything to do with my VM not being part of the domain (I installed updates before so I guess that's not really a problem)
-Confirm if any changes were made regarding internet security in our companies environment (nothing changed)
-Run this command: DISM /Online /Cleanup-Image /RestoreHealth (got an error that the source files can't be downloaded)
-Try to re-register corrupted dlls

Nothing from the things above could solve my problem and I don't have any idea what I should do next. Since this VM is used as a App-V Sequencer it needs to be up-to-date.

Note: The snapshot I have from this VM is right after I installed updates last time but I checked before if everything is alright, still I have this problem now and it makes no difference using the snapshot.

If anyone has an idea on how to fix that problem I would be grateful.

Hi,

I have got a weird problem. It deletes a shared executable file when it installs the windows updates.

I am very confused on this behaviour. I have checked Antivirus and it has got exclusion.

Is there a way to stop this issue?

Thanks, 

I have a virtual WSUS 2012 R2 with simple updates to workstations only, no servers.

Products = Windows 7 and Windows 8.1

Classifications: Critical Updates, Security Updates, and Service Packs

Instead of going to each updates to decide approve or decline, can I just simply approve them all and to apply to all computers? Since updates are directly downloading from Microsoft server, I don't have to worry about local disk space consumption.

To my understanding, any updates that won't apply to the system, they won't be downloaded and installed regardless I approved them.

Approve all updates to all All Computers saving time! I am just one of a lazy system admin to find a way to work smart, not work hard! We have been doing approve and decline each updates, this is a tedious work! Thanks in advance for your input.

Thang Mo

Hi,

We are trying to fix a good number of clients in our environment who are not reporting to the WSUS server for a long time. All seem to have a common error 

WARNING: WinHttp: SendRequestUsingProxy failed for <https://xxxx.yyyy.net/selfupdate/wuident.cab>. error 0x80072f8f

Checked IIS for selfupdate and SSL is not enabled

Certificates are fine. Most clients are getting updates.

Time is not an issue. 

Selfupdate works on port 80 but gives certificate error on 443 which is why I think the error. How do we make the clients point to Selfupdate using port 80 rather than using port 443.

Any help would be appreciated.

Regards,

Vijay

I would appreciate advice on how to Stop a Language Pack for trying to load

Unsure if the Language Pack was requested or not but IT IS NOT NEEDED - yet I cannot find how to delete it - as a consequence it keeps prompting to be allowed to download (which is most kind and helpful if I needed it).

Advice appreciated.

Hello Folks,

I have a question.  Say you have 2 DC's in SF, 2DC's in NY, 2DC's in Australia, 2DC's in China and you want to update each DC in its own time zone at midnight.  Each site will have its own WSUS.

You are in the SF office and that is where AD lives and it lists all the DC's for all sites around the world in the "Domain Controllers" OU And you want SF to run it's updates at midnight SF on just the SF DC's. In other words, each global site will need to run their updates at a different time zone.

Do you need to create and OU for SF and move the SF DC's into that OU and then create a GPO for that OU to achieve this? I hate creating more OU's and then having to move the SF DC's out of the main "Domain Controllers" OU to the SF OU if I can avoid it, not to mention having to see what other GPO's are (hopefully not) assigned to the "Domain Controllers" OU as a whole.

And then having to create OU's for each global site and do the same thing with creating OU's, GPO's, etc., for each site.

Many thanks for your help! :-)

RT

In the console of WSUS into a Windows server 2008 R2, i have any clients in different version XP, 7, 8 and now 8.1 but for this client version 8.1 WSUS report a wrong version Windows 6.3 like first with Windows 8 --> 6.2

Microsoft resolved the problem for wrong version in WSUS console for Windows 8 and 2012 server, but the problem appear again with 8.1 and 2012 R2.

I'm afroid because this issue is know since Windows 8.1 preview exist...

I think there is a bug that not resolved by Microsoft because i have installed the last KB for WSUS : Version
3.2.7600.262

Also i googlelised this problem during 1 hour but i find nothing on this issue ?!  If in a Deutsch forum but anyone find an answer...

Thanks for your help.

Hello,

I am currently struggling with WSUS 6.3 that is included in Windows 2012 R2. The speed WSUS use to download critical updates is ridiculously slow. It annoys me greatly.

I found several solution to this issue but there are too many. What is the easy and the right approach to resolve this mindboggling issue?

Friendly Regards, Master-DXT.

I have a WSUS server in my firm and we manually approve updates to various computer containers. When we approve updates, we never set a deadline on when they need to be installed. We also have WSUS GPOs per site OU (for client side targeting purposes) which direct computers download and install updates every Saturday at 3AM. Most of the computers in our firm follow the scheduled installation of approved updates.

For some reason, we have seen some computers disregard the update schedule and install updates on their own during the day. We used to only have the advanced settings for Automatic Approvals enabled to so we can use the WSUS Server Cleanup Wizard to clean out expired and superseded updates:

WSUS Updates > Automatically approve updates to the WSUS product itself

Revisions to Updates > Automatically approve new revisions of updates that are already approved

I cleared these options out in case they were the cause of issue. I also confirmed the computers affected by this issue are living in their proper OUs where the WSUS GPO is being applied. I am still waiting to see if this pattern will exhibit itself again this weekend after I approve more updates, but  still do not understand why this is happening.

Below is a sample of one of our WSUS GPOs and after that is a snippet from the WindowsUpdate log.

    
GPO

Allow Automatic Updates immediate installation: Disabled 
Allow signed updates from an intranet Microsoft update service location:  Enabled 
Automatic Updates detection frequency: Enabled 
Check for updates at the following
interval (hours):  4

Configure Automatic Updates: Enabled 
Configure automatic updating: 4 - Auto download and schedule the install
The following settings are only required
and applicable if 4 is selected.
Scheduled install day:  7 - Every Saturday
Scheduled install time: 03:00

Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows dialog box: Enabled 
Enable client-side targeting: Enabled 
Target group name for this computer: "SF Computers"

Enabling Windows Update Power Management to automatically wake up the system to install scheduled updates: Enabled 
No auto-restart with logged on users for scheduled automatic updates installations: Disabled 
Re-prompt for restart with scheduled installations: Enabled 
Wait the following period before
prompting again with a scheduled
restart (minutes):  360

Specify intranet Microsoft update service location Enabled 
Set the intranet update service for detecting updates: http: //**WSUSServer**/ 
Set the intranet statistics server: http: //**WSUSServer**/ 

Policy Setting Comment
Turn on recommended updates via Automatic Updates Enabled

Windows Updates Log

015-07-25 19:03:38:941  816 ad0 AU ###########  AU: Initializing Automatic Updates  ###########
2015-07-25 19:03:38:957  816 ad0 AU AU setting next detection timeout to 2015-07-26 02:03:38
2015-07-25 19:03:38:957  816 ad0 AU AU setting next sqm report timeout to 2015-07-26 02:03:38
2015-07-25 19:03:38:957  816 ad0 AU   # WSUS server: http: //**WSUSServer**/ 
2015-07-25 19:03:38:957  816 ad0 AU   # Detection frequency: 4
2015-07-25 19:03:38:957  816 ad0 AU   # Target group: SF Computers
2015-07-25 19:03:38:957  816 ad0 AU   # Approval type: Scheduled (Policy)
2015-07-25 19:03:38:957  816 ad0 AU   # Scheduled install day/time: Saturday at 3:00
2015-07-25 19:03:38:957  816 ad0 AU   # Auto-install minor updates: No (Policy)
2015-07-25 19:03:38:957  816 ad0 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
2015-07-25 19:03:39:206  816 ad0 Report ***********  Report: Initializing static reporting data  ***********
2015-07-25 19:03:39:206  816 ad0 Report   * OS Version = 6.1.7601.1.0.65792
2015-07-25 19:03:39:206  816 ad0 Report   * OS Product Type = 0x00000004
2015-07-25 19:03:39:222  816 ad0 Report   * Computer Brand = Hewlett-Packard
2015-07-25 19:03:39:222  816 ad0 Report   * Computer Model = HP EliteBook Folio 9470m
2015-07-25 19:03:39:222  816 ad0 Report   * Bios Revision = 68IBD Ver. F.47
2015-07-25 19:03:39:222  816 ad0 Report   * Bios Name = Default System BIOS
2015-07-25 19:03:39:222  816 ad0 Report   * Bios Release Date = 2013-10-08T00:00:00
2015-07-25 19:03:39:222  816 ad0 Report   * Locale ID = 1033
2015-07-25 19:03:39:347  816 ad0 AU Initializing featured updates
2015-07-25 19:03:39:347  816 ad0 AU Found 0 cached featured updates
2015-07-25 19:03:39:347  816 ad0 AU Successfully wrote event for AU health state:0
2015-07-25 19:03:39:347  816 ad0 AU AU setting pending client directive to 'Install Approval'
2015-07-25 19:03:39:362  816 ad0 AU Successfully wrote event for AU health state:0
2015-07-25 19:03:39:362  816 ad0 AU AU finished delayed initialization
2015-07-25 19:03:39:362  816 ad0 AU AU setting next sqm report timeout to 2015-07-27 02:03:39
2015-07-25 19:03:39:362  816 ad0 AU #############
2015-07-25 19:03:39:362  816 ad0 AU ## START ##  AU: Search for updates
2015-07-25 19:03:39:362  816 ad0 AU #########
2015-07-25 19:03:39:362  816 ad0 AU <<## SUBMITTED ## AU: Search for updates [CallId = {B9D11034-8F4D-4129-A70D-085299FA05E2}]
2015-07-25 19:03:39:487  816 12f4 Agent *************
2015-07-25 19:03:39:487  816 12f4 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2015-07-25 19:03:39:487  816 12f4 Agent *********
2015-07-25 19:03:39:487  816 12f4 Agent   * Online = Yes; Ignore download priority = No
2015-07-25 19:03:39:487  816 12f4 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2015-07-25 19:03:39:487  816 12f4 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2015-07-25 19:03:39:487  816 12f4 Agent   * Search Scope = {Machine}
2015-07-25 19:03:39:487  816 12f4 Setup Checking for agent SelfUpdate
2015-07-25 19:03:39:487  816 12f4 Setup Client version: Core: 7.6.7601.18847  Aux: 7.6.7601.18847
2015-07-25 19:03:44:464  816 12f4 Misc WARNING: Send failed with hr = 80072ee7.
2015-07-25 19:03:44:464  816 12f4 Misc WARNING: SendRequest failed with hr = 80072ee7. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <>
2015-07-25 19:03:44:464  816 12f4 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <http: //**WSUSServer**//selfupdate/wuident.cab>. error 0x8024402c
2015-07-25 19:03:44:464  816 12f4 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x8024402c
2015-07-25 19:03:44:464  816 12f4 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x8024402c
2015-07-25 19:03:44:464  816 12f4 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x8024402c
2015-07-25 19:03:44:464  816 12f4 Misc WARNING: DownloadFileInternal failed for http: //**WSUSServer**//selfupdate/wuident.cab: error 0x8024402c
2015-07-25 19:03:44:464  816 12f4 Setup FATAL: DownloadCab failed, err = 0x8024402C
2015-07-25 19:03:44:464  816 12f4 Setup WARNING: SelfUpdate check failed to download package information, error = 0x8024402C
2015-07-25 19:03:44:464  816 12f4 Setup FATAL: SelfUpdate check failed, err = 0x8024402C
2015-07-25 19:03:44:464  816 12f4 Agent   * WARNING: Skipping scan, self-update check returned 0x8024402C
2015-07-25 19:03:44:464  816 12f4 Agent   * WARNING: Exit code = 0x8024402C
2015-07-25 19:03:44:464  816 12f4 Agent *********
2015-07-25 19:03:44:464  816 12f4 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
2015-07-25 19:03:44:464  816 12f4 Agent *************
2015-07-25 19:03:44:464  816 12f4 Agent WARNING: WU client failed Searching for update with error 0x8024402c
2015-07-25 19:03:44:464  816 1b4 AU >>##  RESUMED  ## AU: Search for updates [CallId = {B9D11034-8F4D-4129-A70D-085299FA05E2}]
2015-07-25 19:03:44:464  816 1b4 AU   # WARNING: Search callback failed, result = 0x8024402C
2015-07-25 19:03:44:464  816 12f4 Report REPORT EVENT: {137EA465-1405-4514-BFA1-CF378B2E38E0} 2015-07-25 19:03:38:972-0700 1 188 102 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Content Install Installation Ready: The following updates are downloaded and ready for installation. This computer is currently scheduled to install these updates on ‎Saturday, ‎July ‎25, ‎2015 at 7:04 PM:  - Security Update for Windows 7 for x64-based Systems (KB3079904)
2015-07-25 19:03:44:464  816 1b4 AU   # WARNING: Failed to find updates with error code 8024402C
2015-07-25 19:03:44:464  816 1b4 AU #########
2015-07-25 19:03:44:464  816 1b4 AU ##  END  ##  AU: Search for updates [CallId = {B9D11034-8F4D-4129-A70D-085299FA05E2}]
2015-07-25 19:03:44:464  816 1b4 AU #############
2015-07-25 19:03:44:479  816 1b4 AU Successfully wrote event for AU health state:0
2015-07-25 19:03:44:479  816 1b4 AU AU setting next detection timeout to 2015-07-26 05:39:26
2015-07-25 19:03:44:479  816 1b4 AU Successfully wrote event for AU health state:0
2015-07-25 19:03:54:370  816 ad0 AU Launched new AU client for directive 'Install Approval', session id = 0x1
2015-07-25 19:04:03:605  816 ad0 AU Forced install timer expired for AUInstallType = 4
2015-07-25 19:04:03:605  816 ad0 AU UpdateDownloadProperties: 0 download(s) are still in progress.
2015-07-25 19:04:03:605  816 ad0 AU #############
2015-07-25 19:04:03:605  816 ad0 AU ## START ##  AU: Install updates
2015-07-25 19:04:03:605  816 ad0 AU #########
2015-07-25 19:04:03:605  816 ad0 AU   # Initiating scheduled install
2015-07-25 19:04:03:605  816 ad0 AU   # Approved updates = 1
2015-07-25 19:04:03:605  816 ad0 AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {3DED3327-50BD-478E-AC52-679078357047}]
2015-07-25 19:04:03:605  816 de0 Agent *************
2015-07-25 19:04:03:605  816 de0 Agent ** START **  Agent: Installing updates [CallerId = AutomaticUpdates]
2015-07-25 19:04:03:605  816 de0 Agent *********
2015-07-25 19:04:03:605  816 de0 Agent   * Updates to install = 1
2015-07-25 19:04:03:620  816 ad0 AU AU received handle event
2015-07-25 19:04:03:652  816 de0 Agent   *   Title = Security Update for Windows 7 for x64-based Systems (KB3079904)
2015-07-25 19:04:03:652  816 de0 Agent   *   UpdateId = {6D0FC6F5-8079-41BB-B8FE-5240D76FF9E1}.200
2015-07-25 19:04:03:652  816 de0 Agent   *     Bundles 1 updates:
2015-07-25 19:04:03:652  816 de0 Agent   *       {78EE0C4C-298A-4962-8F5F-9E7FB226A606}.200
2015-07-25 19:04:12:076  816 de0 DnldMgr Preparing update for install, updateId = {78EE0C4C-298A-4962-8F5F-9E7FB226A606}.200.
2015-07-25 19:04:12:076 4860 d6c Misc ===========  Logging initialized (build: 7.6.7601.18847, tz: -0700)  ===========
2015-07-25 19:04:12:076 4860 d6c Misc   = Process: C:\Windows\system32\wuauclt.exe
2015-07-25 19:04:12:076 4860 d6c Misc   = Module: C:\Windows\system32\wuaueng.dll
2015-07-25 19:04:12:076 4860 d6c Handler :::::::::::::
2015-07-25 19:04:12:076 4860 d6c Handler :: START ::  Handler: CBS Install
2015-07-25 19:04:12:076 4860 d6c Handler :::::::::
2015-07-25 19:04:12:076 4860 d6c Handler Starting install of CBS update 78EE0C4C-298A-4962-8F5F-9E7FB226A606
2015-07-25 19:04:12:091 4860 d6c Handler CBS package identity: Package_for_KB3079904~31bf3856ad364e35~amd64~~6.1.1.0
2015-07-25 19:04:12:107 4860 d6c Handler Installing self-contained with source=C:\Windows\SoftwareDistribution\Download\3642240aed3fb5f38057dac1e44c2de6\windows6.1-kb3079904-x64.cab, workingdir=C:\Windows\SoftwareDistribution\Download\3642240aed3fb5f38057dac1e44c2de6\inst
2015-07-25 19:04:15:149 4860 d6c Handler Requesting post-reboot reporting for package Package_for_KB3079904~31bf3856ad364e35~amd64~~6.1.1.0.
2015-07-25 19:04:15:149 4860 d6c Handler Completed install of CBS update with type=3, requiresReboot=1, installerError=0, hr=0x0
2015-07-25 19:04:15:149 4860 d6c Handler :::::::::
2015-07-25 19:04:15:149 4860 d6c Handler ::  END  ::  Handler: CBS Install
2015-07-25 19:04:15:149 4860 d6c Handler :::::::::::::
2015-07-25 19:04:15:149  816 1b4 AU >>##  RESUMED  ## AU: Installing update [UpdateId = {6D0FC6F5-8079-41BB-B8FE-5240D76FF9E1}, succeeded]
2015-07-25 19:04:15:149  816 de0 Agent LogHistory called. idUpdate={6D0FC6F5-8079-41BB-B8FE-5240D76FF9E1}.200, resultMapped=80242014, resultUnMapped=0
2015-07-25 19:04:15:180  816 de0 Agent *********
2015-07-25 19:04:15:180  816 de0 Agent **  END  **  Agent: Installing updates [CallerId = AutomaticUpdates]
2015-07-25 19:04:15:180  816 1b4 AU Install call completed.
2015-07-25 19:04:15:180  816 de0 Agent *************
2015-07-25 19:04:15:180  816 1b4 AU   # WARNING: Install call completed, reboot required = Yes, error = 0x00000000
2015-07-25 19:04:15:180  816 1b4 AU #########
2015-07-25 19:04:15:180  816 1b4 AU ##  END  ##  AU: Installing updates [CallId = {3DED3327-50BD-478E-AC52-679078357047}]
2015-07-25 19:04:15:180  816 1b4 AU #############
2015-07-25 19:04:15:180  816 1b4 AU Install complete for all calls, reboot  needed
2015-07-25 19:04:15:180  816 1b4 AU Setting AU scheduled install time to 2015-08-01 10:00:00
2015-07-25 19:04:15:180  816 1b4 AU Successfully wrote event for AU health state:0
2015-07-25 19:04:15:180  816 1b4 AU AU setting pending client directive to 'Reboot Warning'
2015-07-25 19:04:15:180  816 1b4 AU Successfully wrote event for AU health state:0
2015-07-25 19:04:15:180  816 1b4 AU Triggering Offline detection (non-interactive)
2015-07-25 19:04:15:180  816 ad0 AU #############
2015-07-25 19:04:15:180  816 ad0 AU ## START ##  AU: Search for updates
2015-07-25 19:04:15:180  816 ad0 AU #########
2015-07-25 19:04:15:196  816 ad0 AU <<## SUBMITTED ## AU: Search for updates [CallId = {5D75EF71-245D-429C-B459-A83914DBE8B1}]
2015-07-25 19:04:15:196  816 12f4 Agent *************
2015-07-25 19:04:15:196  816 12f4 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
2015-07-25 19:04:15:196  816 12f4 Agent *********
2015-07-25 19:04:15:196  816 12f4 Agent   * Online = No; Ignore download priority = No
2015-07-25 19:04:15:196  816 12f4 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1 or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2015-07-25 19:04:15:196  816 12f4 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2015-07-25 19:04:15:196  816 12f4 Agent   * Search Scope = {Machine}
2015-07-25 19:04:30:187  816 ad0 Misc WARNING: IsSessionNonstandardUI: session 65536 is an unknown session type 0; treating it as a standard session
2015-07-25 19:04:30:187  816 ad0 AU Launched new AU client for directive 'Reboot Warning', session id = 0x1
2015-07-25 19:04:45:226  816 ad0 Misc WARNING: IsSessionNonstandardUI: session 65536 is an unknown session type 0; treating it as a standard session
2015-07-25 19:06:51:071  816 12f4 Agent   * Added update {6D0FC6F5-8079-41BB-B8FE-5240D76FF9E1}.200 to search result
2015-07-25 19:06:51:071  816 12f4 Agent   * Found 1 updates and 85 categories in search; evaluated appl. rules of 2393 out of 4570 deployed entities
2015-07-25 19:06:51:071  816 12f4 Agent *********
2015-07-25 19:06:51:071  816 12f4 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]

dear all, 

i am trying to install wsus on my branch server. 

It will be a downstream server which has IIS, DHCP, File & Print,

When i try to install WSUS through the installer or package the role gets installed but when i try to open the console Server Manager - Wsus - I get a dialog box stating reset server node, cannot connect to server

Port configured for wsus is 8530

I tried to manually add the URL of the server but still cannot connect.

I have also uninstalled the role & tried to install by allowing Internet access to the server.
still same issue

someone please assist.

tfernandes

• I built a new Windows 2012 R2 Standard server and now unable to download patch from microsoft site as it's showing 80072F8F error . I check the forum and and it was asking to check date/timezone . I checked all including route certificate and there is no luck . I would appreciate if anyone can help me fix the issue 

After installing Server 2012 Standard on ESX 5.1 I completed all available Windows Updates and proceeded to add the WSUS role.  I chose the default WID database and the role addition was seemingly successful.  Unfortunately, the Post-deployment Configuration failed.  A log file had been created in the AppData\Local\Temp folder but at initial glance it seemed to imply that my error was likely due to skipping a step during installation via PowerShell.  However, I didn't install using PowerShell and I set off to surf the Internets for clues on resolving this issue.  I searched about a dozen forums that with similar, but different issues until a comment by Lawrence Garvin (http://social.technet.microsoft.com/profile/lawrence%20garvin/?ws=usercard-inline) convinced me to go back and look at my log. 

2013-07-23 11:03:18  Postinstall started
2013-07-23 11:03:18  Detected role services: Api, UI, WidDatabase, Services
2013-07-23 11:03:18  Start: LoadSettingsFromXml
2013-07-23 11:03:18  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentLocal
2013-07-23 11:03:18  Value is true
2013-07-23 11:03:18  End: GetConfigValue
2013-07-23 11:03:18  Start: GetConfigValue with filename=UpdateServices-Services.xml item=ContentDirectory
2013-07-23 11:03:18  Config file did not contain a value "ContentDirectory"
2013-07-23 11:03:18  Microsoft.UpdateServices.Administration.CommandException: A required configuration value was not found in the system. This is usually caused by installing WSUS through PowerShell and not specifying a configuration file. Review the article Managing WSUS Using PowerShell at TechNet Library (http://go.microsoft.com/fwlink/?LinkId=235499) for more information on the recommended steps to perform WSUS installation using PowerShell.
   at Microsoft.UpdateServices.Administration.PostInstall.GetConfigValue(String filename, String item)
   at Microsoft.UpdateServices.Administration.PostInstall.LoadSettingsFromXml()
   at Microsoft.UpdateServices.Administration.PostInstall.Initalize(Parameters parameters)
   at Microsoft.UpdateServices.Administration.PostInstall.Execute(String[] arguments)
Fatal Error: A required configuration value was not found in the system. This is usually caused by installing WSUS through PowerShell and not specifying a configuration file. Review the article Managing WSUS Using PowerShell at TechNet Library (http://go.microsoft.com/fwlink/?LinkId=235499) for more information on the recommended steps to perform WSUS installation using PowerShell.

Upon closer inspection the specifics of my error were right there for me, I just had to look at it long enough to decipher the details.  What I now read is that Post-deployment configuration finds a file called UpdateServices-Services.xml (I found it in Windows\System32\ServerManager\ComponentConfiguration\).  It determines that ContentLocal=True which correctly indicates that my updates are to be stored locally.  It proceeds to inquire about the ContentDirectory, but comes back without a value.  Here are my UpdateServices-Services.xml file contents

<?xml version="1.0" encoding="utf-16"?><INSTANCE CLASSNAME="ServerComponent_UpdateServices_Services"><PROPERTY NAME="ContentDirectory" TYPE="string"></PROPERTY><PROPERTY NAME="ContentLocal" TYPE="boolean"><VALUE>true</VALUE></PROPERTY></INSTANCE>

I can see that the ContentLocal property did indeed have the value true, but the ContentDirectory property did not have a value.  I now needed to figure out if a String value could be specified in the same way a Boolean value was, or if it needed quotes around it, or was supposed to be specified more like an attribute (learned about that somewhere along the way).  I couldn't find any conclusive websites, and I didn't want to just try it for fear of the Post-deployment configuration running with an invalid ContentDirectory.  Once again I returned to my log file and searched for answers at the http://go.microsoft.com/fwlink/?LinkId=235499 that was indicated.  I didn't find any exact matches, but eventually I found a sample .xml file that specified a string value.  It specified it as <VALUE>string</VALUE> with no brackets, so I knew to specify mine as <VALUE>C:\LocalMSUpdateCache</VALUE> and saved it.  My UpdateServices-Services.xml now looks like this:

<?xml version="1.0" encoding="utf-16"?><INSTANCE CLASSNAME="ServerComponent_UpdateServices_Services"><PROPERTY NAME="ContentDirectory" TYPE="string"><VALUE>C:\LocalMSUpdateCache</VALUE></PROPERTY><PROPERTY NAME="ContentLocal" TYPE="boolean"><VALUE>true</VALUE></PROPERTY></INSTANCE>

I returned to Server Manager -> WSUS and re-attempted the Postdeployment configuration.  It completed successfully!

I'm glad that my fix was relatively simple and that Lawrence was particular about the details of the log file. 

1. My exact error isn't always going to be documented

2. Just because the log file looks unintelligible (I have thus far avoided both powershell and xml), doesn't mean it's useless.

Good luck to anyone with a similar issue.  You too may be able to figure it out yourself.

Ok, WSUS is running on Windows server 2008 r2 without problems. Server has SQL Server 2008 r2 running as well. With Windows 10 coming soon, it's time to prepare WSUS to deal with it. So Windows 10 categories are checked in the WSUS console. Now it seems WSUS will refer to Windows 10 as Windows Vista. And we don't want that, so I tried to fix this according to page http://titlerequired.com/2015/07/22/windows-10-on-wsus-shows-as-windows-vista/

I composed the SQL script, but it won't run. The command to run the script looks like this: sqlcmd -I -i WsusDBMaintenance.sql -S \\.\pipe\MSSQL$MICROSOFT##SSEE\sql\query

WsusDBMaintenance.sql being the script responsible for, among maintenance, renaming Windows 10 to, well, Windows 10.

Thing is, there's no database engine called MICROSOFT##SSEE on the box. If I check SQL Server Management Studio, there's a database engine called <servername> holding SUSDB. But specifying <servername> instead of MICROSOFT##SSEEresults in the same error message "Named Pipes Provider: Could not open a connection to SQL Server". Tried fiddling the name like removing the MSSQL$ part, specifying SUSDB etc. but it won't budge.

It's probably something I overlook, so how can I get that script running?

I've got what I consider to be an odd task facing me.  In an server environment where I have no knowledge of the infrastructure, I need to find out where the WSUS server is, and how it's configured.  I can't ask questions of those who are in charge of the environment and I need to identify the WSUS environment ASAP.  I've tried running GPresult and I'm getting access denied for most of the GPResult data even though I'm a domain admin in the environment.

I need to find where the console is installed and whether I have access to it. 

Got a question for everyone here.

I have a WSUS server setup that has been running for the past year or so with great results. With the upcoming Windows 10 update I would like to push that update out to only a select few test computers (desktops and laptops) first before I push it out to the entire company. Once that is done I would like to push out any additional updates to these test computers first before the entire company.

So my question is, if I setup a group (Test Computers) in WSUS just for these certain computers themselves and push any updates to them first, is there a way to see which updates have been pushed out with out having to make manual notes?

Basically what I want to do is to push, lets say 10 updates to 5 computers first, then a week later if everything seems to be working ok, push those same 10 updates out to the rest of the network. I would think there is a report I can run to show me which updates have been pushed, to a certain group and on which date they have been pushed/installed.

I have a strange one it seems.

I'm running Server 2012 with the version of WSUS that's installed through the role. (Version 6.2.9200.16384)

Our computers target WSUS groups / collections via Group Policy and this is working flawlessly.

However for more granular control, we've made a set of extra groups. In order to minimize our administrative overhead, we use a powershell script to scan for the members of an Active Directory group, and subsequently tell WSUS to make them a member of the additional WSUS group.

The script seems to work. As soon as I run it I see computers come in to these WSUS groups, but over the course of the next few hours they start disappearing. But they only disappear from these specific groups and not from the whole WSUS console. In fact, the machines stay in the groups that their GPO's tell them to target, and it's only the additional groups that we put them in that they seem to drop out of.

Any idea what's going on here?

Here's the script with some company specific information redacted.

<# Adds servers that are a member of an AD group to WSUS Computer Groups #>

$Group = "Silver-Applications"
$ADGroup = "Silver-Applications"

## Script begin

Import-Module ActiveDirectory

$Members = Get-ADGroupMember -Identity $ADGroup
$wsus = Get-WsusServer
$Groups = $wsus.GetComputerTargetGroups() | where {$_.Name -eq $Group}

foreach ($line in $Members) { 
$Name = $Line.Name
$DNS = $Name + "FQDN"
write-host $DNS

$wsuscomputer = Get-WSUSComputer -Nameincludes $DNS
Add-WSUSComputer -Computer $wsuscomputer -TargetGroupname $Groups.Name -ErrorAction SilentlyContinue
}

I have WSUS 3 SP2 installed on Windows Server 2008 R2. I recently applied KB2734608  because of new Windows Server 2012 clients on the network.  Since the update, the display console does not show text and buttons properly in any windows with Columnar data.  Text overlaps, does not refresh properly, and buttons are only partially visible.  This does not happen in the summary views (Updates, Computers, Options, or Reports). They display normally.

Is there a .net update that was required or other patch along with KB2734608 that was required?

Fly Navy, Scott MCSE CEH CISSP