<?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: Moving Alfresco to new AD Domain after AD Migration in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/moving-alfresco-to-new-ad-domain-after-ad-migration/m-p/216074#M169204</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Ok, just for testing i brought up a copy of the Alfresco-VM to the new domain and created a user whith the same userename as in the old domain - voila, it works. So i guess Alfresco works only with the sAMAccountName so the users haven't to be migrated. Creating them with their old usernames should do the trick.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Well, but now i run into another problem: the new company should use its own naming convention, so if all users get login names wich differ from the old ones they won't be able to login anymore. If Alfresco is configured to use the new OU structure and the new groups, the won't get their self modified dashboards after login. But Alf Share shouldn't be the problem, all access rights are granted via AD groups. But what's with the Alf Web Client, if there has anybody setted its own rights for workspaces?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 24 Feb 2010 12:25:26 GMT</pubDate>
    <dc:creator>mfischer</dc:creator>
    <dc:date>2010-02-24T12:25:26Z</dc:date>
    <item>
      <title>Moving Alfresco to new AD Domain after AD Migration</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/moving-alfresco-to-new-ad-domain-after-ad-migration/m-p/216073#M169203</link>
      <description>Hey Folks,today i have a very special question belonging to the AD integration of Alfresco. We're using ALF 3.2r on Ubuntu 8.04 Server, users are authenticated against a Active Directory Domain.Due to fusing with another company we're going to migrate our Active Directory objects to a new forest wer</description>
      <pubDate>Wed, 24 Feb 2010 08:43:10 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/moving-alfresco-to-new-ad-domain-after-ad-migration/m-p/216073#M169203</guid>
      <dc:creator>mfischer</dc:creator>
      <dc:date>2010-02-24T08:43:10Z</dc:date>
    </item>
    <item>
      <title>Re: Moving Alfresco to new AD Domain after AD Migration</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/moving-alfresco-to-new-ad-domain-after-ad-migration/m-p/216074#M169204</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Ok, just for testing i brought up a copy of the Alfresco-VM to the new domain and created a user whith the same userename as in the old domain - voila, it works. So i guess Alfresco works only with the sAMAccountName so the users haven't to be migrated. Creating them with their old usernames should do the trick.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Well, but now i run into another problem: the new company should use its own naming convention, so if all users get login names wich differ from the old ones they won't be able to login anymore. If Alfresco is configured to use the new OU structure and the new groups, the won't get their self modified dashboards after login. But Alf Share shouldn't be the problem, all access rights are granted via AD groups. But what's with the Alf Web Client, if there has anybody setted its own rights for workspaces?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Feb 2010 12:25:26 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/moving-alfresco-to-new-ad-domain-after-ad-migration/m-p/216074#M169204</guid>
      <dc:creator>mfischer</dc:creator>
      <dc:date>2010-02-24T12:25:26Z</dc:date>
    </item>
  </channel>
</rss>

