qr code in c# windows application Part 5: Managing Windows Server 2003 Storage and File Systems in C#

Generate QR-Code in C# Part 5: Managing Windows Server 2003 Storage and File Systems

20

Figure 20-9.

20

While you re working with a zipped folder, you can perform tasks similar to those you can with regular folders. You can do the following:

Add other files, programs, or folders to the zipped folder by dragging them to it. Copy a file in the zipped folder and paste it into a different folder. Remove a file from the zipped folder using CUT so that you can paste it into a different

You also have the option to perform additional tasks, which are unique to zipped folders. You can click File, Extract All to start the Extraction Wizard, which can be used to extract all the files in the zipped folder and copy them to a new location. You can click File, Add A Password to add a password to the zipped folder to control access to it.

Even with the large disk drives available today, you ll often find that hard disk space is at a premium, and this is where disk quotas come in handy. Disk quotas are a built-in feature of NTFS that help you manage and limit disk space usage.

Using disk quotas, you can monitor and control the amount of disk space people who access the network can use. Without quota management it is hard to monitor the amount of space being used by individual users and even harder to control the total amount of space they can use. I refer to monitoring and controlling separately because there s a very important difference between monitoring disk space usage and controlling it and the disk quota system allows you to perform these tasks separately or together. You can, in fact, do the following:

Configure the disk quota system to monitor disk space usage only, allowing adminis-

users exceed predefined usage levels, and enforce the limits by denying disk space to users who exceed the quota limit Your organization s culture will probably play a major role in the disk quota technique you use. In some organizations the culture is such that it is acceptable to monitor space usage and periodically notify users that they are over recommended limits, but it wouldn t be well received if administrators enforced controls that limited disk space usage to specific amounts. In other organizations, especially larger organizations where there might be hundreds or thousands of employees on the network, it can make sense to have some controls in place and users might be more understanding of specific controls. Controls at some point become a matter of necessity to help ensure that the administrative staff can keep up with the disk space needs of the organization. Disk quotas are configured on a per-volume basis. When you enable disk quotas, all users who store data on a volume will be affected by the quota. You can set exceptions for individual users as well that either set new limits or remove the limits all together. As users create files and folders on a volume, an ownership flag is applied that says that this particular user owns the file or folder. Thus, if a user creates a file or folder on a volume that user is the owner of, the file or folder and the space used counts toward the user s quota limit. However, because each volume is managed separately, there is no way to set a specific limit for all volumes on a server or across the enterprise. Note

For NTFS compressed files and sparse files, the space usage reported can reflect total space of files rather than the actual space the files use. This happens because the quota system reads the total space used by the file rather than its reduced file size.

Ownership of files and folders can change in several scenarios. If a user creates a copy of a file owned by someone else, the copy is owned by that user. This occurs because a file is created when the copy is made. File and folder ownership can also change when files are restored from backup. This can happen if you restore the files to a volume other than the one the files were created on and copy the files over to the original volume. Here, during the copy operation, the administrator becomes the owner of the files. A workaround for this is to restore files and folders to a different location on the same volume and then move the files and folders rather than copying them. When you move files and folders from one location to another on the same volume, the original ownership information is retained. Administrators can be assigned as the owner of files in other ways as well, such as when they install the operating system or application software. To ensure that administrators can always install programs, restore data, and perform other administrative tasks, members of the