Join Log in
Score:0
avatar Server

How to hide existing Windows shares - step-by-step

dz flag
fred3

We have a few file shares that users access directly using shortcuts or maps. We're converting to DFS-R and will continue to use the same share stores for the most part. Once done, we'd like the shares to not be browseable and are considering the accepted approaches - such as using a "$" suffix on the sharenames.

Example: \server\sharename becomes \server\sharename$ That's my understanding.

If we switch to DFS for a sharename then it seems it would be easy enough (without using GPP) to tell users they need to change: From: \server\sharename To: \[domain][namespace]\newsharename Something like that? AND THEN: folow up by adding the "$" suffix to the share. But then it seems we'd have to edit the DFS setup. If we add the "$" first, before the DFS setup is made and tested, then their current accesses won't work, will they?

So, I'm simply looking for the order in which this process is best done; or, a better process. (And for suggestions if my descriptions are somehow "off").

27
0 + 0
ธงชาติไทย
Elon Musk
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.