You may log off and on to your PC and let the login script map your new M drive and hgtemp for you. Your project/lab share, however, are usually not taken care of by the script at this moment. If your M drive still fails to appear, please refer to the following directions:
After the file server upgrade and the migration of your "M drive", if your M drive isn't automatically mapped for you, this is what you will have to do on a Windows machine:
Go to START, RUN... and cut and paste the following lines EXACTLY, one at a time, into the box and hit ENTER (if you are asked to confirm, type in Y):
net use m: /del
Hit ENTER.
Go to START, RUN... again and paste: (EXACTLY, DO NOT REPLACE %username%)
net use m: \\helix\users\%username% /persistent:yes
A black box might flash by the screen and your M drive should be accessible afterwards.
Go to START, RUN... and cut and paste the following line, EXACTLY, into the box and hit ENTER (if you are asked to confirm, type in Y):
If you had t: already mapped to \\hgserv2\hgtemp from before, you'll have to do this first to get rid of the old one:
net use t: /del
Otherwise, just type this to map it:
net use t: \\helix\hgtemp /persistent:yes
For project shares, replace the [letter] with other letters and the share path with the proper one with this syntax:
net use [letter]: \\helix\[share_name] /persistent:yes
Example: l: is the letter picked for mapping the "Lung Research Project" share e.g.:
net use l: \\helix\lung_research_project /persistent:yes
For Lab shares, replace the [letter] with other letters and the share path with the proper one with this syntax:
net use [letter]: \\helix\[share_name] /persistent:yes
Example: p: is the letter picked for mapping the "Smith Lab Share 1" share e.g.:
net use p: \\helix\smith_lab_share1 /persistent:yes
If you're having difficulties after following this how-to, feel free to contact the IT Helpdesk, we are standing by each morning after the phases of upgrade.