<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Managment on Janik von Rotz</title>
    <link>https://janikvonrotz.ch/tags/managment/</link>
    <description>Recent content in Managment on Janik von Rotz</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 25 Sep 2013 15:33:07 +0000</lastBuildDate>
    <atom:link href="https://janikvonrotz.ch/tags/managment/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Find dead SharePoint ActiveDirectory Groups</title>
      <link>https://janikvonrotz.ch/2013/09/25/find-dead-sharepoint-activedirectory-groups/</link>
      <pubDate>Wed, 25 Sep 2013 15:33:07 +0000</pubDate>
      <guid>https://janikvonrotz.ch/2013/09/25/find-dead-sharepoint-activedirectory-groups/</guid>
      <description>&lt;p&gt;The are three ways to handle access rights in SharePoint.&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;    &lt;li&gt;Using ActiveDirectory Groups&lt;/li&gt;&#xA;    &lt;li&gt;Using SharePoint Groups&lt;/li&gt;&#xA;    &lt;li&gt;Using both of them&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;p&gt;I personally recommend to use the first suggestion. Managing the access rights in one system is much easier to administrate, no switching or log off for administration work.&lt;/p&gt;&#xA;&lt;p&gt;In our SharePoint installation I create for each securable resource and rights type a ActiveDirectory group and assign them organization groups.&lt;/p&gt;&#xA;&lt;p&gt;A huge disadvantage of this strategy is that after a period of adding ActiveDirectory groups it&amp;rsquo;s hard to know which of those groups are really required.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
