• CIFS Mapping Script


    This utility is meant mainly for machines without the Novell client installed, typically off campus, where "regular" drive mappings are required or desired.  (For light use, we still recommend Netstorage or WebDrive.)  Use of this utility simplifies the process of mapping drives to the Novell servers for H: and W: access, etc.  This behavior can be manually simulated -- the utility is merely a convenience.  For more information, please submit a workorder.


    A VPN connection is required for use off-campus.  High speed internet access is also advisable.  Admin rights may be required the first time it is run.  The following drive letters must also be free:  H:, L:, N:, R:, S:, W:, Y:.  Note that some drive letters may be in use by local devices on your system (e.g., usb hard drives, storage card readers).  In some cases, the drive letters for these devices may be reassigned using the Disk Management utility in Windows (diskmgmt.msc) by those with technical knowledge.  Improper use of the Windows disk manager can cause errors, system malfunction, or loss of data.  For more information or assistance, please submit a workorder.


    1. If you are off-campus, connect to the University VPN.
    2. Download the utility from and double-click it.  You can safely ignore any warnings about the executable being unsigned or unknown and allow it to run.
    3. If the utility tells you that a security change is required, click Yes to allow it to happen.  If you are warned that admin rights are needed to make the change, re-launch the program As Administrator (i.e., with elevated rights).  This is only required the first time.  Subsequent runs should be launched "normally" (non-elevated) to allow you to access the drive mappings.*
    4. Follow the prompts to supply Novell context (department), username, and password.
    5. Upon successful drive mapping, access the drive letters through whatever mechanism you normally use -- e.g., Windows Explorer, Word's File --> Open menu, etc.
    6. When you are finished using the drives, run the utility again and choose to Disconnect when prompted.  This will unmap the drives.  Alternatively, you can disconnect each drive manually -- e.g., in Windows Explorer, right click the drive and choose Disconnect.  For performance reasons, it's best to disconnect the drives before disconnecting from the VPN.
    7. Disconnect from the VPN.

    * If you are told the drives mapped successfully but don't see them in Windows Explorer, be sure you have run the utility *without* admin rights.  For security reasons, newer versions of Windows keep elevated processes separate from "normal" processes like your desktop session.  To make the drives accessible to your session, they have to be mapped without elevation.

  • Novell Settings (Douglass Campus Departments)

    Academic Services
    American Studies
    Cinema Studies
    Center for European Studies
    Center for Latin American Studies
    Center for Women's Global Leadership
    Douglass Business Cluster
    Douglass Writing Program
    Exercise Science & Sports Studies
    Institute for Research on Women
    International Programs
    Political Science
    Spanish and Portuguese
    Women's Studies


  • School of Arts and Sciences Data Storage Policy

    Network drive space is a resource provided for the sole purpose of storing current work-related data.  All employees are responsible for managing their own space, which includes deleting non-essential or old files to keep space utilization at a minimum.  Personal files, such as music, photos or video clips are not to be stored on network drives.

    Many of these inappropriate file types can be identified by such extensions as: mp3, avi, exe, dll, jpg, mpg, wav, wmv, gif, bmp and sys. There are more, but these are the most common.  While these are deemed inappropriate for personal storage, they are considered acceptable if they are used for department-related work such as the design of web pages, presentations and documentation.

    Our initial space allocation on the SAS Novell servers is 100MB in each user’s home directory (H:\ drive).  Disk space on this drive is to be used to store your work-related information (word processing documents, Excel spreadsheets or presentations) that is personal in nature, such as performance appraisals.  In addition, many users also have an L:\ drive, used to store html and graphic files for use in publishing a web page.  Only web-related materials should be stored here. Note that the amount of space you have on your H: \ drive is shared with the L:\ drive.  For the vast majority of users, 100MB is sufficient, but upon receipt of a request, the drive space will be reviewed for compliance with the data storage policy and additional space may be allocated based upon need and availability of resources.

    Users should, on a regular basis, review the contents of their drives and delete any files that are unnecessary or do not comply with the policy.  Another misuse of your personal storage space is using it as a backup for your personal computer.   An external hard drive should be used for this purpose.  For detailed instruction on how to clean up your home directory, please review theViewing Files in Windows Explorer documentation.

    The workgroup drive (W:\ drive) is departmental space for sharing work-related files with multiple users or space for individuals to store their work-related documents.  We encourage departmental administrators to use this space to store data even if they are the only ones with access.   If you need to have a directory created on the W: drive, submit a confidential REQUEST and provide the name of the directory you would like created, the list of users who should have access to that directory, and the type of access they should have (read or read\write).  Documents that are being worked on by several individuals should be stored in the W: drive rather than being emailed back and forth.  Not only is this method more efficient, it helps to save resources on the mail server.  The W: drive can be accessed using several methods:

    • NetStorage - allows faculty and staff to securely access their network drives anywhere on campus or at home, using only a web browser.  For detailed instructions on how to connect to your network drives through NetStorage, please go to Netstorage documentation and review the NetStorage documentation.
    • NetDrive -drive mapping utility which allows you to access your network drives.  For detailed instructions on how to connect to your network drives through NetDrive, please review the NetDrive documentation.
    • VPN and Novell Client -uses the internet to provide remote access to network data with the use of the Cisco VPN and Novell Clients.   For detailed instructions on how to connect to your network drives using VPN and the Novell Client, please review the Accessing Network drives through VPN Client documentation.

     The initial space allocation on the SAS e-mail servers is 100MB per user.  As with home directories, additional space will be granted upon request; however, the same policy applies to email as it does to personal space.  It is the responsibility of the user to maintain their mailbox by deleting non-essential emails and attachments in an effort to conserve space.  For detailed instruction on how to clean up your mailbox, please review theCleaning up Thunderbird and Zimbra Mailbox documentation.

     The system administrators periodically run scripts to identify files on the server that appear to fall outside of our usage guidelines.  Any users flagged by that software will be contacted by system administrators to make a final determination regarding the appropriateness of the data being stored.







  • What is the difference between my H: drive and my W: drive, and which should I use?

    Your H: drive is your "home" drive.  The W: drive is the "workgroup" area, typically (though not always) used for file sharing with others in your department.  H: is considered your private space.  Only you have access to it.  There you can store work-related data that only you need. For instance, faculty members can store research-related documents, materials that are their "intellectual property" or works in progress that are for "their eyes only."  Faculty and staff members may find that we store some types of program settings and information in their H: drive -- e.g., Thunderbird profiles, application configuration files, etc.

    A good rule of thumb is that any data that is "departmental" in nature should be stored on W:.  Even if you are the only person who works on a particular set of files at the moment, they should be stored on W: if they are important to the functioning of the department and could potentially be needed by others.  This helps facilitate the efficient sharing of information through hiring transitions, a leave of abscence and other situations when others may need access to departmental files.  If existing folders do not meet your needs, we can create and appropriately secure/restrict access to new folders on W: -- e.g., giving access only to you if necessary.

  • What is your policy on storage space/quota?

    Our goal is to provide everyone with the storage space that they need while also managing a scarce resource. Consumers have seen the prices of mass storage devices drop precipitously over the past few years and, while the prices of server storage have also fallen, the drop in price has not been as pronounced.  Furthermore, server storage is significantly different in many ways, as are the systems that are used to provide you with access to this storage.

    Initial Space Allocation


    Our initial space allocation on the SAS e-mail servers is 100MB.  This may seem small when you compare it to free hosted services like Google that offer in excess of 7TB, but this limited allocation serves multiple purposes.  Since there are a number of different e-mail systems at Rutgers as well as a number of free e-mail servers like Google, many of our users will receive an account on our systems that they will never use.  In the best case, those users will have their mail forwarded to another account and not store any mail on our servers; however, in many cases users simply ignore those accounts.  The account sits idle and collects e-mail such as departmental bulletins and spam. Since no one is using the account, the mail simply builds up until the quota is reached.  By providing a small quota, we minimize the amount of "junk" mail that we store for no reason.

    In cases where the mail account is used, providing a large amount of space to all users imperils the reliability of the mail system.  We currently have over 1000 e-mail account on our mail server.  If every user were granted 1GB of default quota, any malicious user could send repeated large e-mail messages to multiple users on our system and quickly fill all available space allocated for e-mail.  This would bring the entire e-mail system down.  By limiting user quotas we are able to minimize the risk of this happening by decreasing the overall available free space that can be exploited by anyone with an e-mail account and a list of addresses.

    These small initial allocations do not preclude the allocation of additional space when needed.  There are users on our systems with excess of 7GB of mail and, as they use more space, we will allocate them more quota when they need it.  In some cases, we will charge a nominal fee for large amounts of drive space to offset our costs but this only happens in rare cases. 

    File Storage

    Our initial space allocation on the SAS Novell servers is also 100MB in each user's home directory.  For the vast majority of users, this is sufficient but we will increase this allocation as needed upon request.  Since the home directory is primarily used for personal files that are not shared with other users, most additional space requests are for the Workgroup drive.

    There is no default allocation on the Workgroup drive but departments can request up to 5GB of space on this drive without incurring any additional fees.  Requests for space in excess of 5GB are charged at $15/gig/year.  This charge is assessed for two reasons.  First and foremost, it helps us offset the cost of the space; and second, it encourages users to use space efficiently.  For example, we routinely find users that attempt to backup their entire local hard drive to the server simply because they don't realize that perhaps only their My Documents directory is worth copying to the server.  By monitoring individual space allocation and charging for large amounts of space, we're often able to help users store their data more efficiently while simultaneously decreasing costs.

    Why are costs for the storage so high when I can buy a 1TB hard drive for $100?

    With consumer storage prices going down at an ever increasing rate, people are increasingly hard pressed to understand why we are so "stingy" with our storage. 

    The fact is that the drives you can buy in the store bear little in common with those used for our servers. You can walk into a store and get a 1TB hard drive for $79 while the same amount of space on our servers costs about $7000.

    The drives you purchase on the consumer markets are inexpensive SATA drives coupled with relatively slow technology like USB 2.0 to transfer data. They also tend to be single units that have absolutely no redundancy and rely on cheap components like a $5 power supply commonly referred to as a "wall wart".

    We purchase storage arrays -- systems that contain 15-20-30 disk drives in a chassis that has completely redundant power supplies, redundant paths for data access and even redundant hard drives that immediately take over should an individual drive in the chassis fail. They are also configured to stripe data across the drives so that the loss of one drive doesn't result in the loss of data.

    The array chassis is then connected to a SAN fabric that transfers data between the storage and the connected systems over fiber optic cabling that runs at between 2gbps and 8gbps as opposed to the 480mbps of those USB drives.

    That entire infrastructure is then covered with a 24x7x365 warranty with four hour response time so, even though the storage system is entirely redundant (which prevents the users from even knowing about the failure of a component), we have the replacement for the bad part in our hands in four hours or less and can install it with no disruption in service.

    Also consider that we use separate storage arrays with similar redundancy and connectivity to backup all that data on a nightly basis and we keep those backups for 60 days. That infrastructure is then duplicated one more time on our offsite backup server which also keeps 60 days of backups to guard against a catastrophe that destroys our entire data center.

    This means that for every gigabyte you store on the main server, two more gigabytes are used on our backup and offsite backup servers respectively along with 60 days of old versions for all files that have changed.

    As you can see, the storage we are using goes well beyond what you can purchase in the store and this results in a higher cost. There are also other critical components that are part of this infrastructure that haven't been mentioned. They include servers that host the primary and backup storage as well as the network and physical infrastructure that make sure that it is secure and in appropriate environmental conditions.  Finally, there is the staff time that is involved in implementing, supporting, and maintaining this infrastructure.

    In short

    We control the allocation of space closely but we're not opposed to giving out larger chunks of space when needed. All you need to do is let us know how much you'll need, how long you think you'll need it for and what the proposed use is, and we'll be happy to give you what you need so long as we have it available. (We ask for the proposed use because we can provide different types of space depending on use.)  In cases where large amounts of space are needed for extended periods of time we do charge a nominal fee to help offset the cost.

    We're careful not to hand out large amounts of space on a whim because it seems that the amount people store seems to be driven, in part, by the amount of free space they have immediately available. The policy we've developed helps us manage space usage so those that truly need the additional space can have it.