Normally my job is pretty relaxed so most things don't bother me. Apparently not today.
So I help out with some Microsoft SCCM implementations and a question reached me as to whether there are any changes on one of the implementations to the Microsoft Autosave feature. Apparently someone had been working "all day long without saving" and then lost his work. He was at home and his internet went out so when he closed the document it prompted him to save locally instead of the network location originally opened the file from.
Thinking that autosave was magically saving everything to a location he no longer had access to he hit 'No'.
And now its IT's fault that his work is gone. Phrases like "there was a big setup failure here" and "this behavior MUST be fixed".
I guess he's high enough to cause some ruckus over there because normally that should pretty much end at the "I didn't save all day" part of his complaint. Oh well - I don't work for his organization and know the local IT guy who called me pretty well so I was at least able to give him some suggestions to fix the issue that would not necessarily be well received by the end user. Still it bothers me that they have to deal with that crap
So I help out with some Microsoft SCCM implementations and a question reached me as to whether there are any changes on one of the implementations to the Microsoft Autosave feature. Apparently someone had been working "all day long without saving" and then lost his work. He was at home and his internet went out so when he closed the document it prompted him to save locally instead of the network location originally opened the file from.
Thinking that autosave was magically saving everything to a location he no longer had access to he hit 'No'.
And now its IT's fault that his work is gone. Phrases like "there was a big setup failure here" and "this behavior MUST be fixed".
I guess he's high enough to cause some ruckus over there because normally that should pretty much end at the "I didn't save all day" part of his complaint. Oh well - I don't work for his organization and know the local IT guy who called me pretty well so I was at least able to give him some suggestions to fix the issue that would not necessarily be well received by the end user. Still it bothers me that they have to deal with that crap