Here's one I can't find anything on.  I'm referring to the toolbars that can be created on the Windows Task Bar.  We have a user that wants a network share as a toolbar on the taskbar.  So I go to Toolbars/New Toolbar and browse to the network folder.  Once I select that, on the task bar is the toolbar I created with a >> that shows the contents of the network share like one would expect.  Works great.  Until...

Reboot the machine and the toolbar is there but empty and unclickable.  If I delete it and re-add it as above, it works fine.  So my guess is that the toolbar is being constructed at startup before the network share is available.  How do I accomplish this and have the toolbar work after restarting?

Thanks!

Hi,

That is because machine will require a credential to access this share folder again after reboot. If you have same user account with same password, you will find that it works even after reboot. It is actually a security consideration.

If it is OK in your environment, here is what we need to get rid of this issue.

When you access the share folder, please tickle the Remember my credentials for that user.

I tested on my machine and the toolbar works even after singout.

Regards,

D. Wu

Actually, this user has full permissions to the shares in question.  One of them is our "Public" share that grants access to "Everyone".  She is never prompted for credentials because she has valid permissions to each of the shares.

Hi,

I am supposing your environment is WorkGroup, I am not saying your user has no permission to access share folder. Actually the everyone in permission setting only means every account on that computer. Every access from other computers must provide credential (account name and password on share folder host). There is only two situation that share access wont require providing credential

1. You have (using) exactly same account and password on client machine and host machine.
2. You already had valid credential in credential manager.

So try access \\servername and let machine remember that credential in credential manager should resolve this issue.

Regards,

D. Wu