Windows 10: Server 2019

OK, here goes. I Have never posted a question to this, or any, forum regarding windows before, but I'm stumped. I'll try and be as clear as possible.


The scenario: A newly installed windows Server 2019 standard running a Client/Server software called Dentrix. The server is AD/DC/DHCP/DNS.


The secondary adapter is disabled. IPV6 is disabled on the working NIC.


IPV6 is disabled on all client workstations as well.


The client software relies on two parts. an SQL client that will cause all kinds of errors if it looses connection to the server for even a brief second, and access to a shared folder on the server.


The clients are configured with only one DNS, the Server's IP address, I can Ping the server, by name or IP, for hours on end with no dropped packets. DNS queries run on the server all pass. I can browse to the server from any workstation by name or IP without error. I can open the shared folder without error, again from any workstation.


Permissions on the share are: Domain Users\Domain Admins\Everyone - Full

The share is on the root of "C" and inheritance has been disabled, made sure to pass permissions to all sub folders

Guest and Anonymous users have been removed from share


Now the problem:


The client software is comprised of multiple modules, each serves a different purpose, and each one can be launched from within any of the other modules. Since I put in the new Server 2019 I've encountered a problem I can not resolve, and support from the software provider say they have no ideas.


The problem in a nutshell is this, when launching a module from within another module, sometimes, and not all the time, it will tell me it can't access the server share, while showing the absolute correct path to the share. Attempts to browse to and open the share at this point are successful. In normal scenarios this error would indicate a disconnect from the server in some way shape or form. But in this scenario, the client pc is not being disconnected, and hitting "close' on the error still allows the launched module to start. For clarification, this problem occurs maybe a dozen random times a day, out of 100's of launches. Its not tied to a particular workstation. I can not duplicate the error on purpose. I have tried a few things, will wait and see if anyone responds.


Thank you for your time

:)

 

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.

 

Activate RDS CAL 2019 on Windows Server 2016

Dear Microsoft Support,



We recently purchased Windows Server RDS CAL 2019.

When we tried to install Windows Server RDS CAL 2019 into Windows Server 2016, it shows the license is not recognized and couldn’t install.



My questions are :

1. Can’t Windows RDS CAL 2019 be installed in Windows Server 2016? If can, how?
2. Is there any way to downgrade RDS CAL from 2019 to 2016 version?

Thanks,

 

Server 2019 DC - Kerberos RC4

We have recently promoted a 2019 Server to be a domain controller but it won't authenticate access to our EMC VNX datastore which we believe only supports RC4 Kerberos -
is there anyway to enable RC4 Kerberos in Server 2019 as it appears to have been removed?

(Using the IIS Crypto tool we can see the 2019 server does not have any RC4 ciphers)

Access to the EMC VNX datastore works from 2012 and 2016 DC's.

Access from the 2019 server to all other devices on the network also work (we can see these using AES encryption via the klist utility)

I can see no documentation suggesting any changes around Kerberos in server 2019