Wow what a dick move by your provider though jesus.
Not even a quick phone call with "hey we're getting a lot of DNS queries from your side that's unusual, what's up" ? I imagine you guys are big business for them, or at least, big enough to open a dialog to see if it can't be fixed without downtime.
not a doctor, not a lawyer, examples I use may not be fully researched so don't take out of context plz, don't @ me
I'm surprised, but I'm kind of not either. It was bound to happen at some point:
PowerWare - ransom that is utilizing PowerShell to execute. The good news is that it only works on systems where PowerShell's default encryption policy has been elevated. Bad news is that any organization where IT has relaxed local rights restrictions by granting everyone local admin may be at risk.
While I agree that being insensitive is an issue, so is being oversensitive.
since powershell can leverage the whole .NET codebase they wrote their whole ransomware in powershell, and now they don't need a separate executable (which is easier for AV to detect)
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
Downgrading the BIOS back to the original version bypassed bitlocker.
holy fuck I can't believe that worked
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
Downgrading the BIOS back to the original version bypassed bitlocker.
holy fuck I can't believe that worked
I literally don't believe it.
neither do I but I am logged into the machine
I spent more time figuring out how to get the damn BIOS .exe to run lol
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
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
I'm most excited about Bash on Windows because I can just grep things instead of having to fumble through remembering what order to put findstr flags in.
Also, my coworker was 12th in line waiting for dell support over the last 45 minutes.
Him: "Just take over, I have to go"
Me: "It's awfully trusting of you to leave your laptop here and expect to not have your background changed"
Him: "I'm taking my laptop with me, i'll send you the service info"
I'm 20th in line after 20 minutes :rotate:
Are you phoning in? I always use the chat unless it's a server issue. For laptops, I get a chat humanoid immediately. I had to get a keyboard replaced in a 6440 yesterday. Opened chat thing, filled in all my troubleshooting. Dude came on, took 3 minutes or so to setup ticket, read my blurb, "do you just want the part, or a tech?" "send a tech, i'm busy tomorrow." "let me book the parts and a tech, be 3-4 minutes" and 3 minutes later, we were done.
For server stuff, I call and I've never had to wait on hold.
It was for the cooling system on a Precision desktop. I think they just had high volume/low coverage. I normally use chat and have never waited more then 15 minutes but boy howdy.
Also, anyone know a way to query the last time all users logged in to a computer with domain accounts? Net User seems to only bring up local accounts and net user /domain brings up the last time everyone in the domain logged in regardless of workstation.
Also: Vowels, what model computer are you using? I'm surprised rolling back the bios released it from asking for a bitlocker request.
It was for the cooling system on a Precision desktop. I think they just had high volume/low coverage. I normally use chat and have never waited more then 15 minutes but boy howdy.
Also, anyone know a way to query the last time all users logged in to a computer with domain accounts? Net User seems to only bring up local accounts and net user /domain brings up the last time everyone in the domain logged in regardless of workstation.
Also: Vowels, what model computer are you using? I'm surprised rolling back the bios released it from asking for a bitlocker request.
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
It was for the cooling system on a Precision desktop. I think they just had high volume/low coverage. I normally use chat and have never waited more then 15 minutes but boy howdy.
Also, anyone know a way to query the last time all users logged in to a computer with domain accounts? Net User seems to only bring up local accounts and net user /domain brings up the last time everyone in the domain logged in regardless of workstation.
Also: Vowels, what model computer are you using? I'm surprised rolling back the bios released it from asking for a bitlocker request.
We have some e7470s that when running bios 1.0.1 only accept numeric characters for bitlocker. That's been a hoot.
That's only showing me the last time I logged in, it is listing all users though, am I missing something?
I'm trying to determine who's been shutting this device down every night and not letting SCCM run updates for the last year so I can hit them with a trout.
Wait, maybe it's not their fault. Endpoint wasn't removed when we switched AVs.
It was for the cooling system on a Precision desktop. I think they just had high volume/low coverage. I normally use chat and have never waited more then 15 minutes but boy howdy.
Also, anyone know a way to query the last time all users logged in to a computer with domain accounts? Net User seems to only bring up local accounts and net user /domain brings up the last time everyone in the domain logged in regardless of workstation.
Also: Vowels, what model computer are you using? I'm surprised rolling back the bios released it from asking for a bitlocker request.
That's only showing me the last time I logged in, it is listing all users though, am I missing something?
I'm trying to determine who's been shutting this device down every night and not letting SCCM run updates for the last year so I can hit them with a trout.
Wait, maybe it's not their fault. Endpoint wasn't removed when we switched AVs.
run as admin to get the other user's login times
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
on a side note, here's something I hate about the powershell 'community' as it were
look at this monstrosity I pulled the relevant information (the WMI class) from.
Clearly this thing was written by a dev and not a sysadmin, it's essentially a fully-functioning program
if you're not already deep into powershell you'd never be able to penetrate what's happening in there to extract the information you need
MS needs to put out more stuff that instead of being bulletproof, is simpler and show people how they can build their own little queries and scripts. It's a scripting language for sysadmins, it doesn't need to have perfect error handling for every envisioned scenario. We can fix the errors when they come up!
I will say the Hey, Scripting Guy! blog is exactly what I want. I just wish there was more of that and less of giant .NET piles that non-devs couldn't hope to edit or understand.
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
exactly, I mean that 'function' is basically a fully-fleshed out cmdlet, that's not really helpful to anyone. it's either going to get pasted into the top of someone's script and if it ever breaks they'll have no idea how to fix it,
or I'll spend five minutes pouring it over to find the reference I need, then remake the thing in a way that makes sense
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
anything with begin, process, and end blocks gets a dirty look from me
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
Yea, I couldn't make ass or tail feather out of that "function".
0
RandomHajileNot actually a SnatcherThe New KremlinRegistered Userregular
Guys, I'm pretty sure that script is for checking the last logon time on domain servers, rather than an individual PC. I had to write a VBScript to pull from our four different DCs and compare dates and such, and that is about as many lines than this cmdlet. It's definitely more complex than it needs to be for that, but if you have to get 60% of that written to get what you want, may as well make it 100% before you release it to the world.
Guys, I'm pretty sure that script is for checking the last logon time on domain servers, rather than an individual PC. I had to write a VBScript to pull from our four different DCs and compare dates and such, and that is about as many lines than this cmdlet. It's definitely more complex than it needs to be for that, but if you have to get 60% of that written to get what you want, may as well make it 100% before you release it to the world.
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
0
RandomHajileNot actually a SnatcherThe New KremlinRegistered Userregular
Guys, I'm pretty sure that script is for checking the last logon time on domain servers, rather than an individual PC. I had to write a VBScript to pull from our four different DCs and compare dates and such, and that is about as many lines than this cmdlet. It's definitely more complex than it needs to be for that, but if you have to get 60% of that written to get what you want, may as well make it 100% before you release it to the world.
Actually that second one doesn't seem to be pulling from all servers, like I thought. My last logon time is wildly different amongst our servers. But yeah, I'd start with that, build a loop over it, and then compare times between the servers. Maybe one of these days.
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
Guys, I'm pretty sure that script is for checking the last logon time on domain servers, rather than an individual PC. I had to write a VBScript to pull from our four different DCs and compare dates and such, and that is about as many lines than this cmdlet. It's definitely more complex than it needs to be for that, but if you have to get 60% of that written to get what you want, may as well make it 100% before you release it to the world.
Actually that second one doesn't seem to be pulling from all servers, like I thought. My last logon time is wildly different amongst our servers. But yeah, I'd start with that, build a loop over it, and then compare times between the servers. Maybe one of these days.
yeah I'm pretty sure there's ways of specifying specific DCs with the AD cmdlets. I don't have that module installed on my machine to say for sure but yeah that's how I'd do it, too.
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
I should get a tattoo of the powershell logo :rotate:
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
Posts
Wow what a dick move by your provider though jesus.
Not even a quick phone call with "hey we're getting a lot of DNS queries from your side that's unusual, what's up" ? I imagine you guys are big business for them, or at least, big enough to open a dialog to see if it can't be fixed without downtime.
Great opportunity to win the hearts and minds of customers, though.
PowerWare - ransom that is utilizing PowerShell to execute. The good news is that it only works on systems where PowerShell's default encryption policy has been elevated. Bad news is that any organization where IT has relaxed local rights restrictions by granting everyone local admin may be at risk.
since powershell can leverage the whole .NET codebase they wrote their whole ransomware in powershell, and now they don't need a separate executable (which is easier for AV to detect)
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
Downgrading the BIOS back to the original version bypassed bitlocker.
holy fuck I can't believe that worked
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 literally don't believe it.
neither do I but I am logged into the machine
I spent more time figuring out how to get the damn BIOS .exe to run lol
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
Aioua is a 1337 haxx0r violating digital locks!
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
Wooo, Apple is number one...and by a large margin!
http://www.gfi.com/blog/2015s-mvps-the-most-vulnerable-players/
XBL:Phenyhelm - 3DS:Phenyhelm
Are you phoning in? I always use the chat unless it's a server issue. For laptops, I get a chat humanoid immediately. I had to get a keyboard replaced in a 6440 yesterday. Opened chat thing, filled in all my troubleshooting. Dude came on, took 3 minutes or so to setup ticket, read my blurb, "do you just want the part, or a tech?" "send a tech, i'm busy tomorrow." "let me book the parts and a tech, be 3-4 minutes" and 3 minutes later, we were done.
For server stuff, I call and I've never had to wait on hold.
Also, anyone know a way to query the last time all users logged in to a computer with domain accounts? Net User seems to only bring up local accounts and net user /domain brings up the last time everyone in the domain logged in regardless of workstation.
Also: Vowels, what model computer are you using? I'm surprised rolling back the bios released it from asking for a bitlocker request.
it was a dell e6440
also,
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
We have some e7470s that when running bios 1.0.1 only accept numeric characters for bitlocker. That's been a hoot.
That's only showing me the last time I logged in, it is listing all users though, am I missing something?
I'm trying to determine who's been shutting this device down every night and not letting SCCM run updates for the last year so I can hit them with a trout.
Wait, maybe it's not their fault. Endpoint wasn't removed when we switched AVs.
run as admin to get the other user's login times
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
look at this monstrosity I pulled the relevant information (the WMI class) from.
Clearly this thing was written by a dev and not a sysadmin, it's essentially a fully-functioning program
if you're not already deep into powershell you'd never be able to penetrate what's happening in there to extract the information you need
MS needs to put out more stuff that instead of being bulletproof, is simpler and show people how they can build their own little queries and scripts. It's a scripting language for sysadmins, it doesn't need to have perfect error handling for every envisioned scenario. We can fix the errors when they come up!
I will say the Hey, Scripting Guy! blog is exactly what I want. I just wish there was more of that and less of giant .NET piles that non-devs couldn't hope to edit or understand.
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
exactly, I mean that 'function' is basically a fully-fleshed out cmdlet, that's not really helpful to anyone. it's either going to get pasted into the top of someone's script and if it ever breaks they'll have no idea how to fix it,
or I'll spend five minutes pouring it over to find the reference I need, then remake the thing in a way that makes sense
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
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
This is a clickable link to my Steam Profile.
:razz:
unless you meant the last time they logged in anywhere in the domain, in which case
plus some filtering, natch
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
Actually that second one doesn't seem to be pulling from all servers, like I thought. My last logon time is wildly different amongst our servers. But yeah, I'd start with that, build a loop over it, and then compare times between the servers. Maybe one of these days.
This is a clickable link to my Steam Profile.
what's causing the spikes on the aborts?
I demand first priority!
/managment
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
yeah I'm pretty sure there's ways of specifying specific DCs with the AD cmdlets. I don't have that module installed on my machine to say for sure but yeah that's how I'd do it, too.
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
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
Whatever, I'll just use my air card as hotel internet is always...something. But screw you anyway, hotel, for false advertising.
Might allow VPN/SSH tunneling.
They were using Office Picture Manager. Hadn't been updated since 2003, but was included up to office 2010. I forgot that thing even existed.