Re: What Is Windows Server 2022 Cal
Oleta Blaylock
Heya folks, Ned here again. Today I clear up an old idiosyncrasy of Windows Server: if the SMB Server service is always installed, why is there a role called "File Server" and what does enabling it do?
The SMB Server service - "Server", aka "Lanmanserver" - always exists in Windows and isn't something you install; it's just there, as soon as you install the OS. However, since Windows XP and Windows Server 2003, that service can't be contacted from remote machines by default because the built-in firewall blocks it. SMB needs, at a minimum, TCP/445 inbound and without that port opening, there is no remote file serving in SMB2+ on any supported versions of Windows. Even though the C$ and ADMIN$ built-in shares exist by default, no one can access them from a remote machine by default.
But you probably don't remember opening a firewall port on your file server, right? You created a share and it just worked. That's because as soon as you create a custom SMB share, SMB Server automatically enable the various SMB firewall rules for file servers for access, administration, applications, etc. Watch:
That works well for dedicated file servers - as soon as you add a share, everything is taken care of. But we also needed a way to just enable file server administration and grant administrators access to the built-in system shares C$ and Admin$ using SMB2+ on all Windows Servers. We didn't want them to have to create a share just to access some existing built-in shares. And we didn't want them to dig around in the firewall looking for the right rules to enable for management. So when you "install" the file server role, we just enable the basic ports needs for file server administration and accessing those built-in SMB shares; no legacy stuff or historical app compat, just the very basic. In fact, it's very possible the server is not a "file server", so much as one you just want to copy a few files to or from as an administrator.
So now you know. I'm thinking about changing the default firewall rules opened by creating a share as they are a legacy from older times; we'd do this in the Windows Insider builds first and see how many tens of thousands of applications I can break that were piggybacking on those. It's going to take awhile. >_
I have a question because I want to use ws22 (Windows Server 2022) on my ml350p gen 8. I have installed Windows Server 2019 just fine, but I did not want to mess up my semi-working computer. I know there is a TPM 2.0 requirement and a secure boot requirement, and I know I can bypass it, but will windows still work?
Although it is not tested, 2019 is tested even if not listed on the ml350p gen eight drivers because the GPU driver can do 2019 (a separate link, might I add) and is supported is ml350p gen 8 for windows 2019. There are many more drivers like this, iLO 4 drivers are out of date on the ml350p gen 8-page, but on the iLO 4 page, it has 2019. Wow. And ml350 gen nine still is "Only 2016" welp that needs a highly great explanation.
I thought people should know that they do not have to spend lots of money for a gen ten just for windows server 2022 or 2019. Driver support is also crap on GPUs with 2016 and sometimes 2019.
I did not need to do any special tweaks to get a windows server 2022 installer working. Now this may not work in the future as the Vnext builds are the Windows 11 "Feel", which requires a TPM and secure boot, but windows server 2022 or the vnext don't require it at the moment.
My only guess on WHY it would show UEFI in the config is that Belarc Advisor assumes if you have a build higher than 19045 you have Windows 11 and have UEFI? You *cannot* have UEFI on an ML350P Gen 8. You can have a TPM 1.2, which would allow for BitLocker but that's it.
In my org we are using Docker Window - on Windows Server 2019 OS.
Its implementation where our web app client runs in isolation in multiple windows container and server present outside docker and connected with every container 1:1.
My question is till Docker version 4.21.1 I am able to install docker on Windows server 2019 OS.
But now latest version of docker 4.25 + seems not able to install on Windows server 2019 OS.
Due to this I am not able to update latest Docker windows on our Windows server 2019 OS.
Is support completely removed for Windows server 2019 in new release ?
If so then why ?
If someone want to use Docker on Windows server OS then which would be right version of Windows server OS ?