You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Update the NUC device to windows 11 iot Enterprise
Under device group int Meshcentral, there would be no 'Agent' shown for that device.
Delete out the device under My devices group.
Uninstall the meshagent on the device, and install it again.
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
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]
"$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": "[email protected]",
"names": "meshcentral.mydomain.com",
"skipChallengeVerification": true,
"production": true
The text was updated successfully, but these errors were encountered:
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:
Expected behavior
I expect it be like originally. One device with both CIRA+Agent designation.
Screenshots
![image](https://private-user-images.githubusercontent.com/166559124/331293526-55e4abe0-a302-4a0e-a5ea-d77d31533b17.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk3MDUyNjMsIm5iZiI6MTcxOTcwNDk2MywicGF0aCI6Ii8xNjY1NTkxMjQvMzMxMjkzNTI2LTU1ZTRhYmUwLWEzMDItNGEwZS1hNWVhLWQ3N2QzMTUzM2IxNy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjI5JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYyOVQyMzQ5MjNaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT05N2I0ZDBiNjI4ZGU4ZmU2ZjE1YWVlZTQ5M2EzMmE1NzExMThjZmM4YjBlMDQ5OWM3OTZkZTY4MzQxN2MxOTJhJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.WLj7-MhxNBIraKYFs0e4Dv-SHuEuPMz_fR35gAA73ZM)
Server Software (please complete the following information):
Client Device (please complete the following information):
Remote Device (please complete the following information):
console
Tab then typeinfo
]Additional context
Your config.json file
The text was updated successfully, but these errors were encountered: