Quantcast
Channel: WSUS forum
Viewing all 12874 articles
Browse latest View live
↧

Windows Patch installation getting failed on Windows 2016 sevrer

September 7, 2018, 6:26 am
$
0
0

Hi,

I'm using WSUS server (2016) to install windows patches. I'm facing bit strange issue and PFB details.

Issue-  Aug2018 (KB4343887 & KB43438814) patch is not getting installed in few (16 out of 50)  windows 2016 standard edition servers. All these servers are in same network. Last patch success is June cumulative patch on these servers

  • Patch getting detected in clients and installing 100%. While rebooting sever, its undoing the patches.
  • I've tried to install manually and same issue. I've disabled local windows firewall and disabled Antivirus alsoe. still no luck.
  • I've deregister and re-register the patch server & renamed SoftwareDistribution folder also. Still no luck.
  • I've made  bits,cryptsvc,trustedinstaller services automatic and no luck.

We have done the patching in 3 slots. Slot-1 -- 10 server (100% Success), Slot-2 -- 15 servers (1 server failed) and slot-3 on Aug 30th -- 25 servers (16 failed).

I've attached error screenshots.  Please assist me to resolve the issue. Is it failing because any dependent (MAY18 patch is already installed in that sevrers) patch missing or on AUG 30th new patch got release, due to this..?

Error Code From logs: Installation Failure: Windows Failed to install the following update with Error 0x800F0922

↧
Search

Failure configuring Windows updates on Windows 2008 R2 SP1 64bit under VMware

September 21, 2018, 2:14 am
$
0
0

Hello all, I have tried many solution on Google but above error is still occured.

Failure configuration Windows updates Reverting changes. Do not turn off your computer.

Kindly if you guys can provide any other suggestion (except reinstallation of Windows 2008 R2)

↧
↧

WSUS - WSUS Clients(Servers and Desktops) are unable to get patches downloaded.

September 21, 2018, 6:45 am
$
0
0

WSUS Clients(Servers and Desktops) are unable to get patches downloaded.

Can someone help in this regards please.

↧

How to improve the Speed of downloading patches on Windows 2016 WSUS 4.0

September 24, 2018, 8:32 pm
$
0
0

It took WSUS 4 hours to download the patch for 300MB. How to improve the Speed of downloading patches on Windows 2016 WSUS 4.0？

↧

windows 2016 wsus fails in intial synchronization

September 24, 2018, 11:11 pm
$
0
0

after installing and configuring WSUS role in my new 2016 server it fails in initial synchronization.the underlying connection was closed . an unexpected error was occurred

can any one answer

do I need to update the  LOCAL wsus server initially to get it synched

or I need to upgrade any SP

↧
↧

Technical differences WSUS vs SCCM

September 25, 2018, 2:40 am
$
0
0

Microsoft tools to handle their patching needs: Windows Server Update Services (WSUS) or System Center Configuration Manager (SCCM or ConfigMgr).

Can we do OS upgrade or new install or re-image? or only for OS updates?

Please share major differences between these two solutions.

↧

WSUS console unexpected error when choosing All Computers folder

September 25, 2018, 3:32 am
$
0
0



The below are the error code :

Log Name: Application

Source: Windows Server Update Server

Event ID :7053

Level:Error

User:N/A

The WSUS administration console has encountered an unexpected error. This may be a transient error; try restarting the administration console. If this error persists, 

Try removing the persisted preferences for the console by deleting the wsus file under %appdata%\Microsoft\MMC\.


System.NotSupportedException -- The specified IncludedInstallationStates (NotInstalled, Downloaded, InstalledPendingReboot) and ExcludedInstallationStates (0) are not supported.

Source
Microsoft.UpdateServices.UI.AdminApiAccess

Stack Trace:
   at Microsoft.UpdateServices.UI.AdminApiAccess.AdminApiTools.GetSimplifiedUpdateInstallationState(UpdateInstallationStates includedInstallationStates, UpdateInstallationStates excludedInstallationStates)
   at Microsoft.UpdateServices.UI.SnapIn.Pages.ComputersListPage.PopulateFilterDropdown()

I had try the bellow link but still not able to solve the issue :

https://social.technet.microsoft.com/Forums/ie/en-US/90dc15d3-c498-42b8-b36a-bd29be35cf99/wsus-console-unexpected-error-when-choosing-all-computers-folder?forum=winserverwsus

Any solution

↧

no change membership option on upstream server

July 6, 2016, 6:39 am
$
0
0

Hi,

there is no option for changing computer membership on Upstream Server that is reporting to the replica server.

Why? Is there a way to enable this?

Computer on replica WSUS:

The same machine on Upstream server:

--- When you hit a wrong note its the next note that makes it good or bad. --- Miles Davis


↧
Search

WSUS Synchronization failed

September 19, 2018, 11:46 pm
$
0
0

Friends

Can any one help me on the below issue,

I just recently installed WSUS role on 2012r2 server, configuration part went well. after then trying to click synchronize now button, it is getting failed and looked on to the error stating. "Feature unavailable" The microsoft report viewer 2008 Redistributable is required to install this feature. Please close the console before installating this package. Hence have download the report viewer and try installing that, but getting error: prerequisite program are missing , setup has detected that the following prerequisite programs are not installed: Microsoft.net framework 2.0, but the server installed .net framework 3.5 from roles and features. Can any one advise the resolution for this. 

↧
↧

Problems installing KB3159706 on Windows Server 2012 R2

August 1, 2017, 8:32 am
$
0
0

Hi guys,

I'm having a problem when I try to install the KB3159706 on my WSUS Server (Windows Server 2012 R2 Standard Version 6.3 Build 9600).

Whenever I try I get this error message "The updates is not applicable to your computer."

If I look at the Windows Event Viewer it shows me the error below:

Windows update  could not be installed because of error 2149842967 "" (Command line: ""C:\Windows\system32\wusa.exe" "C:\Downloads\windows8.1-kb3159706-x64_034b30c6c261d4e76b8c6f8fe3cc9fa5fa4e977b.msu" ")

Since this update is necessary to provide the Windows 10 upgrades, I have been having problems to accomplish this.

These are the updates already installed:

Hotfix(s):                 153 Hotfix(s) Installed.
                           [01]: KB2868626
                           [02]: KB2883200
                           [03]: KB2887595
                           [04]: KB2894856
                           [05]: KB2903939
                           [06]: KB2911106
                           [07]: KB2919355
                           [08]: KB2919394
                           [09]: KB2920189
                           [10]: KB2928680
                           [11]: KB2934520
                           [12]: KB2938066
                           [13]: KB2954879
                           [14]: KB2955164
                           [15]: KB2961072
                           [16]: KB2961908
                           [17]: KB2962806
                           [18]: KB2967917
                           [19]: KB2973351
                           [20]: KB2975061
                           [21]: KB2977765
                           [22]: KB2978041
                           [23]: KB2978126
                           [24]: KB2979576
                           [25]: KB2989930
                           [26]: KB2999226
                           [27]: KB3000483
                           [28]: KB3000850
                           [29]: KB3003057
                           [30]: KB3004361
                           [31]: KB3004365
                           [32]: KB3004545
                           [33]: KB3012702
                           [34]: KB3013172
                           [35]: KB3013769
                           [36]: KB3013791
                           [37]: KB3013816
                           [38]: KB3014029
                           [39]: KB3014442
                           [40]: KB3018467
                           [41]: KB3019978
                           [42]: KB3021910
                           [43]: KB3022777
                           [44]: KB3023222
                           [45]: KB3023266
                           [46]: KB3024751
                           [47]: KB3024755
                           [48]: KB3029603
                           [49]: KB3030377
                           [50]: KB3030947
                           [51]: KB3032663
                           [52]: KB3033446
                           [53]: KB3034348
                           [54]: KB3035126
                           [55]: KB3035527
                           [56]: KB3036612
                           [57]: KB3037579
                           [58]: KB3037924
                           [59]: KB3038002
                           [60]: KB3038562
                           [61]: KB3041857
                           [62]: KB3042058
                           [63]: KB3042085
                           [64]: KB3043812
                           [65]: KB3044374
                           [66]: KB3044673
                           [67]: KB3045634
                           [68]: KB3045685
                           [69]: KB3045717
                           [70]: KB3045719
                           [71]: KB3045755
                           [72]: KB3045992
                           [73]: KB3045999
                           [74]: KB3046017
                           [75]: KB3046737
                           [76]: KB3047255
                           [77]: KB3048043
                           [78]: KB3054169
                           [79]: KB3054203
                           [80]: KB3054256
                           [81]: KB3054464
                           [82]: KB3055323
                           [83]: KB3055343
                           [84]: KB3055642
                           [85]: KB3058168
                           [86]: KB3059316
                           [87]: KB3059317
                           [88]: KB3060681
                           [89]: KB3060716
                           [90]: KB3060793
                           [91]: KB3061512
                           [92]: KB3061518
                           [93]: KB3063843
                           [94]: KB3065822
                           [95]: KB3067505
                           [96]: KB3068708
                           [97]: KB3071663
                           [98]: KB3071756
                           [99]: KB3073874
                           [100]: KB3074228
                           [101]: KB3074548
                           [102]: KB3075220
                           [103]: KB3075853
                           [104]: KB3077715
                           [105]: KB3078071
                           [106]: KB3078676
                           [107]: KB3080042
                           [108]: KB3080149
                           [109]: KB3081320
                           [110]: KB3082089
                           [111]: KB3082353
                           [112]: KB3083325
                           [113]: KB3083711
                           [114]: KB3083992
                           [115]: KB3084135
                           [116]: KB3086255
                           [117]: KB3087038
                           [118]: KB3087041
                           [119]: KB3087137
                           [120]: KB3087390
                           [121]: KB3092601
                           [122]: KB3092627
                           [123]: KB3095113
                           [124]: KB3102939
                           [125]: KB3108381
                           [126]: KB3109103
                           [127]: KB3110329
                           [128]: KB3121918
                           [129]: KB3126041
                           [130]: KB3126434
                           [131]: KB3126587
                           [132]: KB3132080
                           [133]: KB3133043
                           [134]: KB3139398
                           [135]: KB3139914
                           [136]: KB3146723
                           [137]: KB3153704
                           [138]: KB3155784
                           [139]: KB3156059
                           [140]: KB3159398
                           [141]: KB3161949
                           [142]: KB3161958
                           [143]: KB3162343
                           [144]: KB3169704
                           [145]: KB3170455
                           [146]: KB3172729
                           [147]: KB3173424
                           [148]: KB3175024
                           [149]: KB3178539
                           [150]: KB4012213
                           [151]: KB4022717
                           [152]: KB4025333
                           [153]: KB4025336

Thank you.

Felipe M Ferreira


↧

2016 Updates vs 2016 (buildnumber) updates

September 26, 2018, 5:34 am
$
0
0

In WSUS  we are seeing some 2016 updates without a build number, 1709,1803 etc...  and some with the number.

Also we are currently running 2016 LTSB - currently 1607.   

I'm guessing that the patches with the newer build numbers in the name are for the short term branch and would not apply to the LTSB version.

Just want to double check that this is correct so I can just disapprove them or should I approve them ?

Thanks

↧

KB4054518 - 2017-12 Security Monthly Quality Rollup failed to update - Server 2012 R2

January 6, 2018, 12:02 pm
$
0
0

Using WSUS to update the patches on some servers. Failing to install KB4054518 - 2017-12 Security Monthly Quality Rollup on some of our server running Windows Server 2012 R2. I am out of ideas. I did stopping of Windows update servers, renaming the Software Distribution folder, and a manual download and install, as well as ran a sfc /scannow, with no luck.

So far this issue appears limited to our Hyper-V Hosts.  All the guests were off.  We don't currently use SCVMM, and no migrations or other work was being done.

I checked the CBS log for errors and there was a LOT there (there were 759 instances of ", Error"):

 

There was more detail between the date-time lines, but I wanted to provide a sample of the errors.

2018-01-06 12:08:28, Error                 CSI    00000001 (F) Logged @2018/1/6:19:08:28.725 : [ml:272{136},l:270{135}]"events installer: online=1, install=1, component=amd64_Microsoft-Hyper-V-VStack-VMMS_31bf3856ad364e35_6.3.9600.18841_neutral_release__."
[gle=0x80004005]
2018-01-06 12:08:28, Error                 CSI    00000002 (F) Logged @2018/1/6:19:08:28.959 : [ml:144{72},l:142{71}]"WmiCmiPlugin (-1): InstrumentationManifestAssert failed. HR=0x80070057."
[gle=0x80004005]
2018-01-06 12:08:28, Error                 CSI    00000003 (F) Logged @2018/1/6:19:08:28.959 : [ml:166{83},l:164{82}]"WmiCmiPlugin eventloghandler.cpp(192): ProcessEventsInstall failed. HR=0x80070057."
[gle=0x80004005]
2018-01-06 12:08:28, Error                 CSI    00000004 (F) Logged @2018/1/6:19:08:28.959 : [ml:170{85},l:168{84}]"WmiCmiPlugin eventloghandler.cpp(212): EventLogHandlerInstall failed. HR=0x80070057."
[gle=0x80004005]
2018-01-06 12:08:28, Error                 CSI    00000005@2018/1/6:19:08:28.959 (F) CMIADAPTER: Inner Error Message from AI HRESULT = E_INVALIDARG
 [
[29]"The parameter is incorrect.

"
]
[gle=0x80004005]
2018-01-06 12:08:28, Error                 CSI    00000006@2018/1/6:19:08:28.959 (F) CMIADAPTER: AI failed. HRESULT = E_INVALIDARG
2018-01-06 12:08:28, Error                 CSI    C_VMMS_OPERATIONAL" enabled="true" isolation="System" name="Microsoft-Windows-Hyper-V-VMMS-Operational" symbol="VMC_VMMS_OPERATIONAL" type="Operational">$(string.OperationalChannel)</channel>
2018-01-06 12:08:28, Error                 CSI    " symbol="VMT_VMMS_RESET" value="0x109" />
2018-01-06 12:08:28, Error                 CSI    sk message="$(string.VMT_VMMS_MIGRATION_SRC_GET_COMPATIBILITY_INFO.TaskMessage)" name="VMT_VMMS_MIGRATION_SRC_GET_COMPATIBILITY_INFO" symbol="VMT_VMMS_MIGRATION_SRC_GET_COMPATIBILITY_INFO" value="0x207" />
2018-01-06 12:08:28, Error                 CSI    l="VMT_VMMS_MIGRATION_SRC_FAILURE_RECOVERY" value="0x211" />
2018-01-06 12:08:28, Error                 CSI    ="VMT_VMMS_MIGRATION_DST_COPY_SAVED_STATE_FILES" value="0x245" />
2018-01-06 12:08:28, Error                 CSI        <task message="$(string.VMT_VMMS_MIGRATION_DST_FAILURE_WORKER_EXIT.TaskMessage)" name="VMT_VMMS_MIGRATION_DST_FAILURE_WORKER_EXIT" symbol="VMT_VMMS_MIGRATION_DST_FAILURE_WORKER_EXIT" value="0x250" />
2018-01-06 12:08:28, Error                 CSI    K" value="0x260" />
2018-01-06 12:08:28, Error                 CSI    _TEMPLATE">
2018-01-06 12:08:28, Error                 CSI    plate>
2018-01-06 12:08:28, Error                 CSI    "VmName" />
2018-01-06 12:08:28, Error                 CSI    ring" name="Param1" />
2018-01-06 12:08:28, Error                 CSI           </UserData>
2018-01-06 12:08:28, Error                 CSI    <Parameter1>%2</Parameter1>
2018-01-06 12:08:28, Error                 CSI    ttp://www.microsoft.com/Windows/Virtualization/Events">
2018-01-06 12:08:28, Error                 CSI              <Parameter1>%4</Parameter1>
2018-01-06 12:08:28, Error                 CSI    mName" />
2018-01-06 12:08:28, Error                 CSI         </UserData>
2018-01-06 12:08:28, Error                 CSI    %4</Parameter1>
2018-01-06 12:08:28, Error                 CSI    R3INT_TEMPLATE">
2018-01-06 12:08:28, Error                 CSI    template tid="VMMS_VM_ERROR_MSG2_TEMPLATE">
2018-01-06 12:08:28, Error                 CSI         <VmlEventLog xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
2018-01-06 12:08:28, Error                 CSI    g" name="Parameter2" />
2018-01-06 12:08:28, Error                 CSI    ameter2>%4</Parameter2>
2018-01-06 12:08:28, Error                 CSI            <data inType="win:UnicodeString" name="Parameter2" />
2018-01-06 12:08:28, Error                 CSI    >
2018-01-06 12:08:28, Error                 CSI         </VmlEventLog>
2018-01-06 12:08:28, Error                 CSI     xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
2018-01-06 12:08:28, Error                 CSI    ft.com/Windows/Virtualization/Events">
2018-01-06 12:08:28, Error                 CSI    ageType>%1</StorageType>
2018-01-06 12:08:28, Error                 CSI    tionLatency" />
2018-01-06 12:08:28, Error                 CSI    ts">
2018-01-06 12:08:28, Error                 CSI    ace>
2018-01-06 12:08:28, Error                 CSI    g" message="$(string.MSWVM_GENERIC_TRACE.EventMessage)" symbol="MSVML_VMMS_DEBUG_WARNING" template="MSWVM_GENERIC_TRACE_TEMPLATE" value="1101" />
2018-01-06 12:08:28, Error                 CSI    C_VMMS_ADMIN" level="win:Warning" message="$(string.MSVM_VMMS_VM_SID_ADD_MAPPING_WARNING_SUMMARY.EventMessage)" symbol="MSVM_VMMS_VM_SID_ADD_MAPPING_WARNING_SUMMARY" template="VMMS_ADMIN_ERROR_MSG3_TEMPLATE" value="10023" />
2018-01-06 12:08:28, Error                 CSI    )" symbol="MSVM_VMMS_VM_VSS_BACKUP_SAVE_FAILED" template="VMMS_VM_ERROR2_TEMPLATE" value="10101" />
2018-01-06 12:08:28, Error                 CSI    U_DISKS" template="VMMS_VM_ERROR0_TEMPLATE" value="10109" />
2018-01-06 12:08:28, Error                 CSI    FILE_RESTORE_LOCATION_ERROR.EventMessage)" symbol="MSVM_VMMS_VM_VSS_SNAPSHOT_CONFIG_FILE_RESTORE_LOCATION_ERROR" template="VMMS_VM_ERROR1_TEMPLATE" value="10117" />
2018-01-06 12:08:28, Error                 CSI    ng.MSVM_VMMS_VM_VSS_VALIDATE_VHD_FILES_RESTORED_WARNING.EventMessage)" symbol="MSVM_VMMS_VM_VSS_VALIDATE_VHD_FILES_RESTORED_WARNING" template="VMMS_VM_ERROR0_TEMPLATE" value="10125" />
2018-01-06 12:08:28, Error                 CSI    _FIXUP_FAILED.EventMessage)" symbol="MSVM_VMMS_VM_VSS_VSV_AND_BIN_FIXUP_FAILED" template="VMMS_VM_ERROR2_TEMPLATE" value="10133" />
2018-01-06 12:08:28, Error                 CSI    RNAL_SNAPSHOTS_ERROR.EventMessage)" symbol="MSVM_VMMS_VM_VSS_REGISTER_EXTERNAL_SNAPSHOTS_ERROR" template="VMMS_VM_ERROR_MSG0_TEMPLATE" value="10141" />
2018-01-06 12:08:28, Error                 CSI    T_IN_WRITER_METADATA" template="VMMS_VM_ERROR2_TEMPLATE" value="10149" />
2018-01-06 12:08:28, Error                 CSI    M_VSS_RESOURCE_POOL_FILES_RESTORED_WARNING" template="VMMS_ADMIN_ERROR0_TEMPLATE" value="10157" />
2018-01-06 12:08:28, Error                 CSI    " message="$(string.MSVM_VMMS_VM_VSS_FIX_AVHD_PARENT_POINTERS_FAILED.EventMessage)" symbol="MSVM_VMMS_VM_VSS_FIX_AVHD_PARENT_POINTERS_FAILED" template="VMMS_VM_ERROR2_TEMPLATE" value="10166" />
2018-01-06 12:08:28, Error                 CSI    MIN" level="win:Error" message="$(string.MSVM_VMMS_VM_RESTORE_FAILED_BECAUSE_OF_UNSUPPORTED_VERSION.EventMessage)" symbol="MSVM_VMMS_VM_RESTORE_FAILED_BECAUSE_OF_UNSUPPORTED_VERSION" template="VMMS_ADMIN_ERROR0_TEMPLATE" value="10174" />
2018-01-06 12:08:28, Error                 CSI     channel="VMC_VMMS_ADMIN" level="win:Error" message="$(string.MSVM_VMMS_VM_VSS_SAVE_METRICS_ERROR.EventMessage)" symbol="MSVM_VMMS_VM_VSS_SAVE_METRICS_ERROR" template="VMMS_VM_ERROR2_TEMPLATE" value="10182" />
2018-01-06 12:08:28, Error                 CSI    ntMessage)" symbol="MSVM_VMMS_VM_VSS_FIX_FILE_SECURITY_INFO_FAILED" template="VMMS_VM_ERROR_MSG0_TEMPLATE" value="10191" />
2018-01-06 12:08:28, Error                 CSI    ALFORMED.EventMessage)" symbol="MSVM_MANIFEST_MALFORMED" template="MSWVM_REPORT_WARNING_TEMPLATE" value="12150" />
2018-01-06 12:08:28, Error                 CSI    level="win:Error" message="$(string.MSSTOR_VHD_NO_NA_SUMMARY.EventMessage)" symbol="MSSTOR_VHD_NO_NA_SUMMARY" template="MSWVM_GENERIC_ERROR_TEMPLATE" value="12281" />
2018-01-06 12:08:28, Error                 CSI    _PRIVATE_KEY_ACCESS_WARNING" template="VMMS_ADMIN_ERROR0_TEMPLATE" value="12504" />
2018-01-06 12:08:28, Error                 CSI    VMMS_ADMIN_ERROR0_TEMPLATE" value="12515" />
2018-01-06 12:08:28, Error                 CSI    in:Error" message="$(string.LISTENER_PORT_SET_PORT_ZERO_ERROR_SUMMARY.EventMessage)" symbol="LISTENER_PORT_SET_PORT_ZERO_ERROR_SUMMARY" template="VMMS_ADMIN_ERROR0_TEMPLATE" value="12543" />
2018-01-06 12:08:28, Error                 CSI    T_INIT_FAILURE_SUMMARY" template="VMMS_ADMIN_ERROR_MSG0_TEMPLATE" value="12551" />
2018-01-06 12:08:28, Error                 CSI    MPLATE" value="12585" />
2018-01-06 12:08:28, Error                 CSI    VM_VDEV_STOR_ATTACHMENT_TYPE_MISMATCH" template="MSWVM_GENERIC_ERROR_TEMPLATE" value="12600" />
2018-01-06 12:08:28, Error                 CSI    " />
2018-01-06 12:08:28, Error                 CSI         <event channel="VMC_VMMS_ADMIN" level="win:Error" message="$(string.MSVM_VDEV_STOR_GET_ATTACHMENT_INFO.EventMessage)" symbol="MSVM_VDEV_STOR_GET_ATTACHMENT_INFO" template="MSWVM_GENERIC_ERROR_TEMPLATE" value="12620" />
2018-01-06 12:08:28, Error                 CSI    3" />
2018-01-06 12:08:28, Error                 CSI    ADMIN" level="win:Error" message="$(string.MSVM_VDEV_MEDIA_CHANGE_ONLINE_STATE_SUMMARY.EventMessage)" symbol="MSVM_VDEV_MEDIA_CHANGE_ONLINE_STATE_SUMMARY" template="MSWVM_GENERIC_ERROR_TEMPLATE" value="12651" />
2018-01-06 12:08:28, Error                 CSI    value="12710" />
2018-01-06 12:08:28, Error                 CSI    SECURE_BOOT_IMAGE_VERIFICATION_FAIL.EventMessage)" symbol="MSVM_VDEV_BIOS_SECURE_BOOT_IMAGE_VERIFICATION_FAIL" template="VMMS_VM_ERROR0_TEMPLATE" value="12727" />
2018-01-06 12:08:28, Error                 CSI    LEGACY_BIOS.EventMessage)" symbol="MSVM_VDEV_BIOS_PAUSE_AFTER_BOOT_FAILURE_CHANGE_LEGACY_BIOS" template="MSWVM_GENERIC_ERROR_TEMPLATE" value="12736" />
2018-01-06 12:08:28, Error                 CSI    EV_ENET_INVALID_SWITCH_PORT_REF.EventMessage)" symbol="MSVM_VDEV_ENET_INVALID_SWITCH_PORT_REF" template="MSWVM_GENERIC_ERROR_TEMPLATE" value="12810" />
2018-01-06 12:08:28, Error                 CSI    OPE_SEARCH_ERROR_SUMMARY.EventMessage)" symbol="MSVM_VMMS_SCOPE_SEARCH_ERROR_SUMMARY" template="VMMS_ADMIN_ERROR_MSG1_TEMPLATE" value="13201" />
2018-01-06 12:08:28, Error                 CSI    sage)" symbol="MSVM_VMMS_REGISTER_SPN_ERROR" template="VMMS_ADMIN_ERROR1_TEMPLATE" value="14050" />
2018-01-06 12:08:28, Error                 CSI    " message="$(string.MSVM_VMMS_VM_TERMINATE_ERROR_SUMMARY.EventMessage)" symbol="MSVM_VMMS_VM_TERMINATE_ERROR_SUMMARY" template="VMMS_ADMIN_ERROR2_TEMPLATE" value="14071" />
2018-01-06 12:08:28, Error                 CSI    
2018-01-06 12:08:28, Error                 CSI    ERROR0_TEMPLATE" value="14101" />
2018-01-06 12:08:28, Error                 CSI    144" />
2018-01-06 12:08:28, Error                 CSI    ROR1_TEMPLATE" value="14159" />
2018-01-06 12:08:28, Error                 CSI    IMPORT_FILE_TOO_LARGE_ERROR_SUMMARY.EventMessage)" symbol="MSVM_VMMS_IMPORT_FILE_TOO_LARGE_ERROR_SUMMARY" template="VMMS_ADMIN_ERROR1_TEMPLATE" value="14171" />
2018-01-06 12:08:28, Error                 CSI    ate="VMMS_VM_ERROR1_TEMPLATE" value="14195" />
2018-01-06 12:08:28, Error                 CSI    ADMIN_ERROR1_TEMPLATE" value="14220" />
2018-01-06 12:08:28, Error                 CSI     message="$(string.MSVM_VMMS_SNAPSHOT_VERSION_UPGRADE_OPERATION_FAILED_SUMMARY.EventMessage)" symbol="MSVM_VMMS_SNAPSHOT_VERSION_UPGRADE_OPERATION_FAILED_SUMMARY" template="VMMS_VM_ERROR2_TEMPLATE" value="14239" />
2018-01-06 12:08:28, Error                 CSI    TEMPLATE" value="14251" />
2018-01-06 12:08:28, Error                 CSI    ="VMC_VMMS_ADMIN" level="win:Error" message="$(string.MSVM_ADMIN_CREATE_IN_ROOT_SCOPE_ERROR_SUMMARY.EventMessage)" symbol="MSVM_ADMIN_CREATE_IN_ROOT_SCOPE_ERROR_SUMMARY" template="VMMS_ADMIN_ERROR1_TEMPLATE" value="14301" />
2018-01-06 12:08:28, Error                 CSI    _DELETE_ERROR_SUMMARY" template="VMMS_VM_ERROR2_TEMPLATE" value="14331" />
2018-01-06 12:08:28, Error                 CSI    ERROR_SUMMARY" template="VMMS_VM_ERROR0_TEMPLATE" value="14351" />
2018-01-06 12:08:28, Error                 CSI    N" level="win:Error" message="$(string.MSVM_PROCESSOR_RESERVATION_OUT_OF_RANGE_ERROR.EventMessage)" symbol="MSVM_PROCESSOR_RESERVATION_OUT_OF_RANGE_ERROR" template="VMMS_VM_ERROR2_TEMPLATE" value="14400" />
2018-01-06 12:08:28, Error                 CSI    ror" message="$(string.MSVM_PROCESSOR_UNKNOWN_POOLID_ERROR.EventMessage)" symbol="MSVM_PROCESSOR_UNKNOWN_POOLID_ERROR" template="VMMS_VM_ERROR1_TEMPLATE" value="14424" />
2018-01-06 12:08:28, Error                 CSI    _PER_SOCKET_WHILE_VM_IS_RUNNING_ERROR_SUMMARY" template="VMMS_VM_ERROR0_TEMPLATE" value="14431" />
2018-01-06 12:08:28, Error                 CSI    _APPLY_PROCESSOR_SETTINGS_FOR_RUNNING_VM_ERROR_SUMMARY.EventMessage)" symbol="MSVM_VMMS_APPLY_PROCESSOR_SETTINGS_FOR_RUNNING_VM_ERROR_SUMMARY" template="VMMS_VM_ERROR1_TEMPLATE" value="14439" />
2018-01-06 12:08:28, Error                 CSI    "VMC_VMMS_ADMIN" level="win:Error" message="$(string.MSVM_VMMS_MODIFY_VM_ERROR.EventMessage)" symbol="MSVM_VMMS_MODIFY_VM_ERROR" template="VMMS_VM_ERROR0_TEMPLATE" value="15030" />
2018-01-06 12:08:28, Error                 CSI    PPLY_VM_SNAPSHOT_ERROR_SUMMARY.EventMessage)" symbol="MSVM_VMMS_APPLY_VM_SNAPSHOT_ERROR_SUMMARY" template="VMMS_VM_ERROR0_TEMPLATE" value="15061" />
2018-01-06 12:08:28, Error                 CSI    essage="$(string.MSVM_VMMS_MODIFY_SERVICE_SETTINGS_ERROR.EventMessage)" symbol="MSVM_VMMS_MODIFY_SERVICE_SETTINGS_ERROR" template="VMMS_ADMIN_ERROR0_TEMPLATE" value="15110" />
2018-01-06 12:08:28, Error                 CSI    ="MSVM_VMMS_SAVE_VM_ERROR_SUMMARY" template="VMMS_VM_ERROR0_TEMPLATE" value="15151" />
2018-01-06 12:08:28, Error                 CSI    Error" message="$(string.MSVM_VMMS_MIGRATE_VM_ERROR_SUMMARY.EventMessage)" symbol="MSVM_VMMS_MIGRATE_VM_ERROR_SUMMARY" template="VMMS_VM_ERROR0_TEMPLATE" value="15201" />
2018-01-06 12:08:28, Error                 CSI     message="$(string.MSVM_VMMS_TASK_TEST_ERROR.EventMessage)" symbol="MSVM_VMMS_TASK_TEST_ERROR" template="VMMS_ADMIN_ERROR0_TEMPLATE" value="15230" />

2018-01-06 12:10:57, Error                 CSI    00000007@2018/1/6:19:10:57.406 (F) CMIADAPTER: Exiting with HRESULT code = E_INVALIDARG.2018-01-06 12:10:57, Error     [0x01802b] CSI    0000008b (F) Failed execution of queue item Installer: Events ({3bb9fd2b-351e-4b9c-b1fc-ed0758805998}) with HRESULT E_INVALIDARG.  Failure will be ignored: The failure was encountered during rollback; installer is reliable (2)[gle=0x80004005]

Any assistance is appreciated.

Darryl

↧

WSUS-Clients not seen by server

September 26, 2018, 12:36 pm
$
0
0

This is on Windows server essentials 2016.  

Server has Anywhere Access and WSUS installed and configured (along with DC...)

WSUS repository on second drive and Update Services installed on c:  

Using GP to push down update policy to computers.

I have verified that GP is making changes on clients using rsop.  I have made several changes in see changes show up in the rsop viewer.

WSUS synchronizes with MS and updates are available.  

I have tried to connect to WebServices/ClientWebServices/Client.asmx to test for connectivity via http://FQDN server:8530/WebServices/Client.asmx but it fails   (times out waiting for response).  

I can navigate from client in run using \\fqdn server\Update Services\WebServices and can navigate into ClientWebService and copy the client.asmx and paste it to the client's local directory.  This tells me I have permissions to get there.

The issue seems to be that the http path is not being handle by IIS.  I am assuming this since the intranet setting in GP for Windows updates uses the http:\\ for the server and status server.  I can't find where that is in the config.  

Is it a conflict with Anywhere Access?  I am really stuck on this.  Help....

↧
↧

Windows Server 2016 WSUS all client trough GPO show "not yet reported"

September 26, 2018, 8:43 pm
$
0
0

Hi,

I have fresh WSUS WS 2016. when I first install WSUS detected computer in group "all computer" with the status.

but, when I apply GPO from WSUS, I found all computer status show "not yet reported"

I already clean up the WSUS server wizard, bit seems no result

please help

Thanks

Regards

↧

Windows 10 Updates are "Not Applicable" for versions 1607, 1703, 1709

September 26, 2018, 10:50 pm
$
0
0

Hello,

we currently got an issue with our WSUS. All updates (e.g. Cumulative Updates) for clients with the Windows 10 versions 1607, 1703 and 1709 are showing the state "Not Applicable" in the client statistics.

I've read in different forum contributions that a Group Policy could cause this issue. There we've configured the following policy:

Computer Configuration > Policies > Administrative Templates > Windows Components > Windows Update > Windows Update for Business >Select when Preview Builds and Feature Updates are received to Semi-Annual Channel (Targeted) and we defer Feature Updates for 365 days.

In the Screenshot you can see the other Windows Update policies we configured.

We've already tried to install a new WSUS Server without success. The only solution I currently got is to upgrade to 1803. Could you please help me with that issue?

Thanks!

Kai


↧
Search

WSUS - Email server logon details disabled

September 20, 2018, 10:47 pm
$
0
0

Hello guys, i am unable to change the email-server logon information. Please see below.

Any ideas why it's grayed out?

Thanks for any help.

Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

↧

WSUS choose products

September 27, 2018, 1:49 am
$
0
0

Hello,

I want to build a WSUS server in our company, but I have a problem, I don't know all microsoft products in our company !!

How can I make sure that I have selecte all our prodects ????

Do you have any tools for making sure that I need to selecte in Wsus ???

Can I use a tool to scan a PC or a Server to know which WSUS products I should select in WSUS parameters?

Thanks


↧
↧

Best practices for approving updates

September 27, 2018, 2:48 am
$
0
0
Hello,

I just got a mail from our ERP service provider that we should distribute the update KB4458469 for our Windows 10 (1803) computers.

We are using a WSUS for distributing Windows updates which has been working well the last months.

I have configured it so that it does not release updates automatically. I chose this way because I noticed that if you activated many products and classifications you would need a lot of disk space with automatic release of updates. That's why I connected to the server every Monday and released all necessary updates.

The strange thing is that the update KB4458469 never appeared in the list of "not approved/erroneous or required". This is also the reason why I didn't release the update. Now I wonder if it makes sense to go this way at all, or is it better to release the updates automatically?

Yours sincerely
Andrew

↧

4 - Auto download and schedule the install group policy not working as expected?

September 27, 2018, 4:22 am
$
0
0

Hi All,

We have servers where "4 - Auto download and schedule the install" group policy is configured as below "No auto-restart for scheduled Automatic Update installations" sub policy enabled. Now as per the policy I understand that the system will try to download and install windows update at 3:00 AM "local time" everyday. 

Now we observed that even if we are pushing the update at 8:00 AM from WSUS, the client systems are immediately downloading and installing the updates and rebooting themselves (if users are not logged in) and not waiting for next day 3:00 AM to arrive.

This seems to be an abnormal behavior. Or am I missing something in understanding?



↧

WSUS 3.0 server reporting not applicable for all updates for 2016 servers

September 10, 2018, 2:07 pm
$
0
0

WSUS 3.0 server reporting updates are not applicable for 2016 servers although patches have been downloaded and installed on 2016 servers.

Windows 2016 WindowsUpdate.log server log shows many of the below errors.

1600/12/31 16:00:00.0000000 336   4360   Unknown( 20): GUID=aa07f95d-91be-3f47-51b3-717e4c7ddc98 (No Format Information found).

Other log information is available as seen below.

2018/09/10 11:01:34.7825710 336   3776  Agent           Windows Update access disabled: No
2018/09/10 11:01:34.7884881 336   3776  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2018-09-10 22:19:19, not idle-only, not network-only
2018/09/10 11:01:34.9205997 336   4612  Shared          UpdateNetworkState Ipv6, cNetworkInterfaces = 0.
2018/09/10 11:01:34.9206100 336   4612  Shared          UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2018/09/10 11:01:34.9206200 336   4612  Shared          Power status changed
2018/09/10 11:01:34.9358876 336   3776  Agent           Initializing Windows Update Agent
2018/09/10 11:01:34.9373960 336   3776  DownloadManager Download manager restoring 0 downloads
2018/09/10 11:01:34.9398053 336   3776  Agent           CPersistentTimeoutScheduler | GetTimer, returned hr = 0x00000000
2018/09/10 11:01:37.4730121 336   1592  DownloadManager PurgeExpiredFiles::Found 3 expired files to delete.
2018/09/10 11:01:37.4730293 336   1592  DownloadManager PurgeExpiredFiles::Deleting expired file at C:\Windows\SoftwareDistribution\Download\bd0d73364bf854970f570a2cf51388b435720e6d.
2018/09/10 11:01:37.4776616 336   1592  DownloadManager PurgeExpiredFiles::Deleting expired file at C:\Windows\SoftwareDistribution\Download\48174db2b72cce60c7969dc197020c8ca58c9045.
2018/09/10 11:01:37.4831928 336   1592  DownloadManager PurgeExpiredFiles::Deleting expired file at C:\Windows\SoftwareDistribution\Download\9dcadf092f9e4cca339b5f98a160086902733280.
2018/09/10 11:01:37.5496229 336   1592  DownloadManager PurgeExpiredUpdates::Found 374 non expired updates.
2018/09/10 11:01:37.6491746 336   1592  DownloadManager PurgeExpiredUpdates::Found 3 expired updates.
2018/09/10 11:01:37.7071502 336   1592  DownloadManager PurgeContentForPatchUpdate::Deleting update content at C:\Windows\SoftwareDistribution\Download\898f9fe4b16d1628e7699c9bf1d04700.
2018/09/10 11:01:37.7330569 336   1592  Shared          Effective power state: AC
2018/09/10 11:01:37.7330597 336   1592  DownloadManager Power state change detected. Source now: AC
2018/09/10 11:12:41.8143733 336   3772  Agent           Earliest future timer found:
2018/09/10 11:12:41.8143912 336   3772  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2018-09-10 22:19:19, not idle-only, not network-only
2018/09/10 11:12:42.8306986 336   4612  Agent           Earliest future timer found:
2018/09/10 11:12:42.8307130 336   4612  Agent               Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2018-09-10 22:19:19, not idle-only, not network-only
2018/09/10 11:12:42.8343566 336   4612  Misc            CreateSessionStateChangeTrigger, TYPE:2, Enable:No
2018/09/10 11:12:42.8343620 336   4612  Misc            CreateSessionStateChangeTrigger, TYPE:4, Enable:No
2018/09/10 11:12:42.8776383 336   4612  Handler         CUHCbsHandler::CancelDownloadRequest called
2018/09/10 11:12:42.9330548 336   4612  Shared          * END * Service exit Exit code = 0x240001

An attempt was made to use the Microsoft's public symbol server with no success.

https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/microsoft-public-symbols

This is consistent throughout the Windows 2016 platform. Windows 2008 ad 2012 systems report correctly.

↧
Viewing all 12874 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>