<div>
There isn't a performance hit<br />
<br />
I'd just use DFS instead, Set up some namespaces and then map those using Group policy preferences.
</div>


There isn't a performance hit

I'd just use DFS instead, Set up some namespaces and then map those using Group policy preferences.

System Architect

Eprs_Admin

<div>
Users' machines shouldn't have shares. It's too risky.<br />
Shares belong on servers.
</div>


Users' machines shouldn't have shares. It's too risky.
Shares belong on servers.

A lack of information provides a lack of a decent solution.

Alex

<div>
Hi McKnife,<br />
<br />
of course all my shares on a server.
</div>


Hi McKnife,

of course all my shares on a server.

<div>
1. is it useful for users to do that ?<br />
<br />
<br />
Is indicative you want users to create shares, that's where the confusion is.
</div>


1. is it useful for users to do that ?


Is indicative you want users to create shares, that's where the confusion is.

<div>
I just want to know , does somebody publish the shares into AD ?<br />
What is the advantage ?<br />
Do I need that ?
</div>


I just want to know , does somebody publish the shares into AD ?
What is the advantage ?
Do I need that ?

<div>
Hi Kevin,<br />
<br />
when I create a namespace I also create shares.<br />
What are you doing with these shares ? You especially hide them ?<br />
So just over the namespace they visible ?
</div>


Hi Kevin,

when I create a namespace I also create shares.
What are you doing with these shares ? You especially hide them ?
So just over the namespace they visible ?

<div>
Alex , no, no user creates shares here.<br />
I mean, is it useful for the users when the share is published to AD ?
</div>


Alex , no, no user creates shares here.
I mean, is it useful for the users when the share is published to AD ?

<div>
The publishing is useful if users are &quot;dumb&quot; as in &quot;I know the share is named 'whatever', but I don't know what server its hosted on&quot;. See? Only if users are like that, they would need to query AD. So don't publish, but rather use DFS.
</div>


The publishing is useful if users are "dumb" as in "I know the share is named 'whatever', but I don't know what server its hosted on". See? Only if users are like that, they would need to query AD. So don't publish, but rather use DFS.

<div>
I wouldn't even bother doing it via AD and I would force the share via DFS and Group policy preferences with Item-Level targeting.
</div>


I wouldn't even bother doing it via AD and I would force the share via DFS and Group policy preferences with Item-Level targeting.

<div>
Hi Kevin,<br />
<br />
as far as I understand , each share of you is a hidden share ?<br />
And you will publish the shares just over DFS, right ?<br />
<br />
If I am right, this sounds quite good for me.
</div>


Hi Kevin,

as far as I understand , each share of you is a hidden share ?
And you will publish the shares just over DFS, right ?

If I am right, this sounds quite good for me.

<div>
Hi Alex,<br />
<br />
ok, I will also use DFS for sharing now.<br />
But can you explain, what are you doing with GPO and DFS shares ?<br />
Can you give me an example ?
</div>


Hi Alex,

ok, I will also use DFS for sharing now.
But can you explain, what are you doing with GPO and DFS shares ?
Can you give me an example ?

<div>
what is recommended ?<br />
<br />
Shall I always hide shares and just share in DFS ?
</div>


what is recommended ?

Shall I always hide shares and just share in DFS ?

<div>
<div class="content wysiwyg-content">
Hi experts,<br />
<br />
I have a question about shares and publish them to AD ?<br />
Is it useful to publish shares in AD ?<br />
<br />
1. is it useful for users to do that ?<br />
2. What kind of benefit I have when I publish a share to AD ?<br />
3. Do I get performance issues when I use it ?
</div>
</div>


Hi experts,

I have a question about shares and publish them to AD ?
Is it useful to publish shares in AD ?

1. is it useful for users to do that ?
2. What kind of benefit I have when I publish a share to AD ?
3. Do I get performance issues when I use it ?

publish a windows share

Active Directory (AD) is a Microsoft brand for identity-related capabilities. In the on-premises world, Windows Server AD provides a set of identity capabilities and services, and is hugely popular (88% of Fortune 1000 and 95% of enterprises use AD). This topic includes all things Active Directory including DNS, Group Policy, DFS, troubleshooting, ADFS, and all other topics under the Microsoft AD and identity umbrella.

Active Directory

Windows 10 is a personal computer operating system featuring the "universal application architecture" (UAP); apps can be designed to run across multiple devices with nearly identical code, including PCs, tablets, smartphones, embedded systems, Xbox One, Surface Hub and HoloLens. Windows 10 also includes a virtual desktop system, a window and desktop management feature called Task View, the Microsoft Edge web browser, support for fingerprint and face recognition login, voice-based search (Cortana), new security features for enterprise environments, and DirectX 12 and WDDM 2.0 to improve the operating system's graphics capabilities for games.

Windows 10

Microsoft Azure is a cloud computing platform and infrastructure for building, deploying and managing applications and services through datacenters. It provides both platform-as-a-service (PaaS) and infrastructure-as-a-service (IaaS) services and supports many different programming languages, tools and frameworks, including both Microsoft-specific and third-party software and systems. Cloud Services is a PaaS environment and can be used to create scalable applications and services; there are specific software development kits (SDKs) provided by Microsoft for Python, Java, Node.js and .NET. Azure also has file and storage services, data management, analytics and DNS services.

Azure

Windows Server 2016 is the successor to Windows Server 2012 R2. Built upon the same core code as Windows 10, Windows Server 2016 brings enhancements in security, servicing, and connectivity. A particular focus on this release was hybrid-cloud scenarios, and has close ties to Azure and other Microsoft cloud initiatives. This does not detract from the many improvements that are available for on-premises-only deployments

Windows Server 2016 comes in Datacenter, Standard, and Essentials editions, and for servicing, has adopted windows 10's cumulative model. The new nano-server install is designed to be remotely managed and is designed to be kept current through continuous feature updates. The full GUI install operates similarly to windows 10's "Long Term Servicing Branch" (LTSB) model with cumulative security updates.

Windows Server 2016 has also shifted from a per-processor-and-CAL licensing model to a per-core-and CAL licensing model. This brings Windows Server's licensing more in line with Microsoft's other products and makes hybrid-cloud license planning easier as well.