Windows 10: 2 digit year configuration in Windows Server 2019

Hello,I am trying to change the 2 digit year configuration in a Windows Server 2019.All articles I have found show the "Control Panel" solution see https://stackoverflow.com/questions/58508724/parsing-12-25-35-to-a-date-using-invariantculture-2-digit-year, which I have tried and only applies to the current user.Since this is required for a IIS application running on a service user with no logon access I need to set it up for all users.Is there a way of doing so? Registry Key?I am aware that for at versions of Windows this value is updated to 2049. That should be enough for me, but I could

:)

 

Office 2019

Only supported on Win10. Sorry, 8.1 users, only 4 years old, gotta go.

Microsoft Office 2019 will only work on Windows 10

https://blogs.technet.microsoft.com...-to-office-and-windows-servicing-and-support/

Spoiler Office 2019
Last year at Ignite, we announced Office 2019 – the next perpetual version of Office that includes apps (including Word, Excel, PowerPoint, and Outlook, and Skype for Business) and servers (including Exchange, SharePoint, and Skype for Business). Today we’re pleased to share the following updates:

• Office 2019 will ship in H2 of 2018. Previews of the new apps and servers will start shipping in the second quarter of 2018.
• Office 2019 apps will be supported on:
  • Any supported Windows 10 SAC release
  • Windows 10 Enterprise LTSC 2018
  • The next LTSC release of Windows Server
• The Office 2019 client apps will be released with Click-to-Run installation technology only. We will not provide MSI as a deployment methodology for Office 2019 clients. We will continue to provide MSI for Office Server products.

 

Managing Server 2019 clustering

SQL Server 2019 Always-on implemented on 2 Nodes on Windows Server 2022 and when i perform manual failover to the second node I got this warning "the current wsfc cluster quorum vote configuration is not recommended for this availability group", and the Always-on availability group is healthy and no problem with it.

i tried the following without no luck

1. Update Windows Server 2022 to latest update
   
2. reconfigure WSFC quorum to use Defualt configuration
   
3. reconfigure WSFC quorum to use Witness fileShare.
   

 

Upgrade Step for Windows AD Server to Windows Server 2019

Hi all,

I need your help as my situation below,

Primary server:

Windows 2008 R2 Standard (Master)

AD CS

AD DS

DNS

Secondary Server:

Windows 2012 R2 Standard

AD CS

AD DS

DNS

Replication AD only from Primary to Secondary server.

We have bought Windows Server 2019 Standard for two and we plan to upgrade both server,

I have found lots of step to upgrade AD server for easy ways by adding the bootable Windows iso media and run adprep /forestprep.

But I am worry If some thing else messup the configuration and AD itself.

My Plan,

1: Upgrade windows 2012 to Windows 2019

2: After all done, I will start upgrade Windows 2008 R2 to Windows 2012 R2

3. An then start to Upgrade to Windows 2019

Question : Any step or prerequisite before i start upgrading ? (for example, AD might not working during installation or etc)

Thanks

Ashraf