This is probably common, but still ... sheesh.

[erunamiryene.livejournal.com]

User: "I need access to the S drive."
Me: *checks access* "You're already in the correct group."
User: "The X drive?"
Me: "You said the S drive."
User: *checks post-it note in hand* "Oh, I meant the X drive."
Me: *internal sigh, checks access* "You're in that group, as well."
User: "Oh, okay." *leaves*
Me: *facepalm*

Three minutes later:
*Phone rings*
Me: "ISMO, Sgt Smith speaking, how can I help you?"
User: "It's not there."
Me: "Um ... what isn't?"
User: "The shared drive."
Me: "Have ... have you mapped it?"
User: "I have to map it? It doesn't just show up?"
Me: *headdesk*

I might add that this particular user had been on both access lists since she came to our unit ... so if they were going to "just show up," you'd think they would have done so by now.

I'm going to get more coffee. XD

Comments

[teriwyn.livejournal.com]

Your post makes me "miss" all the time I spent contracting for such individuals at Ft. Detrick before I went back to school.
... to get a degree in Information Assurance so I can just come back and do the same stuff ...

[mattcaron.livejournal.com]

Information Assurance

Haven't ever heard of that one before, but I'm more on the R&D and engineering side of things. What is it? As in "what do they teach you"?

[zzyzx.livejournal.com]

Information Assurance: Yes, your data is still there. Honestly.

[ptstech.livejournal.com]

BWAHAAHAAA!!!

[teriwyn.livejournal.com]

Close. "Yes, your data is still there, and noone else has touched it. Honestly."

[teriwyn.livejournal.com]

In looking for a good resource to link, I found that Wikipedia's entry paints a pretty accurate overview of the field. Simply put, it's an almost DoD specific flavor of Information Systems Security and related disciplines. Focuses are on risk management, data security, etc.

http://en.wikipedia.org/wiki/Information_assurance

[erunamiryene.livejournal.com]

The field in DoD that can really make you a bucketload of cash on the outside. XD

[mattcaron.livejournal.com]

That explains it well. Thanks. Seems very interesting, and perhaps something I might pursue if I get bored (I sortof do those types of things as a hobby now).

Good luck to you.

[xforge.livejournal.com]

Pfah! If we asked one of our users to map their own shared drives, their heads would explode. They're not even aware of the concept. They're not even aware that the letter assignments are actually arbitrary. I get people all the time asking for "the M drive" or such and the only ones we have "reserved" or what have you are R (shared) and U (My Documents).

[freakbarman.livejournal.com]

Yeah same way here. I get users all the time "I need the S drive"... O.k. what is it pointing to? "Well I don't know, You should know that."

*headdesk*

[mtupyro.livejournal.com]

Same here. Luckily we have automagical login scripts that map every network drive their supposed to have access to.

[alcoholiday.livejournal.com]

And here as well.. I work at a university and if I tried to explain the concept of mapping a drive to some of these folks, they'd spontaneously combust.

[mouser.livejournal.com]

Yea, us too. Unfortunetly we've also got people that leave themselves logged in overnight. And the systems auto-disconnect. And certain apps don't get the drives the reconnect.

And LOTS of lusers that have to be asked EVERY TIME "Did you restart your computer?"

[the-s-guy.livejournal.com]

A WORLD of yes to all the above. Argh with extra argh.

Even saying "Which of the ten thousand possible X drives is the one you are after?" gets old after the forty-zillionth repetition.

Triple-fudge-sundae-argh to the teams which decide to implement a manual mapping for their half-a-dozen members and not tell anyone else in the twenty-thousand-person company about it, so when a new starter in that team calls us up asking for the "J drive", we get to say "What the hell are you talking about?"

Note to self: write an application which displays the current AND userprofile-saved drive mappings for any person on a network, so that when callers say "The J drive that Mary has", I can call up Mary's mappings and either clone them to the caller's profile (and current mappings), or (if I'm feeling vengeful), blow away EVERY current and user-specific mapping to the given directory and leave the not-following-procedure team flapping around like electroshocked thalidomide babies.

[the-s-guy.livejournal.com]

Come to think of it, I'm adding that to my list of techsupport software which needs to be written.

[trixtah.livejournal.com]

Really, I thought the WTF was that the OP expected the user to do their own drive mapping. Have they not heard of logon scripts?

[enchanrenan.livejournal.com]

Some people in our company are totally awful/lazy as a result of this though. Marketing especially.

"Can we have I: go to our images folder, inside our M: drive?"

/sigh

[nomoremystery.livejournal.com]

Our users have H drives (unique to them), G drives (group drives) and P drives (actually a collection of G drives from across the organisation, generally with read only access to other areas).
On more than one occasion when I was on support I had someone say a document is on the P drive, then when I couldn't find it they'd pipe up "P for Personal"... Now if you'd said that earlier I'd have gone looking in your H drive...
Now I'm an operator I just get cases from the front office asking for a file to be restored on "the P drive" - and which of the 20 or 30 servers that make up "the P drive" would that be then...