This section will describe the process for configuring the server control program to communicate with an IIS web server to create personal home pages. The process is similar to that described in the NT User Manager section.
In the following example, we will set up the server control program to create personal homepage accounts on an IIS web server. The following steps outline the process for configuring the above example.
1. Install the plug-ins on the remote server.
The best way to do this is to run the server control installation file on the remote server. It does not matter what directory you install the files into.
2. Register the IISHomepage plug-in on both web servers.
To register the plug-in, right-click on the SCPWeb.exe file and select Register Component.
In addition, register the SCPFram.dll and the SCPAsync.exe files in the same manner.
3. Configure DCOM on the web server, and install ADSI on both servers.
ADSI must be installed on both servers, and DCOM must be configured on the web server.
4. Create a "user" or "home" directory in the Inetpub directory.
This directory will contain you users’ web files. The directory can be called anything, as long as you remember the directory name for later reference. In our example, let’s call this directory, "Home."
5. Set the proper permissions for the Home directory.
For the directory you just created in #4, set the proper permissions. You will want to give the Administrator group and the System group full control. You will also want to give Read only access to whatever group your web page customers will belong to. This group will most likely be "Users" unless you have customized the configuration settings to add them into another group. In the example below, the figure shows that we have created a user group called Test Group. To this group, we have granted Read-only access to the Home directory.
Grant permissions to user directory – IIS Example
6. Create a virtual directory on the web server.
Go into the Microsoft Internet Information Server and create a new virtual directory for the user home pages. The directory path should correspond with the folder created in #4. In the figure below, note how the directory path is "C:\inetpub\wwwroot\home". Also, make sure you set the permissions to "Read" and "Script" access.
Create a virtual directory on the web server
7. Create a virtual directory on the FTP server.
Go into the Microsoft Internet Information Server and create a new virtual directory for FTP. Again, the directory path should correspond with the folder created in #4. Make sure this directory has "Read" and "Write" access.
8. Change the security setting of the FTP site.
In the IIS Internet Service Manager, go to the Properties box of the FTP site. If you have not changed it, the default FTP site should be "Default FTP Site." Go to the Security Accounts tab, and uncheck mark the "Allow Anonymous Connections" option. This is because we do not want to allow anonymous access to the FTP sites, since only account users should be able to log in.
9. Set Read access permission to the FTP root directory for the appropriate User Group.
Using Windows Explorer, find the FTP root directory, and go to the Properties box. The default FTP root directory is "C:\inetpub\ftproot". Make sure that the user group specified in #5 has at least Read permission to this directory.
10. Configure the Web server.
Go to the Server Control server, and configure the web server in the Server Control – Servers section.
Server Control – Servers – IIS Example
11. Configure the required parameters
Configure the required parameters as you normally would.
Server Control – Server Parameters – IIS Example
|
|
Although the parameters RootDir and UserGroup are not required, configuring them will cause the values in the Server Parameters section to override the default values in the Server Type Parameters section. |
12. Create a server group for web services.
13. Map the server group created in #12 to the web server.
Server Control – Server Group Mapping – IIS Example
14. Assign the appropriate service types to the server group.
Let’s now assign the appropriate service type to the server group we created in #12..
Service Type Configuration – IIS Example
15. Launch the server control program
If everything has been configured properly, the server control program will connect to the remote server and initialize. Click Start to begin processing. The server control program will remain in this status until an event triggers it.
