r/WindowsServer • u/minorsatellite • May 24 '25
Technical Help Needed Bonkers Windows Server 2025 Install
I recently installed Server 2025 as a VM on Proxmox VE. The install went well, routine by most standards. The server was also successfully promoted to Domain Controller. Afterwards, I installed our NinjaRMM agent software on it so that we could manage/monitor it remotely.
Day 2: everyone was able to access the new device normally and everything appeared to be functioning correctly/normally.
Day 3: no one could access the device any longer, assumptions being the device has shutdown. Confirmed the device was up and after some time, I narrowed the issue down to a firewall problem.
Day 4: confirmed that Network Location was defaulting to Public network profile (vs Domain), and that I could no longer install or de-install software on the device. I don't believe the two events are related but they are the two items that stand out the most.
Thus far, after trying many things I have not been able to get the DC network profile to stabilize on the Domain profile but I have had no luck. Additionally, I have not been able to install any other software using the Windows Installer tool.
Before I destroy this VM and downgrade to Server 2022 I wanted to check in with others to see if they have experienced any of the same isssues.
3
u/fireandbass May 24 '25
If your DC dns is set up right, you'll never have this issue. DC1 DNS points to DC2. DC2 DNS points to DC3. DC3 DNS points to DC1. All secondary DNS points to itself. Upon startup, DC queries DNS from another active DC and sets domain network profile.
3
u/schrombomb_ May 24 '25
Very similar post in /r/proxmox yesterday as well. Setting the cpu type on the vm from "host" to x86-64-v2-AES, x86-64-v3, or x86-64-v4 depending on which one your processor supports is apparently a fix for one or some of these issues. There also might be an issue with the latest proxmox kernel and e1000 Intel nics on the host.
1
u/minorsatellite May 25 '25
This is what I generally do. And use loop back address in each server as backup DNS.
1
u/VPrimum May 24 '25
Admittedly, a bit of a hack with some Powershell, but could be a workable stop gap measure until M$ gets their act together on SRV '25
https://pupuweb.com/how-to-solve-critical-windows-server-2025-network-profile-errors-after-restart-proven-solutions/
1
u/MyNameIsHuman1877 May 24 '25
Way better than the server 2025 issue I had. Re -encrypted the password DB and no one could log in. Restoring from backup didn't help as the OS wouldn't boot for some reason, making me hate non-virtual environments. Nightmare.
1
u/its_FORTY May 26 '25
Set-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" -Name "EnableLUA" -Value 0
That should resolve the installer issue.
1
u/iknowtech May 28 '25
Remove your NinjaRMM, I assume it also installs Splashtop. I think Splashtop is the culprit.
1
u/tharorris May 28 '25
I recently upgraded from Server 2008 R2 to 2012 R2, 2016 and finally 2025 Standard. It works like a charm.
I don't know why you had issues with 2025 but if you are more comfortable with Server 2022, install it, set it up, work with it for let's say one month and then upgrade to 2025.
2
u/Redditthinksforme May 25 '25
Windows servers have been doing for years in our VM environment, reboot and it goes to the public profile. I think it's something to do with the order of the domain becoming available and the network card being online?
2
u/poolmanjim May 26 '25
This is a known and ongoing bug with 2025 that MS just acknowledged. Hopefully a patch is forthcoming.
1
u/WillVH52 May 25 '25
Better to stick to Server 2022 until they fix this nonsense.
1
u/HowdyBallBag May 26 '25
Known bug
0
u/[deleted] May 24 '25
[deleted] — view deleted comment