When is orange not orange? When it is blue. Tech Support |
- When is orange not orange? When it is blue.
- Does “a” mean “at”?
- I know how SCCM works
- Just...make it work!
| When is orange not orange? When it is blue. Posted: 29 Dec 2020 01:35 PM PST I shall spare you the background but as I work for a software firm I am the IT help desk for all of mine and my wife's family. As many of us are I guess. My wife in her wisdom got her Mum and some other family members an Echo Dot for Christmas. She managed to get all apart from her Mum set up, and as I had to be that side of town today anyway I called in. Cast: Nana and Ben (me) (my name isn't Ben by the way). Nana > [wife] has got it connected to your WiFi Ben > ok, [talks her through the settings on her phone, to the point where it says.....] See where it says 'is echo in setup mode with the orange light?' Nana > yes, [presses continue] Ben > so why is it blue? Nana > I don't know Ben > [takes the phone off her and click through answering the questions correctly] - there you go, what's your WiFi details? Nana > here [passes piece of paper] that's the password Ben > What is the network name? Nana > I don't know Ben > ok, where is the internet box (yes I called it that) Nana > [shrugs] Ben > is 08:30 too early for Gin? [link] [comments]  |
| Posted: 30 Dec 2020 01:53 AM PST So this literally just happened to me. I got a call from a user at a remote branch asking for assistance to update teamviewer on a PC so that a software vendor can assist with troubleshooting why it isn't printing. Crappy software, but that's a whole different series of posts... So the first thing I ask the user is to confirm if this pc has Quick Assist installed (our entire pc fleet should have it, as it's our primary remote assistance tool). She says no it doesn't. Right, that's weird, but into plan B... We have an admin account that we leave disabled and only enable for situations like this one. So I enable the account, reset the password and proceed to give the user these creds. Now, before you tell me off for giving a user creds to an account with admin privileges, this account is normally kept disabled in Active Directory. The conversation went more or less like this: $Me: "OK $User, in the username field I want you to enter the following username for me. Now keep in mind this will be in all lower case. The word admin, followed by underscore and then a." $User: "admin... underscore... Now, by 'a', do you mean the 'at a'? Like in an email address?" It's moments like these that make me want to bang my head on the table. To make matters worse, she found Quick Assist moments later by typing it into the Cortana search box. I logon, and guess what I find... the Quick Assist icon right in the desktop where it should be... Edit: Fixed a typo [link] [comments]  |
| Posted: 29 Dec 2020 05:13 AM PST A few years ago I was a contractor doing mostly second-line desktop support for a MSP based in a clients site. At the time we had Config Mgr 2007 which us desktop guys would use for the builds and app deployments, usual stuff etc. Anyway one day we had a guy sent to site to back-fill for someone who was on holiday. I had never met him but he had been on site before and had a bit of a "reputation" as a know it all from the clients staff and the onsite MSP team. I'm down the road at a satellite office finishing up something and head back to H.Q. around lunchtime. As I walk into the office I notice a lot of activity with my team mates displaying a mixture of worry and concentration. I ask what's going on and am told that SCCM has seemingly gone full Skynet and started reimaging workstations and servers all over the estate. Oh f**k. The plug is pulled (literally) on the SCCM server and cue the ensuing chaos and triage to work out what the hell happened. As it turns out, matey was learning the build process for workstations but seemingly was so confident in his abilities he successfully added All Systems to the Windows 7 x64 build collection. Whoopsie. Cue a weeks worth of overtime whilst we reimage 300+ workstations and restore the 30+ bricked servers from tape. Suffice to say, matey was never invited back to site. [link] [comments]  |
| Posted: 29 Dec 2020 04:10 AM PST Several years ago I worked as desktop support for a hospital system. I got my job because this system had just purchased a small community hospital in the middle of nowhere and they only had one IT guy to begin with, so I came in as backup so to speak. Some years prior the community hospital had contracted with another local doctor to set up a cancer treatment center. Again, small community in the middle of nowhere. The treatment center was kind of a joke, but it did exist. The contract was about as poorly written as it gets. The hospital gave him the building and paid for the initial equipment, he maintained 51% of the business. He also did his own IT work and the hospital "would provide computer support as needed". That was the actual clause in the contract, so often times we would get called for things we had no business touching and it would start a fight because I didn't know how to work on a spectrometer. One day I get a call, and it goes a little something like this: $me = "Me" $doc = "Doctor who knows just enough to be dangerous" $vsguy = "Vendor support guy" $doc: "Hey! So...Windows XP is going out of support. I bought all new SSDs, flashed the new Windows onto them, and replaced all the hard drives in my building at once without testing, and now I have a machine that doesn't work. Come fix it!" The problem was that he had a piece of diagnostic software that would no longer work properly post-upgrade. All kinds of weird things going wrong with it. Doctor just says "It won't work". I called vendor support and, after about ten minutes of this guy getting more and more confused that I don't have the buttons and fields I should have, he asks for the version. $me: "Version...4.3" $vsguy: "Oh, dude. I'm so sorry. I'm afraid I can't help you. We're on version 8!!! I don't even have documentation for that version anymore. It's like fifteen years old..." $me: "Say no more and don't apologize! I have my answer. I know exactly what I need to tell the doctor." - *Ahem* "Doctor? Yea, you're stuff is ancient. You gotta upgrade" $doc: "Huh? Yea, I talked to them too. They want like $200,000 for that software. I'm not paying that. That's why I called you." $me: "Well, doc, I'm sorry, but I can't help you. If I was able to both A) Understand medical diagnostics at that level and B) Completely rewrite the source code of a medical diagnostic application and make it work properly and securely, I sure wouldn't be working here. You gotta upgrade." The next day.... $doc: "Hey! I think I found a way to fix that software! But now I can't get out to the internet. I need you to come fix it" $me: *facepalm* Be right there... $doc: "So...the problem was that it wouldn't run properly on the new windows, so I installed virtual box on the machine and put Windows XP on the vm, and installed the software there. It launches properly now! Unfortunately the license for the software is tied to the mac address of the computer, so I had to change the mac address of the vm to match the license so I could get it to launch, but now it can't get out to the internet. I need you to fix it." I didn't even respond. I just gave him a deadpan stare and then walked away. Last I knew he left the new Windows SSD in and swapped out to the old hard drive when he needed to use the software. Shortly before I left the organization they had forced him out for various hippa violations and completely reworked the office into a proper facility. Edit: Realized I typed Windows 7 instead of Windows XP. [link] [comments]  |
| You are subscribed to email updates from Tales From Tech Support. To stop receiving these emails, you may unsubscribe now. | Email delivery powered by Google |
| Google, 1600 Amphitheatre Parkway, Mountain View, CA 94043, United States | |
No comments:
Post a Comment