Skip to main content Skip to navigation
Washington State University CAHNRS Information Technology

Adobe Connect End of Life

Support for Adobe Flash and is ending, and subsequently, the Adobe Connect instance hosted by CAHNRS IT.  Starting in 2019 most browsers will not work by default with our Adobe Connect system, and in 2020 no browser will be able to connect.  CAHNRS IT will no longer be able to support the Adobe Connect platform moving forward, with an end of life date of 12/31/19, and we recommend any remaining users look for alternative platforms.

If you have any questions regarding alternative tools, please submit a request to cit.support@wsu.edu.  If you have questions about the end-of-life of Adobe Flash, please see the below information.

Adobe Flash has been used for displaying animations, videos, and interactive content on websites. By the end of 2020, Adobe will no longer support Flash. Recently, newer formats for displaying the same content have been favored over Flash due to security issues with Flash. Over the past several years, these newer formats like HTML 5, WebGL, and WebAssembly have made Flash obsolete. Because of this, Adobe will stop updating and distributing Adobe Flash Player at the end of 2020. It is recommended to move any Flash content on websites into the new formats.

Additionally, web browsers like Microsoft Edge, Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, and Apple’s Safari have all planned to phase out Flash starting in 2018. Support for Adobe Flash for all browsers will end at the end of 2020.

Microsoft Edge currently asks for permission to run Flash. In mid to late 2019 Microsoft will disable Flash by default for Edge and Internet Explorer. From then on, users will have to re-enable it and provide permission each time to run it. By the end of 2020, Flash will be gone completely from all supported Windows browsers.

Mozilla Firefox users will need to permit Flash for every session beginning mid-2018. In early 2019, users will see warnings about Flash a few months before it is disabled by default. In early 2020, Flash will be removed from consumer Firefox versions, but an extended support release version will support Flash until the end of 2020.

Google Chrome already supports HTML5 by default. Users are currently asked permission to run Flash. Flash will be completely removed from Chrome by the end of 2020.

Apple’s Safari currently requires permission to run Flash, and support will end at the end of 2020.

Changes to Hulbert and Vogel Lab Scheduling

Changes are being made to the process of scheduling and reserving lab spaces in Hulbert and Vogel.  The scheduling changes are being made to improve the ability to self-serve room reservations while ensuring that academic classes retain priority access.  Once this change is in effect, CAHNRS IT will no longer schedule meetings in affected spaces and instead will provide instructions on how to reserve the rooms.  The affected laboratory spaces include

  • CAHNRS Lab Hulbert 5,
  • CAHNRS Lab Hulbert 21,
  • CAHNRS Lab Vogel 31,
  • CAHNRS Lab Vogel 35,
  • CAHNRS Lab Vogel 39,
  • CAHNRS Lab Vogel 43.

Beginning Monday, August 20th, 2018, resource calendars will be available for the above laboratories.  Faculty and staff in CAHNRS will be able to schedule a meeting or event in the laboratory spaces by creating an Exchange/Office365 meeting and inviting the appropriate resource calendar to the meeting.  Requests will be automatically accepted if they do not conflict with an existing event, making these spaces first come first serve, except for academic classes.

The scheduling of classes will take priority over any other event scheduled in these spaces.  At the start of the semester, CAHNRS Operations will review the official course listings, and create the reoccurring meetings for each class in the appropriate laboratory space.  When a conflict arises, we will send a notice to the event organizer canceling their reservation for the laboratory space.

Academic Coordinators can elect to directly create meeting events for their classes on these calendars by creating a reoccurring meeting, but this is not necessary.  If you choose to create entries for your department’s courses directly, please adhere to the naming convention of “Department – Course Number – Section” when scheduling the meeting.  For all other events planned in the laboratory spaces, please use descriptive names.

CAHNRS Operations will continue to post a print-out of the reoccurring course schedule outside of each of these spaces.  However, for the time being, you will need to look at the room’s resource calendar to see the current non-course meetings.  CAHNRS IT is evaluating digital signage solutions that will allow a real-time schedule to be visible outside of each space at all times.

Finally, please note that generally these spaces are locked or have limited accessibility outside of regular business hours, Monday through Friday, 8 am to 5 pm.  If you are scheduling an event outside of this time window, please plan accordingly.

For a list of the addresses of each laboratory space, please refer to the following table.

CAHNRS Lab Hulbert 21 hulbert.21@wsu.edu
CAHNRS Lab Hulbert 5 hulbert.5@wsu.edu
CAHNRS Lab Vogel 31 vogel.31@wsu.edu
CAHNRS Lab Vogel 35 vogel.35@wsu.edu
CAHNRS Lab Vogel 39 vogel.39@wsu.edu
CAHNRS Lab Vogel 43 vogel.43@wsu.edu

Changes to departmental mailboxes – 9/4/2018

WSU Information Technology Services (ITS) is in the process of completing the conversion of Departmental Mailboxes into Shared Mailboxes, a required step for WSU after the Office 365 migration.  Shared Mailboxes, like Departmental Mailboxes, are mail accounts not tied to an individual.  However, permissions for Shared Mailboxes are administered centrally, and those with access will automatically see their Shared Mailbox appear in their Outlook and Office 365 (office365.wsu.edu).

The conversion of Department Mailboxes has been postponed from Thursday, August 16 to Tuesday, September 4th.  The current owner of the Departmental Mail account will automatically be granted access to the converted Shared Mailbox.  If additional individuals will need access to the Shared Mailbox, please submit a ticket to CAHNRS IT https://support.it.cahnrs.wsu.edu or send an email to cit.support@wsu.edu with a list of additional Network ID’s that you wish to have access.

The newly converted Shared Mailbox will be added to your existing email account as a separate (mailbox) entry in Outlook.  When a client needs to send a message as the Shared Mailbox, they will select the From field in Outlook and select the Shared Mailbox as the sender.  The Shared Mailbox can be accessed using the Office365 web interface by adding a shared folder.

Please contact CAHNRS IT with any questions and assistance.

Cougar Manager updates

With the February 1st deadline for the CAHNRS cut over to Cougar Manager fast approaching, here is the latest news and information regarding the migration to Cougar Manager.

Training Sessions and Q&A – Updated

  • 2/14/18 9-10am on Skype – Join Skype Meeting – Join by phone 509-335-2277, access code 8482461
  • 2/15/18 11-12am on Skype – Join Skype Meeting – Join by phone 509-335-2277, access code 69645240

Cougar Manager FAQ

https://wiki.cahnrs.wsu.edu/wiki/80/cougar-manager-faq

This FAQ includes a number of links to task focused youtube vidoes showing how to perform core tasks in Cougar Manager, along with written instructions.  As we receive questions in the Q&A sessions we will update the FAQ.

Additionally, you can find all of our CAHNRS IT videos on our channel at https://www.youtube.com/channel/UCB7WHuxdDHkrZzqaNTwfcjA.

Project Status

Operations and the Business Center has determined a standard set of naming conventions, and are in the process of bulk creating the organization structure of CAHNRS, in Cougar Manager.  We have identified all of the positions and employees to be entered, and have begun adding them.  As we finish a unit’s structure, we will send a notification to the department admin and unit head asking for them to review and approve the structure.  This is a significant data entry project, but we expect to be complete by close of day 1/26/18.

Continue to use Timekeeper until February 1st

For now please continue to use Timekeeper to record hours worked, and only begin using Cougar Manager to record time worked starting February 1st.

New email list manager

Introduction to Dada Mail – Video Primer

On 1/13/18 CAHNRS IT retired the Lyris email list manager, and stood up a replacement list manager called Dada Mail.  The primary reason to retire Lyris was due to increasing costs.  While Lyris had been increasing in cost year over year for some time, the most recent renewal, a 300% increase, was untenable.  Despite the short time frame, we decided the best course of action was to retire Lyris and begin testing alternatives.  After installing and testing PHPlist, Dada Mail, and Group Server, it was determined that Dada Mail provided the functionality most used by CAHNRS mailing lists.

To facilitate the migration to the new list manager we have migrated the lists that were in Lyris to the new system.  However, because of differences in the list managers, some action is necessary on the part of list owners to complete the migration.  In Lyris each list owner had a user account and could administer multiple lists with a single login.  In Dada Mail, each list has a list password which grants access to the administrative interface for the distribution list, and each list has a collection of subscribers or recipients.  In order to facilitate the migration to the new system, we need each list owner to submit a support request through our support portal at https://support.it.cahnrs.wsu.edu or by emailing cit.support@wsu.edu with the following information:

  1. The name of your mailing list.
  2. The email addresses of your authorized senders OR tell us you want your list to be a discussion list that all members can send to.

Update 1/19/2018 5:13pm – You do not need to send us the members/subscribers of your mailing list.  The lists and their members have been moved, we just need to know who the official owner is and give them the list password.

Once submitted, you will first receive the list password, allowing you to login at http://lists.cahnrs.wsu.edu/cgi-bin/dada/mail.cgi/admin and begin sending mailings to your list.  Next, if you requested the ability to send messages via email you will be notified when your list is ready to receive email based messages and that the list of authorized senders has been put in place.

Note that there are two outstanding functionality limitations that we are currently working to resolve:

  1. Messages sent for distribution to the list by email is currently being blocked by WSU’s spam mail service, Proof Point.  This prevents recipients with WSU addresses from receiving messages sent to the list by email.  We are actively working with ITS to resolve this issue, but in the mean time if your distribution list is internal to WSU we recommend sending messages from the web interface.  Until then, if your list includes WSU email addresses, please use the web interface to send messages.
  2. We currently have a support request with the vendor regarding attachments on messages sent from the web interface not properly uploading.

As we work to resolve these issues we will update this post.

Lastly, we have begun a FAQ at https://wiki.cahnrs.wsu.edu/wiki/79/dada-mail-faq.  As we receive questions we will expand our FAQ, and work to provide information on the new features available.

 

Update 1/18/2018 8:43am

Here is a list of Lyris mailing lists to help with submitting your request.

2-snomginterns
2011_4-h_forum
2011wrlfcoordinators
4-hclothtext
4-hforevergreen
4-hhorseleaders
4-hnatural_resource
4h
4h-tuesdaynews
4hassociation
4hbudgetrequest
4hdairynewsletter
4hequine
4hfaculty
4hfoodleaders
4hstaff
4htalk
abpc
acegrant
action-opportunities
adsystemsnifa
afs
afs-ips
ag-action
ag-econ-ext
ag-in-uncertain-times
ag_plastics_recycling
agcommunicationsgroup
aghappenings
agpilotsoc
agriculture
aiow-alumni
all_foresters
allansci
allext-clone
allext_retired
allstat
alumni
alumniofcolor
ambassadors
amdt-alumni-group
amid-seniors
amt
anrprogunit
anrunitaps
anrunitfaculty
ansci
anscifaculty
anscigrad
anscisearch
anscistaff
apktestlist1
apples
appraisers_e_wa
appraisers_e_wa-copy
appraisers_w_wa
arc-units
arc_rfp
aroundthetable
asid
ateam
auto_academic_faculty_graduates
auto_bc_constituents
auto_cahnrs_all
auto_cahnrs_announce
auto_cahnrs_exempt
auto_cahnrs_faculty
auto_cahnrs_it_updates
auto_cahnrs_spokane_all
auto_cahnrs_spokane_faculty
auto_cahnrs_staff
auto_cahnrs_tricities_all
auto_cahnrs_tricities_faculty
auto_cahnrs_vancouver_all
auto_cahnrs_vancouver_faculty
auto_extension_all
auto_extension_non_program_units
auto_extension_program_units
auto_prototype
auto_research_faculty
auto_research_faculty_graduates
auto_research_graduates
auto_test
awn_users
basinag
bc-volunteers
beachwatchers
benefits
biofuel_cap
biofuels
brainnet
breeze
bugsandblights
businessdevelopment
bwadvisory
bwelist
cadre-nrla
cahnrs-all-hands-farm-list
cahnrs-chairs
cahnrs-it
cahnrs_freight
cahnrs_it_staff_all
cahnrs_nids
cahnrs_web_service_center
cahnrsacadcoor
cahnrsadministrators
cahnrsadvisors
cahnrsagstudents
cahnrsall
cahnrsall-copy
cahnrsannounce_deprecated
cahnrsassessment
cahnrscug
cahnrsfaculty
cahnrsfaculty_old
cahnrsgradcoor
cahnrsgradstudents
cahnrsnetstaff
cahnrsonly
cahnrspublicfolders
cahnrsundergrads
cahnrsundgradcoor
camelinanetwork
carbonconversations
carbonconversations2
career_fair
cattlemen
ccat
ccatleadership
ccsfp
cdchallenge
cdpeextpd
cdpeextr-edir
cedext
cereolist
cfi
cgcwma
chairs-assts
chelanmastergardeners
clallam-mgfcc
clallamag
clallamco4h
clallamgen
clallamgleaners
clallamgrown-copy
clallammg
clark-4h-leaders
clarkcountyfood
clarkvolunteer
clearwaterds
climgen
clovertrainings
club-advisors
club_officers
cms
cmsupdate
cns-interview
codirectors
comdata-jhbc
communitygardeners
companimclub
compost
contact-pdi
cookpp_users
coordcorner
copy-cahnrsall
corecommittee
cougarfeeds
county-l-do-not-use
county_shooting_sports_leaders
countyfaculty
cowlitzceha
cowlitzfoodpolicy
cowlizworkshop
cpoprogram
cranefly
cropnotes
cropsyst
crutalk
crutalk-clone
csanrac
csanrlt
csinstructors
css_adjuncts
css_alumni
css_card_users
css_corefaculty
css_emeritus
css_faculty
css_friends
css_gs
css_staff
cssadvisorycouncil
cssannounce
cstalk
cta
ctteam
cuds
cultivatingsuccess
cwr_programmers
cwr_ssl
cwrtest
d_and_ad
dairynews
dhlab
disaster_capacity_planning
disgroup
dpit-test
dpp
dreamcatchers
drill
duvallfmsc
e_wa_forestry
econs598_spring09
edamame
eebulletin
ela
ela-sw
emergingentrepreneurs
energize
enology
erysiphales
evalteam
exec_ruckelshaus
ext_forestry_team
extension
extension_courses
extensiononlinecourses
extensionps
extyandfamunit
f2sconnections
f2sconnections-original
facil-alumni
facilitationext
faculty
famfaculty-ar
familyforests
farmincubators
farmkc_technical-assistance-team
farmtour
fast
fathering
ferryco-4hl
ferrycomg
fibershed
fieldtours
firecongress
fltalk
fmat
food_systems_ed
foodandfarm
foodsafety
foodsafetyteam
foodsense
foragefish
forest-gen
forest-stewardship
forestjobs
forstewnotes
forum2010
friendsofccmg
frtep
gardenhotline
gardening
ghpc-mg
goatprogram
grainconnectionswesternwa
growfood
hd-faculty-extension
healthyaging
hecg
heritagefarm
hhhhub
highdrivebluffs
horizonslp
hort-advisors
hortfaculty
hortmpsgradstudents
htbdm
hulbert-4
hulbert-emergency
human-development-adjunct-faculty
icapp
iclas
id-spokane
ignite
impact
inra-ssgp_tech
ips
italyabroad
itsag
iufrosmallscale
iufrosmallscale-copy
ivma
jbtest
jbtest3
jbtest4
jcommunityfndtn
jeff4hleaders
jeffco4hchat
jeffcofarmers
jeffcoglencove
jeffcosmallfarms
jefferson-forestry
jefferson-mg
jefferson-wsu
jefferson-ww
jhbcfaculty
jhbcgs
jhbcstaff
kamiak_cluster_announcements
kcfficollaborative
keysnomg
kids-weight
king4h
kingcountymgs
kingfairsupers
kingleaders
kingteens
kitsapag
kitsapagriculture
kittitas4hfocus
kittitasmg
kittitasmg-copy
kygcommitte
kygcoord
kygcore
l-a4h
l-ahorse4h
l-ahorse4hold
la-faculty
la-grad
la-students
la-west
lakingpierce
lavfest2011
lcc-demo-team
lclead
lclearn
leadershipkcffi
lewis-ced
lewis-co-4h
lewis-co-beez
lewis-co-ext
lewis-co-food
lewis-co-mfp
lewis-co-mg
lewis-co-mrc
lewis-co-mushroom
lincolngrowers
list1
list2
livestockmarkets
livestocknutmangnews
lol
lyndenrasp
lyris-owners
lyristest
markets_fortenbery
mason_ag_producers
mason_shore_stewards
masoncounty4h
mastergardener
mcanrteam
mccowlitz
meatproject
mgcoords
mgcowliz
mgfcc
mgforum
mgfws
mgnewsletter
mgpe-newsletter
mgtraining-ghpc
mgv-clark
midpacific
militarykidsfamiliesworkgroup
msag-advising-faculty
msag-allstudents
msag-fsm
msag-general
msag-grad-faculty
msag-phm
msag-review-committee
msag-steering-committee
napeoples
nc_ne_wildfire_recovery
ndtrainers
neighborhoodharvest
new-teaching-faculty
next_gen_network
nopfarmers
nopfoodrecovery
northolympicwater
noxiousweeds
noxweeds
nrla
nrleadership
nwaec
nwfstewards
nwsalmon-water
nwwfmarketsale
nycmentors
oc4h
ocmg
oldpasswordlist
onsolidground
onsolidground-advisorycouncil
onsolidground-cahnrsadmin
onsolidground-commodity
onsolidground-fedlegisaides
onsolidground-houseecondevagtrade
onsolidground-lyrisadmins
onsolidground-senateagruraldev
onsolidground-stakeholders
onsolidground-test
onsolidground-wsu
operationskcffi
organicag
organicgrain
orgreducedtill-pnw
ost
p_o_clientele
palouseds
parentupdate
pc4hactivityldr
pc4halumni
pc4hambassadors
pc4hchallenge
pc4hconsultants
pc4hdogleaders
pc4hfamilyliving
pc4hgeneralldr
pc4hhorseboard
pc4hhorseleaders
pc4hhorsemembers
pc4hkygmembers
pc4hleaders
pc4hleaderscouncil
pc4hlivestock
pc4hmembers
pc4hprojectldr
pc4hsmallanimals
pcmgleaders
pcmgraingardens
pdat
pdnotes
pesticide_disposal
pesticide_stewardship
pestsightings-hg
pgeducators
pierce-mg
piercefarmnews
plclist
pm10
pnrecboard
pnw-barberry
pnw_directseed
pnwcompost
pnwparenting
pnwsanews
pnwshare
poaquinvasives
pobirds
poc4h-leaders
poc4h-members
pomastergardeners
pooutdoored
powildfire
practitionersforum
prelimdata
presscontacts
prevention
progcoord
programstaff
psextconveners
public
pullman_css_farms
puy-r-user
raingardens
rangelivestock
rapidmethod
re_clallam
re_clark
re_cowlitz
re_e_wa
re_grays_harbor
re_island
re_jefferson
re_king
re_kitsap
re_lewis
re_mason
re_pierce
re_skagit
re_snohomish
re_thurston
researchgrants
rewatereduc
rgmentors
riparian
ripplemapping
rockdoc_publishers
ruckelshaus-enews
ruckelshaus_center
ruckelshausasst
ruckelshausboard
rural-broadband
ruralhealthwa
rust_update
sacresources
salo
scga
scmgf
scs_forum
scs_vols
seattlekcfoodpolicy
seattlekingafpc
seattleservicelearning
seattleservicelearning-core
sensoryevaluation
service_learning
ses_alumni
ses_emeriti
ses_faculty
ses_faculty_staff
ses_grads
ses_staff
ses_undergrads
sesfaculty
sfpfac
sfpmem
sfpseeds
sfpstate
sfpteam
sfptot
shorestewardscoord
shorestewclallco
shorestewjeffco
silverlake
silverlakecouncil
sjcbeekeeping
sjcfarmandfood
skagit-ag
skagit-forum
skagit-mg
skagit-mgevents
skagit4h
skagit4hleaders
skagitbeachwatchers
smallacreage
smallfarm
smallfarmlivestock
smallgrains
smallgrains-copy
sno-valley-tilth
snobeachwatchers
snoco4hcloverleaf
snocoevents
snocoext
snocta
snofoodsense
snogg
snogg-trainees
snohomish_camano_econet
snomg
snomgdiagnostics
snomginterns
snomgoffice
snomgteamoffice
southidaho_direct_seeders
southsoundag
southsoundfarms
spf-sig
spillman_users
spnw
spokaneco4-h
spokanegrowers
srsf
state_shooting_sports_trainers
statefairboard
statfaculty
statgrads
statneill
statseminars
statstaff
stem_pqa
stemmentors
stormwater
straiteconet
student-records
supporttest
sustainable
sustainnw-l
svfc
swd
swdinterestgroup
swmsu
taacommodity
tahomafoodshed
tami-test
tcmc
tcmg-mrc-friends
tdiagsnomg
teaching-faculty
teaching-faculty-copy
teamm
teamr
temporary
temptest
testdp
testjbforum
testjillwilson
testlist1
testpk
tffacstaff
tfrec-faculty
tfrec-l
tfrec-temp
tfrec-text
tfrec-usda
tfrecfaculty-admin
tfrecgradlistserv
tfrecoffice
thurston4h
transformation_research_team
tristate_agronomy
ufteam
undergraduate-student-advisors
urbanext
urbanpugetsound
vancouver_omk
ve-acinungradstudents
ve-alumni
ve-extnetwork
ve-faculty
ve-gradstudents
ve-pullungradstudents
ve-tcungradstudents
ve-ungradstudents
ve_certificate
ventenata
vesensoryevaluation
vetclinicteam
vidatest
vinevoice
virtualentnet
viticulture_online
viticultureextension
w-and-g-news
w-w-w
wa-penldr
wa-saves
wa-wineries
wa_realestate
wa4hadvisoryboard
wa4hambassadors
wa4hcamps
wa4hcoofficers
wa4hpoultry
wachall
wagrownschools
wahkiakum4-h
waomk
waor-horseteam
wcc-77
weasa-l
weavers
webpest
wecn
wedadirectors
wedaprinonly
wera20
west2008
west2009
west2010
westernclb
westrme
westrmeinfo
westrmeweb
westtaa
wffr
whatcom-mg
whatcom4h
whatcomcfa
whatcomcfa_sc
whatcomgardening
whatcomleaders
whatcommcr
whatcomparent
whatcomwaters
wheatu
wi_volunteers
wia
wia-cps
wiag-lewis
wildhorsecrm
wine-ed
wireworm
wnveducation
wownet
wqmt-l
wrap!
wrapspecialists
wrha
wricops
wrml
ws4-ha
wsclark
wsu-ic-smallfarm
wsu-mason
wsu-snoco
wsu_kc_goatnews
wsu_puyallup_lid
wsualumni-jeffco
wsuce-stewards
wsuenews
wsuext-pcards
wsufoodprocessing
wsufriends-jeffco
wsulivestock
wsuseed
wsusmallgrains
wsutcmg
wsuwest
ww
ww4hnews
wwcamano
wwextnews
wwf2fx
wwwhidbey
wxcafe
ya4h
yandfamfaculty
yandfamspecialists

Ending support for nested permissions

When does support end?

Beginning FY17 (7/1/2016) CAHNRS IT will end support for nested permissions on the file shares that we manage for our colleagues around the college.  For many users there will be little to no impact on how you use your file shares, while for others there will be a significant change in how your data is structured and how you access your data.

What are nested permissions?

Nested permissions are when sub-directories within a shared folder have different permissions from the root of the file share.  For example consider a file share named Admin, and within that file share there were two folders, Finance and Personnel.  If the users who had access to Finance were different than the users who had access to Personnel, then these folders would have nested permissions, or permissions that differed from their parent folder Admin.

What is wrong with nested permissions?

Nested permissions add substantial complexity to the management of file shares.  Each layer of permissions in a directory structure increases the amount of time it takes to apply new permissions and verify that files are properly secured.  To determine if someone had access to a folder that is nested ten layers deep, you would have to analyze ten different sets of permissions, and ensure that the user had appropriate permissions in all permission sets.

This complexity often prompts the use of nested file shares to help side step these problems.  This is the practice of creating file shares within file shares, so you can provide direct access to nested folders.  However this creates its own set of challenges, including the ability for users to create nested directories that exceed their systems maximum path length, rendering them unable to access all of their data.

Another downside to all of this complexity is that it hinders both our ability to ensure the security of your data, and our ability to rapidly resolve issues.  The more complex a system is, and in this case the more complex a permission structure is, the less confident you can be that only the people who should have access to the data, do.

Why is this change happening now?

The first reason this change is happening now is that it coincides with the roll out of our new storage platform.  This gives us an opportunity to implement best practices that will ensure we can efficiently meet your storage needs for years into the future.  The migration to this new platform was also fraught with many challenges, in large part due to problems created by nested permissions.  The challenges of this migration served to underscore the need for new file storage policies so that when the next migration occurs years down the road, the college won’t be impacted the way it was during this migration.

Additionally, it is no secret that the college is trying to become more efficient administratively.  Between the budgetary reallocation and our drive to lower costs for our customers, we simply cannot afford to spend time unproductively.  Given the time involved in managing and fixing complex nested permissions or file shares, we just can’t continue to support them without either raising rates, or removing other services.

What will happen to file shares with nested permissions on 7/1/16

All file shares will continue to work as they currently do, and we will not be taking any action that will change permissions on any file share.  However, after 7/1/16 when we receive a request to update permissions on a nested file share, we will not be able to process the request without some changes.  The two most common uses of nested file shares, and how we will handle permission requests on them, are as follows.

Changes to user subdirectories

For those who have departmental file shares with subdirectories for each faculty or staff we would encourage that the user in question migrate their data over to their official CAHNRS home directory (https://spiceworks.cahnrs.wsu.edu/portal/kb/local/3).  If a user needs more space than what is provided for free, additional space can be purchased (http://it.cahnrs.wsu.edu/storage-services/), or quotas can be shifted from the file share to the home directory.

Changes to project or group subdirectories

If you need to make changes to a group directory our recommendation will be to create a new stand alone file share for use by the group or project.  We can transfer a portion of the quota from the existing file share to provide space for the new file share, or new space can be purchased.

Please remember that this will only be necessary in the case where subdirectories would need different permissions than the root of the file share.  For the majority of users this will not present any change in how you manage your file shares or data.

If you have any questions or concerns please contact the IT Support group by sending an email to cit.support@wsu.edu.