The new forums will be named Coin Return (based on the most recent vote)! You can check on the status and timeline of the transition to the new forums here.
Please vote in the Forum Structure Poll. Polling will close at 2PM EST on January 21, 2025.
My backup file server was using DFS for the backup of the files on it. Someone was using offline file synching on the old server to synch all the files on their laptop with those on the server.
When the old file server gave up its ghost, I put the backup server in play and it was all good. Come Monday, the offline files were access denied to the person and to the admin account. Seems that the synching was altering the permissions somehow and did not like it that they were on a new server. I grabbed ownership of the folder and then changed permissions for the folder and then they could access the entire folder.
I don't know if this is your exact issue, but we had a problem with our main shared DFS folder after upgrading to WS2012R2. Since nobody maps at the top level folder (all drives are mapped one level down), we didn't give users any read permissions to the top level folder. When we moved to 2012 clients started having problems mapping drives until we gave read and list to domain users at that folder level. It was super weird.
You know what's crazy about this? I've been hearing more stories along these lines (my shop is also just a two-man show) and it seems like companies are quick to hire extra help for other departments, but when it comes to IT asking for help they just shrug, give a high five and shout "You can do it!" as if that's going to help us out at all. I get that most people don't understand (or even care about) what we do, but that translates directly into not giving a damn about the department at all.
It's the norm where I'm at, it's as though the assumption is IT is easy and a couple clicks of the mouse is all that it takes to sort out a problem. Perhaps it's due to the decision makers having experience with IT accessing their workstation remotely and sorting out an issue swiftly and I'd wager in most shops the bulk majority of single user incidents are probably quick resolutions so they just assume everything is just as easy. Also, as the years have gone by costs seem to be going down at least in the hardware realm while also getting a larger feature set. This in tandem with downtime being less desirable as we rely more on IT has likely pushed more shops, even smaller ones, to leverage tech that increases reliability and availability. So even with some significant failures in an environment with redundancy and/or automatic or manual failover in place that might take the IT staff many hours of work to make whole again, the actual downtime a user experiences might be pretty insignificant if we're doing things right back in IT. Guess how long upper management is going to think you spent fixing the issue? The 15 minutes of downtime they experienced, not the day or two of work you spent troubleshooting, ordering replacement parts/equipment, installing and ultimately reconfiguring said items and they certainly wouldn't begin to contemplate the time you've invested in maintaining said equipment in the time it had been online prior to the failure. People still seem to just assume that we're only working when we're on the phone with someone and any other time we're just back here twiddling our thumbs waiting for a fire to put out.
Apparently with today's set of updates, Microsoft is releasing a consumer-only "patch" (KB3035583) which is essentially adware for the Windows 10 free upgrade for Windows 7 & 8.1. Once installed, it will receive a trigger which begins informing the user that their Windows 10 free upgrade is ready to install. While that might not seem terrible, it apparently become quite obnoxious and insistent. If a consumer has automatic Windows Update installed, it will get installed. Those that do not can ignore the Recommended category, but how many end users do you know that do not have automatic updates enabled?
What I find the most disturbing is that typical users are going to view this with skepticism and believe it is malware. Once they find out that it is legitimate, they'll let their guard down and do something stupid with the thought of "The last one was legitimate, so this one must be too!"
Good news: this won't affect enterprise products (i.e., volume license key installs).
Also who the fuck strips screws, then decides, "yeah cool, let's just ratchet these right back down as tight as humanly possible" I cannot for the life of me get these screws out.
0
KakodaimonosCode fondlerHelping the 1% get richerRegistered Userregular
Just posted that to D&D, but this is why you don't let your boss decide if something is safe.
Hang on to that, hide any other stash of power cords if you keep a stash then steal your bosses power cord. When they ask you for one, you know what to do.
I'd worry someone would abscond with it without my knowledge and hurt themselves. Already cut in half and in the trash.
Cut in half you say? Yes, you see, because someone in their right mind thought it would be cool to go into the trash and take wires and equipment out of it.
It's in the trash.
There's a reason for it.
You pay me for my expertise and knowledge, I don't just throw shit away because its old (I have done this though).
My shitty ex-boss that I tell so many stories about actually had old BNC coax monitor stuff.
He was holding onto about a box worth of it because "just in case."
Okay, maybe a few cables here or there, if you absolutely need them you can bill clients for them and order them (they still make those).
But when he was out of town one of the other techs that was learning from me (probably to replace me when he was more confident) was in the storage room resetting equipment. The problem was this equipment was stashed behind all those boxes. They were piled haphazardly.
They fell on him. He hurt himself, not seriously, but it put him out of commission for a day. So when he returned I had him go through the boxes and sort shit. Triplicates of items get saved, anything more than that gets tossed. Save the boxes.
We organized that storage room and categorized all the stuff.
Apparently my exboss lost his shit when he found out after a few months after I left.
Funny you mention cutting it in half, that reminds me of one of my part-timers about 11-12 years ago or so before I was in a pure IT role and was running a PC shop. We're in the back room on a slow day getting caught up on machines in for service when I hear a loud pop followed by one side of the shop going dark. The fucking idiot happened to be playing around with a pair of scissors and for whatever dumb ass reason they just randomly cut a power cord in half - that was plugged in. They didn't get hurt but I'm pretty sure they shit themselves.
We were actually installing a camera system for a client.
Instead of teaching us how to properly crimp BNC, my boss decided the best strategy was to talk 2 programmers and let us install it via twist on BNC connectors. Problem with twist on BNC connectors, they're extremely finicky, and the tight quarters of the equipment meant a lot of electrical tape to keep everything kosher.
It looked terrible.
It lost connection once a week on certain cameras.
Seriously, do shit right, how hard is it to crimp BNC? (Not hard at all with the right tools and some practice)
Funny you mention cutting it in half, that reminds me of one of my part-timers about 11-12 years ago or so before I was in a pure IT role and was running a PC shop. We're in the back room on a slow day getting caught up on machines in for service when I hear a loud pop followed by one side of the shop going dark. The fucking idiot happened to be playing around with a pair of scissors and for whatever dumb ass reason they just randomly cut a power cord in half - that was plugged in. They didn't get hurt but I'm pretty sure they shit themselves.
Funny you mention cutting it in half, that reminds me of one of my part-timers about 11-12 years ago or so before I was in a pure IT role and was running a PC shop. We're in the back room on a slow day getting caught up on machines in for service when I hear a loud pop followed by one side of the shop going dark. The fucking idiot happened to be playing around with a pair of scissors and for whatever dumb ass reason they just randomly cut a power cord in half - that was plugged in. They didn't get hurt but I'm pretty sure they shit themselves.
How fucking stupid do you have to be to do this?
Very stoopid, but those people exist. We had a co-op at one point who I was training. I gave him a new machine and said to swap it out with the old one for a user. Moments later the user comes back and said she was going to kill him. Turns out that while she was working in Dynamics cutting checks, he flat out unplugged the computer and giggled "uh... hee hee, whoops."
People like that don't check if shit is plugged in.
While I agree that being insensitive is an issue, so is being oversensitive.
Funny you mention cutting it in half, that reminds me of one of my part-timers about 11-12 years ago or so before I was in a pure IT role and was running a PC shop. We're in the back room on a slow day getting caught up on machines in for service when I hear a loud pop followed by one side of the shop going dark. The fucking idiot happened to be playing around with a pair of scissors and for whatever dumb ass reason they just randomly cut a power cord in half - that was plugged in. They didn't get hurt but I'm pretty sure they shit themselves.
How fucking stupid do you have to be to do this?
Pretty stupid, but that's usually par for the course when it comes to a lot of techs working jobs like that. We just needed people who basically could run malware scans and make backup images and reload Windows. Most of the techs I'd hire it didn't make any sense to try and get them to do any hardware troubleshooting. Now most of the people I hired often had aspirations of getting into the IT industry and were going to use their employment with me as a stepping stone to get some real world experience before transitioning to a help desk type role. I had at least a couple dozen part timers over the years, only one that I know of ended up making a career for themselves in an IT role.
Also who the fuck strips screws, then decides, "yeah cool, let's just ratchet these right back down as tight as humanly possible" I cannot for the life of me get these screws out.
I have, on more than one occasion gotten a drill out (its a corded 2 handed hammer drill, though not on the hammer setting) and just drilled a screw out. Not drill as in unscrew, drill as in drill through it.
Not because it was the best thing to do, but it always feels awesome doing it. Even more so when the guy who stripped it is right there.
Draygo on
0
TL DRNot at all confident in his reflexive opinions of thingsRegistered Userregular
Also who the fuck strips screws, then decides, "yeah cool, let's just ratchet these right back down as tight as humanly possible" I cannot for the life of me get these screws out.
I have, on more than one occasion gotten a drill out (its a corded 2 handed hammer drill, though not on the hammer setting) and just drilled a screw out. Not drill as in unscrew, drill as in drill through it.
Not because it was the best thing to do, but it always feels awesome doing it. Even more so when the guy who stripped it is right there.
Just maintaining eye contact with him the whole time.
tl;dr: a modified network packet can bluescreen the server. There are code examples running right now essentially scanning the internet for servers that are vulnerable and BSOD'ing them. This is remote code execution so it won't be long before this modified packet method can be used to execute something other than a bluescreen.
This is a big deal.
EDIT: So I've been doing some research on this vulnerability and http.sys in general, and holy shit this could be a bad one. http.sys is a kernel level driver, which means it has full access to the system account. And a ton of things access it. I just about had a heart attack when I saw that WinRM (aka remote powershell) also uses http.sys, but apparently by default traffic on WinRM is encrypted so I *hope* that powershell is ok.
From what I'm gathering anything that can hit http.sys with a specific header can trigger this. Servers with IIS are more vulnerable to it because they have more ports open and are easier to get at http.sys externally. But in theory anything that can hit http.sys can execute code.
Listen if you think you can do my job, go right ahead.
But no, someone's printer queue being stuck wouldn't "lock" the access to the patient record.
And because this is foxpro, it's an old DB system, so only one person can be in a patient record at once.
So that means you can't get into the record to print your documents because someone is still in it.
Just because they said they're not in it, doesn't mean they're not in it, they are lying to you.
"Someone would lie about this?"
Yes, people lie to me all fucking day. They don't see it as a lie, but omission of the truth to cover their ass is still a lie when you boil away all the fucking bullshit.
Yes, people lie to me all fucking day. They don't see it as a lie, but omission of the truth to cover their ass is still a lie when you boil away all the fucking bullshit.
Exactly. And what they don't realize (more like don't care) is that when they lie about something, it takes up our time trying to figure shit out. It's not hard to say "Oops, I did this or that. My bad." I'm more likely to thank you for letting me know than to give you shit about doing something stupid.
While I agree that being insensitive is an issue, so is being oversensitive.
I've definitely helped people in the past with really bad tremors and watched as they selected a bunch of files on the desktop and tried to drag them, only to accidentally release at the wrong time and hit copy. Over and over.
A machine was pissing me off, it would get an IP but not actually be able to talk to anything on the network.
I accidentally hit the "Let Windows search for solutions" thing while navigating menus.
I let the thing run cause why not.
It fixed it.
It actually happened.
Incredible.
life's a game that you're bound to lose / like using a hammer to pound in screws
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
Walked in early this morning, all set to sit and slowly go over the morning monitoring events while sipping tea. What's that noise I hear before even entering my office? Is that... are those the server fans? I open the door and get blasted with heat, only to find that the HVAC system shut down at some point. A few of the LED panels on the front of the servers are blaring temperature warnings. System board temperatures are over 42C.
...god fucking damnit
While I agree that being insensitive is an issue, so is being oversensitive.
Walked in early this morning, all set to sit and slowly go over the morning monitoring events while sipping tea. What's that noise I hear before even entering my office? Is that... are those the server fans? I open the door and get blasted with heat, only to find that the HVAC system shut down at some point. A few of the LED panels on the front of the servers are blaring temperature warnings. System board temperatures are over 42C.
Posts
This is a clickable link to my Steam Profile.
It's the norm where I'm at, it's as though the assumption is IT is easy and a couple clicks of the mouse is all that it takes to sort out a problem. Perhaps it's due to the decision makers having experience with IT accessing their workstation remotely and sorting out an issue swiftly and I'd wager in most shops the bulk majority of single user incidents are probably quick resolutions so they just assume everything is just as easy. Also, as the years have gone by costs seem to be going down at least in the hardware realm while also getting a larger feature set. This in tandem with downtime being less desirable as we rely more on IT has likely pushed more shops, even smaller ones, to leverage tech that increases reliability and availability. So even with some significant failures in an environment with redundancy and/or automatic or manual failover in place that might take the IT staff many hours of work to make whole again, the actual downtime a user experiences might be pretty insignificant if we're doing things right back in IT. Guess how long upper management is going to think you spent fixing the issue? The 15 minutes of downtime they experienced, not the day or two of work you spent troubleshooting, ordering replacement parts/equipment, installing and ultimately reconfiguring said items and they certainly wouldn't begin to contemplate the time you've invested in maintaining said equipment in the time it had been online prior to the failure. People still seem to just assume that we're only working when we're on the phone with someone and any other time we're just back here twiddling our thumbs waiting for a fire to put out.
Prior to 2012, you had to use UAG to do it.
What I find the most disturbing is that typical users are going to view this with skepticism and believe it is malware. Once they find out that it is legitimate, they'll let their guard down and do something stupid with the thought of "The last one was legitimate, so this one must be too!"
Good news: this won't affect enterprise products (i.e., volume license key installs).
For more information
XBL:Phenyhelm - 3DS:Phenyhelm
As a developer, it a down right pleasure to work in.
As a system admin.. meh it's unix.
Just posted that to D&D, but this is why you don't let your boss decide if something is safe.
Look. Unless you're standing in water or touching some metal it's very unlikely you'll complete the circuit. Don't be such a baby.
Hang on to that, hide any other stash of power cords if you keep a stash then steal your bosses power cord. When they ask you for one, you know what to do.
Cut in half you say? Yes, you see, because someone in their right mind thought it would be cool to go into the trash and take wires and equipment out of it.
It's in the trash.
There's a reason for it.
You pay me for my expertise and knowledge, I don't just throw shit away because its old (I have done this though).
He was holding onto about a box worth of it because "just in case."
Okay, maybe a few cables here or there, if you absolutely need them you can bill clients for them and order them (they still make those).
But when he was out of town one of the other techs that was learning from me (probably to replace me when he was more confident) was in the storage room resetting equipment. The problem was this equipment was stashed behind all those boxes. They were piled haphazardly.
They fell on him. He hurt himself, not seriously, but it put him out of commission for a day. So when he returned I had him go through the boxes and sort shit. Triplicates of items get saved, anything more than that gets tossed. Save the boxes.
We organized that storage room and categorized all the stuff.
Apparently my exboss lost his shit when he found out after a few months after I left.
Instead of teaching us how to properly crimp BNC, my boss decided the best strategy was to talk 2 programmers and let us install it via twist on BNC connectors. Problem with twist on BNC connectors, they're extremely finicky, and the tight quarters of the equipment meant a lot of electrical tape to keep everything kosher.
It looked terrible.
It lost connection once a week on certain cameras.
Seriously, do shit right, how hard is it to crimp BNC? (Not hard at all with the right tools and some practice)
How fucking stupid do you have to be to do this?
People like that don't check if shit is plugged in.
Pretty stupid, but that's usually par for the course when it comes to a lot of techs working jobs like that. We just needed people who basically could run malware scans and make backup images and reload Windows. Most of the techs I'd hire it didn't make any sense to try and get them to do any hardware troubleshooting. Now most of the people I hired often had aspirations of getting into the IT industry and were going to use their employment with me as a stepping stone to get some real world experience before transitioning to a help desk type role. I had at least a couple dozen part timers over the years, only one that I know of ended up making a career for themselves in an IT role.
I have, on more than one occasion gotten a drill out (its a corded 2 handed hammer drill, though not on the hammer setting) and just drilled a screw out. Not drill as in unscrew, drill as in drill through it.
Not because it was the best thing to do, but it always feels awesome doing it. Even more so when the guy who stripped it is right there.
Just maintaining eye contact with him the whole time.
https://support.microsoft.com/en-us/kb/3042553
tl;dr: a modified network packet can bluescreen the server. There are code examples running right now essentially scanning the internet for servers that are vulnerable and BSOD'ing them. This is remote code execution so it won't be long before this modified packet method can be used to execute something other than a bluescreen.
This is a big deal.
EDIT: So I've been doing some research on this vulnerability and http.sys in general, and holy shit this could be a bad one. http.sys is a kernel level driver, which means it has full access to the system account. And a ton of things access it. I just about had a heart attack when I saw that WinRM (aka remote powershell) also uses http.sys, but apparently by default traffic on WinRM is encrypted so I *hope* that powershell is ok.
From what I'm gathering anything that can hit http.sys with a specific header can trigger this. Servers with IIS are more vulnerable to it because they have more ports open and are easier to get at http.sys externally. But in theory anything that can hit http.sys can execute code.
This is a really big deal.
Listen if you think you can do my job, go right ahead.
But no, someone's printer queue being stuck wouldn't "lock" the access to the patient record.
And because this is foxpro, it's an old DB system, so only one person can be in a patient record at once.
So that means you can't get into the record to print your documents because someone is still in it.
Just because they said they're not in it, doesn't mean they're not in it, they are lying to you.
"Someone would lie about this?"
Yes, people lie to me all fucking day. They don't see it as a lie, but omission of the truth to cover their ass is still a lie when you boil away all the fucking bullshit.
Yeah, No. It's the Idiot part timer you hired even though she "says she isn't doing it" I can prove she is.
XBL:Phenyhelm - 3DS:Phenyhelm
A machine was pissing me off, it would get an IP but not actually be able to talk to anything on the network.
I accidentally hit the "Let Windows search for solutions" thing while navigating menus.
I let the thing run cause why not.
It fixed it.
It actually happened.
Incredible.
fuck up once and you break your thumb / if you're happy at all then you're god damn dumb
that's right we're on a fucked up cruise / God is dead but at least we have booze
bad things happen, no one knows why / the sun burns out and everyone dies
I've had success with that with that exact issue a couple times. I have no idea why.
This is a clickable link to my Steam Profile.
...god fucking damnit
:bro: