none
Clients not installing updates from Downstream WSUS Server

    Frage

  • Hello,

    This is my first post in Technet, I am a new Administrator so please bare with me. My initial setup is as follows:

    Upstream WSUS server named Bak-WSUS1, Downstream server name Atl-WSUS1; Atl-WSUS1 is a replica. We have made the wsus servers site based through GPOs named WSUS(Bakersfield), WSUS (Atlanta), all remote sites and computers get added to the WSUS (atlanta) GPO and they all report to the Atl-WSUS1 Server as they should, the same is true for the WSUS(Bakersfield) computers.

    Every computer that is joined to the WSUS(Bakersfield) GPO reports to the Bak-WSUS1 server (as I just stated) and receives updates as I approve them, however, the approved updates will not install on ANY computer that is reporting to the Atl-wsus1 server. When checking reports on the server it shows the sites as "Approved for Install" but the computers as "Not Installed". 

    I have forced remote clients with wuauclt /resetauthorization /detectnow. When checking the Downstream server status it shows the following: 

    Mode: Replica Installed/NA: 0% Last Synchronization:(Today). So the servers are infact syncing, the downstream server has the files to install, or atleast thats what the file status says. 

    Any and all suggestions, help, comments, ANYTHING would be greatly appreciated, I have been crawling every related forum for the past couple of days.

    Thank you.

    Freitag, 14. Juni 2013 22:34

Antworten

  • Lawrence,

    Thank you for all your help, it was infact a duplicate SusClientID issue. Here is the solution:

    CMD Window net stop wuauserv

    regedit HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

    Delete the subkeys SusClientID, SusClientIDValidation

    CMD Window net start wuauserv

    wuauclt.exe /resetauthorization /detectnow

    the /resetauthorization switch re-issues the SusclientID and Validation

    Thank you again Lawrence.

    Mittwoch, 19. Juni 2013 14:49

Alle Antworten

  • Am 15.06.2013 schrieb Ryan Blaeholder:

    Upstream WSUS server named Bak-WSUS1, Downstream server name Atl-WSUS1; Atl-WSUS1 is a replica. We have made the wsus servers site based through GPOs named WSUS(Bakersfield), WSUS (Atlanta), all remote sites and computers get added to the WSUS (atlanta) GPO and they all report to the Atl-WSUS1 Server as they should, the same is true for the WSUS(Bakersfield) computers.

    Every computer that is joined to the WSUS(Bakersfield) GPO reports to the Bak-WSUS1 server (as I just stated) and receives updates as I approve them, however, the approved updates will not install on ANY computer that is reporting to the Atl-wsus1 server. When checking reports on the server it shows the sites as "Approved for Install" but the computers as "Not Installed". 

    I have forced remote clients with wuauclt /resetauthorization /detectnow. When checking the Downstream server status it shows the following: 

    Look at the Clients who not reporting in %windir%\Windows for
    errormessages.

    Winfried


    WSUS Package Publisher: http://wsuspackagepublisher.codeplex.com/
    http://technet.microsoft.com/en-us/windowsserver/bb332157.aspx
    http://www.wsuswiki.com/Home

    Samstag, 15. Juni 2013 15:32
  • however, the approved updates will not install on ANY computer that is reporting to the Atl-wsus1 server.

    So the servers are infact syncing, the downstream server has the files to install, or atleast thats what the file status says. 

    Eliminating the question of sync/download to the replica WSUS server, the next most common impact of a NEW WSUS installation that would affect clients, in toto, is that those clients have already been updated with the latest WUAgent, compliments of AU/WU, but the WSUS server has not been patched with KB2720211 or KB2734608.

    To Winfried's point of inspecting the WindowsUpdate.log, this scenario will be manifested by the presence of 0x800B0001 error codes.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Sonntag, 16. Juni 2013 16:03
    Moderator
  • Lawrence,

    I am VERY glad to see you post on this thread. I have been following your forum solutions and best practices since I started this WSUS project, thank you for your input. I dont see the " 0x800B0001" error code on the client that I checked, are you suggesting that I should download and install "KB2720211","KB2734608" on my WSUS servers? I can also post the exact log file if needed. 

    I apologize if this seems redundant or simple, I am very new to this.

    Thank you all for your input.

    Montag, 17. Juni 2013 20:19
  • I am VERY glad to see you post on this thread. I have been following your forum solutions and best practices since I started this WSUS project, thank you for your input. I dont see the " 0x800B0001" error code on the client that I checked, are you suggesting that I should download and install "KB2720211","KB2734608" on my WSUS servers?

    *If* you had clients displaying that specific error, it would be appropriate to install the update. However, even if you've not yet installed the update, doing so is required. KB2720211 or KB2734608 must be installed to WSUS to maintain operational capabilities, so keep that on your to-do list if not already done.

    Yet, there are many other reasons why a client might be failing to communicate with a WSUS server, so diagnostics are still the first order of business. Once we have a known symptom, we can implement a solution.

    Please do the following:

    1. Reboot one of these client systems.
    2. Run the command: wuauclt /resetauthorization /detectnow from an Admin Command Prompt.
    3. Wait 30 minutes.
    4. Post the entries from the WindowsUpdate.log starting with the reboot event performed in Step #1.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Montag, 17. Juni 2013 22:37
    Moderator
  • Lawrence,

    Interesting events, first, I searched for those KB Articles, I had KB2720211 on both of my servers, but not KB2734608. I made sure they both had KB2734608 rebooted and then started with the step by step process that you provided me with. Keep in mind I started the WUAUCLT command at 4:28 (after reboot) and the log is stating it didnt do anything after I ran the command, here is the log from the time requested:

    2013-06-17 16:28:04:923 1240 e2c AU AU found 0 updates for install at shutdown
    2013-06-17 16:28:05:002 748 2f0 Misc ===========  Logging initialized (build: 7.6.7600.256, tz: -0700)  ===========
    2013-06-17 16:28:05:002 748 2f0 Misc  = Process: \??\C:\WINDOWS\system32\winlogon.exe
    2013-06-17 16:28:05:002 748 2f0 Misc  = Module: C:\WINDOWS\system32\wuaueng.dll
    2013-06-17 16:28:05:002 748 2f0 Shutdwn Install at shutdown: no updates to install
    2013-06-17 16:28:12:783 1240 328 AU ###########  AU: Uninitializing Automatic Updates  ###########
    2013-06-17 16:28:13:736 1240 328 Service *********
    2013-06-17 16:28:13:736 1240 328 Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2013-06-17 16:28:13:736 1240 328 Service *************
    2013-06-17 16:28:49:875 1236 2c0 Misc ===========  Logging initialized (build: 7.6.7600.256, tz: -0700)  ===========
    2013-06-17 16:28:49:890 1236 2c0 Misc  = Process: C:\WINDOWS\System32\svchost.exe
    2013-06-17 16:28:49:890 1236 2c0 Misc  = Module: C:\WINDOWS\system32\wuaueng.dll
    2013-06-17 16:28:49:875 1236 2c0 Service *************
    2013-06-17 16:28:49:890 1236 2c0 Service ** START **  Service: Service startup
    2013-06-17 16:28:49:890 1236 2c0 Service *********
    2013-06-17 16:28:49:906 1236 2c0 Agent  * WU client version 7.6.7600.256
    2013-06-17 16:28:49:906 1236 2c0 Agent  * Base directory: C:\WINDOWS\SoftwareDistribution
    2013-06-17 16:28:49:906 1236 2c0 Agent  * Access type: No proxy
    2013-06-17 16:28:49:906 1236 2c0 Agent  * Network state: Connected
    2013-06-17 16:29:36:358 1236 2c0 Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2013-06-17 16:29:36:358 1236 2c0 Agent ***********  Agent: Initializing global settings cache  ***********
    2013-06-17 16:29:36:358 1236 2c0 Agent  * WSUS server: http://atl-wsus1
    2013-06-17 16:29:36:358 1236 2c0 Agent  * WSUS status server: http://atl-wsus1
    2013-06-17 16:29:36:358 1236 2c0 Agent  * Target group: (Unassigned Computers)
    2013-06-17 16:29:36:358 1236 2c0 Agent  * Windows Update access disabled: No
    2013-06-17 16:29:36:390 1236 2c0 DnldMgr Download manager restoring 0 downloads
    2013-06-17 16:29:36:406 1236 2c0 AU ###########  AU: Initializing Automatic Updates  ###########
    2013-06-17 16:29:36:406 1236 2c0 AU AU setting next sqm report timeout to 2013-06-17 23:29:36
    2013-06-17 16:29:36:406 1236 2c0 AU  # WSUS server: http://atl-wsus1
    2013-06-17 16:29:36:406 1236 2c0 AU  # Detection frequency: 22
    2013-06-17 16:29:36:406 1236 2c0 AU  # Approval type: Scheduled (Policy)
    2013-06-17 16:29:36:406 1236 2c0 AU  # Scheduled install day/time: Every day at 3:00
    2013-06-17 16:29:36:406 1236 2c0 AU  # Auto-install minor updates: Yes (User preference)
    2013-06-17 16:29:36:406 1236 2c0 AU  # Will interact with non-admins (Non-admins are elevated (Policy))
    2013-06-17 16:29:36:422 1236 2c0 AU Setting AU scheduled install time to 2013-06-18 10:00:00
    2013-06-17 16:29:36:422 1236 2c0 AU Initializing featured updates
    2013-06-17 16:29:36:422 1236 2c0 AU Found 0 cached featured updates
    2013-06-17 16:29:36:438 1236 2c0 AU AU finished delayed initialization
    2013-06-17 16:29:38:258 1236 2c0 Report ***********  Report: Initializing static reporting data  ***********
    2013-06-17 16:29:38:258 1236 2c0 Report  * OS Version = 5.1.2600.3.0.65792
    2013-06-17 16:29:38:370 1236 2c0 Report  * Computer Brand = Dell Inc.
    2013-06-17 16:29:38:370 1236 2c0 Report  * Computer Model = Precision WorkStation T3500  
    2013-06-17 16:29:38:402 1236 2c0 Report  * Bios Revision = A14
    2013-06-17 16:29:38:402 1236 2c0 Report  * Bios Name = Phoenix ROM BIOS PLUS Version 1.10 A14
    2013-06-17 16:29:38:402 1236 2c0 Report  * Bios Release Date = 2011-12-29T00:00:00
    2013-06-17 16:29:38:402 1236 2c0 Report  * Locale ID = 1033
    2013-06-17 16:33:54:025 1236 614 AU Triggering AU detection through DetectNow API
    2013-06-17 16:33:54:025 1236 614 AU Triggering Online detection (non-interactive)
    2013-06-17 16:33:54:025 1236 2c0 AU #############
    2013-06-17 16:33:54:025 1236 2c0 AU ## START ##  AU: Search for updates
    2013-06-17 16:33:54:025 1236 2c0 AU #########
    2013-06-17 16:33:54:041 1236 2c0 AU <<## SUBMITTED ## AU: Search for updates [CallId = {88A20036-FD4B-42F0-8791-2777162A138E}]
    2013-06-17 16:33:54:041 1236 808 Agent *************
    2013-06-17 16:33:54:041 1236 808 Agent ** START **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-06-17 16:33:54:041 1236 808 Agent *********
    2013-06-17 16:33:54:041 1236 808 Agent  * Online = Yes; Ignore download priority = No
    2013-06-17 16:33:54:041 1236 808 Agent  * Criteria = "IsHidden=0 and IsInstalled=0 and DeploymentAction='Installation' and IsAssigned=1 or IsHidden=0 and IsPresent=1 and DeploymentAction='Uninstallation' and IsAssigned=1 or IsHidden=0 and IsInstalled=1 and DeploymentAction='Installation' and IsAssigned=1 and RebootRequired=1 or IsHidden=0 and IsInstalled=0 and DeploymentAction='Uninstallation' and IsAssigned=1 and RebootRequired=1"
    2013-06-17 16:33:54:041 1236 808 Agent  * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
    2013-06-17 16:33:54:041 1236 808 Agent  * Search Scope = {Machine}
    2013-06-17 16:33:54:089 1236 808 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2013-06-17 16:33:54:169 1236 808 Misc Microsoft signed: Yes
    2013-06-17 16:33:54:744 1236 808 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wuident.cab:
    2013-06-17 16:33:54:760 1236 808 Misc Microsoft signed: Yes
    2013-06-17 16:33:55:079 1236 808 Misc Validating signature for C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.cab:
    2013-06-17 16:33:55:079 1236 808 Misc Microsoft signed: Yes
    2013-06-17 16:33:55:095 1236 808 Setup ***********  Setup: Checking whether self-update is required  ***********
    2013-06-17 16:33:55:095 1236 808 Setup  * Inf file: C:\WINDOWS\SoftwareDistribution\SelfUpdate\Default\wsus3setup.inf
    2013-06-17 16:33:55:111 1236 808 Setup Update NOT required for C:\WINDOWS\system32\cdm.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-06-17 16:33:55:111 1236 808 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-06-17 16:33:55:207 1236 808 Setup Update NOT required for C:\WINDOWS\system32\wuapi.dll.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-06-17 16:33:55:207 1236 808 Setup Update NOT required for C:\WINDOWS\system32\wuauclt.exe: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-06-17 16:33:55:207 1236 808 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-06-17 16:33:55:223 1236 808 Setup Update NOT required for C:\WINDOWS\system32\wuaucpl.cpl.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-06-17 16:33:55:223 1236 808 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-06-17 16:33:55:239 1236 808 Setup Update NOT required for C:\WINDOWS\system32\wuaueng.dll.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-06-17 16:33:55:239 1236 808 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-06-17 16:33:55:255 1236 808 Setup Update NOT required for C:\WINDOWS\system32\wucltui.dll.mui: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-06-17 16:33:55:255 1236 808 Setup Update NOT required for C:\WINDOWS\system32\wups.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-06-17 16:33:55:255 1236 808 Setup Update NOT required for C:\WINDOWS\system32\wups2.dll: target version = 7.6.7600.256, required version = 7.6.7600.256
    2013-06-17 16:33:55:271 1236 808 Setup Update NOT required for C:\WINDOWS\system32\wuweb.dll: target version = 7.6.7600.257, required version = 7.6.7600.256
    2013-06-17 16:33:55:287 1236 808 Setup  * IsUpdateRequired = No
    2013-06-17 16:33:59:870 1236 808 PT +++++++++++  PT: Synchronizing server updates  +++++++++++
    2013-06-17 16:33:59:870 1236 808 PT  + ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}, Server URL = http://atl-wsus1/ClientWebService/client.asmx
    2013-06-17 16:34:00:109 1236 808 PT WARNING: Cached cookie has expired or new PID is available
    2013-06-17 16:34:00:109 1236 808 PT Initializing simple targeting cookie, clientId = 530b8555-702c-40bd-8762-c860a000232c, target group = , DNS name = prou-1nc8ps1.ntserver.local
    2013-06-17 16:34:00:109 1236 808 PT  Server URL = http://atl-wsus1/SimpleAuthWebService/SimpleAuth.asmx
    2013-06-17 16:34:00:604 1236 808 PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2013-06-17 16:34:00:604 1236 808 PT WARNING: SOAP Fault: 0x00012c
    2013-06-17 16:34:00:604 1236 808 PT WARNING:     faultstring:Fault occurred
    2013-06-17 16:34:00:604 1236 808 PT WARNING:     ErrorCode:ConfigChanged(2)
    2013-06-17 16:34:00:604 1236 808 PT WARNING:     Message:(null)
    2013-06-17 16:34:00:604 1236 808 PT WARNING:     Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/GetCookie"
    2013-06-17 16:34:00:604 1236 808 PT WARNING:     ID:71ceda14-c2db-4c98-ac8f-0143faa60aa4
    2013-06-17 16:34:00:796 1236 808 PT WARNING: Cached cookie has expired or new PID is available
    2013-06-17 16:34:00:796 1236 808 PT Initializing simple targeting cookie, clientId = 530b8555-702c-40bd-8762-c860a000232c, target group = , DNS name = prou-1nc8ps1.ntserver.local
    2013-06-17 16:34:00:796 1236 808 PT  Server URL = http://atl-wsus1/SimpleAuthWebService/SimpleAuth.asmx
    2013-06-17 16:35:38:740 1236 808 Agent  * Found 0 updates and 72 categories in search; evaluated appl. rules of 1194 out of 2487 deployed entities
    2013-06-17 16:35:38:866 1236 808 Agent *********
    2013-06-17 16:35:38:866 1236 808 Agent **  END  **  Agent: Finding updates [CallerId = AutomaticUpdates]
    2013-06-17 16:35:38:866 1236 808 Agent *************
    2013-06-17 16:35:38:866 1236 ae0 AU >>##  RESUMED  ## AU: Search for updates [CallId = {88A20036-FD4B-42F0-8791-2777162A138E}]
    2013-06-17 16:35:38:866 1236 ae0 AU  # 0 updates detected
    2013-06-17 16:35:38:866 1236 ae0 AU #########
    2013-06-17 16:35:38:866 1236 ae0 AU ##  END  ##  AU: Search for updates [CallId = {88A20036-FD4B-42F0-8791-2777162A138E}]
    2013-06-17 16:35:38:866 1236 ae0 AU #############
    2013-06-17 16:35:38:866 1236 ae0 AU Featured notifications is disabled.
    2013-06-17 16:35:38:866 1236 ae0 AU AU setting next detection timeout to 2013-06-18 21:21:23
    2013-06-17 16:35:38:866 1236 ae0 AU Setting AU scheduled install time to 2013-06-18 10:00:00
    2013-06-17 16:35:43:906 1236 808 Report REPORT EVENT: {661CF590-B080-474E-A467-C859097CE635} 2013-06-17 16:35:38:866-0700 1 147 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Software Synchronization Windows Update Client successfully detected 0 updates.
    2013-06-17 16:35:43:906 1236 808 Report REPORT EVENT: {E6EDAC44-6104-41AA-904C-94E37C6BBE5D} 2013-06-17 16:35:38:866-0700 1 156 101 {00000000-0000-0000-0000-000000000000} 0 0 AutomaticUpdates Success Pre-Deployment Check Reporting client status.
    2013-06-17 16:38:17:218 1236 808 Report Uploading 2 events using cached cookie, reporting URL = http://atl-wsus1/ReportingWebService/ReportingWebService.asmx
    2013-06-17 16:38:17:644 1236 808 Report Reporter successfully uploaded 2 events.

    Please let me know what to look for (I have searched for the weird SOAP error and didnt find anything on it).

    Dienstag, 18. Juni 2013 00:12
  • 2013-06-17 16:34:00:604 1236 808 PT WARNING: GetCookie failure, error = 0x8024400D, soap client error = 7, soap error code = 300, HTTP status code = 200
    2013-06-17 16:34:00:604 1236 808 PT WARNING: SOAP Fault: 0x00012c

    This error is most often symptomatic of a duplicate SusClientID.

    2013-06-17 16:35:38:740 1236 808 Agent * Found 0 updates and 72 categories in search; evaluated appl. rules of 1194 out of 2487 deployed entities

    And quite often results in the inability to identify available updates.

    But these results are often seen to be ambiguous. For example, I've seen the 0x8024400D/SOAP 0x12c error thrown spontaneously and randomly on clients of replica servers, and then perform absolutely perfectly. So the "Found 0 updates..." could be a manifestation of a dupe SusClientID, or it could be indicative of no updates being available for download/install.

    Check the download status of the assigned WSUS Server (atl-wsus1) and verify that there are no downloads pending. If not, then it's likely the result of a duplicate SusClientID, so follow the guidance in KB903262, and then repeat the log generation instructions from the previous message.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Dienstag, 18. Juni 2013 00:49
    Moderator
  • Lawrence,

    If by checking to make sure there no downloads on the Atl-wsus1 server, means to check the file status, I have and it shows the they are ready for installation. Which I think means that i now need to look into the duplicate SusClientID issue... I have already started looking into this, but I am still curious as to why this would effect only those that are reporting to the Atl-wsus1 server and not the Bak-wsus1 server. (Meaning the downstream server and not the upstream server). 

    This also brings up another question, if I remove the downstream server and have all the computers instead report to the upstream server, will this still be an issue? Or is this a specific problem with the Hierarchy of WSUS?

    Dienstag, 18. Juni 2013 23:02
  • if I remove the downstream server and have all the computers instead report to the upstream server, will this still be an issue?

    If it's a duplicate SusClientID issue.. yes. That's a client-side defect, not a server-side defect. If two or more clients are talking to the same WSUS server with the same SusClientID, it will present problems.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Mittwoch, 19. Juni 2013 01:40
    Moderator
  • Lawrence,

    Thank you for all your help, it was infact a duplicate SusClientID issue. Here is the solution:

    CMD Window net stop wuauserv

    regedit HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate

    Delete the subkeys SusClientID, SusClientIDValidation

    CMD Window net start wuauserv

    wuauclt.exe /resetauthorization /detectnow

    the /resetauthorization switch re-issues the SusclientID and Validation

    Thank you again Lawrence.

    Mittwoch, 19. Juni 2013 14:49