Using modernized architecture, the SCCM mobility agent documentation refers to 'classic' file paths / tools

Question

Using modernized architecture, the SCCM mobility agent documentation refers to 'classic' file paths / tools

Simon Burbery 731

Hi, we had a pause in an ASR project late last year, after which we were forced into the modern architecture (we are protecting VMs on a shared infra so have no access to the hypervisor). SCCM team had already packaged the mobility agent.

Looking at the modernized deployment, we are directed to a page which has the SCCM deployment method, but it does not appear to have been updated from the 'classic' deployment which says "generate the pass-phrase on the CS". Before that it has modern (but manual) instructions which include:

running set up on the source machine to get a 'machine-specific' code.
running the configuration server utility (on the configuration server), input the machine code and it generates a registration code for the particular source machine.
run set up on the source machine again to register it with the CS.

Please tell me there is a way to automate this deployment using SCCM? Or if not, how do I feed a 'bulk' list of endpoints into ASR? All I can see is a manual GUI where you can enter one machine at a time.

Thanks, Simon

Simon Burbery 731 Reputation points

2023-09-22T06:37:17.1866667+00:00

Here are the docs re client installation https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview. In true ASR documentation fashion (i.e., constantly linking to other documentation that is for a different architecture than you are using), it starts by referencing "(Modernized)" all over the show, then you get to the SCCM deployment and it's the same as it was for Classic, referencing paths and files that do not exist, with absolutely no hint of an approach for "Modernized" at all. Who would update that without thinking "Hmm... there's a really important part missing here!" LOL.
Simon Burbery 731 Reputation points

2023-09-25T20:16:57.2066667+00:00

Thanks @Sadiqh Ahmed I will do the needful.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-09-26T09:33:29.0566667+00:00

@Simon Burbery Please share the feedback link. I will work with the content team to ensure a note is added to the document that mentions about support not being enabled yet for SCCM.
Simon Burbery 731 Reputation points

2023-09-27T09:39:51.5833333+00:00

Thanks, I appreciate your time to find this out, but it is a shame... the only way to roll out the agent en-masse is via push-installation, and auto-update isn't supported when using private links. Hopefully once the agent is installed manually, we can install updates via SCCM without having to generate the config.json again. It would be difficult to stay up to date otherwise. Although the appliance is great, we would have been better off being able to continue with the classic architecture until another method of deployment was available. A case of bad timing I guess!
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-09-27T14:55:56.17+00:00

@Simon Burbery I understand your concern and appreciate your valuable feedback and sharing experience on Microsoft Q&A community. We will discuss this with the concerned team and try to get traction from PG to prioritize enabling this functionality.

Thanks!

Answer accepted by question author

0 additional answers

Your answer

Simon Burbery 731 Reputation points

2023-09-22T06:37:17.1866667+00:00

Here are the docs re client installation https://learn.microsoft.com/en-us/azure/site-recovery/vmware-physical-mobility-service-overview. In true ASR documentation fashion (i.e., constantly linking to other documentation that is for a different architecture than you are using), it starts by referencing "(Modernized)" all over the show, then you get to the SCCM deployment and it's the same as it was for Classic, referencing paths and files that do not exist, with absolutely no hint of an approach for "Modernized" at all. Who would update that without thinking "Hmm... there's a really important part missing here!" LOL.
Simon Burbery 731 Reputation points

2023-09-25T20:16:57.2066667+00:00

Thanks @Sadiqh Ahmed I will do the needful.
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-09-26T09:33:29.0566667+00:00

@Simon Burbery Please share the feedback link. I will work with the content team to ensure a note is added to the document that mentions about support not being enabled yet for SCCM.
Simon Burbery 731 Reputation points

2023-09-27T09:39:51.5833333+00:00

Thanks, I appreciate your time to find this out, but it is a shame... the only way to roll out the agent en-masse is via push-installation, and auto-update isn't supported when using private links. Hopefully once the agent is installed manually, we can install updates via SCCM without having to generate the config.json again. It would be difficult to stay up to date otherwise. Although the appliance is great, we would have been better off being able to continue with the classic architecture until another method of deployment was available. A case of bad timing I guess!
Sadiqh Ahmed 49,571 Reputation points Microsoft External Staff Moderator

2023-09-27T14:55:56.17+00:00

@Simon Burbery I understand your concern and appreciate your valuable feedback and sharing experience on Microsoft Q&A community. We will discuss this with the concerned team and try to get traction from PG to prioritize enabling this functionality.

Thanks!

Answer 1

Sadiqh Ahmed 49,571 Microsoft External Staff Moderator

@Simon Burbery Thank you for your valuable feedback. Could you please share your feedback on the same document using the option "This page", so that the content team will review it with product team and get that updated?

User's image

Update:

@Simon Burbery Relayed your feedback to the product team. Response from the PM - "we don't yet have SCCM support. Thus, the document hasn't been updated yet"

Hope this answers your question!

If the response helped, do "Accept Answer" and up-vote it

0 comments

Share via

Using modernized architecture, the SCCM mobility agent documentation refers to 'classic' file paths / tools

0 additional answers

Your answer