|
administrators, Server Operators, the system, and some processes. Now where does it say guests, users, or power users. But the users and power users need access to the applications. Ok, put the application on a different volume and give them access they require to do their tasks. The only exception is for IIS (Internet Information Service) this application has a special user id that allows 'guests' or 'anonymous' users access to your web site, see my IIS installation guide for this application. Another reason you would not want to install all your applications on the Operating System volume is storage space. Normally you would create a small (compared to the rest of the volumes) volume for your OS, say 20 to 30 gig. Applications take up a lot of storage especially those that create data such as a data base program.
Scenario: You have just completed your new server build, it is not a domain controller but an application server. You have gone through the installation guide and have hardened the server against cyber attack. Now you have a hand full of CD's that you need to install and your job is complete. You have backup, data base, and fax applications to install. Solution: You would install your applications on different volumes because: The backup application can reside on the OS volume but the logs will have to be located on another volume because of the storage requirement for the catalogs and backup logs. (Backup catalogs and the backup logs will become quite large as time goes by). The Data Base software should reside on a separate volume due to the fact that the data will consume large amounts of storage over time and you don't want the OS volume to run out of space and crash the server.
The Fax application will also need to be installed on a separate volume because
of the requirement that all faxes sent or received have to be stored for certain
time period and this will also consume large amounts of storage over time. Before you begin you installations it would be better for you to setup your security. It will be faster and easier to set the default security at the root before all the applications create their directory structures. Once the application is installed if a special security access is required on separate directories then the task is simplified to just those directories and not the complete directory structure. Large directory structures that have to have a security change can take up to 24 hours to complete and then you may instigate errors into the security data base also. Summery: You should consider the application and company defined needs when installing new applications, this includes long term storage and security.
You should always lock down your Operating System volume and restrict access to the
minimum of only those that need to maintain the server Operating System.
![]() Return to previous page
|
|
Home Page Servers Index Hardware considerations Configuration considerations RAID Configurations Teaming for NIC's Configuring DNS Configuring your IP Configuring WINS Configuring Domain Controller Configuring Active Directory Configuring DHCP IIS -Configuring a Internet Information Service Software and Applications Installation |