...
Also, a daily snapshop of your home directory is kept in a subfolder named "Yesterday". This daily snapshot folder may also be available for some of the CNF shares.
Installing
Windows
- If installing on 64 bit Windows, see CNF staff
- d/l MIT Kerberos for Windows 3.x from http://web.mit.edu/kerberos/dist/index.html
- Grab the MSI installer, not the regular installer
- Do a Typical install
- d/l 1.5.x MSI client installer (for Managed installations) from http://www.openafs.org
- run the openafs installer
- For the type of install, if not already selected, choose "AFS Client"
- This will select the optional components (if not, select these two): AFS Client and MS Loopback Adapter
- CellServDB Configuration - Choose to Download from web address
- Client Cell Name Configuration
- Cell name is: cnf.cornell.edu
- Check Enable AFS crypt security, Enable AFS Freelance client, and Use DNS to Search for Cell Servers
- AFS Credentials Configuration
- Check Start AFS Credentials at system login
- Check Auto initialize AFS Credentials
- Check Renew drive maps
- Check IP Address change detection
- Check Quiet
- DO NOT REBOOT - Install attached Kerberos for OpenAFS first!!!
- Select a Custom install
- Accept the defaults for which components to install
- Change the cell name from openafs.org to cnf.cornell.edu
- Accept defaults on the rest of the screens
- Run the attached .reg files to set OpenAFS registry settingsInstall Kerberos for OpenAFS msi package (attached zip file) - no options to choose, just run the installer
- Copy the attached krb5.ini to c:\windows (e:\windows on some computers) overwriting the krb5.ini file that may be already there
- Firewall Configuration - Under Windows XP and Vista, we recommend that you just use the built in Windows firewall. For other firewalls:
- SYMANTEC - If the Symantec Client Firewall is installed, you will need to add a rule allowing all traffic to/from 10.254.254.253
- If, during the Symantec configuration process, you get a popup window about a script error, you have two choices:
- Reinstall Symantec - this MAY fix the problem
- Disable the Symantec firewall and enable the Windows firewall - consult CNF IT staff for help on doing this
- If, during the Symantec configuration process, you get a popup window about a script error, you have two choices:
- SYMANTEC - If the Symantec Client Firewall is installed, you will need to add a rule allowing all traffic to/from 10.254.254.253
...