Basically AD and the workstation management that uses it. Could all be run on a VM and snapshotted because you know it’s going to fuck up an update eventually. Perhaps SQL Server but that’s getting harder to justify the expense of anymore.
We run a lot of Windows servers for specialized applications that don’t really have viable alternatives. It sucks, but it’s the same reason we use Windows clients.
A bunch of enterprise services are Windows only. Also Active Directory is by far the best and easiest way to manage users and computers in an org filled with a bunch of end users on Windows desktops. Not to mention the metric shitload of legacy internal asp applications…
I guess not actually but the amount of weird bugs I got from running a working script makes me think there’s something wrong with the way we have ours set up.
I’m truly, totally, completely shocked … that Windows is still being used on the server side.
Basically AD and the workstation management that uses it. Could all be run on a VM and snapshotted because you know it’s going to fuck up an update eventually. Perhaps SQL Server but that’s getting harder to justify the expense of anymore.
We run a lot of Windows servers for specialized applications that don’t really have viable alternatives. It sucks, but it’s the same reason we use Windows clients.
A bunch of enterprise services are Windows only. Also Active Directory is by far the best and easiest way to manage users and computers in an org filled with a bunch of end users on Windows desktops. Not to mention the metric shitload of legacy internal asp applications…
Yeah at work we do a lot of internal microsoft asp stuff, poweshell, AD, ms access, all that old legacy ms stuff
Is powershell “legacy”?
Windows Powershell sort of is legacy, but Powershell 7 definitely isn’t
I guess not actually but the amount of weird bugs I got from running a working script makes me think there’s something wrong with the way we have ours set up.