Mark LaGrange

<div>
<div class="content wysiwyg-content">
Hello – I have a client with a large MS Access application that &nbsp;has asked me to migrate their backend database to SQL Server. <br />
The admin there set up a Windows Server 2016 evaluation instance (on VMWare), and installed SQL Server 2017 Express on it, so I could work out the details in an isolated environment.<br />
I have migrated the Access database to that SQL Server, but I have not been able to create a DSN to it from a client PC.<br />
I have tried following a couple of troubleshooters, changing several settings, but nothing has worked.<br />
I am an Access developer, and I’m out of my element with this. The network admin there is not able to help.<br />
Is the WS 2016 eval crippled in any way that would cause this? <br />
<br />
Thanks
</div>
</div>


Hello – I have a client with a large MS Access application that  has asked me to migrate their backend database to SQL Server. 
The admin there set up a Windows Server 2016 evaluation instance (on VMWare), and installed SQL Server 2017 Express on it, so I could work out the details in an isolated environment.
I have migrated the Access database to that SQL Server, but I have not been able to create a DSN to it from a client PC.
I have tried following a couple of troubleshooters, changing several settings, but nothing has worked.
I am an Access developer, and I’m out of my element with this. The network admin there is not able to help.
Is the WS 2016 eval crippled in any way that would cause this? 

Thanks

Windows Server 2016 evaluation with SQL Server 2017 Express

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.