Anti-Virus
General
Microsoft Office
Database Connectivity
Labview
CAD Software (maintained by MDCAD: Solid Edge, Microstation,
EMS)
Browsing
(admin)
Citrix/Windows Terminal
Server
Email
File
Quotas
Remote Access (applicable to Home Computers)
Security
How do I do this?
Laptops
UNIX Access from Windows client
Future Issues in Windows 2000
AFS client for Windows
FTP
WinSCP
Samba
XWIN32
Web Browsers
Getting Started with Windows XP
at SLAC
User FAQs begin
When a Windows XP computer authenticates to a SLAC
Web Server, at the authentication screen you need to type in
- User name: 'slac\your_username' (e.g.,
slac\achan)
Then you can put in your password as usual.
Windows XP by default puts in the local
machine account instead at the login screen (i.e., 'localmachine\your_username'),
so you have to qualify it with 'slac\youruseraccount'.
Symantec AntiVirus can protect your computer from destructive programs
known as viruses and Trojan horses, and can protect against malicious Active
X and Java applets. SLAC users are included in the Stanford campus
Symantec AntiVirus Corporate Edition licensing.
For
centrally-managed Windows computers at SLAC, the software is
automatically installed and configured. There is no installation
or configuration needed by the user. If you have any questions, please
contact your
local administrator.
For
home computers, users should install from the
Xweb. The installed
version of Symantec AntiVirus will already be pre-configured for 'Live
Updates', so there is no configuration needed by the user. Beyond
making the software available on the Xweb, SCS offers no support of the
software for home computers. Home users, please
note that you must de-install any existing anti-virus program through 'Add/Remove
Programs' on your computer before installing Symantec AntiVirus.
Other topics on Symantec AntiVirus:
Symantec AntiVirus - How do I know this is
installed and running properly?
Checks for the installed program
1) On your local drive, Program Files directory->Symantec
AntiVirus sub-directory, the VPC32.exe program is present.
2) Go to 'Start' button, select 'Settings',
select 'Control Panel', select 'Administrative Tools',
select 'Services'.
2 Symantec services ('SavRoam', 'Symantec Antivirus', 'Symantec Antivirus
Definition Watcher')
appear under 'Services', with 'Status: Started' and
'Startup Type: Automatic'.
3) Press Control/Alt/Delete keys to bring up
the 'Windows Security' dialog box, select 'Task Manager'.
Under 'Processes', 3 Symantec processes (DefWatch.exe, Rtvscan.exe
and SavRoam.exe) appear.
If you have any problems, please contact your
local administrator.
Check for up-to-date 'Virus
Definition File'
In order to keep up with new virus, the Symantec AntiVirus program will
need to regularly download up-to-date virus definition files as part of the
'LiveUpdate'. To check that the 'Virus Definition File' is up-to-date,
bring up the Symantec AntiVirus window by clicking on the executable file
'C:\Program Files\Symantec AntiVirust\VPC32.exe'
Check that the date listed under : ''Virus Definition File: Version' is
recent.
'LiveUpdate' is pre-configured to check for updates hourly, if there is a
network connection. You can click on the 'LiveUpdate' button to do a
manual update. More information. If you have any
problems, please contact your
local administrator.
Symantec AntiVirus - How are 'LiveUpdates'
done for off-site computers?
'LiveUpdate' is configured to first check the SLAC server for downloads,
and if that is not available it will go to the Symantec server for
downloads. Therefore computers within the SLAC internal network will
primarily use the SLAC server, and computers off-site will go to the
Symantec server. 'LiveUpdate' is pre-configured for you to check for
updates hourly. You can click on the 'LiveUpdate' button to do a manual
update.
More information.
Symantec AntiVirus - How do I do a scan?
To scan you local drives, you can right click on the drive or folder you
want to scan within 'Windows Explorer', select 'Scan for viruses'.
Symantec AntiVirus will appear in the Task Bar, click on the icon to
bring up the scan window.
Alternatively you can scan within the Symantec AntiVirus program.
- Bring up the Symantec AntiVirus window by clicking on the executable
file
'C:\Program Files\Symantec AntiVirust\VPC32.exe'
- Click the 'Scan' menu and select 'Scan Computer'.
- Select the drive that you need scanned. Then, click 'Scan'.
Note: There is no scheduled scan of local drives on user computers.
But users may want to do a scan themselves if they suspect any problems.
Users will not be able to scan the network drives (e.g., V drive or home
directory Z drive) since this will impede performance on the servers, and
anti-virus procedures on the servers are maintained by the SCS system
administrators. The realtime scanner on the local computer
automatically scans every file that has been opened, moved, copied,
executed, or deleted. In addition, the servers are also running
Antivirus software. If one really wants to scan a file, it can be
copied to the local computer and then right-click and select 'Scan for
viruses'. So in essence that file is scanned twice, once by the local
computer and once by the server when one copies the file there, and then
again by the local computer when the file is accessed.
Your local administrator has
asked for certain programs to be made available to you via 'Add/Remove
Programs'. You do not need administrator privilege on the computer
to install these programs. Please check
what is available for
your SLAC group.
To install these programs, go to the 'Start' menu -> Settings ->
Control Panel -> Add/Remove Programs
Choose 'Add New Programs', and a list of programs available to you will
be listed. Click on the program you need, then click on 'Add'.
Please contact your local
administrator if you have questions about the list of programs.
-Why is Netscape Navigator not included in the Windows
XP BootCD installation?
-Am I allowed to install Netscape Navigator on my
workstation if I want to?
-Is it true that there are no new fixes for Netscape
4.7?
-BootCD computers will not have Netscape. How about
the ones that are have Netscape and not being reinstalled with the
BootCD?
-Will mods to web programs continue to be de-bugged
on Netscape? How much longer
Q. Why is Netscape Navigator not included in the Windows XP BootCD
installation?
A. As announced at the August 5,
2002 "Town Hall" meeting on the Windows migration plan, SCS plan to
offer only the Internet Explorer browser option on the system
installation (BootCD) disks that it provides to system administrators
for installing Windows XP on workstations. Netscape is not planned to be
installed by the BootCD. The effort of supporting a second browser
across all 1700 Windows systems at SLAC is difficult to justify
considering that there is already a fully functional browser delivered
with the operating system. Moving to Netscape Navigator 6 would require
a large effort in testing, rollout, and problem resolution since that
version of the browser was totally rewritten from the ground up, with a
new user interface, and a completely different rendering engine. It
would also require additional long-term maintenance to stay current with
security fixes. Staying with the 4.79 version of Navigator is not
acceptable from a security point of view (fixes are no longer provided
by Netscape).
Q. Am I allowed to install Netscape Navigator on my workstation
if I want to?
A. You or your department may
choose to install and maintain an alternative browser. There is no
prohibition against doing so, though you will be required to install
security patches when serious problems are discovered.
Q. Is it true that there are no new fixes for Netscape 4.7?
A. The last version of the 4.x
series of Netscape Navigator is 4.79, released in November of 2001.
Netscape does not issue patches to its browser, it only releases new
versions (even if the modifications are minor). We're fairly certain
that there will be no more releases of the 4.x browser � with Navigator
7 nearly ready for release they can't spend effort patching a four and a
half year old program. Also, 4.79 lacks support for XML and has
incomplete support for CSS.
Q. BootCD computers will not have Netscape. How about the ones
that are have Netscape and not being reinstalled with the BootCD?
A. All workstations on site
will be installed with the BootCD to Windows XP. Until your workstation
is converted to Windows XP whatever programs were installed will remain
there unless you choose to remove them (unless Computer Security
requests its removal).
Q. Will mods to web programs continue to be de-bugged on
Netscape? How much longer?
A. With 88.5% of the browser
market belonging to IE (including 3.5% due to AOL browser) vs. 7.3% for
Navigator (all versions -- 2.6% for 4.x) you can draw your own
conclusions about how much testing will be done. See browsers war for
details. Presumably SLAC authors will continue to test Navigator for a
while, but with Mozilla as a likely candidate for replacing Navigator on
UNIX, it is not clear how much testing web authors can do.
Q. Windows Explorer disappears on new Dell machines installed with
Plextor CDRWs and Roxio software:
A. Update Roxio to the latest XP compatible
version:
Updates Easy CD Creator 5.xx Basic
Updates Easy CD Creator 5.xx Platinum
(submitted by Ken Zhou)
Updates for software may come out several times a year. Some
of the updates are security-related, and are
required by SLAC Computing Security. Where possible, updates
will go through a
process of testing, and user notification before it is rolled out.
- For software that is installed on the computer upon reboot by
Active Directory GPO (assigned by computer), such as Office and
InoculateIT, the updates are automatically delivered to the client
computer when it is rebooted. You will be notified by your
local administrators when there are such updates. Upon reboot,
the updates will take a few minutes to install for faster hardware, and
longer for slower hardware (~5-10 minutes). Please note that these
updates are in addition to the monthly
security updates, and may happen on a different schedule.
Desktop users should do this reboot at a convenient time to them -- a
recommended time is to reboot when leaving work for the day.
Laptop users who need to reboot often, will need to take this schedule
into account when they get notified by e-mail that there are software
updates.
- For software that is installed on the computer with 'Add/Remove
Programs' by
Active Directory GPO (published by user), you will need to go to 'Add/Remove
Programs' to get the updates.
- For software that is not installed by
Active Directory GPO (i.e., installed from the
Xweb Windows Software
Installation Site,
installed from CD, etc.), you will need to get the updates and manually
install yourself.
Info from
Microsoft
Security Bulletins. Users should work with the
local administrators for any questions or troubleshooting.
Automatic security updates are rolled out to
Windows client computers that are in the SLAC Active Directory on a
regular schedule.
The updates may require that the client computer be rebooted after the
installation.
Desktop users should
1) save their work before leaving for the evening, and before
any announced schedule
2) keep their computers powered on at night.
Laptops that are in Active Directory will also get all the patches when
they are connected to the internal SLAC Network (please note that the
Visitor/Wireless Network is not part of the internal SLAC Network, and
laptops connected there will not get patches through this process).
Since laptop users may be required to reboot to install security patches
when on the SLAC Network, they will need to take this software update
schedule into account.
SLAC Schedule for Hot Fix Rollouts
- To allow for testing of security updates before they are rolled out
to Windows computers site-wide, any available hot fixes are rolled
out daily to computers of:
- the SCS Windows Infrastructure Group (Windows Infrastructure Group OU)
- the local administrators and test users (Test OU)
- On the third Tuesday of every
month at
3am in the morning, the approved new Hot Fixes will be applied site-wide to all
Windows clients where the patches have not been installed.
This will be done during the night, so that the client computers may
reboot during off-hours after the installation.
- Remaining machines that were not updated on Tuesday morning (e.g., machines
powered off, not on the network, etc.) will be patched and perhaps
rebooted on Wednesday between 6-9pm, since this time coincides with the
third Wednesday of the month
Windows server outage.
Machines that are still not patched will be patched and perhaps rebooted
upon connecting to the SLAC network.
This completes
one Hot Fix Rollout cycle, and stabilizes the site to a current baseline.
On
occasion, it is possible that a previously installed Hot Fix will be
reinstalled through the automated process. We will attempt to keep
this from occurring as much as possible.
- Some of these updates may be urgent due to serious security
vulnerabilities and will need to be applied
within a day or two notice, rather than according to the above schedule.
Please note that:
Background
Microsoft sends out periodic software updates to Windows operating
system and Windows components (such as Microsoft Internet Explorer,
Microsoft Windows Media Player) for both security and functional fixes.
At SLAC, the SCS Windows Infrastructure Group and department local
administrators will attempt to test such updates on various hardware and
software configurations before rolling such updates to the
user community, but not all problems may be detected. Users should
work with the
local administrators for any troubleshooting. Most of the
updates will be
required by SLAC Computing Security. Some of these
updates may be urgent and will need to be applied within a day or two,
due to serious security vulnerabilities. Other updates will follow
the schedule below. Microsoft releases 2 types of updates:
- Service Packs-which are large software packages comprising of
cumulative Hot Fixes and functional/security enhancements. These
may be released by Microsoft a few times a year.
- Hot Fixes-which are patches for a particular problem (often security
related). These are normally released monthly by Microsoft,
but can be more frequent for critical fixes.
Updates required by SLAC Computing Security.
Info from
Microsoft Security Bulletins. Users should work with the
local administrators for any questions or troubleshooting.
All Windows servers need to be updated also with the
latest service packs and hotfixes, and maintain new patches as they are
released. The outage will affect ALL Central Windows servers. The
outage will include all Windows file server services.
Services affected will also include printing, VPN, Citrix, Windows web
servers and all other central Windows services. The date and time
of the outage is on the third Wednesday of each month from 6:00 PM to
9:00 PM. All services during this time will be intermittent and
should be considered unavailable.
All files stored on the central Windows files
servers need to be saved and closed before 6:00 PM on each third
Wednesday of the month.
All central Windows file services and the WTS/Citrix farm
will be affected. This includes the U, V, X, and Z drives. These consist
of the Pub, Groups, Home, Network Install and the NLCTA Backup Space
directories.
The WTS/Citrix farm will be unavailable from 6:00 PM - 9:00 PM on the
third Wednesday of every month. New connections to the farm will not be
allowed starting at 5:30 PM on the scheduled outage day.
EPN systems will follow a different schedule that will be
announced in a timely manner to users of those systems.
Most of the
updates required by SLAC Computing Security. For Windows client in Active Directory,
Security Updates and
Office (and other software) Updates are updated through another process
What to do if a computer is hacked?
- Immediately pull the power plug and network cable
(yes, pull the cables and do not do a 'clean' shutdown.)
- Do not remove/install any software.
- Do not modify any system configurations.
Anything you do to the computer could compromise the forensics,
so it is very important that you leave it exactly
as it was when it was hacked.
- Label it appropriately so that no one will touch it.
- Notify your
local administrator and
SLAC Computing Security
( if they do not already know)
of
-- the nodename/IP address (for computers on the SLAC network)
-- the SLAC user accounts suspected of being used on the computer
since the infection.
- Either deliver the computer to a member of the
SLAC Computer Security
Team or notify them where to pick it up.
- SCS will follow up on disabling network
access (e.g., VPN, dialup, DHCP) until the computer has been Fdisk
re-formatted and re-installed.
For all SLAC accounts used on the infected
machine, SCS will change the accounts so that "user must change
password at next login".
- In order to regain network access, the machine must be
Fdisk, re-formatted and re-installed. Patching it or less aggressive
methods are not reliable in ensuring that infected files are cleaned
off.
For Active Directory Windows computers,
local administrator will Fdisk, re-format and bootCD the computer
to install the standard SLAC Windows configuration.
For user-maintained computers
-- Fdisk and then re-format the hard drive
-- install the operating system
--
manually install all critical security updates and configure the
computer for automatic updates
-- install your anti-virus program and update the signature files
(More information is listed on the Stanford web pages
http://securecomputing.stanford.edu/win-rpc.html)
- Notify SLAC Computing
Security to enable network access
For virus infections, see the
Anti-virus FAQ's.
For instructions on adding a printer from within
a Citrix session, please refer to the
Citrix FAQ.
From the Start Menu:
- Select "Settings",
- �Control Panel�
- Then "Printers and Faxes".
- Double-click on the "Add a Printer" icon.
- �Next� on the Add Printer Wizard
- Select "A network printer, or a printer attached
to another computer "
- Click "Next".
- Select �Find a printer in the directory�
- Click on �Next�
- Enter in the Name field �XXX�
(XXX must be replaced by the 3 digit of the building number that the
printer is located in).
The printer name is derived from the building-room-manufacturer and
model-device. See
the
document on 'Administrator FAQ->Documentation->Naming Standards' for
more information on printer naming conventions.
The Location field gives more detail information.
e.g., printers in Building
084 (Central Lab Annex)
New Name
Old Name
Comment|
084-209-HP5100PS-01
HPCLA2
A or B size paper
084-209-HPMVPS-01
HPBCLA2
084-209-HP4500CPST-01
HP Color
transparency
11. Select the printer
you wish to add and click OK.
- Click "Next". (If you want this printer to
be your default click �Yes� otherwise selects �No�.)
- Click �Finish�
What do I do when I
suspect the print server is down?
The recommended practice is for
printers to be served from the SCS central printservers (rather than from
department printservers or peer-to-peer printing).
For printers that are on the SCS
printservers, each printer is served from 2 central print servers (in the
Server Name field, they are listed as scs050print01 and
scs050print02) to provide a backup print server when one of them is not
working. When you suspect that the print server you are connected to
is down, go through the procedures above and select the printer being served
from the other print server.
Overview SCS maintains several
varieties of permanent and temporary disk storage on the central SLAC
Windows systems, each appropriate for different levels of ownership, data
access, lifetime, and backup. The purpose of this FAQ is to aid you in
understanding the Windows storage repositories available from SCS and their
proper usage. Z drive user home directories
U drive all users home directories
V drive groups directories (list of
V drive group directory owners)
Scratch Space
Backup and Restore
Private Workstation Space (e.g., local
C drive)
Notification of network disk
space usage?
Finding out the quota for your Z
drive user home directory?
Clean up and proper use
of network disk space
Searching for Files and Folders
Directory listing of Folders and their sizes (the DIRUSE
command)
Other
FAQ's
Each user has a
home directory (Z drive) on the Windows file servers. The home directories
are a place to store data specific to the individual user. Data that
requires access or participation of multiple users may be better suited for
a Group directory. Each user at SLAC, upon receiving a Windows computer
account, receives a user home directory. The initial repository contains
500MB of space.
You may request
an increase in quota by filling out the
Windows Space Request Form. User directories above 1 GB are discouraged,
and repositories above 5 GB require special approval.
Instructions on finding
out the quota for your Z drive user home directory.
All Users Home Directories (U drive)
This is the
logical view of all SLAC users home directories A-Z shared through
Microsoft Distributed File System (Dfs). This
is for the convenience of accessing other users� home directories on the
network file servers. If you delete files from your own user home
directory on the U drive, it is the same as deleting files from your Z drive
user home directory.
Each group can
request a group directory (V drive) for the storage of group files. Groups
space is better suited for projects that encompass more than 1 person or
data that needs to be shared with more than 1 person. Each new group
repository will initially receive 10 GB of storage. Each year additional
storage will be procured (amount of storage procured will depend on market
cost) and distributed to each group repository. If data growth exceeds an
individual groups limit then additional storage can be procured at the
expense of the individual group.
Reports of disk usage will be e-mailed to
V drive group directory owners monthly and yearly data planning sessions will be
held. All requests
for permissions changes to the V drive should be sent to the
V drive group directory owners.
You may request an
increase in quota by filling out the
Windows Space Request Form.
Scratch space is
space on the central Windows file servers that is not backed up. Groups may
request scratch space (Windows
Space Request Form), depending on the expected data size and growth
there may be a cost.
With the
exception of scratch space, all central Windows repositories are
backed up on a regular basis.
You can restore directories and files your self by following these
instructions or you can request restoration of any of one
of your central Windows directories or individual files by filling out a
Help Track request. Please include a range of dates from which you want
the directory or file restored. We will restore the applicable information
into a temporary location so that you can move the data.
SCS does not backup files
stored on the local drives (e.g., C drive).
As the raw cost of
disk space falls, and the size of low-end disks increases, you may be
tempted to use the "left-over" space on your local disks of your computer.
Allocating this space as a large scratch area is a reasonable way to do so.
However, SCS
strongly recommends that you not store any non-temporary data on your
workstation. Here are some of the reasons:
- SCS policy
is to only backup our centrally-maintained file servers; it is your
responsibility to backup any data you store locally.
- Our
standard procedure for upgrading the operating system or recovering from
any non-trivial corruption of system files is to do a fresh install,
destroying any data on the system disk.
- SCS does
not support sharing data between workstations, and strongly recommends
against this practice because of its effect on the stability of both the
server and the clients.
If you feel your
application requires the use of local storage (e.g., for performance
reasons) we recommend that you: buy and install a second hard disk so that
the system can be re-installed without overwriting your data; and develop
and implement a procedure for backing up your data.
Notification
of network disk space usage?
Upon reaching
75%, 85%, 95% and 100% of your disk quota you will receive an e-mail
informing you of:
- your quota
- the present disk
usage
- recommended ways to
clean up and
consolidate space.
Owners
of
group and user repositories can
at any time
request
more reports regarding their disk usage. SCS needs to plan with you in order
to allocate the right kind of disk space, and to
predict disk space growth (see
Real Costs of Disk Space). For example, space for a project
involving more than one person should usually be allocated as
group space rather than personal space; and large data files used by
I/O-intensive programs should probably not be stored on the Windows file
servers at all.
As a general rule, we do not allocate more than 2GB to an
individual's home directory; such large requests are nearly always an
indication that there is a better way of meeting your storage requirements.
Instructions on
finding out the quota for your Z drive user home directory.
Finding out the quota for your
Z drive user home directory?
Open the command line window with 'Start button ->
Programs -> Accessories -> Command Prompt' Type '\\slac\netlogon\finduserquota'
The first time you use this, a shortcut will be created in the All
Programs menu.
Click 'OK'.
A second dialog box will appear with your quota and disk space usage.
Click 'OK' to close the dialog box.
Subsequently, you will be able to go into 'Start button ->
Programs -> Find User File Space Quota' to run this
utility. You will only be able to check on your own Z drive user home
directory.
Clean up and proper use of the network
disk space
Please do not
use the Z drive and other network drives for storing:
--program files
There is no need for multiple copies of Microsoft Office executables, etc.
to be on the network drive which is on RAID storage and adds to the backup
load.
--backing up the entire C drive, which would include system and
program files. This method of backup is not useful for restoring a crashed
workstation. The only way to attempt a full recovery of a failed system
from backups is to use an appropriate Backup application that knows how to
adequately snapshot a working system state, which includes various Windows
System files, and Registry database components. Even if an appropriate
backup exist, the recovery process does not guarantee bringing the system
into a working state due to the numerous and different causes of a system
failure. In addition, backup applications running in individual workstation
may modify the properties of the data/files stored in our network drives in
ways that our central backup system wouldn't recognize for its continued and
successful operations.
There is no need for multiple copies of Windows system files and Microsoft
Office executables, etc. to be on the network drive which is on RAID storage
and adds to the backup load.
--personal multi-media files (mp3, avi, mov, mpg, etc.)
--When
cleaning up your Z drive, please do not work off the U drive
except to copy files from another user. The U drive is just a reflection of
ALL USER home directories (their Z drives). Therefore, if you delete a file
on the U drive, you will be deleting the same file on the Z drive.
--Clean
up periodically so that this RAID disk space does not carry a lot of
temp and junk files, and add to the backup load.
--It is proper
to use the Z drive user home directory and other network drives for
business-related user data files.
The Z drive user home directory and other SCS-maintained network drives
(e.g., V drive for group space) are backed up nightly, so users should store
work data here rather than on the local drive of their computers (which is
not generally backed up and therefore can be lost if the computer crashes).
If you need file(s) restored from the network drives, please submit in a
Help Track request.
--If these are
files used by your department, it is better to keep them on the V drive
group space.
Having files in a user home directory just makes it even harder to clean up
home directories and delete user accounts when people leave. Ask your
department Windows Administrator regarding your department group space on
the V drive.
If you need file(s) restored, submit in a
Help Track request.
--In order for
administration duties to be performed on the file servers, the
permissions for files and directories on the central servers must include:
1) System: Full Control
2) Administrators: Full Control
Searching for Files and Folders
You can use the 'Search
Companion' feature in Windows XP built into Explorer to help you track down
files for clean up (obsolete files, large size files, etc.).
Click on the 'Start'
button, select 'Search'.
Select 'All files and
folders' and the 'Search Companion' panel presented to you will
allow you to build a set of search criteria (filename, file content,
location, date modified, file size, type of file, etc.). Results of
the search will appear in the right-hand panel.
Listing of Folders sizes (using
Properties, using the DIRUSE command)
To get the size of your Z drive home directory, go to the U drive
and select your own home directory. Right click and
select 'Properties'. (You cannot do this directly from the Z
drive because the network share is established at this level.)
Alternatively you can use the DIRUSE command, which has the ability to
list the sizes of all sub-directories in one command. The DIRUSE
command is available to centrally-managed Windows XP machines. For
machines that are not centrally-managed, please download DIRUSE from the
http://xweb.slac.stanford.edu
Start button->Programs->Accessories->Command
Prompt
You can look up DIRUSE 'Help' file with the command
C:\>diruse /?
Example of the DIRUSE command for listing sizes of directories.
- To list the size in megabytes of your z drive home directory:
C:\>diruse z:\ /m
(the syntax of the command requires a space between z:\ /m)
- To list the sizes in megabytes of the top level sub-directories
of your z drive home directory(this will not include the sizes of
files at the root of the z drive, the command may take a while to
complete)
C:\>diruse z:\ /* /m
- To list the sizes in megabytes of all sub-directories of your z
drive home directory (, the command may take a while to complete)
C:\>diruse z:\ /s /m
- To write the output to a file C:\z_drive.txt (instead of
displaying the output on screen, , the command may take a while to
complete)
C:\>diruse z:\ /s /m >Z_drive.txt
- To list the sizes in megabytes of a sub-directory of your z drive
home directory (this will not include the sizes of files at
sub-directory z:\Desktop, , the command may take a while to complete)
C:\>diruse z:\Desktop /* /m
*Access requires a SLAC Windows password.
|