Windows Server Stuff
We are using Akcelerant for collections purposes and during the course of administering this application, I have compiled a couple of issues and fixes.
Here are the common issues and fixes I have found:
1. reseapp.asp won’t complete the process
– check and make sure that the global.asa, resetapp.asp and web.config has the correct value set. Most of the upgrades wipe the connection string on these files. These files are under ..\website, application\exe.
The value should look like value=”Server=<dbserver>;Database=<dbname>;UID=<sqluser>;PWD=<sqlpassword>”
– Under the application pool in IIS, make sure to assign the identity to the service account you have created
– Under the Basic Settings of the default website, assign the service account to connect to the path. Click ‘Test Settings’ after setting up the service account to confirm it works.
– Check Component Services in MMC and check the Akcelerant COM+ object and make sure that it is using the same identity as the application pool.
2. The home page does not show a login screen
– make sure that the web.config file does not have an entry for ‘Provider=SQLOLEDB’
I have more troubleshooting steps for reporting servers, and I will add them here shortly…
Create an IIS 7.5 FTP site (Windows Server 2008 R2)
Part 1: Create a basic FTP site
1. Create a new user for the FTP site
1. Open Server Manager
2. Go to Configuration > Local Users and Groups > User
3. From the Actions pane select More Actions > New User…
4. Enter the username and password that you want to use for this FTP site
5. Uncheck – User must change password at next logon
6. Check – User cannot change password
7. Check – Password never expires
8. Click Create and then the Close button.
9. Open the user properties of the user you created above (double-click or right-click > Properties on the username in Server Manager)
10. Go to the Remote Desktop Services Profile tab
11. Check – Deny this user permissions to log on to Remote Desktop Session Host server
12. Click OK
13. Close Server Manager
2. Launch Internet Information Services (IIS) Manager. This is found by clicking the “Start button” > Administrative Tools > Internet Information Services (IIS) Manager.
3.Expand the tree view (left pane in IIS Manager) under the Connections pane – click the ‘+’ next to the server name – and select Sites.
4.From the Actions pane select “Add FTP Site”
5.Complete the Add FTP Site wizard.
1.FTP site name: The name you wish to give this FTP site
2.Physical path: The location of your site or where you want the FTP site files to go
4.Set the IP address that you want to use for FTP
5.Select Allow SSL
6.Choose the self-signed, server generated certificate from the SSL Certificate: drop-down list
8.Check Basic authentication
9.Change the Allow access to: drop-down to Specified users
10.Enter the name of the user that you previously created in the text area below the drop-down list
11.Check Read and Write from Permissions
6.You should now see the name of your FTP site under the main Sites pane
7.Double-click on the FTP site that you setup from the main pane, or expand Sites from the tree view and select the FTP site that you setup
8.Check folder permissions on the folder that you pointed the FTP site to
1.Click Edit Permissions… under the Actions pane
2.Click Security tab
3.Make sure the user that you created above has modify rights to the folder
9.At this point FTP is setup and working using the most basic configuration.
Part 2: User Isolation
Note: There are five types of FTP User Isolation that IIS7.x supports. In this KB article we will only cover two: “FTP Root Directory” which is the basic, default option and “User name directory (disable global virtual directories)” which is used for user isolation. If you would like information on all five types of FTP User Isolation you can look here: http://learn.iis.net/page.aspx/305/configuring-ftp-75-user-isolation/#002
1.With the FTP site that you created above selected in the IIS Manager, launch the FTP User Isolation module by clicking on the FTP User Isolation icon
2.Change the isolation method from “FTP root directory” to “User name directory (disable global virtual directories)”
3.Click Apply under the Actions pane.
4.Go back to the root of your FTP Site.
5.Create a virtual directory named LocalUser.
Note 1: This is one of the rare cases where Windows requires case-sensitivity. The virtual directory name must be LocalUser, with the capital â€œLâ€ and â€œUâ€, or FTP user isolation will fail.
Note 2: The LocalUser folder only works for server level (local) usernames. Domain level usernames are covered in later steps.
1.Right-click on Test FTP Site from the tree view and select Add Virtual Directory…
2.Alias: LocalUser (case-sensitive!)
3.Physical path: C:\inetpub\ftproot
6.Now create a second virtual directory (vdir) under the LocalUser vdir.
1.Right-click on LocalUser from the tree view and select Add Virtual Directory…
2.Alias: Use the name of the user that you created above for FTP
3.Physical path: The actual path to where you want this user to be directed to
7.Select the vdir in step 6 above from the tree view then Edit Permissions… from the Actions pane. 8.Under the Security tab, give your FTP user “Modify” permissions to the folder then OK out of everything.
For a domain user, follow the steps below:
1.In IIS Manager, create a new vdir under the root of your FTP Site named OW.
Note 1: When setting up user isolation for domain user names you must create a vdir using the domain’s nickname. This directory acts in the same way LocalUser does but for domain level users.
Note 2: An Active Directory domain has two names: the domain name and the nickname. The nickname is actually the “pre-Windows 2000 domain name” from when the domain names did not use a DNS/LDAP like naming structure.
The post-Windows 2000 domain names are like an internet domain name, like orcsweb.com. The pre-Windows 2000 domain name, or nickname, is just a single word with hostname like attributes. In OrcsWeb’s case the nickname is OW, and the domain name is orcsweb.com.
1.Right-click on your FTP Site from the tree view and select Add Virtual Directory…
2.Alias: OW (all upper case)
3.Physical path: C:\inetpub\ftproot
2.Now create a second and third virtual directory (vdir) under the OW vdir.
1.Right-click on the OW vdir from the tree view and select Add Virtual Directory…
2.Alias: <your domain user name> (without the OW\ in front if it)
3.Physical path: The path to your site
5.Repeat for any other users as needed.
3.Add the user to the NTFS permission on disk for the folders that you pointed the FTP users to 4.Authorize the domain users in FTP.
1.In IIS Manager, select your FTP Site and then the FTP Authorization Rules module
2.Here is where you can authorize users to access the FTP site.
There are a couple of options you can choose:
1. Add the individual users or groups,
2. Allow all authenticated users. By default we add individual users or a user group when setting up isolated users.
3.Add any domains users to the existing rule (if there are any – or create a new one).
1.Select the rule then Edit from the Actions pane
2.After existing user enter a comma-space (“, “) then OW\ and the Active Directory user name.