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 11 UPDATE MESSES UP MESH AGENT AND DISPLAY IN MESHCENTRAL #6098

Open
mtran-88 opened this issue May 16, 2024 · 0 comments
Open

WINDOWS 11 UPDATE MESSES UP MESH AGENT AND DISPLAY IN MESHCENTRAL #6098

mtran-88 opened this issue May 16, 2024 · 0 comments
Labels

Comments

@mtran-88
Copy link

Describe the bug
When I updated my NUC to Windows 11 iot Enterprise, I had to reinstall the mesh agent. When I did that, it would not show up. I delete out the device, and reinstall the mesh agent. Now, it shows up as same name with 2 different types. One with CIRA and one with Agent.

To Reproduce
Steps to reproduce the behavior:

  1. Update the NUC device to windows 11 iot Enterprise
  2. Under device group int Meshcentral, there would be no 'Agent' shown for that device.
  3. Delete out the device under My devices group.
  4. Uninstall the meshagent on the device, and install it again.
  5. Under the group, the device now shows up as 2 different connectivity. CIRA and Agent.

Expected behavior
I expect it be like originally. One device with both CIRA+Agent designation.

Screenshots
image

Server Software (please complete the following information):

  • OS: Windows 10 Pro -64
  • Virtualization: No
  • Network: Hybrid
  • Version: 1.1.22
  • Node: v21.7.2

Client Device (please complete the following information):

  • Device: NUC
  • OS: Windows 11 pro-64
  • Network: Local to Meshcentral
  • Browser: Edge
  • MeshCentralRouter Version: N/A

Remote Device (please complete the following information):

  • Device: NUC
  • OS: Windows 11 iot Enterprise
  • Network: [e.g. Local to Meshcentral, remote over WAN
  • Current Core Version (if known): [HINT: Go to a device then console Tab then type info]

info{ "meshVersion": "v1.1.22", "nodeVersion": "v21.7.2", "runMode": "Hybrid (LAN + WAN) mode", "productionMode": false, "database": "NeDB", "platform": "win32", "arch": "x64", "pid": 9884, "uptime": 579218.0794424, "cpuUsage": { "user": 175890000, "system": 63750000 }, "memoryUsage": { "rss": 140374016, "heapTotal": 67346432, "heapUsed": 63948976, "external": 33147537, "arrayBuffers": 30798628 }, "warnings": [], "allDevGroupManagers": []

Additional context

Your config.json file

 "$schema": "https://raw.githubusercontent.com/Ylianst/MeshCentral/master/meshcentral-config-schema.json",
 "__comment1__": "This is a simple configuration file, all values and sections that start with underscore (_) are ignored. Edit a section and remove the _ in front of the name. Refer to the user's guide for details.",
 "__comment2__": "See node_modules/meshcentral/sample-config-advanced.json for a more advanced example.",
 "settings": {
   "cert": "meshcentral.mydomain.com",
   "_WANonly": true,
   "_LANonly": true,
   "_sessionKey": "MyReallySecretPassword1",
   "port": 443,
   "_aliasPort": 443,
   "redirPort": 80,
   "_redirAliasPort": 80
 },
 "domains": {
   "": {
     "title": "MyMeshCentral Server",
     "_title2": "Servername",
     "_minify": true,
     "_newAccounts": true,
     "_userNameIsEmail": true
   }
 },
 "letsencrypt": {
   "__comment__": "Requires NodeJS 8.x or better, Go to https://letsdebug.net/ first before trying Let's Encrypt.",
   "email": "myemail@domain.com",
   "names": "meshcentral.mydomain.com",
   "skipChallengeVerification": true,
   "production": true
@mtran-88 mtran-88 added the bug label May 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant