Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows Server 2025 MeshAgent Installation Fails #6551

Closed
nmincone opened this issue Nov 23, 2024 · 4 comments
Closed

Windows Server 2025 MeshAgent Installation Fails #6551

nmincone opened this issue Nov 23, 2024 · 4 comments

Comments

@nmincone
Copy link

Describe the bug
Unable to install on Windows Server 2025

To Reproduce
Meshagent installer launches to black cmd screen then abruptly quits.

Expected behavior
Installer dialog never appears

Screenshots
N/A

Server Software (please complete the following information):

  • OS: Debian Bookworm
  • Virtualization: Docker
  • Network: LAN
  • Version: 1.1.33
  • Node: N/A

Client Device (please complete the following information):

  • Device: Proxmox VM
  • OS: Windows 2025 Server
  • Network: LOCAL
  • Browser: N/A
  • MeshCentralRouter Version: N/A

Remote Device (please complete the following information):

  • Device: all LAN devices remoteing into Proxmox
  • OS: Windows/Mac OS
  • Network: Remote over LAN
  • Current Core Version (if known): 1.1.33
@nmincone nmincone added the bug label Nov 23, 2024
@si458
Copy link
Collaborator

si458 commented Nov 23, 2024

duplicate #6457 #6433 #6383 #6540

fix is here in this issue - #6162

simply install wmic add on FIRST then install meshagent
OR
try the new agent from within the issue which DOESNT require wmic
(you must upload new agent to your meshcentral)

@si458 si458 closed this as completed Nov 23, 2024
@nmincone
Copy link
Author

Apologize, I'll work on my pre-search skills. Thank you!

@si458
Copy link
Collaborator

si458 commented Nov 23, 2024

@nmincone no worries! we do have a new agent as explained, which i HOPE will be included in the next release,
then from 1.1.34+ it should be fixed when u download a new agent
just waiting for @Ylianst to verify everything first before i push the agent to the main repo!

@nmincone
Copy link
Author

Appreciate all the work you guys are doing!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants