Upgrading from ActiveShareFS 2010 v5.3 and older

ActiveShareFS 2010 version 5.3.x and below uses the old configuration format. You will need to convert the old configuration to the new configuration manually. You should be able to achieve the same functionality using the new format except for the ability to remove a user from a SharePoint group. This feature is not supported in v5.4.x.

When upgrading from v5.3.x and older, the upgrade process will be more like a new install. Here are the general steps to take when upgrading. Note that this will require downtime for the webapp.:

  1. Backup a copy of <ASFS_HOME>/etc/asfs.xml in a safe place. You will need it in order to manually convert your configuration to the new format.
  2. Uninstall ActiveShareFS via the control panel.
  3. The uninstaller will not remove the <ASFS_HOME>/etc directory nor its contents. You will need to manually delete this directory in order for the new installer to replace files.
  4. Install the new version using the same installation path as the previous one. Run the installer as administrator. The installer should have populated the <ASFS_HOME>/etc with four files:
    1. asfs.xml – default configuration file.
    2. asfs.xsd – schema file used for validation
    3. asfs-example.xml – example configuration file for reference
    4. web.config.template.xml – for easy copy/pasting elements within the ASFS-enabled web.config
  5. Make a backup of the web.config of the ASFS-enabled webapp.
  6. Go to Central Administration, Manage Web Applications, Select the ASFS-enabled webapp, Authentication Providers, Select the ASFS-enabled zone, Select Custom Sign In Page, and use the value: /_layouts/ASFSLoginPage.aspx
  7. The above step may have reset the web.config of the ASFS-enabled webapp. Please follow the instructions here to reconfigure the web.config. The main difference in the new version is that we do not replace Microsoft’s SPClaimsAuthRoleProvider under the <roleManager>. It should look like the following:
    <membership defaultProvider="i">
      <providers>
        <add name="i" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthMembershipProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
        <add name="smp" type="ActiveShareFS.Providers.ShibbolethMembershipProvider, ActiveShareFS, Version=1.0.0.0, Culture=neutral, PublicKeyToken=4399a4b0b78bd79c" applicationName="/" />
      </providers>
    </membership>
    <roleManager defaultProvider="c" enabled="true" cacheRolesInCookie="false">
      <providers>
        <add name="c" type="Microsoft.SharePoint.Administration.Claims.SPClaimsAuthRoleProvider, Microsoft.SharePoint, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
        <add name="srp" type="ActiveShareFS.Providers.ShibbolethRoleProvider, ActiveShareFS, Version=1.0.0.0, Culture=neutral, PublicKeyToken=4399a4b0b78bd79c" applicationName="/" />
      </providers>
    </roleManager>
  8. Copy <ASFS_HOME>/layouts/ASFSLoginPage.aspx to the hive’s LAYOUTS directory if not already done so.
  9. Convert your old asfs.xml configuration to the new one.
  10. Restart the shibd service and recycle the AppPool of the ASFS-enabled webapp.
  11. Test login.