BestSync - Domain Accounts

Welcome to BestSync Support Forum!
If you have any questions, comments, concerns, suggestion, please summit here, we'll try to reply you in short time.
Thank you!
Post Reply
Pascal
Posts: 6
Joined: Tue Sep 27, 2016 2:01 pm

BestSync - Domain Accounts

Post by Pascal »

Hi,

we are running BestSync on a large Server cluster with many AD domain users.
Now we have the problem that on one server only the person which configured the sync can see the tasks in BestSync.

So he opens BestSync and has all current tasks in his view.
If any other person opens BestSync on this server there are no tasks.

Do you have any idea how this can be possible? All persons are domain admins and have almost the same rights.
On every other server it is working fine.

Kind regards,
Pascal
RiseFly
Site Admin
Posts: 1077
Joined: Tue Nov 03, 2009 2:51 pm

Re: BestSync - Domain Accounts

Post by RiseFly »

Basically, BestSync task settings are user independent.
If you want users share the settings, you can use "File"/"Save as" menu to save the tasks to a file in a shared folder, then let users to open the file by "File"/"Open" menu. By this way users can shared the same settings.
Pascal
Posts: 6
Joined: Tue Sep 27, 2016 2:01 pm

Re: BestSync - Domain Accounts

Post by Pascal »

Yeah, I know that is why I asked. This is a weird behavior which isn't like that on all other 30 servers.

But why on this installation only the creator of the tasks can see these tasks? Normally everyone can see the tasks?!

Any idea what could be the problem and how we can fix it? Try to remove and insert the tasks again?
RiseFly
Site Admin
Posts: 1077
Joined: Tue Nov 03, 2009 2:51 pm

Re: BestSync - Domain Accounts

Post by RiseFly »

If you schedule the task run as Windows Service, then all the user can see the task in the "Service" tab.
Pascal
Posts: 6
Joined: Tue Sep 27, 2016 2:01 pm

Re: BestSync - Domain Accounts

Post by Pascal »

Ohh, thanks.

That was the only server we didn't configure these tasks as a service... :mrgreen:
Sorry, that was our mistake.

Thank you for your help :)
Post Reply