Hi, yes the Workflow will be the same, except that you do the subscription handling in Greenlake and the device moving as well. But still the device will get online within your new Central instance and you can create a group from the config on the VC.
BR
Florian
------------------------------
-------------------------------------------------------------------------------
Florian Baaske
-------------------------------------------------------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
-------------------------------------------------------------------------------
Also visit the AirHeads Youtube Channel:
https://www.youtube.com/channel/UCFJCnuXFGfEbwEzfcgU_ERQ-------------------------------------------------------------------------------
Feel free to visit my personal Blog
https://www.flomain.de------------------------------
Original Message:
Sent: Dec 07, 2022 10:54 AM
From: TS87
Subject: Migrating AP's and Config from one Central Account to another
Hi Florian,
Is the workflow you describe also true after the migration to the Greenlake platform?
Original Message:
Sent: Mar 30, 2020 11:30 PM
From: Florian Baaske
Subject: Migrating AP's and Config from one Central Account to another
hi,
I have never done before this kind of scenario, but from my point of view, the high-level workflow should be like this:
- remove the subscription from the devices in the old company central account. The config of the IAP's will stay in the IAP and they will work as before, just without central.
- Add the devices to the new company central account
- After some time, they should come up in the new central account without being a member of a group
- Select the VC in the Group settings and use the "Import Configuration to New Group" button to create a Group using the existing config of the VC
Hope this helps.
BR
Florian