Bare Metal Configuration

[srivera42]

I'm having problems setting up my bare metal configuration

ACM activation is successful using MESHCMD, I'm using the same FQDN as my fancy CA cert, my option 15 is set to to my FQDN, and my devices are hardwired to my switch.

Cisco Switch , Windows 2022 server, Hybrid mode config.

  "settings": {
    "AmtProvisioningServer": {
      "port": 9971,
      "deviceGroup": "mesh//groupnamehash...",
      "newMebxPassword": "xXXXXX1!,
      "trustedFqdn": "mydomain.com",
      "ip": "meshcentralserverip"
    }
  },

is anyone else having problems with bare metal, or am I doing something wrong?

[Ylianst]

FYI. Some background. As discussed in #4619 4795, Bryan and I just got downsized and so, no longer going work for Intel. This was a big surprise, it happened 2 weeks back. Intel AMT development requires a "hardware rich" environment that I will no longer have access to, so, I am not going to be in a position to test and fix these issues. For example, I don't have access to an Intel AMT v16 anymore. I am wondering what to do about this. One thing I may do is disable Intel AMT support from MeshCentral by default, but put in a switch to turn it on for people that want to try it out. Otherwise, you will need to call Intel support to see what they can offer.

[srivera42]

Sorry to hear about your job.

If you're in search of contracting out for professional hours, I'm sure plenty of people would be willing to hire your services.

Obviously, you're going to land on your feet with whatever you decide your next journey will be.

Thank you for all the support, and happy holidays.

[dinger1986]

@si458 AMT