1

This document explains how to configure an IIS Web server to run AM.NET. The steps below detail how to set up Web directories and folders that enable AM.NET to run correctly from an IIS Web server. AM.NET can use the internal IP address for your web server and the internal IP Address for your Sql Server. If you use AM.NET remotely then the external IP address for the web server is used too. Using a DNS is preferred though in case you ever change the ip address and\or change the server. Changing eithe r of these IP addresses will break AM.NET. AM.NET also uses your web server for sending emails. The web server must have Internet access. In order for us to build your client install file we will need the following information:

• Internal DNS or ip address for the web server AM.NET will be installed on • External DNS or ip address for the web server AM.NET will be installed on. • IP Address or machine name for SQL Server • New SQL Server Id named “AmNetUser”. Please let us know the password.

After completing the steps below, please contact Greg Robinson or Larry Austin at CDS regarding copying the AM.NET files to your Web server. We can copy the files for you or walk you through the process of copying the files. If you have any questions regarding the steps below, please contact Greg Robinson at CDS: greg@cds-am.net 804.422.6730 Creating the AM.NET IIS Web folders

1. Open windows explorer on the Web server that will host the assemblies 2. Create a directory under Inetpub\wwwroot named “AMNET”

2

3. Create two folders, one named “Client” and one named “Server” under “AMNET”

4. Create a folder under the “Server” folder named “bin”. 5. Create a folder under the “Client” folder named “ReportLayouts”

a. Create the following folders under the “ReportLayouts” folder: “Common Layouts”, “Dues”, “Events”, “Firms” and “Names”.

Creating a Virtual Root in IIS

3

1. Open Internet Services Manager 2. Select the Web site that will host AM.NET (Default or custom Web sites) 3. Right click on the AMNET\Server folder and chose Properties

4. Click the Create Button and set the Application name to “AMNETServer”

4

5. Click Apply 6. Click OK 7. Open the “Server” virtual directories properties window by right clicking on

“Server” and selecting Properties

a. Chose the Directory Security tab and click Edit

5

b. Make sure that Allow Anonymous is checked

i. The User Name: value in the below screenshot is from CDS’s development Web server. Do not use this value. Leave the default value.

6

If you are running IIS 6.0 on the Web server (Windows 2003), you will need to do the following:

• http://support.microsoft.com/default.aspx?scid=kb;en-us;326965

• Define a MIME type for “.remoteconfig” and set the MIME Type = application/octet-stream

• Restart IIS after doing this If the Web server’s OS is Windows 2000, you will need to install the .NET Framework. First check to see if it’s already installed.

• Check to see if this directory exists on the Web server: C:\WINNT\Microsoft.NET\Framework

o If it does, make sure you see C:\WINNT\Microsoft.NET\Framework\v1.1.4322 § If you do not see the v1.1.4322 folder, you will need to install v 1.1

of the framework. • http://www.microsoft.com/downloads/details.aspx?FamilyI

d=262D25E3-F589-4842-8157-034D1E7CF3A3&displaylang=en

o If this directory does not exist then you need to install the .NET

Framework § http://www.microsoft.com/downloads/details.aspx?FamilyId=262

D25E3-F589-4842-8157-034D1E7CF3A3&displaylang=en If the web server’s OS is Windows 2003 with SP1 you will need to update any client machines running Windows XP.

• Windows 2003 SP1 installs a newer version of a dll that is used by AM.NET. Windows XP client machines need to install a hotfix that installs the newer version of this dll.

o Call Microsoft support at 1-800-MICROSOFT. Tell them you need the Hotfix for Knowledge Base (KB) article 887549.

MDAC 2.6 or higher is required on the web server

• We recommend you have MDAC 2.8 installed on the web server. 2.6 or higher is required.

• http://www.microsoft.com/downloads/details.aspx?FamilyID=6c050fe3-c795-4b7d-b037-185d0506396c&displaylang=en

7

Configure the Default SMTP Virtual Server on the Web Server

• If the Default SMTP Virtual Server is not installed on your Web server

Then you will need to install it. Go here http://support.microsoft.com/default.aspx?scid=kb;en-us;308161 for assistance on how to install this.

• We suggest you restrict access to the Default SMTP Virtual Server. This will prevent folks from the outside from using it as a relay mail server. Restricting access is not a requirement for AM.NET. AM.NET will use the Default SMTP Virtual Server when it needs to send emails. However, once you install the Default SMTP Virtual Server, anyone can use it as a relay mail server. See this link if you do not understand how the Default SMTP Virtual Server works and behaves:

o http://www.resortdata.com/Customers/Knowledge/KB-Crystal/KC00003.htm

• To restrict access to the Default SMTP Virtual Server, go to IIS Manager.

1. Right click on the Default SMTP Virtual Server and select Properties.

8

2. Click on the Access Tab.

3. Click on the Connection... button.

9

4. Leave "Only the list below" selected.

5. Click Add and add the internal ip address for that machine (the Web server) to the list.

§ “10.1.1.117” in the above screen shot is the internal IP Address for

CDS’s development Web server, do not use this ip address

6. Click OK, click Apply.

7. Do the same thing for the Relay button.

10

• Now, only folks that have access to that machine by internal ip (which AM.NET will have) can send emails through the Default SMTP Virtual Server.

• Create a *.com Domain 1. Right click on Domains, click New, click Domain… 2. Select Remote 3. Click Next, in the Name: textbox enter “*.com” 4. Click Finish 5. Repeat these 4 steps for “*.org” and “*.net”

If we sent you the AM.NET files to copy to your web server, do the following:

• Copy all of the files (dlls, exe, remoteconfig) to the AMNET\Client web folder. Do not copy AM.NET.msi to this folder

• Copy the following dll files to the AMNET\Server\bin folder (these can be found in the AMNETAssemblies folder):

1. CDSDataAccess.dll

11

2. DataAccessGeneral.dll 3. CDSSecurity.dll 4. CustomDataSystems.AMNET.DataEntities.dll

**Note – There is a known Microsoft bug with installing WSUS and running applications like AM.NET.

• WSUS turns on compression • AM.NET is not able to download the code files from the web server with

compression turned on • The workaround is to turn off compression on the web server • Another option is to go to IEàToolsàInternet OptionsàAdvancedàUncheck

Use HTTP 1.1 and Use HTTP 1.1 through proxy connections