Step 2 - Enable Web-Installer

1. Follow step by step instructions located under "Enable Installer" here: http://docs.communityserver.org/default.aspx/CS.WebBasedInstaller. This will be ONLY done for initial install.

Step 3 - Run Installer

1. After enabling installer in Step 2, go to your website either by IP Address (http://x.x.x.x/installer/) or your domain name (http://YourDomain.com/installer/). 2. 2. Follow instructions located under Detailed Steps at this link http://docs.communityserver.org/default.aspx/CS.WebBasedInstaller You'll use database login information gathered at beginning.

Step 4 - Run and Enjoy

1. In your web browser, go to root of your website and enjoy. You will be required to log in for administrative features. Use username and password you set up while installing Community Server.

Note: To run in a sub-folder

* When completed with your install, send an email to webteam@orcsweb.com and we'll grant write permissions on 'blogs' and 'photos' directories. * Community Server can also be installed in a sub-folder of your site (http://YourDomain.com/subFolder) . Just send an email to webteam@orcsweb.com to mark folder as an application.

Steve Schofield is a Senior Internet support specialist with ORCS Web, Inc. - a company that provides managed hosting services for clients who develop and deploy their applications on Microsoft Windows platforms.

Attaching Database

1. Right-click database, select 'All Tasks', and then click 'Attach Database…'. 2. Navigate to data file by clicking button that has 3 dots on it (…). 3. Once you've selected database .mdf file, you'll see data file path (which should be verified for both data and transaction log file) and have option to choose database name and owner. Attach it as database name, and ensure owner name is 'sa'. 4. Verify path for transaction log file is correct. If path isn’t correct, update it to appropriate directory. 5. Click ‘OK’.

Note: If you didn't move transaction log file to new server with data file, you'll be prompted to create a new one. If you choose to create a new one, it will be done for you automatically.

Orphaned Users

If database user doesn't exist on new server, create it now. When creating it, you may receive an error that it already exists, but that's ok, work that needs completed by SQL Server to add user account is done. After you receive error that user already exists, press cancel and continue on to next user.

Moving database to a new server will result in orphaned users. You will need to run a stored procedure that will map user in database to a user on server. This stored procedure will change relationship between a Microsoft SQL Server login and a SQL Server user in current database. Basically, it changes SID in database to match one generated by local server, which allows all custom permissions to be retained - it remembers access and permissions.

1. Open Query Analyzer. 2. Select database in drop-down box on tool bar if it isn't already selected. 3. For each database user, we'll need to execute command: "sp_change_users_login 'update_one', 'db_username', 'db_username'*" (without double-quotes).

*change db_username to actual database username in both places.

Now update any connection strings to point to new SQL server (this could have been done while database was moving between servers to utilize all available time) and test it well. Also, check any DTS jobs, Full-Text Indexes and Replication configurations to ensure that they are set up on new server as they won't fully move during this process. Now you should be set. Test it well and sit back, relax and reflect on a job well done.

Sources: http://vyaskn.tripod.com/moving_sql_server.htm http://www.databasejournal.com/features/mssql/article.php/2224361 http://vyaskn.tripod.com/troubleshooting_orphan_users.htm

Desirée Harris is a support specialist with ORCS Web - a company that provides managed hosting services for clients who develop and deploy their applications on Microsoft Windows platforms.