Creating a New FTP Site in IIS 7 on windows server

Creating a New FTP Site in IIS 7

Compatibility

Version	Notes
IIS 7.5	The FTP 7.5 service ships as a feature for IIS 7.5 in Windows 7 and Windows Server 2008 R2.
IIS 7.0	The FTP 7.0 and FTP 7.5 services were shipped out-of-band for IIS 7.0, which required downloading and installing the service from the following URL: http://www.iis.net/download/FTP.

Introduction

Microsoft has updated the FTP service for Windows Server® 2008 and above. This updated FTP service incorporates many new features that enable Web authors to publish content better than before, and offers Web administrators more security and deployment options.
This document walks you through creating FTP sites from scratch using the new FTP user interface and by directly editing the IIS configuration files. It contains:

• Creating a New FTP Site Using the IIS Manager
• Creating a New FTP Site by Editing the IIS Configuration Files

Note: This walk-through contains a series of steps in which you log in to your FTP site using the local administrator account. These steps should only be followed on the server itself using the loopback address or over SSL from a remote server. If you prefer to use a separate user account instead of the administrator account, you will need to create the appropriate folders and set the correct permissions for that user account when necessary.

Prerequisites

The following items are required to complete the procedures in this article:

1. IIS must be installed on your Windows 2008 Server, and the Internet Information Services Manager must be installed.
2. The new FTP service must be installed. You can download and install the FTP service from the http://www.iis.net/ Web site using one of the following links:
   • FTP 7.5 for IIS 7 (x64)
   • FTP 7.5 for IIS 7 (x86)
3. You must create a root folder for FTP publishing.

Creating a New FTP Site Using IIS Manager

The new FTP service makes it easy to create new FTP sites by providing you with a wizard that walks you through all of the required steps to create a new FTP site from scratch.

Step 1: Use the FTP Site Wizard to Create an FTP Site

In this first step you will create a new FTP site that anonymous users can open.
Note: The settings listed in this walkthrough specify "%SYSTEMDRIVE%\inetpub\ftproot" as the path to your FTP site. You are not required to use this path; however, if you change the location for your site you will have to change the site-related paths that are used throughout this walkthrough.

1. Open IIS Manager. In the Connections pane, click the Sites node in the tree.
2. As shown in the image below, right-click the Sites node in the tree and click Add FTP Site, or click Add FTP Site in the Actions pane.
   • Create a folder at "%SystemDrive%\inetpub\ftproot"
   • Set the permissions to allow anonymous access:
     1. Open a command prompt.
     2. Type the following command:
        ICACLS "%SystemDrive%\inetpub\ftproot" /Grant IUSR:R /T
     3. Close the command prompt.
   
3. When the Add FTP Site wizard appears:
   • Enter "My New FTP Site" in the FTP site name box, then navigate to the %SystemDrive%\inetpub\ftproot folder that you created in the Prerequisites section. Note that if you choose to type in the path to your content folder, you can use environment variables in your paths.
   • When you have completed these items, click Next.
   
4. On the next page of the wizard:
   • Choose an IP address for your FTP site from the IP Address drop-down, or choose to accept the default selection of "All Unassigned." Because you will be using the administrator account later in this walk-through, you must ensure that you restrict access to the server and enter the local loopback IP address for your computer by typing "127.0.0.1" in the IP Address box. (Note: If you are using IPv6, you should also add the IPv6 localhost binding of "::1".)
   • Enter the TCP/IP port for the FTP site in the Port box. For this walk-through, choose to accept the default port of 21.
   • For this walk- through, do not use a host name, so make sure that the Virtual Host box is blank.
   • Make sure that the Certificates drop-down is set to "Not Selected" and that the Allow SSL option is selected.
   • When you have completed these items, click Next.
   
5. On the next page of the wizard:
   • Select Anonymous for the Authentication settings.
   • For the Authorization settings, choose "Anonymous users" from the Allow access to drop-down, and select Read for the Permissions option.
   • When you have completed these items, click Finish.
   

Summary

You have successfully created a new FTP site using the new FTP service. To recap the items that you completed in this step:

1. You created a new FTP site named "My New FTP Site", with the site's content root at "%SystemDrive%\inetpub\ftproot".
2. You bound the FTP site to the local loopback address for your computer on port 21, and you chose not to use Secure Sockets Layer (SSL) for the FTP site.
3. You created a default rule for the FTP site to allow anonymous users "Read" access to the files.

Step 2: Adding Additional FTP Security Settings

Creating a new FTP site that anonymous users can browse is useful for public download sites, but web authoring is equally important. In this step, you add additional authentication and authorization settings for the administrator account. To do so, follow these steps:

1. In IIS Manager, click the node for the FTP site that you created earlier, then double-click FTP Authentication to open the FTP authentication feature page.
   
2. When the FTP Authentication page displays, highlight Basic Authentication and then click Enable in the Actions pane.
   
3. In IIS Manager, click the node for the FTP site to re-display the icons for all of the FTP features.
4. You must add an authorization rule so that the administrator can log in. To do so, double-click the FTP Authorization Rules icon to open the FTP authorization rules feature page.
   
5. When the FTP Authorization Rules page is displayed, click Add Allow Rule in the Actions pane.
   
6. When the Add Allow Authorization Rule dialog box displays:
   • Select Specified users, then type "administrator" in the box.
   • For Permissions, select both Read and Write.
   • When you have completed these items, click OK.
     

Summary

To recap the items that you completed in this step:

1. You added Basic authentication to the FTP site.
2. You added an authorization rule that allows the administrator account both "Read" and "Write" permissions for the FTP site.

Step 3: Logging in to Your FTP Site

In Step 1, you created an FTP site that anonymous users can access, and in Step 2 you added additional security settings that allow an administrator to log in. In this step, you log in anonymously using your administrator account.
Note: In this step log in to your FTP site using the local administrator account. When creating the FTP site in Step 1 you bound the FTP site to the local loopback IP address. If you did not use the local loopback address, use SSL to protect your account settings. If you prefer to use a separate user account instead of the administrator account, set the correct permissions for that user account for the appropriate folders.

Logging in to your FTP site anonymously

1. On your FTP server, open a command prompt session.
2. Type the following command to connect to your FTP server: FTP localhost
   
3. When prompted for a user name, enter "anonymous".
4. When prompted for a password, enter your email address.

You should now be logged in to your FTP site anonymously. Based on the authorization rule that you added in Step 1, you should only have Read access to the content folder.

Logging in to your FTP site using your administrator account

1. On your FTP server, open a command prompt session.
2. Type the following command to connect to your FTP server: FTP localhost
   
3. When prompted for a user name, enter "administrator".
4. When prompted for a password, enter your administrator password.

You should now be logged in to your FTP site as the local administrator. Based on the authorization rule that you added in Step 2 you should have both Read and Write access to the content folder.

Summary

To recap the items that you completed in this step:

1. You logged in to your FTP site anonymously.
2. You logged in to your FTP site as the local administrator.

Creating a New FTP Site by Editing the IIS Configuration Files

You can also create FTP sites for the new FTP service by editing the IIS configuration files.
Note: Editing your ApplicationHost.config file requires full administrative permissions. This is best accomplished using one of two methods:

• Log in to your computer using the local "administrator" account.
• If you are logged in using an account with administrative permissions that is not the local "administrator" account, open Notepad using the "Run as Administrator" option.

Note: The above steps are required because the User Account Control (UAC) security component in the Windows Vista and Windows Server 2008 operating systems prevent access to your ApplicationHost.config file. For more information about UAC, please see the following documentation:
http://go.microsoft.com/fwlink/?LinkID=113664
The following steps walk you through all of the required settings to create a new FTP site from scratch.

1. Using a text editor such as Windows Notepad, open your ApplicationHost.config file, which is located in your %SystemRoot%\System32\inetsrv\config folder by default.
2. Locate the <sites> section. This section contains your Default Web Site and should begin with something like the following:
   <sites>
   <site name="Default Web Site" id="1">
   <application path="/">
   <virtualDirectory path="/" physicalPath="%SystemDrive%\inetpub\wwwroot" />
   </application>
   <bindings>
   <binding protocol="http" bindingInformation="*:80:" />
   </bindings>
   </site>
3. Copy the entire section for the Default Web Site and paste it on a new line just below the closing </site> tag.
4. Change the site's settings to create a unique FTP site:
   • Modify the name and id attributes for the new site to respectively contain "Default FTP Site" and "2".
     Note: You may need to choose a different number than "2" for the site ID if any site is currently using that site identifier.
   • Change the value of the protocol attribute on the binding element to contain "ftp".
   • Change the physicalPath attribute to "%SystemDrive%\inetpub\ftproot".
   • Change the port value of the bindingInformation attribute to contain "21".
5. Add an <ftpServer> section beneath the closing bindings tag that will contain your authentication settings.
   <ftpServer>
   <security>
   <authentication>
   <anonymousAuthentication enabled="true" userName="IUSR" />
   <basicAuthentication enabled="true" />
   </authentication>
   <ssl controlChannelPolicy="SslAllow" dataChannelPolicy="SslAllow" />
   </security>
   </ftpServer>Note: The authentication settings for FTP sites are configured at the site-level, unlike authentication for Web sites, which can be configured per URL.
   
   Your <sites> section should now contain something similar to the following example:
   <sites>
   <site name="Default Web Site" id="1">
   <application path="/">
   <virtualDirectory path="/" physicalPath="%SystemDrive%\inetpub\wwwroot" />
   </application>
   <bindings>
   <binding protocol="http" bindingInformation="*:80:" />
   </bindings>
   </site>
   <site name="Default FTP Site" id="2">
   <application path="/">
   <virtualDirectory path="/" physicalPath="%SystemDrive%\inetpub\ftproot" />
   </application>
   <bindings>
   <binding protocol="ftp" bindingInformation="*:21:" />
   </bindings>
   <ftpServer>
   <security>
   <authentication>
   <anonymousAuthentication enabled="true" userName="IUSR" />
   <basicAuthentication enabled="true" />
   </authentication>
   <ssl controlChannelPolicy="SslAllow" dataChannelPolicy="SslAllow" />
   </security>
   </ftpServer>
   </site>
6. Scroll to the bottom of your ApplicationHost.config file and add a location section for your Default FTP Site that will contain your authorization settings.
   <location path="Your FTP Site Name">
   <system.ftpServer>
   <security>
   <authorization>
   <add accessType="Allow" users="*" permissions="Read" />
   <add accessType="Allow" users="administrator" permissions="Read, Write" />
   </authorization>
   </security>
   </system.ftpServer>
   </location>Note: In this example, the authorization settings for FTP sites are configured per URL, and these settings specifically enable Read permissions for all users, and Read/Write permissions for the administrator account.
7. Save your ApplicationHost.config file.

You should now be able to log in to your newly created FTP site using an FTP client. To use Internet Explorer anonymously on your IIS server, enter ftp://localhost in the Internet Explorer address bar. You should be logged in and see your files anonymously; you should not be prompted for user credentials.

Summary

In this task you created an FTP site by editing the IIS configuration files. To recap the items that you completed in this step:

1. You created a new FTP site by using the Default Web Site's settings as a template.
2. You configured the following authorization rules for the FTP site:
   • All users have Read permissions.
   • The administrator account had Read/Write permissions.

Step by Step for install and configure setup Apache web server using XAMPP on Windows

 Step-by-step

1. Download XAMPP for Windows. Browse to www.apachefriends.org/en/xampp.html and click XAMPP for Windows.
   
2. Scroll down to Download section, there are 3 formats which you can choose to download. In this example, I select ZIP format.
   
3. Unzip the file into the folder of your choice. If you extract XAMPP in a top level folder like “C:\” or “D:\”, you can skip to step 5. Otherwise, you have to run “setup_xampp.bat” in \xampp folder. In this example, I extract to C:\ so I can skip to step 5.
   
4. Here is the screenshot of the execution of file setup_xampp.bat.
   
5. Open XAMPP Control Panel by right-click on xampp-control.exe and select Run as administrator.
   Note: If you’re using Windows XP, you just double-click on the file.
   
6. On XAMPP Control Panel Application, select Svc checkbox of Apache and click OK. This will install Apache as a service on this computer.
   
7. Click Start to start Apache web server.
   
8. Repeat step 6-7 on MySQL. Now Apache and MySQL are installed as Windows services and already started.
   
9. You can check if the services are really installed on the computer by click SCM.
   
10. On Services, you will see Apache and MySQL services are started and startup type are set to Automatic which means that services will be started automatically when the computer starts.
    
11. Now it’s time to test, browse to “http://localhost” or “http://127.0.0.1″. You will see the screen as below. This is XAMPP’s splash screen, select English language.
    
12. Here is the XAMPP’s main page. You can view other pages using navigation menu on the left side. For example, XAMPP’s status to see which components are running, security page to view current security configuration of the XAMPP installation, etc.
    
13. The main directory for all WWW documents is \xampp\htdocs. If you put a file “test.html” in this directory, you can access it with the URI “http://localhost/test.html”.
    
14. You can manage MySQL using phpMyAdmin by browse to “http://localhost/phpmyadmin” or you can select phpMyAdmin link on the XAMPP’s main page (in Tools section).
    Note: By default, the root’s password is empty (blank password).
    

more details click

Step by step for install and configure setuo of appserv on windows 2008 seerver

Step 1: Get the file
At the time of writing this article, there are 2 version;

1. 2.4.x contains PHP 4 and most software are older versions so it’s more stable.
2. 2.5.x contains PHP 5 and most are newest releases at the official sites so it’s supports more function, but may less stable than 2.4.x.

It’s up to you to decide which is suitable for you.

• Get download by go to developer site.
• Or if you don’t want to go to the site, you can download 2.5.7 at here.

Step 2: Installation

2.1 When you finished download, double-click the file. The welcome screen will be shown, click Next.

2.2 Click ‘I Agree’ to accept the license agreement.

2.3 Choose the directory where you want to install AppServ, I use the default one. click Next.

2.4 Choose the components to install, click Next.

2.5 This is apache configuration. The server name use ‘localhost’ so you can access at http://localhost. Specify admin’s e-mail and port for apache. (recommend to leave 80 as it’s default)

2.6 Now configure MySql, enter password for root account. Also, you can choose charset at here. Then click Install. The installation will start.

2.7 Now installation is finished, you can run Apache and MySql now by click Finish or if you want to run it later uncheck the box that you want.

2.8 To verify that installation is complete, simply open http://localhost (or any server name that you provide while set up). The page will look similar this.

That’s it. Now you have your own web server just in few minutes.

more details click

Step By Step Procedure for Install and Configure Openfire Instant Messaging Server on Windows Server Latest verssion

Having a chat or instant messaging (IM) server running on a Home or Small business network is some-what a good idea, even if you are at work or school and other of your family is at home or even around the world.
The Chat server that I choose to install and run on my Windows Home Server has plug-ins that allow your clients/users to sign in using their mainstream accounts such as Yahoo, AOL and Windows Live (MSN).
You guessed it, I am talking about Openfire from ignite realtime – Jive Software.  They also have a desktop (Windows, Mac, Linux) and a Web-based client to allow users to login and chat.

Openfire is a real time collaboration (RTC) server licensed under the Open Source GPL. It uses the only widely adopted open protocol for instant messaging, XMPP (also called Jabber). Openfire is incredibly easy to setup and administer, but offers rock-solid security and performance.

Installing Openfire on Windows Home Server

You will need to download the Openfire software from http://www.igniterealtime.org/downloads/index.jsp select Windows platform and then the “openfire 3 6 4.exe Includes Java JRE (recommended)” put it on the \\Server\Sofware folder on your Windows Home Server.
Next, remote desktop into your Windows Home Server and Start the install off, it will prepare the files.

Select your language and then click OK

Now the main install will take place, as usual it will recommend that you close all other applications before you continue with the install, and if you require you can cancel the install by clicking on the Cancel button.
It is now time to read the License Agreement (EULA) and accept it to continue with the install, you need to select the “I accept the agreement” and then the Next button will be unlocked.

Next, you select the destination directory, this is important bit of information, if you are going to use the embedded database then select the destination (install) directory in the D drive but not in the shares.
If you have MySQL up and running then the default C:\Program Files\Openfire will do.

It will ask you where the program’s shortcuts should be.  I just leaved this as the defaulted as it will not cause any problems.  Click on the Next button.

The setup/install program will now extract and install all the files to the destination directory.

It will then complete/finish the install of Openfire and will ask you if you wish to start/run Openfire when you exit the setup program.

If you selected the “Run Openfire” on the last stage then it will start.  At the same time as the Openfire program starting up the Windows Firewall will pop up. With this Security Alert you wish to “Unblock” the Openfire Server so you can have access to the Chat server anywhere on your network and then the Internet when you sort out Port Forward on your router.

Configuring Openfire for Windows Home Server

After you installed the Openfire server, and you started it you cant either click on the “Launch Admin”
Or you can either on the WHS go to http://localhost:9090 or http://127.0.0.1:9090 but make sure that you have either disabled the advanced security on Internet Explorer or have another browser installed such as Firefox.  If you are using any computer on the network go to http://whs:9090 or the IP assigned to the WHS in you network for example http://192.168.1.2:9090.
When you go to the above address the setup will start and you would have to select your language, then click the Continue button.

On this step of the configuration you can change the domain and ports however as it automatically gets the server name most people can leave that as it is, click on the Continue button.

Now you can configure the database settings, you can pick the easy way and choose the Embedded Database or if you have got a WordPress instance of a forum running on your WHS then you would have a MySQL database and this is a Standard database connection in the Openfire Server world.  If you want to run a MySQL database keep checking this site as we will be uploading a guide.  But it is better running Openfire on a Standard database connection as there is more feature open to you.
 
You have to choose which external database (Standard database connection) once you select the database type then you will have to type in all the details such as the username and password.  Then click on the Continue button once you are finish completing the details, it may take up to 1 minute if you have everything correct.

On the Profile settings since the WHS can’t run Active Directory natively then select the Default option.

You will now need to setup an administrator account, try not to use the same password as your WHS administrator.  Enter an email address, note that you can enter something like: admin@whs.local if you do not want or trust the software but I used my real email address and have not collected any unwanted emails from Openfire.
Once you complete this you can click the Continue button.
Remember: if you prefer to use a hard to remember passwords then write them down

Once you specified the Administrator credentials, click on the continue button which will complete the installation and configuration of Openfire.

Click on “Login to the admin console” and authenticate using your previously configured administrator credentials.

More Details Click Here
          Author by:-homeserverland