Cloud Managed Networks

It's there, it just changed names. The mDNS profile you found is the switch-side reflector: the doc says it can only be configured for the Aggregation Switch and Core Switch device functions, which is why the APs are excluded. AirGroup itself is under Application Services now (renamed in the April 2026 release). Configuration, then Global, then the Services tab, then Manage on the Application Services card. It's off by default, and the Advertising Servers card is where you pin a printer's MAC to the APs allowed to advertise it.

One catch that applies to you specifically. The same page says that for deployments migrated from Classic, monitoring is in New Central but service configuration continues to be performed through Classic; only new deployments get both. So check whether the Enable box is live in your tenant before you build the next site around it. If it's greyed out, that's the migrated-tenant rule, not a missing feature.

Hi Dustin

If I go to the Services Tab I just have the option for "Dynamic Application Prio". Where the Application Services moved recently?

I'm also trying to achieve the same thing, because with new central Airprint is no longer working.

Regards

MF

It's there, it just changed names. The mDNS profile you found is the switch-side reflector: the doc says it can only be configured for the Aggregation Switch and Core Switch device functions, which is why the APs are excluded. AirGroup itself is under Application Services now (renamed in the April 2026 release). Configuration, then Global, then the Services tab, then Manage on the Application Services card. It's off by default, and the Advertising Servers card is where you pin a printer's MAC to the APs allowed to advertise it.

One catch that applies to you specifically. The same page says that for deployments migrated from Classic, monitoring is in New Central but service configuration continues to be performed through Classic; only new deployments get both. So check whether the Enable box is live in your tenant before you build the next site around it. If it's greyed out, that's the migrated-tenant rule, not a missing feature.

Hi,

I ended up logging a call with HPE which is still in progress. However, what they have said is that some of the configuration is still done in Classic.  At the moment I can see that Airgroup is at least partially working in our new site, but with testing to date we have not been able to print to across vlans as we do at our other sites which were configured fully in classic.

Thanks,

CJ

Hi Dustin

If I go to the Services Tab I just have the option for "Dynamic Application Prio". Where the Application Services moved recently?

I'm also trying to achieve the same thing, because with new central Airprint is no longer working.

Regards

MF

It's there, it just changed names. The mDNS profile you found is the switch-side reflector: the doc says it can only be configured for the Aggregation Switch and Core Switch device functions, which is why the APs are excluded. AirGroup itself is under Application Services now (renamed in the April 2026 release). Configuration, then Global, then the Services tab, then Manage on the Application Services card. It's off by default, and the Advertising Servers card is where you pin a printer's MAC to the APs allowed to advertise it.

One catch that applies to you specifically. The same page says that for deployments migrated from Classic, monitoring is in New Central but service configuration continues to be performed through Classic; only new deployments get both. So check whether the Enable box is live in your tenant before you build the next site around it. If it's greyed out, that's the migrated-tenant rule, not a missing feature.

Hi Dustin

If I go to the Services Tab I just have the option for "Dynamic Application Prio". Where the Application Services moved recently?

I'm also trying to achieve the same thing, because with new central Airprint is no longer working.

Regards

MF

It's there, it just changed names. The mDNS profile you found is the switch-side reflector: the doc says it can only be configured for the Aggregation Switch and Core Switch device functions, which is why the APs are excluded. AirGroup itself is under Application Services now (renamed in the April 2026 release). Configuration, then Global, then the Services tab, then Manage on the Application Services card. It's off by default, and the Advertising Servers card is where you pin a printer's MAC to the APs allowed to advertise it.

One catch that applies to you specifically. The same page says that for deployments migrated from Classic, monitoring is in New Central but service configuration continues to be performed through Classic; only new deployments get both. So check whether the Enable box is live in your tenant before you build the next site around it. If it's greyed out, that's the migrated-tenant rule, not a missing feature.

I am also in this scenario. Where the Application Services is not present in the same drop down tree.

Hi Dustin

If I go to the Services Tab I just have the option for "Dynamic Application Prio". Where the Application Services moved recently?

I'm also trying to achieve the same thing, because with new central Airprint is no longer working.

Regards

MF

It's there, it just changed names. The mDNS profile you found is the switch-side reflector: the doc says it can only be configured for the Aggregation Switch and Core Switch device functions, which is why the APs are excluded. AirGroup itself is under Application Services now (renamed in the April 2026 release). Configuration, then Global, then the Services tab, then Manage on the Application Services card. It's off by default, and the Advertising Servers card is where you pin a printer's MAC to the APs allowed to advertise it.

One catch that applies to you specifically. The same page says that for deployments migrated from Classic, monitoring is in New Central but service configuration continues to be performed through Classic; only new deployments get both. So check whether the Enable box is live in your tenant before you build the next site around it. If it's greyed out, that's the migrated-tenant rule, not a missing feature.