I am thinking of putting Windows Server 2022 Essentials on the machine
that acts as a server here and setting up a domain so my PCs can join it.
Objective is to have absolute control over when and how updates are
applied so I can run them centrally when it suits me.
Anybody actually doing this who can point out the pitfalls please?
I forgot to run my "NoShutdown" app and last night MSFT decided to
re-boot my main PC.
I am thinking of putting Windows Server 2022 Essentials on the machine
that acts as a server here and setting up a domain so my PCs can join it.
Objective is to have absolute control over when and how updates are
applied so I can run them centrally when it suits me.
Anybody actually doing this who can point out the pitfalls please? I
have unused MSDN keys for various flavours of Server 2003 but that's
probably a bit ancient even for me!
Happy to read online articles but haven't found any useful ones yet...
Jeff Gaines wrote:
I am thinking of putting Windows Server 2022 Essentials on the machine
that acts as a server here and setting up a domain so my PCs can join it.
Objective is to have absolute control over when and how updates are
applied so I can run them centrally when it suits me.
Anybody actually doing this who can point out the pitfalls please?
I have yet to install a server2022 with wsus, so can't say if it's any >different from the past ... but you should be able to control them
On 10/07/2024 13:12, Jeff Gaines wrote:
I forgot to run my "NoShutdown" app and last night MSFT decided to >>re-boot my main PC.
I am thinking of putting Windows Server 2022 Essentials on the machine
that acts as a server here and setting up a domain so my PCs can join it.
Objective is to have absolute control over when and how updates are
applied so I can run them centrally when it suits me.
Anybody actually doing this who can point out the pitfalls please? I have >>unused MSDN keys for various flavours of Server 2003 but that's probably
a bit ancient even for me!
Happy to read online articles but haven't found any useful ones yet...
I do this, but it's my day job so am familiar with the tools, and it helps >with personal training for someone in employment as such.
Looking after a WSUS service instance and getting clients to talk to it,
will drive you mad. WSUS is a crap MS product with bugs. IMHO Completely
over the top solution for taming Windows Update on a single client, but
that is Microsoft for ya.
But anyway, for Active Directory to work you will have to have the server >looking after DNS, and then worry about DNS provision for your network
when the server is down. So you will be deep in networks theory.
I have multiple domain controllers, some virtualised for high
availability. You will need something for Server backup, and then worry
about tombstone lifetime. And apart from Microsoft defender, there are no >cheap anti-malware suites available.
This is "home lab" territory and there is PLENTY of online articles and >videos out there. You can also ask chat-gpt for specifics instead of
reading a lot of guff.
I forgot to run my "NoShutdown" app and last night MSFT decided to
re-boot my main PC.
I am thinking of putting Windows Server 2022 Essentials on the machine
that acts as a server here and setting up a domain so my PCs can join it.
I forgot to run my "NoShutdown" app and last night MSFT decided to
re-boot my main PC.
I am thinking of putting Windows Server 2022 Essentials on the machine
that acts as a server here and setting up a domain so my PCs can join it.
Objective is to have absolute control over when and how updates are
applied so I can run them centrally when it suits me.
I would suggest instead:
On 10/07/2024 in message <lf7lp2Fth7U1@mid.individual.net> Jaimie
Vandenbergh wrote:
I would suggest instead:
[snipped]
I am not changing OS at my age, I have far too much invested in Windows!
I have a Linux box (HP N54L) that just runs Braserio and a Mac Mini M1
that my Re.Corder connects to - because it is much better for music than Windows.
I spend 99% of my time programming in Visual Studio, something I have thoroughly enjoyed since my Vic 20, and there is nothing that good for
any other OS.
I did try XCode when I had a Mac Pro but its logic and
mine were somewhat different. Whatever MSFT says the Windows API hasn't changed since forever and apps I wrote for Win 98 using the API all work perfectly on Win 10.
There is a 180 day trial of Server 2022 and of Windows 11 IoT Enterprise
LTSC (thanks Theo!) and I will give them both a try on a spare machine.
I forgot to run my "NoShutdown" app and last night MSFT decided to
re-boot my main PC.
On 10/07/2024 in message <xn0oo5jfhi3yjo003@news.individual.net> Jeff
Gaines wrote:
I forgot to run my "NoShutdown" app and last night MSFT decided to
re-boot my main PC.
Just to say Server 2022 demo went on my HP Z230 sweet as a nut, much easier/quicker than a Win 10 install. Once installed the windows that
pop up are just wire frames so very difficult to tell one from another.
It runs fine but as some people said setting up a domain controller is
an exercise in frustration and it struck me part way through that my
laptops have Win 10 Home, only my desktops have Pro so the laptops
couldn't join a domain anyway.
I've called halt for now and put Win 8.1 on, running fine, asked me for
the computer name during install and updates are set to download and ask
when to install. Such simple differences, no idea why they aren't in 10, perhaps the programmers are bored and looking for things to do?
Many thanks for all the input :-)
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 415 |
Nodes: | 16 (2 / 14) |
Uptime: | 22:10:54 |
Calls: | 8,717 |
Calls today: | 6 |
Files: | 13,273 |
Messages: | 5,954,786 |