The Community Server manual installation gives you complete control over what is installed and configured on your system.
The procedure below is for new installations of Community Server. To upgrade your existing package's web files and database, follow the directions provided in the upgraded version's read_me.txt file and how_to_setup_database.txt file (found in the "\SqlScripts" folder).
Telligent recommends that only advanced users use the manual installation method.
Procedure
1. Go to the following link to download Community Server: Download the Community Server Web installation package.
2. Extract the '\Web' folder from the .zip archive to your hard drive, for example c:\Inetpub\wwwroot\Web\.
3, Configure a new virtual directory in Internet Information Services (IIS) that points to the location of the 'Web' folder in Step 2.
4. Configure the virtual directory as an application by clicking on the 'Create' button located on the Virtual Directory tab of the Properties tab.
5. Configure Permissions.
Under the '\Web' folder you created in Step 2, give the [machine name]\ASPNET (or NT Authority\Network Service on Windows Server 2003) "Read" access to the "\Web" folder and "Full Control" access to the "filestorage" folder found in the "\Web" folder.
To apply these permissions open File Explorer and navigate to the install directory. Select each file/folder, right-click and select "Sharing and Security…" next select the "Security" tab. Finally apply the permissions listed above.
6. Create and Configure the Database by doing the following:
a) Create a new SQL Server database named 'CommunityServer'.
b) Grant your desired login access to the new CommunityServer database.
If you're using Windows Authentication, enable Integrated Security (you can run the user.sql file, only recommended for development/test machines)
If you're using Sql Authentication, use a database management tool (i.e. Enterprise Manager) to grant your SQL Login access to the new database.
Note: At a minimum, Community Server will require the following database roles:
db_securityadmin
db_ddladmin
db_datareader
db_datawriter
7. If you are running SQL Server 2005 or 2008 then execute the cs_CreateFullDatabase.sql script. If you are running SQL Server 2000 then you'll need to execute the sql scripts found in this SQL Server 2000 specific download.
8. Create a Community by running the cs_system_CreateCommunity stored procedure. For example:
exec dbo.cs_system_CreateCommunity 'localhost/cs', 'dev', '[email protected]', 'AdminUserName', 'AdminPassword', 0, 0
Where you replace "localhost/cs" with your URL, and replace the Admin account email, username and password with your desired values.
If you would like to have a sample blog and gallery created for you, change the last zero (0) to a one (1) in the line above. For example:
exec dbo.cs_system_CreateCommunity 'localhost/cs', 'dev', '[email protected]', 'AdminUserName', 'AdminPassword', 0, 1
9. Configure Connection Strings in the connectionStrings.config file. Ensure the SiteSqlServer entry contains the correct database connection information.
Unless I am mistaken, the folder privileges should be the same for the manual installation of community server. You reference photo and file galleries in the instruction, but they do not exist anymore.
"Assign privileges.
* The directory should also be configured as a web application in IIS with the "Read" and "Run Scripts" checkboxes checked for permissions.
* For the "web" folder, give the ASPNET (or NETWORK SERVICE) account read privileges.
* Give "Full Control" privileges on the filestorage folder (found in the web folder of your CS/Evolution installation):"