I’m 99% sure this is normal (you likely have a FS agent or MA installed on the CS) but like you, I want to be 100% sure. I have asked internally to make sure since it’s been a while since I’ve done one, myself!
Confirmed, the CS showing up is normal!
Thanks Mike, appreciate it.
Would you also know if I need to request the CCM authorize code for the source Commcell if I want to be able to move a migrated client back again. This may be required for restores of historical data as we do not plan to migrate or access that in the new Commcell as it is only short retention data.
I have applied the authorize code on the target CC.
/Patrik
I would expect so. As far as I know, every CCM will require an auth code.
You do have to request the authentication code for the source and destination CommServe to be able to export and import the metadata.
If the imported clients are not going to be registered against the destination CommServe, you will be able to restore their data from the source CommCell, there is no need to migrate clients back.
The Clients will be registered in the target Commcell and backed up there. We will decomission the old Commcell once everything is migrated to the new Commcell and all old data has expired. We just need a simple routine for migrating back in case anyone would require restore of historical data.
When requesting the authcode the web-form asked only for one Commcell and support never asked any questions about target and/or source !? Are you sure both require an authcode?
/Patrik
If you aren’t actually pulling anything back (restoring out of place?), then you may not need to migrate, but all CCMs will require an auth code, if that makes sense.
@Patrik , @Mike Struening
CCM Auth code is like a switch, once you have obtained an auth code for a Commcell, it flips the switch and enables the CCM feature in that Commcell permanently.
So CCM auth code to enable the feature in any Commcell is a one time task for that Commcell.
Thanks,
Stuart