Windows Server 2022: Install, Configure, and Deploy Windows Server Update Services (WSUS)
ฝัง
- เผยแพร่เมื่อ 30 มิ.ย. 2024
- See More for more information and the blog post! Skip to 2:00 to get right to the instructions!
Blog Post: www.stephenwagner.com/2021/09...
Skip to 2:00 to get right to the instructions!
Check out my full Windows Server 2022 playlist at • Windows Server 2022: H...
In this video I show you how to install, configure, and deploy Windows Server Update Services (WSUS) on a Windows Server 2022 Server.
In this guide, I cover:
-Server Manager
--Windows Server Update Services Role Installation
-WSUS Considerations and Requirements
--WID (Windows Internal Database)
--SQL Express
--GPO Group Policy Objects
--WSUS Maintenance
--Upstream and Downstream WSUS Servers
--Bandwidth Optimization
-WSUS Usage and Platform
--WSUS Infrastructure Design
--WSUS Synchronization Schedule
--WSUS Language, Products, and Classifications selections
--WSUS MMC Overview
--"gpupdate /force" usage
--WSUS Update Approval
--WSUS Reporting
This video is part of a multi-video playlist containing howto's on deploying various technologies with Microsoft Windows Server 2022.
Hardware/Software used in this demonstration
-VMware vSphere
-HPE DL360p Gen8 Server
-Microsoft Windows Server 2022
-pfSense Firewall
For more content visit my blogs at www.stephenwagner.com
To hire me and my company, visit:
www.stephenwagner.com/hire-st...
www.digitallyaccurate.com/con...
#Windows #WindowsServer #WindowsServer2022 #WSUS #WindowsServiceUpdateServices #Guide #HowTo #VMware #ESXi #VirtualMachine #Demo #Demonstration
Hey man. I know these videos take time. Thank you for the post. I had a couple random questions since I am migrating my WSUS to a new VM and its been forever since I installed the service. Thank you for laying out the whole process. I appreciate it.
Thanks for this video. This really helped in setting up WSUS in my lab.
Thankyou for making this elaborately explained long video on the WSUS topic. Its much better than all the short videos out there on the subject.
Glad it was helpful!!!
Thank you so very much for making these videos. Finally someone who explains process's well and I can understand the person speaking. Very helpful.
Glad it was helpful and I appreciate the feedback! :)
Thank you for creating this content. This helps a lot!
Happy that it helps! 🙂
Great tutorial, easy to follow and understand! Keep up the good work.
Great video. Just for reference, the WSUS changed to "Configuration successfully completed" around 13:00.
Thank you so much! Excellent video.
Tech support specialist here; amazing video! Will be using this to implement WSUS at work!
Glad it helped!
Thank you for detailed tutorial.
You are welcome!
you are very good thanks for this tutorial.
You're certainly welcome! Glad it helped!
Great Videos keep up the good work
Thanks, will do! I appreciate the feedback!
thank you, pura vida!!
Well done.
thanks for the information.
Glad it helped!
Great tutorial! Thank you very much. It was super clear and straightforward even for junior admins like me, who are installing the WSUS for the first time. I like your comments about two WSUS in A-vpn-B or about what yours servers should doing about 3 am :) I'm first time on this channel, so you definitely encourage me to check your others videos ;)
Thanks Scynk, I really appreciate feedback like this! Thank you so much and I'm happy if the videos are of help! :)
Big Like
Big thanks! :D
Awesome tutorial! Thanks for investing your time in creating this educative piece of work. My question quickly is this: how do you exempt the domain controller from automatically installing the updates as you mentioned that it is not safe to allow the server to run updates automatically? I noticed in this video, that you approved updates for the domain controller.
Hi Johnson, thanks for the feedback! As for your question, you should have different OUs (Organizational Units) for different computer objects. You always leave your domain controllers in the domain controllers OU (don't touch this), and your computers should be in the "Computers" OU. When you create GPOs, you should only link them to the OUs you want them to have effect on.
So, with that being said, you can have both your DCs and Computers use your WSUS configuration GPO (which only specifies the WSUS server address), but then you'd want different GPOs for automatic updates. In most cases you'd have a GPO configured for automatic updates attached to Computers (or a custom OU you create), and then for your Domain Controllers, you'd leave it, or configure a GPO that disables automatic updates.
I prefer WSUS to SCCM when it comes to patching servers. WSUS old school but the best
This is a great video. thank you. Can you please assist with a question? I would like to know, for example, if in error you approve a Server 2016 update and deploy it to Server 2019 group in error, would this update be attempted to install on these 2019 servers? Also is there a way to schedule restarts via WSUS, because I would not like the servers to restart randomly after the updates are installed.
Hi Navin, thank you! And that's a great question! You should look at WSUS as an approval and caching mechanism, as it doesn't actually control Windows Updates on the servers, it only approves and makes the updates available. As far as controlling the behavior of Windows Updates on computers and servers, this is all done via GPO.
On the GPOs you can specify things like to only download, download and install, etc, and you can also configure scheduled maintenance windows to install the updates. For example, in my environment, I confiugred the GPOs to only download the updates, as I would prefer to install them manually when I do updates every couple weeks.
Hope this helps!
@@StephenWagner Thank you very much for the reply and great info!
nice treadmill.
Thanks! :D
Hi! Thanks for the video! One question. When you update all your computers using WSUS your main panel is telling you that there are no pending updates. Seems okay. But then, on the top of the panel I noticed "2151 security updates are waiting for approval", "950 critical updates..." and so on. About what approval is it talking about? As we saw on you video, your virtual machines didn't want new upgrades at all.
Hi ivor, I generally never pay attention to that list. Those are the updates pending approval that include updates that do not apply to your environment. I recommend only paying attention to the update list that by default only shows updates that are required and pending approval.
Good video! I have configured and set up WSUS and it is working except for home users connecting via VPN. When I look at the computer in WSUS it shows the IP address of our firewall instead of the computer. If I ping the computer from the WSUS server it resolves the correct IP. So the WSUS server knows the correct IP of the computer. It's just that WSUS itself doesn't know the correct IP. I also can ping the server from the computer. The VPN computers are also not reporting to WSUS and I'm assuming that it is because of the IP issue. Any thoughts? Thanks!
Hi CryptoChristian, What type of VPN are you using and how do you have it configured? Technically this type of config should work fine. I've completed many deployments where systems either VPN in, or they connect via Site-to-Site VPNs.
Hi. How uninstalling Windows Server 2022 as a Virtual Machine is done?
Can we deploy the updates to Byos laptops as well,those are having the Windows 10/11 home editions through WSUS?
To be honest I'm not too sure if the home editions support using WSUS servers. You'd have to test.
hi bro, i just follow up all of the steps, also the sync finished. but at my computers section, the only computers that are showing is the DC and the wsus itself, any idea of what i might be missing?
Hey Homero, it sounds like those two computers are the only ones that received the group policy updates. Are the rest of your systems domain joined? And is the policy applying to other systems? Also, did you give it time for them to run through the invisible first time processes?
@@StephenWagner It was a problem with the firewall, now everything showed up. thanks a lot!!
W00t! Glad to hear!
I have configured WSUS and it is working perfectly. But I have an issue with it as soon as I click check for updates, it automatically downloads and installs the update and restarts the system. Same thing was also seen at the time 49:50 of this video. How to get rid of auto install and restarts
Hey there and thanks for the comment! 🙂 You'll need to configure another GPO for your OUs to control whether they install or just download. Usually on servers you can configure it to download (This way it waits for an admin to initiate the install), and on workstations you can have it auto install.
I had recently bought the "HPE ProLiant MicroServer Gen10 Plus v2" and would like to run Windows Server 2022 Essentials, however MS no longer provides the iso for this and I was wondering if anyone knows how to obtain this? What makes this worse is the Microserver that I have does NOT come with an optical drive. Any help is appreciated.
Hello, I believe the "Essential Experience" is now a Windows Server Feature and Role that you install after you install the operating system.
Can you provide cleanup procedure for WSUS Server 2022. I have assign 300 GB for WSUS download Destination drive, but it is full with in 2 days.
If you need more space, I would recommend moving the WSUS data to another drive/volume. There's a process and workflow to do this.
@@StephenWagner, Thanks for your valuable reply kindly share the process or workflow details if you have them. thanks ones again.
is it best practice to create a separate server for wsus or can it be in the DC?
Never install WSUS on a DC. It should be on it's own server, or a server that you verify can house multiple services.
@@StephenWagner if you were starting fresh in IT now, what skills would you focus on?
@mrmuffin5046, starting fresh, I'd say: VMware vSphere, VMware Horizon, Networking, and cloud integrations (Azure AD/Entra ID, etc)! :)
A help, I have Windows server 2022 with 5 remote RDP users, in some situations where when logging on the black screen, without any action. In the client I already disabled the bitmap, and one detail, this black screen has already happened when I try to log in with the user administrator. Has anyone ever experienced this? Thanks
Hi Anderson, I've never seen this before. Is there a chance that a 3rd party application is causing this? Additionally, were all the applications installed properly using install mode on the RDS Server?
I hate this guy. Handsome, fit, good hair, Wagner as surname....oh my god. GIGACHAD!
Gigachad loves the support! 😁😂
Not really sure why you said not to let MSFT send improvement information - "thank you very much". I understand if you are worried about people spying on your data but it seems safe and helps with improving products. I will do it on companies I trust and MSFT and Nvidia come to mind.
I understand what you're saying and it's a valid point. But you know how it goes, IT people always crack jokes about EULAs as well as sending diagnostic information. And on a serious note, I just don't like software transmitting information from my network, especially when monitoring outbound traffic not knowing what something is.
Hi, I am facing fatal error in post configuration step. Could you help?
Hi Naruto, does it say anything else other than fatal error?
@@StephenWagner After that I tried removing and re installing the role but now it's not producing any temp file for the event and just giving fatal error, if you can share your mail, I'll send the screenshot of it
Hi Naruto, if you uninstalled the role, there's a chance the old database is still present. You'll have to clear the WSUS database and reinitialize it to restart the configuration of the role.
@@StephenWagner I used the WID instead of SQL DB, but as I can see some other processes are also using WID.. But my AD is not installed in this server fyi
What helped me is removing the 'WSUS Administration' website in IIS manager and restart the post configuration. After that, the post configuration was completed succesfully.
Pro Tip - open start menu and just type wsus....
Amen to that buddy! lol I'm still surprised when I see people use the Start Menu to find applications. You just need 2 clicks and maybe the first 3-4 letters. :) Thanks for leaving the tip for the viewers!