The procedure below no longer applies to the current version of K2.net SQL User Manager (v3.4201.1.0).
Click the following link for more information: http://forum.k2workflow.com/viewtopic.php?t=44

============================
Here's a procedure to perform an installation of K2.net SQL User Manager (3.3322.1.0) on a distributed K2.net installation (K2.net Server and SQL Server sitting in separate machines).

You will need to have the "sa" account to SQL Server ready for the installation process. For installing SQLUM onto a distributed K2.net installation, the SQLUM database must first be installed locally onto the K2.net Machine, and then moved to the SQL Machine manually. Therefore, SQL Server will be required on the K2.net Machine to facilitate this.

K2.net Machine's software requirements:
- Windows 2003 Server (Standard or Enterprise)
- IIS 6.0
- SQL Server 2000 SP3a
- VS.NET 2003 (optional)

1. SQL Machine: Perfom custom install of K2.net 2003 Server, install only the K2 and K2Log databases.
2. K2.net Machine: Perfom custom install of K2.net 2003 Server, pointing to the K2 DBs on SQL Machine.
3. K2.net Machine: Apply K2.net Server Hotfix (3.3282.1.0)
4. K2.net Machine: Install SQLUM Server (3.3322.1.0) component, using K2 DB on SQL Machine, and putting K2SQLUM DB on K2.net Machine.
5. K2.net Machine: Start K2.net Server from the Program Group link. See that it loads without errors.
6. K2.net Machine: Test Workspace, sign-in using "K2" user, empty password. If you can access Workspace, SQLUM is working properly.
7. K2.net Machine: Install SQLUM Studio template component (if this machine has K2.net Studio installed)
8. K2.net Machine: Stop K2.net Server by closing the console window.
9. K2.net Machine: Using SQL Enterprise Manager, detach the K2SQLUM database, such that the physical database files can be copied to the SQL Machine.
10. K2.net Machine: Copy the SQLUM database files (K2SQLUM_Data.mdf and K2SQLUM.ldf) in C:Program FilesK2.net 2003Data to the same folder in the SQL Machine.
11. SQL Machine: Using SQL Enterprise Manager, attach the K2SQLUM database using the K2SQLUM_Data.mdf file.
12. K2.net Machine: Goto the K2 database, open _Setting table, edit UMData record to the value "<SQL Machine name>,K2SQLUM,sa,<password>", where <SQL Machine name> and <password> denotes the SQL Machine hostname and the sa account password respectively.
13. K2.net Machine: Start K2.net Server in console mode.
14. K2.net Machine: Test Workspace, sign-in using "K2" user, empty password. If you can access Workspace, SQLUM is working properly for the distributed K2.net topology.

You may proceed to add more users to the K2SQLUM.Users table to test the Workspace.