A spanned volume is created from free disk space that is linked together from multiple disks. You can extend a spanned volume onto a maximum of 32 disks. A spanned volume cannot be mirrored and is not fault-tolerant.

A striped volume is a volume whose data is interleaved across two or more physical disks. The data on this type of volume is allocated alternately and evenly to each of the physical disks. A striped volume cannot be mirrored or extended and is not fault-tolerant. Striping is also known as RAID-0.

A mirrored volume is a fault-tolerant volume whose data is duplicated on two physical disks. All of the data on one volume is copied to another disk to provide data redundancy. If one of the disks fails, the data can still be accessed from the remaining disk. A mirrored volume cannot be extended. Mirroring is also known as RAID-1.

A RAID-5 volume is a fault-tolerant volume whose data is striped across an array of three or more disks. Parity (a calculated value that can be used to reconstruct data after a failure) is also striped across the disk array. If a physical disk fails, the portion of the RAID-5 volume that was on that failed disk can be re-created from the remaining data and the parity. A RAID-5 volume cannot be mirrored or extended.

The system volume contains the hardware-specific files that are needed to load Windows (for example, Ntldr, Boot.ini, and Ntdetect.com). The system volume can be, but does not have to be, the same as the boot volume.

The boot volume contains the Windows operating system files that are located in the %Systemroot% and %Systemroot%’System32 folders. The boot volume can be, but does not have to be, the same as the system volume.

ort numbers are assigned by an organisation called IANA and ports are allocated to various needs to avoid confusion.

Ports are classified into 3 main categories..

• Well Known Ports (Port numbers 0 – 1023)
• Registered Ports (Port numbers1024 – 49151)
• Private or Dynamic Ports (Port numbers 49152 – 65535)

Well Known Ports
Well known ports are used by system or processes run by root or with specific previleges. The port numbers range from 0 to 1023.

Registered Ports
The registered port numbers range from 1024-49151. Such ports are used by programs run by users in the system.

Private/Dynamic Ports
Private ports are not assigned for any specific purpose. its range are from range 49152–65535

Commonly Used Port Numbers

The following port numbers are unofficial list of commonly used for linux/unix based servers.

More unofficial list of ports and assignments s available here

Port Knowledgebase

List of frequently seen TCP and UDP ports and what they mean. The goal of this port table is to point to further resources for more information.

A previous post has been written on this topic here but I have found a few other methods of doing such a thing, excluding download programs that can be easily accessible to others.

Here are five other methods:

Windows

Method 1 (the easy one)

1. Click “Start”, “Run,” and then type cmd. When the command prompt opens type “CD C:\Test” (replace “Test” with the name of the folder you want to hide.)2. Now type “attrib file +s +h” and replace “file” with the name of the actual file name you would like to hide.3. Now, go back to C:\Test and look for your file or folder, it’s not there! You cannot find it through simply browsing around, through the command prompt, or even if you click “Show Hidden Files and Folders”.

4. To find the folder and it’s contents again simply go back to the command prompt, type “CD C:\Test” (of course, again replacing “Test” with the name of the folder,) and then type “attrib filename -s -h”. You should now be able to find your file again!

Method 2 (this is where it starts to get slightly more difficult)

This method, unlike the previous one, hides an entire drive instead of individual files or folders:

(Before you ever use the registry I HIGHLY RECOMMEND backing up your registry with a tool similar to Registry Tool or CCleaner. You may as well use a manual method similar to this.)

1. Go to “Start,” “Run,” and type regedit.2. When the registry editor loads, navigate to: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\
Policies\Explorer3. Right click on “Explorer” and select “New” and “DWORD Value.”

4. Name the value NoDrives and select “Decimal” as the base.

5. In the value type the number that corresponds with the drive below:



(E.g. If you would like to hide drive E, type 16. You may also hide multiple drives by adding the two numbers. E.g. If you would like to hide drives E and G, 16+64=80.)

6. Now, after you restart your computer, you should not be able to see the drive.

Method 3

1. Create a folder in a drive for easy access, e.g. C:. (Name it something related to the Control Panel, e.g. Users.)2. Create a new file in Notepad and copy and paste the following into it:ren Users Users.{21EC2020-3AEA-1069-A2DD-08002B30309D}

3. Replace “Users” with the name of the folder you created and save the file as loc.bat.

(You should now be able to see your folder and the loc.bat file, with the loc.bat in the same directory as the folder Not in it.)

4. Now, right-click and create another text file. Copy and Paste the following into it:

ren Users.{21EC2020-3AEA-1069-A2DD-08002B30309D} Users
(Make sure to replace the word “Users” with the name of your folder.)

5. Save it as key.bat.

6. Now you should see the loc.bat and the key.bat files in the same directory as the folder you created.

7. Now, all you need to do is double-click on the loc.bat file and the folder should have an icon that looks like the control panel. If you click on the folder it should redirect you to the Control Panel and thus you have locked the folder.

8. Of course, to unlock it, simply double-click on the key.bat file and the folder should turn back into the folder you first created.

Method 4

This final method allows users to hide files in a JPEG image:

1. Create a folder in C:\, e.g. C:\Folder1.2. Put all the files you want to hide in there, as well as a JPEG image that you would like to hide the files in.

3. Select all of the files you want to hide, and create a ZIP or RAR file with them using a program like WinRAR, WinZip, 7Zip, etc.

4. Now you should have your archive next to your files that you want to hide, even though they are in the archived file already, with the JPEG image you would like to hide all of this in.

5. Go to “Start,” “Run,” and type: cmd.

6. Now type: cd \, then type: cd Folder1. (Of course, replace Folder1 with the name of your folder.)

7. Type the following: copy /b myimage.JPG + archivedthing.rar myimage.jpg

(Note: Replace the name “myimage” with the name of your image, and replace “archivedthing” with the name of your compressed file.)

8. You should receive a response similar to the following: “1 file(s) copied.”

9. To find the files in your image, all you need to do is right-click on the image and select “Open With…” and select “WinRAR” or the name of the program you used to archive the original files.

The main difference between a 32 bit and 64 is that 32 bit system has 4gb(gigabytes) of space for addressing means that the 32 bit system has a limit of 4GB RAM to process data where as the 64 bit operating system has 2^64 bits of space to address and supports 16 hexabytes of RAM to process data.

In simple words an operating system of 32 bit has a 4GB limit to process any data depending upon the sizes of files and RAM

A person who does not care about the category will find 64 bit more beneficial than 32 bit because he can use 64 bit OS with 32 bit OS and software. If we compare 64 bit with 32 bit OS, 64 bit is faster and performs more upgraded silicon processes and have more no of transistors which proves it to be more advantageous than 32 bit.

Now most of the software companies are developing their software in accordance to the 64 bit environment, it’s really hard for the consumers to run a 64 bit application in 32 bit environment, in this case they have to upgrade their hardware’s such as RAM which is also a big issue because most of the computer users have less than 1Gb in their systems.

So instead of changing your hardware often I would recommend 32 bit OS over 64 bit which is more user friendly and enables its user to run applications of 64 bit in 32 bit environment.

From the command line, you can shut down or reboot any Windows Server 2003 computer (or even Windows XP or Vista machines) with the Shutdown.exe command. (Note: The exe file extension is optional for the Shutdown command.) Shutdown.exe contains a number of switches that allow you to specify different actions for the server when the Shutdown command executes. The Shutdown.exe switches are as follows:

Enable Remote Connections and Configure Identity Credentials

Enable remote connections so that Windows users and IIS Manager users (configured later in this article) can connect to this computer by using IIS Manager on their computers. By default, the Management Service allows connections only from users that have Windows credentials, but you can configure it to also allow connections from users with IIS Manager credentials. For the purposes of this article, configure the Management Service to allow both credential types as shown in the image below.

Note: The next section in this article explains IIS Manager credentials.

To enable remote connections and allow connections from Windows users and IIS Manager users:

1. In IIS Manager, in the Connections pane, click the server node in the tree.
2. Double-click Management Service to open the Management Service feature page.

4 .Select the Enable remote connections check-box.

5. Under Identity Credentials, select Windows credentials or IIS Manager credentials.

6. In the Actions pane, click Apply to save the changes, and then click Start to start the Management Service.

Additional Information

You do not have to enable remote connections to start the Management Service. If remote connections are disabled and the Management Service is started, you can connect to the Management Service from the local computer but not from a remote computer. If you cannot connect from a remote computer, make sure that remote connections are enabled.

You should check your firewall settings to ensure that connections are allowed to the Management Service. When the Management Service is installed, the setup process adds a firewall rule that allows traffic to the Management Service on port 8172 (the default port) which is on by default. If you ever change the port that the Management Service uses, you must add a new firewall rule to allow traffic to the Management Service on that port.

Configure Connection and Logging Settings for the Management Service

In addition to the Management Service settings that were configured in the above section, you can configure connection settings and specify where to log requests. The following table describes each field and its default setting. If you change any settings, make sure to click Apply in the Actions pane and then restart the Management Service.

Configure IP and Domain Restrictions for the Management Service

By default, the Management Service accepts all requests made to its configured IP address and port, and users are allowed to connect when they are added to IIS Manager (as explained in the next section). However, you can configure the service to deny access for unspecified requests and instead add specific allow rules so that only requests made from a specific IP address or domain are accepted. For more information about allowing or denying requests from IP addresses or domains, see the procedures under Configuring Remote Management on Microsoft TechNet.

Configuring Users and Permissions for IIS Manager

When you configured the Management Service in the above section, you selected the Windows credentials or IIS Manager credentials option. This option enables users with either Windows user accounts or IIS Manager user accounts to connect to a site or application on the remote computer by using IIS Manager. Both types of users must provide valid credentials (a user name and password pair) when they connect remotely. A Windows user must provide valid Windows credentials for a user account on the remote computer or for a user account in the domain if the computer is a member of a domain. An IIS Manager user must provide valid IIS Manager credentials, which are configured in IIS Manager by a server administrator on the remote computer. In both cases, a user is able to use IIS Manager to connect to sites or applications for which the server administrator has given the user permission.

Add an IIS Manager User

The following procedures explain how to open the IIS Manager Users feature and add a user. When the IIS Manager Users feature page opens, the list displays each IIS Manager user name and whether the account is enabled or disabled. Only enabled accounts are allowed to connect to sites or applications for which they have been granted permission.

To add an IIS Manager user:

1. In IIS Manager, in the Connections pane, click the server node in the tree.
2. On the server home page, double-click IIS Manager Users.

3. On the IIS Manager Users page, in the Actions pane, click Add User.

4. In the User name box, type a user name.

5. In the Password box, type a password and then retype the password in the Confirm password box.

6. Click OK.

Configure IIS Manager Permissions for a Site or an Application

In order for a user to remotely connect to a site or application on the server, they must be granted permission to a site or application by the server administrator. After they are granted permission, they can use IIS Manager to connect to the site or application using either their Windows credentials (if they are a Windows user) or their IIS Manager user credentials (if they are an IIS Manager user).

To permit an IIS Manager user to connect to a site or an application:

1. In IIS Manager, in the Connections pane, select the site or application for which you want to configure permissions.
2. On the home page for the site or application, double-click IIS Manager Permissions.

3. On the IIS Manager Permissions page, in the Actions pane, click Allow User.
4. On the Allow User dialog box, select IIS Manager and click Select.

5. On the Users dialog box, select one or more IIS Manager users from the list and then click OK.

6. Click OK to dismiss the Allow User dialog box.

To permit a Windows user to connect to a site or an application:

1. On the IIS Manager Permissions page, in the Actions pane, click Allow User.
2. On the Allow User dialog box, select Windows and then click Select.
3. On the Select User or Group dialog box, type a user name or search for a user account, and then click OK.

4. Click OK to dismiss the Allow User dialog box.

Configure Access Control Lists (ACLs) for Content Directories

In order for IIS Manager to work correctly when a user connects to a site or an application, the ACLs must be configured properly for the physical directory of the site or application. For Windows users, you must configure directory and file ACLs for each Windows user or group that needs to access the directories and files. For IIS Manager users, you must configure directory and file ACLs for the WMSVC user (NT Service\WMSVC by default).

For the physical directory of a site or an application, configure read, write, and execute permissions for the WMSVC user (if you are permitting IIS Manager users to connect) and for any Windows users who need to connect to that site or application.

If the physical directory of the site or application is on a different machine (i.e. on a UNC share) then you will need to configure WMSVC to run as a user which has read, write, and execute permissions for the content on that UNC share (the default user, NT Service\WMSVC, cannot access items on a different machine).

Connect to a Site or an Application in IIS Manager

After you have configured the Management Service and configured users and permissions, a user can connect to his or her site or application.

To connect to a site or an application

1. In IIS Manager, click File and then click Connect to a Site (or Connect to an Application).
2. On the Connect to Site or Connect to Application wizard, type the server name and the site name to which you want to connect. If you are connecting to an application, type the application name also. Then click Next.

3. On the Provide Credentials page of the Connect to Site or Connect to Application wizard, select whether you want to use current credentials or to specify the credentials to connect to the site. When you specify credentials, the default is Windows credentials unless you select the Use IIS Manager credentials check-box. After you specify the credentials, click Next to connect to the server.

4. If the connection succeeds, IIS Manager will display a final page on the Connect to Site or Connect to Application wizard to name the connection. As shown in the image below, the TestAdmin user has created a site connection to the Contoso.com site.

Additional Information

In the next section, we look at Feature Delegation. However, before we do that, and to better explain Feature Delegation and what it does, we look at one feature of the site we have just connected to. The site should be highlighted and the site home page should be displayed. On the home page, double-click Error Pages.

As shown in the image below, on the right-hand side of the page there is an alert saying “This feature has been locked and is read only.” This alert is displayed when a feature has been locked; the next section explains Feature Delegation and locking in more detail.

Delegating Features in IIS Manager

The Feature Delegation feature page lets a server administrator configure the delegation state of features that are configurable in Web.config files at the site and application levels in IIS Manager. He or she might want to delegate configuration of certain features, such as Default Documents and Directory Browsing, to an individual site owner so that the owner can configure those delegated features in his or her site.

Or a server administrator might delegate a feature as read only so that a site owner can view the configuration of a feature but cannot change the settings. The server administrator can even prevent features from appearing in IIS Manager at the site and application levels.

There are several different delegation states, each of which determines whether a feature is delegated to lower levels in the configuration system and whether the feature displays in IIS Manager when users are connected at lower levels. The following table describes each delegation state.

Note: Server administrators can modify the configuration for all features, so if they are connected to the server, they will see all features at all levels even if a feature has been configured to not display at lower levels.

Configure Default Delegation States for Features in IIS Manager

When you first open the Feature Delegation feature page, you can configure the default delegation state of features in IIS Manager. These delegation states are the default settings used by IIS Manager for all sites and applications on the server.

To configure default delegation states for features in IIS Manager

1. In IIS Manager, in the Connections pane, click the server node in the tree.
2. On the server home page, double-click Feature Delegation.

3. Select Delegation from the Group by list to organize the list of features by their current delegation states.

4. Select Error Pages in the Feature Delegation list, and then review the available delegation states in the Actions pane. The Error Pages feature is selected and the available options under Set Feature Delegation are Read/Write, Remove Delegation and Reset to Inherited.

5. Select Error Pages. In the Actions pane, click Read/Write to unlock the configuration section that is related to the Error Pages feature. This makes the feature configurable in Web.config files and in IIS Manager at the site and application levels.

Additional Information

The following excerpt from the IIS configuration files shows that the values can be overridden at every location (also referred to as “path”):

<location path="" overrideMode="Allow">

    <system.webServer>

        <httpErrors>

            ...

            ...

        </httpErrors>

    </system.webServer>

</location>

  

To further demonstrate what this action does, look at Error Pages feature at a site level. In the Connections pane, connect to a site and then double-click Error Pages on the site home page. As shown in the image below, the Error Pages feature can now be configured by the user connected to the site level.

Configure Custom Delegation States for Features in a Site or an Application

The steps above configured the default delegation state for the Error Pages feature in all sites on the server. There may also be a time when you do not want the delegation state that you configure to be applicable to all sites. In this case, you can configure a custom delegation state for a specific site. You can also copy custom delegation states of all features from one site to another site.

To configure custom delegation states for features in a specific site

1. In IIS Manager, double-click Feature Delegation.
2. On the Feature Delegation page, in the Actions pane, click Custom Web Site Delegation.
3. From the Sites list, select the site for which you want to configure custom delegation settings.

4. Select a feature, and then click a delegation state in the Actions pane.

To copy custom delegation states from one site to another site

1. On the Custom Web Site Delegation page, in the Sites list, select the site from which you want to copy delegation to another site.
2. Click Copy Delegation.
3. On the Copy Delegation dialog box, select the site or sites to which you want to copy the delegation states and then click OK.

Reset Feature Delegation States

There may be a time in which it is necessary to undo the changes that have been made to the delegation states of features. Perhaps the changes were made to a particular site or application by accident, or some ‘experimentation’ with the feature has gone wrong. In this case, reset the delegation states of all features back to their default states. Or, reset only one feature back to its default state.

To reset feature delegation states

1. Open the Feature Delegation feature page.
2. To reset all feature delegation states, in the Actions pane click Reset All Delegation.

To reset the delegation state of a specific feature, select the feature in the list, and in the Actions pane click Reset to Inherited.

Windows Server 2003, Web Edition is mainly for building and hosting Web applications, Web pages, and XML Web Services. It is designed to be used primarily as an IIS 6.0 Web server and provides a platform for rapidly developing and deploying XML Web services and applications that use ASP.NET technology, a key part of the .NET Framework. This edition does not require Client Access Licenses and Terminal Server mode is not included on Web Edition. However, Remote Desktop for Administration is available on Windows Server 2003, Web Edition. Only 10 concurrent file-sharing connections are allowed at any moment. It is not possible to install Microsoft SQL Server and Microsoft Exchange software on this version of Windows, although MSDE and SQL Server 2005 Express are fully supported after service pack 1 is installed. The most important limitation of Web edition is a maximum memory of 2 GB RAM. Additionally, Windows Server 2003, Web Edition cannot act as a domain controller. See Compare the Editions of Windows Server 2003.

Windows Server 2003 Standard Edition
Windows Server 2003, Standard Edition is aimed towards small to medium sized businesses. Flexible yet versatile, Standard Edition supports file and printer sharing, offers secure Internet connectivity, and allows centralized desktop application deployment. This edition of Windows will run on up to 4 processors with up to 4 GB RAM. 64-bit versions are also available for the AMD x86-64 architecture and the Intel clone of that same architecture, EM64T. The 64-bit version of Windows Server 2003, Standard Edition is capable of addressing up to 32 GB of RAM and it also supports Non-Uniform Memory Access (NUMA), something the 32-bit version does not.
Windows Server 2003 Enterprise Edition
Windows Server 2003, Enterprise Edition is aimed towards medium to large businesses. It is a full-function server operating system that supports up to eight processors and provides enterprise-class features such as eight-node clustering using Microsoft Cluster Server (MSCS) software and support for up to 32 GB of memory. Enterprise Edition also comes in a 64-bit edition for Intel. 64-bit versions are also available for the AMD x86-64 architecture and the Intel clone of that same architecture, EM64T. The 64-bit version of Windows Server 2003, Enterprise Edition is capable of addressing up to 1 TB of RAM. Both 32-bit and 64-bit versions support Non-Uniform Memory Access (NUMA).

Windows Server 2003 Datacenter Edition
Windows Server 2003, Datacenter Edition is the flagship of the Windows Server line and designed for immense infrastructures demanding high reliability and scalablity. Datacenter supports up to 64 processors. It also supports Non-Uniform Memory Access (NUMA).

Windows Server 2003 Compute Cluster Edition
Windows Server 2003, Compute Cluster Edition is designed for working with the most difficult computing problems that would require high performance computing clusters. Compute Cluster edition deploys in clusters of multiple servers to form large supercomputers. Microsoft intends to release this edition in 2006.

Windows Server 2003 Storage Server
Windows Storage Server 2003 is optimised to provide dedicated file and print sharing services. It is only available through OEMs when purchased pre-configured with network attached storage devices, which are available in a wide variety of sizes from a couple hundred gigabytes to a few terabytes. One significant difference, when compared with the other Windows Server 2003 editions that provide file and print services, is that Storage Server does not require client access licenses.