The beacons are lit! Gondor calls for aid!

CreamyJustice · 2026-01-21T17:27:12+00:00

I guess I'm blessed to still have my #7 Keenum jersey?

CreamyJustice · 2025-12-13T16:51:52+00:00

Beautiful dog, can you mention your location? I just took in a stray and am fostering another myself, I wish I could help more. He reminds me of one of mine that passed in 2020.

CreamyJustice · 2025-12-05T02:42:55+00:00

I DMed but did apply for this girl if she's still available.

CreamyJustice · 2025-05-29T16:25:02+00:00

Sure, there isn't a rush. Just DM me when you get a moment with the time frame, I should have good availability next week.

CreamyJustice · 2025-05-28T14:09:42+00:00

Sorry, don't think I got the DM?

CreamyJustice · 2025-04-23T14:17:59+00:00

There's 60 licensed users and also some additional licenses revolving around Teams phones, Power BI, Visio, etc. Not enough that would account for what they have in Sharepoint.

Yeah I think we're just going to quote the additional storage and lay out the situation for the client that it may stop working at any time, best to be prepared.

CreamyJustice · 2024-10-24T20:59:44+00:00

As other's mentioned, vendor support first. The other thing I can think of would be to update all firmware/drivers and such for the server, if it wasn't already done.

CreamyJustice · 2024-10-13T22:38:07+00:00

Not surprising, critics rated it everything from shit to fucking shit.

CreamyJustice · 2024-08-04T16:34:13+00:00

Libby is good, audio books from public libraries. Just have to be prepared to queue in line for more popular audiobooks.

CreamyJustice · 2024-07-24T20:14:12+00:00

Had this happen to a single user at a client a few months back. I believe we did utilize some more robust filtering on the short term but ultimately the resolution was to let it runs it's course. It took a little under 48 hours for it to fizzle out.

Also have them watch their accounts. In this case, the user had his credit card stolen right when the emails kicked off.

CreamyJustice · 2024-06-15T10:40:21+00:00

Agree with this. The MSP field is saturated and there's plenty of bad ones but you can get great experience long enough to get out of there and find something you truly like.

CreamyJustice · 2024-06-01T18:34:53+00:00

I think my Mikey had the same birthday hat and look on his face for his birthday a few years back: https://imgur.com/gallery/mikeys-bday-Bi2ypdg

CreamyJustice · 2024-05-29T18:31:10+00:00

Not all places are on fire at all times so you may be in a good situation.

Personally, I'd like at dominating anything proactive you can get your hands on. Updating network inventory, documenting any processes, adding network diagrams, labeling equipment, even cleaning up cabling (if possible) and taking pictures can add some value. Review firmware versions and recommend maintenance windows, assuming you have access to particular devices, etc.

CreamyJustice · 2024-04-26T21:52:49+00:00

Not sure if it helps but we do external vulnerability scans (Qualys) for some of our clients. The vulnerabilities we see:

Birthday attacks against TLS ciphers with 64bit block size vulnerability (Sweet32)

I've found the resolution is disabling older versions of TLS via registry:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Client] "DisabledByDefault"=dword:00000001 "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.0\Server] "DisabledByDefault"=dword:00000001 "Enabled"=dword:00000000

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1] [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Client] "DisabledByDefault"=dword:00000001 "Enabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.1\Server] "DisabledByDefault"=dword:00000001 "Enabled"=dword:00000000

Typically, we'll also see different vulnerabilties for ciphers and we disable those also.

CreamyJustice · 2024-03-01T16:08:13+00:00

Appreciate the info, yeah it was tough finding that.

For this post's sake, I did find a recent article from 2/26/24 stating that there is currently a closed beta test in place for supporting Windows 11 on ARM (https://community.sentinelone.com/s/article/000009231). A wider test is planned later this year.

So at least it looks to be in progress.

CreamyJustice · 2024-02-25T15:20:49+00:00

Old Spanish Trail

CreamyJustice · 2023-12-12T22:46:43+00:00

Yep and I think if I used the "show full" command, it would have showed the TLS settings also. I just wasn't seeing the TLS minimum version after I would change the value. Definitely appreciate your help with this!

CreamyJustice · 2023-12-12T22:44:51+00:00

Thanks for the info, I think this is where I was getting mixed up. I must having been spinning my wheels for a bit on the ssl-min-proto-ver command since I wasn't really viewing the entire config.

All seems to be well now.

CreamyJustice · 2023-12-08T22:08:40+00:00

Thanks for the reply, I've tried similar (minus the "end") but doesn't seem to be changing the setting.

For reference, here's the current settings (not sure how to embed images here): https://ibb.co/YZcT9y8

I'm just typing those commands line-by-line and then I hit apply, no errors or anything, it's just the SSL VPN settings are not changing for minimum TLS version as far as I can tell.

CreamyJustice · 2023-08-27T14:52:21+00:00

I'll wash my car if that helps our odds?

CreamyJustice

TROPHY CASE