Created a local user with admin access on server. Shared the credentials to all users to map that server folder on their individual machines.
I would suggest that this is a [fairly] Bad Idea.
OK, it's not the worst idea in the World by any means, but definitely towards the "red end" of the Risk scale.
Using the Hidden Administrative shares is not a Good Idea.
These shares are not visible to those End Users who know enough to be able to "browse" to the machine itself. Believe me, they will complain about this.
Giving out Administrative credentials for a server to End Users is a [really] Bad Idea.
- Create a regular, shared directory.
If you want it to stay hidden, append "$" to the Share name but, as
above, I would suggest this is not ideal ("Security through
Obscurity" is rarely effective).
- Create a Domain Group to hold the Users who should have access to this Share.
If you really want to allow Everyone access to it, then you can use "Everyone", but I would question this as well. What is the purpose of this file share? For what will it be used?
- Grant permissions on the Share and the underlying Directory to that Group.
... the registry settings are not accessible ...
Assuming you mean the Windows Registry ...
Why are End Users doing anything with [Windows] Registry settings??
This is especially critical because, armed with their current, Administrative credentials, that can basically destroy the server.
I think you need to take some time and reevaluate what you're trying to achieve.
Ask yourself: What [Business] Problem are you trying to solve?