Windows Server 2019 Enter License Key

0 views

Skip to first unread message

Nakita Heitmann

unread,

Aug 3, 2024, 4:40:10 PM8/3/24

to meerscamnemat

Hi,
Wondering if Server 2025 can be AAD joined. this would help some businesses that have their laptops joined as well as would also like to have the option to join their Server for their line of business apps etc.

Seems really strange you can have win11 AAD joined but not server 2025.

Or am i just missing something here. Having to use Azure Arc comes with extra headaches and costs.

Microsoft Azure Arc is free, but it adds a new layer of complexity and security if you want to make it right, just as AAD join would, too. This is because Azure Arc adds the Server to the management plane of Azure Portal and also the control and security plane of Entra ID which is intertwined with your AAD accounts.

Hi, Brent here from the Windows Server team. Can I ask you to elaborate a bit more on how you would use Entra ID device join on Windows Servers? When is it most painful to be missing this capability? Servers in the cloud, Servers at the edge, in your datacenter? Would you use this with traditional AD or no? Would this be most convenient for configuring and deploying, or troubleshooting, or other tasks? You mention accessing corporate resources from the Server, would to know more about this. Thanks!

@workalotdave Thank you for the feedback. This makes sense. How many user accounts do you typically have to manage for Servers at the edge today? Have you tried Entra ID pass-through and/or AD federation services?

@Brent Forman Sorry for the delay. We have around 10 admins that administer edge boxes. We don't have a local domain and do not want to setup a Active Directory instance on azure just for this. If we provision boxes from azure they have AAD join / authentication built-in so it already exists but its not available to just download and use.

- Thinking about local kerberos tickets coming to Windows 11, I suppose Windows Server, too, when DC is not in sight.

Imagine this with Windows Server using Entra, MFA / Conditional Access, PAM / PIM for Windows Server, eventually thinking about Entra Roles which would also automatically predefine PowerShell limited commandlets
- Manage Application Deployment (winget) and (Defender) Security Policies via Intune
- might be even feasible to combine this Azure Policy via Azure Arc

You said the server has a static IP address, but you didn't mention the PC. Most APs have DHCP running. If that's where the PC got it's address, then you need to either enter your domain controller as the DNS server that your AP gives out, or manually override the DNS server used by the PC when it gets an address from the AP.

ISP DNS is being query'd and not your DNS server regardless if you input your static IP in preferred DNS in TCP settings.I wrestled with this for a few days before being able to piece together various info on the net. I have built small networks before and this problem had me stumped. The only difference was this network was at home lab. Made sense that it did not work with my Uverse because the options are so limited on my modem. Not sure if you have to contact your ISP Host to make changes, but I just created a host only environment, cutting out the access to the internet and any need to query ISP DNS and the clients connect without a problem. This solved my issue but you may have the need to connect to the internet. If your ISP can not make adjustments, possibly bridge a VM router or use Windows DHCP server to pass traffic.

In my case i just installed a "Windows Server 2008 R2" to be the Active Directory and I added only the AD role.I was receiving the same error message ("The following domain either does not exist or could not be contacted") while joining a new computer to the just created domain, which presented no problem during the creation.

In resume, my problem was that I did not add the DNS role together AD role in the "Windows Server 2008 R2". After add the DNS role and include a new computer in the AD group, it worked like a charm, so you will need at least both roles to have your AD properly working.

Hello (I use google translator),
I finally got Lucee running on a Windows Server 2019 with IIS.
Now I would like to access Access databases (mdb) with Lucee.
Are there instructions for this?
Do I really need ucanaccess?
How do I install ucanaccess?
I downloaded it but there is no setup file, what next?

My personal advice is migrate that DB to another one (e.g. mariaDB or mySQL) in first place. There are lots of tools around and docs that makes that pretty easy. Probably easier than trying to make a data source connection to a modern web app engine like Lucee work.

I use Access as DB for more than 20 years, it works fine for small sites,
and it is very simple and flexible.
I just cut and paste my MDB file, and do what ever I want with the MDB on local.
In Lucee , you use ODBC driver : Update datasource connection Other - JDBC Driver (deprecated)
I work on Linux, but before I worked on windows.
Set Class and connection string in the declared datasource.
It is good to me to know other users with Ucanaccess driver.
mdb_file742434 59.1 KB

1, You are better off converting your access DB to MS sql express, which will import all your data into the tables / databases and have far better performance than access plus lucee supports MSSQL
2. You will need to install the ODBC drivers for your windows version, and you will need to install microsoft office Unable to use the Access ODBC, OLEDB or DAO interfaces outside Office Click-to-Run applications - Office Microsoft Learn
3. Lastly, you can follow this tutorial if you cant JUST LIVE without access, it is the JAVA connector how to, which you will have to wrap cfcode around
Java JDBC Example Connect to Microsoft Access Database

Ok, it took about 30min to try this, and I was able to make an access database work with an Lucee Express Version 5.3.10.97 on my Windows 10 Lap. You need to translate that to your installed server. But this works!!! If you have populated your Lucee installation with some other files, please restart from scratch. Here is a solution and the steps you need to make:

Amazon FSx for Windows File Server provides fully managed Microsoft Windows file servers, backed by a fully native Windows file system. FSx for Windows File Server has the features, performance, and compatibility to easily lift and shift enterprise applications to the AWS Cloud.

Amazon FSx supports a broad set of enterprise Windows workloads with fully managed file storage built on Microsoft Windows Server. Amazon FSx has native support for Windows file system features and for the industry-standard Server Message Block (SMB) protocol to access file storage over a network. Amazon FSx is optimized for enterprise applications in the AWS Cloud, with native Windows compatibility, enterprise performance and features, and consistent sub-millisecond latencies.

With file storage on Amazon FSx, the code, applications, and tools that Windows developers and administrators use today can continue to work unchanged. Windows applications and workloads ideal for Amazon FSx include business applications, home directories, web serving, content management, data analytics, software build setups, and media processing workloads.

As a fully managed service, FSx for Windows File Server eliminates the administrative overhead of setting up and provisioning file servers and storage volumes. Additionally, Amazon FSx keeps Windows software up to date, detects and addresses hardware failures, and performs backups. It also provides rich integration with other AWS services like AWS IAM, AWS Directory Service for Microsoft Active Directory, Amazon WorkSpaces, AWS Key Management Service, and AWS CloudTrail.

The primary resources in Amazon FSx are file systems and backups. A file system is where you store and access your files and folders. A file system is made up of one or more Windows file servers and storage volumes. When you create a file system, you specify an amount of storage capacity (in GiB), SSD IOPS, and throughput capacity (in MB/s). You can modify these properties as your needs change after you create the file system. For more information, see Managing storage capacity, Managing SSD IOPS, and Managing throughput capacity on FSx for Windows File Server file systems.

FSx for Windows File Server backups are file-system-consistent, highly durable, and incremental. To ensure file system consistency, Amazon FSx uses the Volume Shadow Copy Service (VSS) in Microsoft Windows. Automatic daily backups are turned on by default when you create a file system, and you can also take additional manual backups at any time. For more information, see Protecting your data with backups.

A Windows file share is a specific folder (and its subfolders) within your file system that you make accessible to your compute instances with SMB. Your file system already comes with a default Windows file share called \share. You can create and manage as many other Windows file shares as you want by using the Shared Folders graphical user interface (GUI) tool on Windows. For more information, see Using file shares to access data.

Amazon FSx is accessible from compute instances with the SMB protocol (supporting versions 2.0 to 3.1.1). You can access your shares from all Windows versions starting from Windows Server 2008 and Windows 7, and also from current versions of Linux. You can map your Amazon FSx file shares on Amazon Elastic Compute Cloud (Amazon EC2) instances, and on WorkSpaces instances, Amazon AppStream 2.0 instances, and VMware Cloud on AWS VMs.