ARC resources switching Log analytics workspaces

GerhardK 6

Having some trouble moving an ARC VM from one log analytics workspace to another. Vm does not show up under VMs on the LAW as the filter auto applies subscription machines only. What can I do other than deleting the ARC machine and redeploying to the new LAW?

bharathn-msft 5,086 Reputation points Microsoft Employee

2021-03-05T17:14:19.237+00:00

@GerhardK Thank you for reaching out, looking into your scenario . Will get back to you at the earliest.
GerhardK 6 Reputation points

2021-03-08T08:43:14.363+00:00

Thanks Bharathn, Looking forward to any feedback.

As a side note: I've also tried deleting the ARC server from the portal and re-adding it. The log analytics agent or (insights agent?) seems to dictate which workspace it connects to. I also can't manage the agent from the Az side as it doesn't show up under extensions for the ARC resource.

1 answer

bharathn-msft 5,086 Reputation points Microsoft Employee

2021-03-12T04:07:08.403+00:00

<<Resurfacing the information from comments for broader community usage >>

@GerhardK Apologies for delay in getting back to the thread.

Checking in to see, as part of the initial setup Azure Arc enabled server was connected to Log Analytics via agent or using the VM extensions ?

If its via the agent, have you tried looking into MMA agent on the VM and see if you can remove the existing LA workspace and add a new one.

Please see if above information is helping in your scenario, if not this might need a deeper troubleshooting for your environment. Looking forward to hear from you.
Please sign in to rate this answer.

1 person found this answer helpful.
GerhardK 6 Reputation points

2021-03-12T10:38:41.9+00:00

Thanks!

I deleted the ARC resource Az side and removed the LAW entry configured on the agent.

After I re-ran the on boarding script I got the option Az side to select a new LAW target for the agent.

Thank you for your help!

bharathn-msft 5,086 Reputation points Microsoft Employee

2021-03-16T21:31:33.37+00:00

@GerhardK - Glad to hear that the issue is fixed . Thank you
Sign in to comment