Introduction

This document provides an approach that can be used to divide up the client side drive mappings so that they can present a logical view to the clients. This also has the advantage of allowing the administrator to monitor the space usage and act accordingly

Table 1. Summary of the Drive Mappings

Table 2. Sample Volume Sizes and physical locations on a server

This section outlines the physical locations and sizes of the NT volumes used in this document's examples. It has been assumed that the server sees a single logical disk size of 27GBytes. This has been achieved by the use of a RAID set of 4x9.1GByte Hard disk.

The drive mappings have been split onto separate NT partitions to simplify the space management of the users by the administrator.

Note: All drives are to be NTFS formatted and no compression is to be applied so that statistics per drive can be accurately tracked.

H: drive definition

All H drives are stored on the physical D: drive of the server and are mapped to the user’s H: drive when they login by a setting in the login script.

Example 1

Username=mikea

Physical location on server=D:\mikea

Security on directory=(mikea, Domain Admin Group, Domain Backup Group)

Server share name=mikea

UNC=\\server\mikea

User’s view=H:\

J: drive definition

All departments have a directory stored on the physical F: drive on the server. A user belongs to a master department and this is the drive mapping that is carried out at logon via the login script.

Example 2

Username=mikea

Department=technical

Physical location on the server=F:\technical

Security on directory=(Technical Dept Group, Domain Admin Group, Domain Backup Group)

Server share name=dept_technical

UNC=\\server\dept_technical

User’s view=J:\

K: drive definition

The K: drive is a drive utilised so that the IT section has a place where they can store personalised setting and configuration information for users. For example the user’s mail folders can be stored here, or their Office personal template files, or any configuration file that is personal to that user.

Example 3

Username=mikea

Physical location on server=E:\mikea

Security on directory=(mikea, Domain Admin Group, Domain Backup Group)

Server share name=mikeacfg

UNC=\\server\mikeacfg

User’s view=K:\

S: drive definition

All companies need an area where information can be passed between departments, or available to all individuals. This area is used as such with the appropriate security implemented to refine access requirements. Always create a sub directory and apply security at this level as opposed to the topmost level.

Example 4

Username=mikea

Department=technical

Physical location on the server=G:\

Security on directory=(Domain Admin Group, Domain Backup Group)

Server share name=corporate

UNC=\\server\corporate

User’s view=S:\

Within the corporate drive there is a technical directory:

Physical location on the server=G:\technical

Security on directory=(Others (Read Only), Technical Dept Group, Domain Admin Group, Domain Backup Group)

UNC=\\server\corporate\technical

User’s view=S:\technical