I can't even
-
@dustinb3403 said in I can't even:
@dashrender said in I can't even:
@dustinb3403 said in I can't even:
@dashrender said in I can't even:
@dustinb3403 said in I can't even:
@voip_n00b said in I can't even:
@dustinb3403 I blocked port 80. Give me 443 or nothing.
And how are you blocking that while you're mobile? I can understand from a location you have control over, but roaming seems to be a challenge and doesn't fix the issue.
Assuming there's a firewall available for your mobile device, you could conceivably do it.
Conceivability verse practicality is what I'm wondering about, could someone setup a firewall to use for their cellphone etc, sure but would you really want to?
Of course not - who wants to manage that?
but the same can be said for boycotting those that don't use HTTPS - if you care enough, you're potentially already doing it - if you don't, well you never will.
I will not be purchasing smithfield products if they can't provide the lowest level of security across their sites, that is a go forward rule for me.
Do you know all of the products/vendors you use and can confirm that their sites are secured and would you do such a thing?
I only look when I'm buying something - so yeah... I look, because I care. I can tell you even in my own company - my new boss surely doesn't look, it's not on her mind to know about this. But I don't mean to single her out - almost no one else here likely looks for that.
-
@dustinb3403 said in I can't even:
So when do we start boycotting businesses that refuse to use SSL...
They have SSL, it just doesn't redirect you properly.
-
-
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
-
@gjacobse said in I can't even:
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
With the W10 fast-boot / hybrid shutdown I've seen last boot times upwards of 9 months and a year on some machines.
-
@notverypunny said in I can't even:
@gjacobse said in I can't even:
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
With the W10 fast-boot / hybrid shutdown I've seen last boot times upwards of 9 months and a year on some machines.
Jeez - It's been several years,... but a friend had me check the uptime of the Linux server after him.... just to 'prove a point'... maybe.. Uptime was on the order of 960 days... Insanity.
-
Really....
-
@gjacobse said in I can't even:
@notverypunny said in I can't even:
@gjacobse said in I can't even:
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
With the W10 fast-boot / hybrid shutdown I've seen last boot times upwards of 9 months and a year on some machines.
Jeez - It's been several years,... but a friend had me check the uptime of the Linux server after him.... just to 'prove a point'... maybe.. Uptime was on the order of 960 days... Insanity.
You need to reboot to verify hardware hasn't failed at least once a month, sheesh.
-
@travisdh1 said in I can't even:
@gjacobse said in I can't even:
@notverypunny said in I can't even:
@gjacobse said in I can't even:
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
With the W10 fast-boot / hybrid shutdown I've seen last boot times upwards of 9 months and a year on some machines.
Jeez - It's been several years,... but a friend had me check the uptime of the Linux server after him.... just to 'prove a point'... maybe.. Uptime was on the order of 960 days... Insanity.
You need to reboot to verify hardware hasn't failed at least once a month, sheesh.
No argument there - and more know this better than I do,.. There are just some system updates (regardless of OS) that you must restart to finalize... Even my insignificant Ubuntu Server needs it with autoupdates (not configured to restart though I know it could be).
-
@gjacobse said in I can't even:
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
We go from 22days to
47:13:50:12
-
@notverypunny said in I can't even:
With the W10 fast-boot / hybrid shutdown
I alway disabled that piece of shit functionality.
-
@jaredbusch said in I can't even:
@notverypunny said in I can't even:
With the W10 fast-boot / hybrid shutdown
I alway disabled that piece of shit functionality.
GPO'd that out of our network and suddenly a noticible chunk of stupid issues just stopped.
-
@nadnerb said in I can't even:
suddenly a noticible chunk of stupid issues just stopped.
Had the same thing happened when I added a 4am reboot to all users systems on Monday mornings.
-
@jaredbusch said in I can't even:
@nadnerb said in I can't even:
suddenly a noticible chunk of stupid issues just stopped.
Had the same thing happened when I added a 4am reboot to all users systems on Monday mornings.
I would like to add that. But so many of our staff won't be on network, on at that time. Nearly 85% of the PCs are laptops...
ETA:
That and a force kick from the Citrix and RDS servers at 1am daily. -
@gjacobse said in I can't even:
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
This isn't always a user's fault.
F'n MS doesn't always do a full shutdown... in fact by default choosing shutdown does a fast shutdown... choosing reboot supposedly always does a full shutdown memory clear reboot whatever.. and windows resets the clock.
-
@dashrender said in I can't even:
@gjacobse said in I can't even:
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
This isn't always a user's fault.
F'n MS doesn't always do a full shutdown... in fact by default choosing shutdown does a fast shutdown... choosing reboot supposedly always does a full shutdown memory clear reboot whatever.. and windows resets the clock.
I never, ever shut down anything. I either hibernate or reboot. Mostly hibernate, and reboot when not given the choice (updates). So for me, I don't care what shutdown does.
-
@obsolesce said in I can't even:
@dashrender said in I can't even:
@gjacobse said in I can't even:
Users who can't do a proper shut down or restart of their computer. And then complaining that it's dog in winter slow.
Uptime was 22days (not the worst I've seen). Disk and Memory were at 100% usage before restart.....
This isn't always a user's fault.
F'n MS doesn't always do a full shutdown... in fact by default choosing shutdown does a fast shutdown... choosing reboot supposedly always does a full shutdown memory clear reboot whatever.. and windows resets the clock.
I never, ever shut down anything. I either hibernate or reboot. Mostly hibernate, and reboot when not given the choice (updates). So for me, I don't care what shutdown does.
yeah - well users CLAIM that they choose reboot - yet when I look at how long since last reboot and it says 10+ days... something seems fishy.
-
Oh for FFS -
An alert has been fired on local host DOMAIN\COMPUTER regarding user myuser. A suspicious powershell script has been found in C:\Users\myuser\Desktop\Teams_ODfB.ps1. Please let us know if this is legitimate.
This is the script
Start-Process -File "$($env:USERProfile)\AppData\Local\Microsoft\Teams\Update.exe" -ArgumentList '--processStart "Teams.exe"' Start-Process -FilePath "$env:LOCALAPPDATA\Microsoft\OneDrive\OneDrive.exe" -ArgumentList "/background"
Which only starts Teams and ODfB.... Like.. JFC -
-
@gjacobse said in I can't even:
Oh for FFS -
An alert has been fired on local host DOMAIN\COMPUTER regarding user myuser. A suspicious powershell script has been found in C:\Users\myuser\Desktop\Teams_ODfB.ps1. Please let us know if this is legitimate.
This is the script
Start-Process -File "$($env:USERProfile)\AppData\Local\Microsoft\Teams\Update.exe" -ArgumentList '--processStart "Teams.exe"' Start-Process -FilePath "$env:LOCALAPPDATA\Microsoft\OneDrive\OneDrive.exe" -ArgumentList "/background"
Which only starts Teams and ODfB.... Like.. JFC -
Hey we don't know what it does we're just script kiddies out here, tell us if this is kosher, thanks!
-
oh FFS People!
Ah you don't unstand why your computer doesn't work right...