We are installing a brand new Server 2019 as WSUS server. Most of our clients computershave been deployed with Windows 10 Pro (Build 10.0.18362.30). But occasionally there are 1803, 1809 and 1903 computers connecting too, needing to be offered full upgrades to 1909. All are Windows 10 Pro, no S or LTS editions...
A freshly installed WSUS server come with ALL windows versions and editions checked. Even with only the different Win 10 versions and editions checked the WSUS filestore will grow to more that 500+ gigabyte. So, in our case we need both current
updates AND upgrades from 1803, 1903, 1909 and later, which product(s) do we actually select? Logically I would think that the product 'Windows 10 Version 1803 and later Upgrade & Servicing drivers' would do for ALL future updates AND upgrades,
but that was not the case. And I have read in this forum that it is not a good idea to have WSUS install drivers for Win10.
So please help me which WSUS product checkboxes we need to check to properly maintain and upgrade ONLY Windows 10 Pro from 1803 and all future versions…?
Our first Windows 2016 servers are reporting to the WSUS 4.0 server as Windows 10 OS. Is there an issue here or will the server get the correct patches? We will be migrating to SCCM servers in the near future but for now the Windows 2016 server
will need to be patched. Is there a fix available for correct OS identification?
I am trying to upgrade my computer from windows 7 to windows 10. It comes up saying that it needs my attention that i need to uninstall Microsoft Office 2010 Starter. I have looked at my programs and files and there is no Microsoft Office 2010 on this
computer. I have Microsoft Office 2013 installed not 2010. This is my Business computer I want to keep my files and programs on the computer if possible. What do I need to do to be able to upgrade?
We are going to install WSUS server on new Windows Server 2012 R2 server and want to Import Groups and Approvals from existing server. After the command "WsusMigrationExport.exe groupsandapprovals.xml" below error is displayed. Please guide to
get out of it;
We have an AD OU and WSUS group policy at our office running Win10 ver 1803, we have a WSUS group policy and have not approved running a newer Windows version yet beyond 1803.
Our company purchased some new laptops that have Win10 ver 1903 pre installed.
I am afraid if I put the newer laptops that have Win10 ver 1903 pre installed in the same OU as our other WSUS pc's that only have version 1803 approved a rollback might happen or it could do something bad to the OS?
Can someone guide me here with a recommendation or best practices for this situation? I'm not sure we are ready to move everyone to version 1903 just yet.
Wondered if someone could explain to me how WSUS works in terms of 2008 ESU.
I understand any 2008 boxes needs a new product key, but how does WSUS work in terms of pulling down the updates? Will it continue to pull down 2008 updates as normal and any machine licensed for ESU will be the only ones that actually pull down t he updates?
Just wondered if there was anything special we needed to do with WSUS??
We had to create a new WSUS Server due to the old one being decommissioned.
I created and configured the server exactly as the original settings, it is a replica downstream to our main WSUS server at our local HQ office. I had to amend one of the GPO's (Specify intranet Microsoft update service location) to point to the new
server name. All other GPO's such as Client Side Targeting etc remain the same.
The issues I am facing are
Unable to see any Servers or Client machines.
WSUS folder is created but there does not appear to be any data in folder.
On the To Do list it states "Your WUS server currently shows that no computers are registered to receive updates."
The synchronization completes successfully. I see the updates in WSUS Services Manager but I don't see the content on the reserved HDD D:\. The folders have been created but there are no content, which I find very strange.
Please could someone help and offer advice of how I go about resolving this problem. Much appreciated for your support.
I setup a new WSUS Server in my network. It's a Windows Server 2016 (Build 10.0.14393) with SSL setup (default ports 8530 / 8531). I have some Windows 10 clients, these are pulling updates and report to the WSUS without problems.
The other 2016 Servers are partly recognised as "Windows (Version 10.0)", some as "Windows Server 2016 Standard", but all have the problem 0x8024401c
I've just spun up a new WSUS server (10.0.17763.134) on Windows Server 2019 Standard. Upon initial startup of the WSUS admin console I'm unable to synchronize, the progress bar moves along and eventually times out. I've contacted our Network Admin who has
reviewed our firewall logs and determined there is two-way communication between the server and Microsoft's Update server. I've also ruled out the Windows Firewall and AV software.
It's been a few years since the last time I installed the WSUS role, any help is appreciated.
I'm running a WSUS on a Server 2012r2 current WSUS version 6.3.9600.18838 I have a number of Windows 10 systems that report to the server that are current at build 18363.535 but the WSUS shows them as being at build 18362.449 The 2012R2 server
is up to date on all it's patches. The systems are checking in with the WSUS on a regular basis it's just that the current build isn't being shown on the WSUS. The WSUS knows that the patch KB4530684 which I believe corresponds to that build number
has been installed by the clients. That was verified by doing a report from the WSUS.
Any ideas as to why the WSUS is reporting the incorrect version and what steps are required to fix this issue. Is this something that will be resolved in the next patch for the server?
I'm running a WSUS on a Server 2012r2 current WSUS version 6.3.9600.18838 I have a number of Windows 10 systems that report to the server that are current at build 18363.535 but the WSUS shows them as being at build 18362.449 The 2012R2 server
is up to date on all it's patches. The systems are checking in with the WSUS on a regular basis it's just that the current build isn't being shown on the WSUS. The WSUS knows that the patch KB4530684 which I believe corresponds to that build number
has been installed by the clients. That was verified by doing a report from the WSUS.
Any ideas as to why the WSUS is reporting the incorrect version and what steps are required to fix this issue. Is this something that will be resolved in the next patch for the server?
I have WSUS on Windows server 2019. I am configuring the GPO to enable auto updates. I want the auto install is scheduled to happen at 2:00 AM on the second Thursday each month. Is below the right place to configure it? What could cause the issue that I
couldn't select option 4? After I select option 4 and save the change. It will change to option 2 when I come back. Image may be NSFW. Clik here to view.
I am working in a small shop and my boss would like to apply WSUS to apply Windows Updates on Servers.
May I ask how Windows Update is performed ? Will any precaution be taken before the update ? Like Taking snapshot for VMware VM or Full Backup of Physical Servers ? What if the Server doesn't work properly after the Update ?
How frequent Windows Update be applied ? Monthly / Quarterly or Half Yearly ? When the update be applied ? Friday night should be good but there is Batch Job Run and SQL Server Backup. Is there any rule of thumb to estimate
how long it takes for Update ?
Will all security updates are applied or only selected ones ? How can we identify which update should not be applied ? Will Windows Update be applied to all Servers in one go Or by Group ? Is
there any sequence to apply Patches like Apply to Domain Controller and then Application Servers ?
I have a new WSUS server installed (our only one). Although all workstations seem to be connecting to this server, they all are listed as "not yet reported." This has been sitting over the past 2 weeks in the same state. I have turned my
firewall off on the wsus server to ensure connectivity, although the fact that machines are listed in the WSUS console should mean they can communicate.
When I go to any workstation, I get windows update errors stating that they can't connect to the update server.