<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Migrating to Enterprise Logins in ArcGIS Online Questions</title>
    <link>https://community.esri.com/t5/arcgis-online-questions/migrating-to-enterprise-logins-beta/m-p/140123#M6899</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Wanted to expand on the discussion of transfer of &lt;/SPAN&gt;&lt;SPAN style="text-decoration:underline;"&gt;group ownership&lt;/SPAN&gt;&lt;SPAN&gt; and &lt;/SPAN&gt;&lt;SPAN style="text-decoration:underline;"&gt;group membership&lt;/SPAN&gt;&lt;SPAN&gt; as these are not trivial.&lt;/SPAN&gt;&lt;BR /&gt;&lt;UL&gt;&lt;BR /&gt;&lt;LI&gt;The admin would also have to manually transfer &lt;STRONG style="text-decoration: underline;"&gt;ownership&lt;/STRONG&gt; of all users' groups to their new enterprise accounts during a migration to enterprise logins.&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;Group &lt;STRONG style="text-decoration: underline;"&gt;membership&lt;/STRONG&gt; would also have to be re-created for each new enterprise user account.&amp;nbsp; The admin would have to add the new enterprise account to all the groups the original account was a member of.&lt;/LI&gt;&lt;BR /&gt;&lt;/UL&gt;&lt;SPAN&gt;In the case of both ownership and membership, the admin would need to somehow (manually or through a custom script/tool using the Portal API) determine all the groups the old AGO account owned or was a member of.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Mar 2013 17:44:22 GMT</pubDate>
    <dc:creator>OwenGeo</dc:creator>
    <dc:date>2013-03-27T17:44:22Z</dc:date>
    <item>
      <title>Migrating to Enterprise Logins (Beta)</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/migrating-to-enterprise-logins-beta/m-p/140122#M6898</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN style="color: #000000; font-family: Avenir;"&gt;Below are some questions/observations/feedback on migrating to enterprise logins.&amp;nbsp; This applies to any customer that started using ArcGIS Online with AGO accounts and/or Esri Global IDs and wishes to migrate to using enterprise logins based on SAML (new in March 2013 release).&lt;BR /&gt;&lt;/SPAN&gt;&lt;OL&gt;&lt;BR /&gt;&lt;LI&gt;&lt;SPAN style="color: #000000; font-family: Avenir;"&gt;Migrating content/groups&lt;/SPAN&gt;&lt;/LI&gt;&lt;BR /&gt;&lt;UL&gt;&lt;BR /&gt;&lt;LI&gt;&lt;SPAN style="color: #000000; font-family: Avenir;"&gt;When someone who has previously used ArcGIS Online with an existing organizational user account logs in for the first time with their enterprise account they essentially start over using a brand new account.&amp;nbsp; This means there is nothing in their "My Content" area and they are not a member/owner of any groups; all their content/groups must now be migrated by an Admin from the person's previous AGO account to their new enterprise account.&lt;/SPAN&gt;&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;&lt;SPAN style="color: #000000; font-family: Avenir;"&gt;�??&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Avenir;"&gt;With no migration process or official (or community sanctioned, maybe the &lt;A href="http://esrifederal.maps.arcgis.com/home/item.html?id=c7a3df4b77f042e09132ebc335f6544f"&gt;AGOL Assistant&lt;/A&gt; is a candidate?) migration tool, this puts a heavy burden on the &lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Avenir;"&gt;admin&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Avenir;"&gt; that increases as the number of users increases.&amp;nbsp; As the admin of an org account with ~130 members, I have to say I'm not looking forward to migrating everyone's groups and content (including all their My Content subfolder structure).&lt;/SPAN&gt;&lt;/LI&gt;&lt;BR /&gt;&lt;/UL&gt;&lt;/OL&gt;&lt;LI&gt;&lt;SPAN style="color: #000000; font-family: Avenir;"&gt;�??&lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Avenir;"&gt;Managing user accounts&lt;/SPAN&gt;&lt;/LI&gt;&lt;BR /&gt;&lt;UL&gt;&lt;BR /&gt;&lt;LI&gt;&lt;SPAN style="color: #000000; font-family: Avenir;"&gt;Any person logging in with their enterprise account is treated as a new user account, so the number of "users" in the subscription could potentially double after enabling this feature.&amp;nbsp; This is something the admin must manage by either 1) purchasing more users, and/or 2) methodically removing user accounts as people migrate to their enterprise logins.&amp;nbsp; As a result of this, &lt;/SPAN&gt;&lt;SPAN style="color: #000000; font-family: Avenir;"&gt;I am also now considering a request to add more user accounts "just in case" we don't manage the migration to enterprise log-in properly so we don't exceed our current allotment of users.&lt;/SPAN&gt;&lt;/LI&gt;&lt;BR /&gt;&lt;/UL&gt;&lt;SPAN style="color: #000000; font-family: Avenir;"&gt;Ideally, it would be very useful for &lt;SPAN style="text-decoration:underline;"&gt;the system to migrate content/groups and clean up old AGO accounts during a person's initial login with their enterprise account&lt;/SPAN&gt;.&amp;nbsp; After the first login with an enterprise account, the user would be prompted asking them if they already have an account in the organization, then they'd be prompted for those credentials.&amp;nbsp; The &lt;SPAN style="text-decoration:underline;"&gt;content would then be migrated&lt;/SPAN&gt;, &lt;SPAN style="text-decoration:underline;"&gt;group ownership/membership would be transferred,&lt;/SPAN&gt; and &lt;SPAN style="text-decoration:underline;"&gt;the old account removed&lt;/SPAN&gt;.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Mar 2013 16:26:13 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/migrating-to-enterprise-logins-beta/m-p/140122#M6898</guid>
      <dc:creator>OwenGeo</dc:creator>
      <dc:date>2013-03-27T16:26:13Z</dc:date>
    </item>
    <item>
      <title>Re: Migrating to Enterprise Logins</title>
      <link>https://community.esri.com/t5/arcgis-online-questions/migrating-to-enterprise-logins-beta/m-p/140123#M6899</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Wanted to expand on the discussion of transfer of &lt;/SPAN&gt;&lt;SPAN style="text-decoration:underline;"&gt;group ownership&lt;/SPAN&gt;&lt;SPAN&gt; and &lt;/SPAN&gt;&lt;SPAN style="text-decoration:underline;"&gt;group membership&lt;/SPAN&gt;&lt;SPAN&gt; as these are not trivial.&lt;/SPAN&gt;&lt;BR /&gt;&lt;UL&gt;&lt;BR /&gt;&lt;LI&gt;The admin would also have to manually transfer &lt;STRONG style="text-decoration: underline;"&gt;ownership&lt;/STRONG&gt; of all users' groups to their new enterprise accounts during a migration to enterprise logins.&lt;/LI&gt;&lt;BR /&gt;&lt;LI&gt;Group &lt;STRONG style="text-decoration: underline;"&gt;membership&lt;/STRONG&gt; would also have to be re-created for each new enterprise user account.&amp;nbsp; The admin would have to add the new enterprise account to all the groups the original account was a member of.&lt;/LI&gt;&lt;BR /&gt;&lt;/UL&gt;&lt;SPAN&gt;In the case of both ownership and membership, the admin would need to somehow (manually or through a custom script/tool using the Portal API) determine all the groups the old AGO account owned or was a member of.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Mar 2013 17:44:22 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-online-questions/migrating-to-enterprise-logins-beta/m-p/140123#M6899</guid>
      <dc:creator>OwenGeo</dc:creator>
      <dc:date>2013-03-27T17:44:22Z</dc:date>
    </item>
  </channel>
</rss>

