|
kensei posted:At the risk of an epic derail: Just because I know someone who complained about the 'monkeys' part of that saying, I have changed my blurb to, "Not my circus, not my clowns." I've been using "Not my elephants."
|
#
?
Nov 6, 2024 19:28
|
|
|
|
| # ? Nov 9, 2025 19:46 |
|
|
Sorry for not having the promised cookie pictures, that line isn't running this week. Please accept this substitute showing how pecan pie is created. 
|
|
#
?
Nov 7, 2024 13:47
|
|
|
So how big is the grinder for those?
|
|
#
?
Nov 7, 2024 13:52
|
|
|
Arquinsiel posted:So how big is the grinder for those? Teeth size and composition vary widely across the user base!
|
|
#
?
Nov 7, 2024 14:00
|
|
|
Dick Trauma posted:My favorite was the Lenovo laptop with the almost imperceptible slider built into the top edge of the frame. I have users put our branded privacy slider on those and our Dells (which also got harder to see lately.) My favorite is when they put them on Macs and then crack the screen because there's no clearance for it when closed. I also learned a few years ago, that the Lenovos of that time (T470s or T480s, I think) not only shuttered the camera, but actually disabled it. User had it shuttered, forgot they had done that, and then called in when Zoom complained they had no camera.
|
|
#
?
Nov 7, 2024 15:56
|
|
|
mllaneza posted:I've been using "Not my elephants." Im in industrial maintenance, we have preventive maintenance schedule with a described process on how go get stuff into a monthly maintenance day. We lock the maintenance day a week before, yet one of our project engineers decided to bypass our system by telling us that our dept manager had greenlit moving his machine lines's day back by a week, giving him a new window of bringing in more work orders. Boss hadn't and this doesnt mean I will be accepting new tickets. Boss asked me if I was scheduling "The engineers worries" for the day. "Engineer's worries are not my worries." seemed to be valid answer.
|
|
#
?
Nov 11, 2024 21:13
|
|
|
A ticket came in some days ago iPhone prompting for corp account password when installing apps, despite not being logged into the App Store, and MDM not affecting app installation  "Hey I'm contacting you about your iPhone issue - can we do a call to see what's going on?" "I've already sent an email""I know, I want to work on the problem with you""What's not clear?""[answer about what the issue could probably be]""It's not that, I've done X""[elaboration and confirmation on the correct sign in] Can you do a call so we can look at it?""If it was that simple, I'd have fixed it myself""Okay, then call Apple, here's the details""Call them and tell me what to do""I don't have the phone, so they can't tell me what to do without seeing what's going on""You have all the details of my device, let me know if you need anything else"At this point it could be that they need to log in to Intune just to remove it or to sync the new policy or whatever (but I doubt it), all the way to them not actually logging in to the right account, or any number of things, but with that conversation (paraphrased) having taken about a week, since there's at least 7 time zones of difference, the amount I care has cratered very rapidly, and is at this point mostly curiosity, and not much of it. I do kinda wanna call Apple tho. "Hey I am calling about iPhone with SN D0N65NBU77S, can you tell me what to do? No I don't have it with me. Sure, I'll tell them to restart, and get back to you if it doesn't work, thanks."
|
|
#
?
Nov 13, 2024 21:03
|
|
|
I mean, I am the type that will avoid calls at almost any cost. But seriously, this is some next-level poo poo.
|
|
#
?
Nov 13, 2024 21:47
|
|
|
Serperoth posted:A ticket came in some days ago Ticket closed due to user refusing to troubleshoot.
|
|
#
?
Nov 13, 2024 22:13
|
|
|
MF_James posted:Ticket closed due to user refusing to troubleshoot.
|
|
#
?
Nov 13, 2024 23:50
|
|
|
MF_James posted:Ticket closed due to user refusing to troubleshoot. Ticket reopened by CFO, user is very important and needs this fixed immediately!!111!
|
|
#
?
Nov 14, 2024 00:22
|
|
|
Methylethylaldehyde posted:Ticket reopened by CFO, user is very important and needs this fixed immediately!!111! Access HR database, set CFO's termination date to last Friday. Checkmate.
|
|
#
?
Nov 14, 2024 01:06
|
|
|
MF_James posted:Ticket closed due to user refusing to troubleshoot.
|
|
#
?
Nov 14, 2024 04:54
|
|
|
MF_James posted:Ticket closed due to user refusing to troubleshoot. Pretty much. I don't know if this is an individual ticket, or if it's part of some other thing, but at some point I'm cutting my losses and saving my time. It's your problem, if you want it solved (like you say), you gotta do a bit more than tell us "Solve it"
|
|
#
?
Nov 14, 2024 05:48
|
|
|
Yup. We’re about to disable a laptop that is way out of compliance and the user has not responded at all to contact, both direct and through the automated warning workflow. It’s nice when we have compliance policy with teeth to back us up.
|
|
#
?
Nov 14, 2024 14:10
|
|
|
Serperoth posted:Pretty much. I don't know if this is an individual ticket, or if it's part of some other thing, but at some point I'm cutting my losses and saving my time. It's your problem, if you want it solved (like you say), you gotta do a bit more than tell us "Solve it" The time is now. Also I'm spiteful enough to that I'd phrase it "user refused to co-operate" so that it becomes a "user is immature" thing rather than "user was just too busy to troubleshoot (which is IT's job y'know!)" with their manager.
|
|
#
?
Nov 14, 2024 17:55
|
|
|
Weatherman posted:The time is now. "Unable to troubleshoot remotely, recommend user travel to office with IT on site, closing ticket".
|
|
#
?
Nov 15, 2024 02:53
|
|
|
User unable to troubleshoot on iPhone, issuing user flipphone
|
|
#
?
Nov 15, 2024 18:23
|
|
|
Knormal posted:User unable to troubleshoot on iPhone, issuing user flipphone brb pretending i don't know how to use my iphone
|
|
#
?
Nov 15, 2024 19:14
|
|
|
A situation that baffled us came in User reports hitting the connections cap on a file server (Win10 Business), after it's already raised to the max (20). Checked sessions, 20 sessions indeed, all with reasonably long total connection times. Idle times all under 10m. Today morning, after user restarted the server, checked again. Sessions active (not 20), idle times all under 10m... Turns out, idle time resets to 0 when hitting 10m, so the idle timeout (15m by default) is never hit, so sessions stay connected. I connect from their DC (happened to have an RDP open while looking into it), session closes without issue after closing the Explorer window. Restarting client device clears the connection, so that's a temporary thing, but all my looking up is only bringing up RDP idle timers, and I can't find a thing about the idle timer keeping alive. I have some workaround ideas (restarting clients, etc), but I haven't been able to find much in terms of configuration, I'm tempted to look into if we can figure out the keep alive packet or something. Edit: for another not-awful thing, I spoke to the sweetest user today. She was stressed in general, the issue was basically nothing, but she closed with "thank you so much for your prompt assistance", I didn't even do my usual "all in a day's work" joke. Serperoth fucked around with this message at 14:10 on Nov 21, 2024 |
|
#
?
Nov 21, 2024 13:54
|
|
|
How are users connecting? Is there any chance they have a mouse jiggler active on their machine and interacting with the RDP window? Are there any task being launched every 10 minutes ran as whoever is logged on?
|
|
#
?
Nov 21, 2024 20:02
|
|
|
Isn't the issue that you're trying to run a Windows client PC as a NAS and could buy an actual NAS with the cost of the time being spent on this?
|
|
#
?
Nov 21, 2024 20:08
|
|
|
minusX posted:How are users connecting? Is there any chance they have a mouse jiggler active on their machine and interacting with the RDP window? Are there any task being launched every 10 minutes ran as whoever is logged on? It's not RDP, it's a file share, so a mouse jiggle or something wouldn't do it, but even so, 15+ different machines having a jiggler seems like a stretch. Might be something running every 10 mins, but it could just be some service or process keeping the share alive. LanManWorkstation is a possible candidate, but I can't stop that without turning off Winlogon and a couple of others, which I want to avoid. Thanks Ants posted:Isn't the issue that you're trying to run a Windows client PC as a NAS and could buy an actual NAS with the cost of the time being spent on this? It's a client OS but the machine isn't a client, it acts as the server. Plus, we're the MSP, they've already paid for us to look into this, if they want upgrades etc, that'd be a possible additional cost. The bigger limitation of the OS would be that the concurrent connections limit is capped to 20, but they don't need more than 20, as long as the connections close when they're supposed to. They SHOULD be using the right stuff, I don't disagree, but from what I've been able to figure out, it's the clients that are resetting the idle time.
|
|
#
?
Nov 21, 2024 21:39
|
|
|
At a pure guess, file shares aren't timing out after just 10 mins and they hang around for as long as the client is alive for, or possibly you're using SMB multichannel and one client is more than one connection. Where are you seeing the connection has timed out? IIRC if it's showing in "net use" in the client then it hasn't timed out. Thanks Ants fucked around with this message at 21:48 on Nov 21, 2024 |
|
#
?
Nov 21, 2024 21:45
|
|
|
Thanks Ants posted:At a pure guess, file shares aren't timing out after just 10 mins and they hang around for as long as the client is alive for, or possibly you're using SMB multichannel and one client is more than one connection. The connections do not time out, that's the problem. I'm seeing the timers on Computer Management, as open sessions. What they're supposed to do is that the idle time goes up, it reaches the limit (default is 15), and the session disconnects. What happens is that it reaches 10 minutes, then the idle timer goes back to zero, so it never hits the auto-disconnect like it should.
|
|
#
?
Nov 21, 2024 21:57
|
|
|
Do we know it's definitely meant to work that way? I assumed that figure was a timeout that would end a session when a client wasn't around any more, and that as long as it was on the network it would get asked by the server if it was still there, and then go "yup" and start the timer again. If it is meant to work in that way I'd isolate a client and observe things in procmon and see what might be trying to access this path as soon as the connection is taken down by the server, you might have to do some management of things like search indexers, icon preview generation, third-party security apps etc. Edit: Are the shares connected as mapped drives? Thanks Ants fucked around with this message at 22:13 on Nov 21, 2024 |
|
#
?
Nov 21, 2024 22:05
|
|
|
Just set the timeout to 9:59 IMHO
|
|
#
?
Nov 21, 2024 22:17
|
|
|
Thanks Ants posted:Edit: Are the shares connected as mapped drives? came here to post this windows will keepalive smb connections if they're a mapped drive and/or the explorer window is left open
|
|
#
?
Nov 21, 2024 22:29
|
|
|
Yeah, trying to manage SMB timeouts for a Windows "server" because you're using the client version of Windows and are trying to stay under the limit is a fools errands. Redoing things correctly is the right move. Guess you get to find out if you work for a bad MSP or a worse MSP!
|
|
#
?
Nov 21, 2024 23:03
|
|
|
sometimes I hate that I can understand this stuff
|
|
#
?
Nov 22, 2024 03:20
|
|
|
Internet Explorer posted:Yeah, trying to manage SMB timeouts for a Windows "server" because you're using the client version of Windows and are trying to stay under the limit is a fools errands. Redoing things correctly is the right move. Guess you get to find out if you work for a bad MSP or a worse MSP! Obviously, but that's not even my scope at this time. The thing (and the reason I'm stumped) is that this seems like it's the clients keeping the connection alive, not the "server" not obeying the rule or the like, and if that's the case, the same situation could arise again with a server OS (even if it doesn't hit the limit, the connections refreshing themselves rather than the idle timer counting up correctly) johnny park posted:Just set the timeout to 9:59 IMHO Also an option. I'll see about that or the mapped drive thing. Edit: this is for around 100GB of data. They already have SharePoint and all the rest of the 365 jazz. So at this point it's just my curiosity. Serperoth fucked around with this message at 10:38 on Nov 22, 2024 |
|
#
?
Nov 22, 2024 06:33
|
|
|
my cat is norris posted:sometimes I hate that I can understand this stuff
|
|
#
?
Nov 22, 2024 12:24
|
|
|
I don't know if I would trust a seasoned IT professional who didn't hate computers.
|
|
#
?
Nov 22, 2024 14:20
|
|
|
BlankSystemDaemon posted:Hating computers is proof you know computers.
|
|
#
?
Nov 22, 2024 14:45
|
|
|
my cat is norris posted:sometimes I hate that I can understand this stuff god dammit same
|
|
#
?
Nov 22, 2024 15:13
|
|
|
Wife: I had a bad day at work, I had to call CPS on a family, the whole thing's hosed up. Me: I also had a bad day at work, and obscure bug broke multicast on our entire access layer and not even Cisco could figure out why so I had to sit there and manually configure SSM on - you know what nevermind
|
|
#
?
Nov 22, 2024 15:16
|
|
|
Serperoth posted:Obviously, but that's not even my scope at this time. The thing (and the reason I'm stumped) is that this seems like it's the clients keeping the connection alive, not the "server" not obeying the rule or the like, and if that's the case, the same situation could arise again with a server OS (even if it doesn't hit the limit, the connections refreshing themselves rather than the idle timer counting up correctly)
|
|
#
?
Nov 22, 2024 16:06
|
|
|
A ticket came in: Numbers have changed in <report> That's it. That's the entire ticket, no screenshots, no additional information to indicate what the numbers should be, were, are, no information on anything the user has or hasn't done that might have caused this, nothing. Amazing work, 5 stars to the ticket creator.
|
|
#
?
Nov 22, 2024 16:44
|
|
|
Categorise it as user providing you information, thank them for it, close the case
|
|
#
?
Nov 22, 2024 16:46
|
|
|
|
| # ? Nov 9, 2025 19:46 |
|
|
Oh I went one better and let someone else take it.
|
|
#
?
Nov 22, 2024 16:47
|
|