Support Forum

We recently bought the plugin(like in the past week)

I configure it this morning by following the documentation by adding a password on Client location,configuring a new app registration and setting the O365 API permissions(3 of them)

I have configure a single Client by adding the tenandid,client ...

A while ago we subscribed to C4A and also to Habitat so we can test out both application managers
Now that C4A replaced the app manager in habitat,do we still need to pay for the separate C4A subscrition?

Is C4A now fully included in the habitat monthly fee?

Thank you for your assistance so far,again.

I have done the steps as you suggested and it seems to be resolved.
I am able to read all the searches.the groups exist and the scripts have been scheduled on them al,along with the searches too.All the scripts are readable too.

I just noticed that the ...

I have completely removed the plugin from automate,deleted the existing .dll file in the plugins folder,deleted the existing chocolatey groups and searches

Reinstalled the plugin afterwards with no luck
groups are created,searches are created but the searches are not automatically linked to the ...

I removed the searches from the linked groups then deleted the searches that were unreadable

They have been recreated,but still not able to open them

I think we will need to completely remove the plugin,scripts and groups from automate,then reinstall fresh and see what happens

I will provide an ...

2024-05-23 02_32_27-GLC-MIS-AUTO - ScreenConnect - Connected.png
I have removed the plugin completely from automate
I made sure the .dll is not in the automate server program files directory
I cleared the labtech lugins folder on the server and also cleared the control center cache all at the same ...

I have done that already with no luck

What I have not done yet is perhaps remove the plugin completely from automate,including the .dll file on the automate server.then reinstalling it afterward,the .dll could be stuck on the server instead maybe

Thanks for pointing that out,I will provide ...

Thank you for you response and assistance

The groups are there and the scripts and searches are set up as you indicated too
The searches are in the correct location aswell, but if I go directly to the search and try to open it, automate throws out an error like it is unable to read the search to ...

We have been having this error for a while the moment we click on the filehog tab on the client console
We have also update to version 1.0.5,but the plugin still seems to reflect v1.0.4 in the filehog interface

How can we resolve this error?I think it is causing the background scripts not to run ...

I just need to check if this could be an issue

The only group that is populating is C4A Deploy Chocolatey and I am able to open the autojoin search attached to it
All 4 of the other groups does not seem to populate and when trying to open the autojoin searches, automate is unable to read the ...