Monday, December 1, 2014

DocAve 6 Manager for SharePoint 2013: Installation Guide


This posting walks through the process of preparing for and installing DocAve 6 Manager for SharePoint 2013.  Preparing for DocAve Manager involves configuring account permissions in three areas: local, SQL and SharePoint; and adding the Web Server Role to the prospective server to be used for hosting DocAve Manager.  This guide presents steps for installing to Windows Server 2012, on Hyper-V 2012, where servers are configured with both external and private networking.

Step 1: Identify Resources
  1. Identify the server that you want to use as the DocAve Manager management server.
  2. Verify that this server meets the following technical requirements:
    1. 54-bit, 4 cores
    2. 4 GB RAM
    3. 60 GB HD
Step 2: Create new domain account for DocAve Manager agent service
  1. Create new domain account for DocAve SharePoint Agent, for example, spDocAve
Step 3: Provision DocAve agent service account
  1. Provision local permissions for account
    1. Add the DocAve agent service account to local Administrators group on each farm server.
  2. Provision SQL Server permissions
    1. Grant dbcreator and securityadmin roles on farm SQL Server
    2. Grant db_owner role on all farm databases
  3. Provision SharePoint permissions
    1. Add to Farm Administrators group
      1. Central Administration > Security > Manage the farm administrators group
    2. Grant Full Control and Operates as System account all web applications
      1. Central Administration > Application Management > Manage Web Applications
    3. Grant Create Personal Site, Follow People and Edit Profile and Use Tags and Notes permissions to the User Profile Service Application.
      1. Central Administration > Application Management > Mange Service Applications > User Profile Service (click on it) > People > Manage User Permissions
    4. Grant Term Store Administrator to Managed Metadata Service
      1. Central Administration > Application Management > Mange Service Applications (select, don't click) > Administrators
    5. Grant Full Control to Search Service application
      1. Central Administration > Manage Service Applications > Search Service (select only) > Administrators
Step 4: Configure Firewall
  1. If your farm has both external and private networks (with private unrestricted), configure exception for port 14000 on external NIC to enable management interface access.
  2. If the farm has only one network, need to configure port exceptions as indicated in DocAve documentation.
Step 5: Configure Server
  1. Roles
    1. Add Web Server (IIS)
      1. Application Development
        1. ASP.NET 3.5
        2. .NET Extensibility 3.5
        3. ISAPI Extensions and ISAPI Filters
      2. Management Tools
        1. IIS Management Console
        2. IIS6 Management Compatability
        3. IIS6 Metabase Compatability
  2. Features
    1. .NET Framework 3.5.1
    2. HTTP Activation
    3. Non-HTTP Activation
    4. WCF Services
    5. TCP Port Sharing (and started)
    6. Common HTTP Features
      1. Static Content
      2. Default Content
    7. PowerShell 2.0 or greater
  3. Services
    1. Windows process Activation Service
      1. Started
      2. Process Model, .NET Environment and Configuration APIs installed
    2. WWW Publishing Service
      1. Started
    3. IIS Admin Service
      1. Started
Step 6: Install DocAve Manager
  1. login to the prospective DocAve management server using the SharePoint Setup User Administrator account (eg, spAdmin).
  2. Download the DocAve Management software (zip), and save locally.
  3. Extract locally.
  4. Right-click Setup.exe and run as administrator.
Step 7: Intall DocAve Agent
  1. Login to a SharePoint farm server using the SharePoint Setup User Administrator account (eg, spAdmin).
  2. Verify that your designated DocAve agent service account has been added to the local Administrators group.  If it's not, add it.
  3. Download the DocAve Management software (zip), and save locally.
  4. Right-click Setup.exe and run as administrator.
Step 8: Setup Administrator Access to DocAve (for NTLM)
  1. Launch the DocAve management interface.
  2. Login (default: admin/admin).
    OOTB, there is a single local administrative account, admin, that enables you to access the DocAve Control Panel. To add domain accounts, you must first configure DocAve to recognize NTLM authentication.
  3. Click a Control Panel link.
  4. In the Authentication Manager group, click Authentication Manager.
  5. On the Ribbon, in the Integration group, click Windows Authentication.
  6. From the Authentication Type dropdown, select NTLM.
  7. Click OK.
  8. On Control Panel, in the Account Manager group, click Account Manager.
  9. On the Ribbon, in the View group, click Users.
  10. On the Ribbon, in the Actions group, click Add User.
  11. From the User Type dropdown, select Windows User/Group Name.
  12. In the Windows User/Group Name box, enter a user account as DOMAIN\UserName.
  13. In the Group area, select the Add user to administrators group radio button.
  14. Click OK.
  • The Installation UI is buggy.  You'll find that if you use the TAB key, the cursor focus can disappear, even when tabbing from one adjacent field to the next.  It's also possible to put the installation wizard into a permanently ambiguous state, from which the only exit is to terminate it and start over.
  • Invalid username/password.  I found that during the intsallation, at the Control Service Configuration panel, after entering the username and password I wanted to use for a new application pool, I kept experiencing invalid username/password errors.  On a hunch, I added the DocAve agent service account to the local Administrators group and then tried again: success. This is mentioned in the DocAve Installation guide at page 23, first sentence.
  • Installation Rule Scanning: Web Server (IIS) Role: Failed.  If you see this rule violation,
    it is likely due to not installing the IIS 6 Management Compatibility and the ASP.NET 3.5 features, which are not default role features installed automatically.  This rule violation will be accompanied by the IIS Admin Service rule violation.  This is because the IIS Admin Service is only installed when IIS 6 compatibility features are installed.  It's easy to check.  Just launch the Add roles and features tool.  Then expand Web Server (IIS) > Web Server > Application Development.  ASP.NET 3.5, ISAPI Extensions and ISAPI Filters won't be installed. Checking the box for ASP.NET 3.5 will automatically also select the other two.  Next, expand Web Server (IIS) > Web Server > Management Tools > IIS 6 Management Compatibility:
    Check the box for IIS 6 Management Compatibility; then complete installation.
  • Page Not Found!!  If you see this when you fire up the DocAve UI for the first time, don't panic. Check the IE Enhanced Security Configuration setting.  If it's enabled, this will block the UI scripts from executing.  Disabled this setting and try again.

1 comment:

Robert said...

This is wonderful! I was having issues getting DocAve to run but after going through this walk-through, it is now working. Thank You Al!