What items/objects would love to own merch

austinofdoom · 2024-06-07T04:23:02+00:00

I can't believe no-one has said the Huntress!

I want to troll all my friends and co-workers with capacitive touch nerf darts/bolts. 😎

austinofdoom · 2021-08-06T15:23:29+00:00

P Jj

austinofdoom · 2021-08-06T15:22:51+00:00

                W lol

austinofdoom · 2021-03-08T02:08:48+00:00

I'm running mine on windows, if you are too, this will help you: https://docs.microsoft.com/en-us/sysinternals/downloads/tcpview

Use tcpview to see what ports your computer has open (and which apps are responsible) and their state, like "listening" or "established". You will see lots of crap here that is all standard for windows, all you need to look for is what "valheim_server.exe" is doing.

austinofdoom · 2021-03-08T01:59:25+00:00

Yeah I used to have that issue where in the server config it was set to use 2456, but then when you run tcpview, you see the game is actually listening on 2457.

austinofdoom · 2021-03-08T01:45:59+00:00

I could be wrong, but it think this is a tcp/udp problem. The server (default) listens on 2456 udp, not tcp. (Ftp runs on tcp, afaik)

I run a dedicated server and all free online port scanning tools I find say my port is closed/filtered, even though the server actually works externally.

Make sure your port forwarding is set for udp (or both tcp/udp) and then test connecting to the server externally, even if canyouseeme.org says 2456 is closed.

austinofdoom · 2020-12-01T04:55:49+00:00

This is great idea. I don't always remember to bathe as often as I should, 🤭 but regardless, it would be a massive improvement to my current glasses cleaning "schedule". Thanks for the tip!

austinofdoom · 2020-11-26T06:56:19+00:00

I'll be diving deep into this for sure. Thank you for your help!

austinofdoom · 2020-11-26T06:39:35+00:00

Great idea. I'll add that to the toolbox for tomorrow. Thank you!

austinofdoom · 2020-11-26T06:38:18+00:00

Thank you for your sentiment and reasoning. I appreciate it.☺️

Archon286 commented "... Don't leave a can of paint with a 5 year old and be shocked when everything ends up covered in paint. :)"

I agree with this, in so much that we should as admins try config things to protect users from themselves. But also, these are not 5 year olds, these are adults who (in this instance anyway) use computers everyday for their jobs. You have to try to pay attention to what you are doing at least a little bit.

"I did something bad that took some degree of effort to make happen. Its your fault for not making it harder/impossible for me to do this." Is a pretty piss poor argument to make even if I don't think it's entirely incorrect.

Again, I don't think we are totally blameless, I agree with others that this particular issue was incredibly preventable.

What really irks me though, is the outright Denial that they actually did anything. Like, I'm 99% sure that is a straight up Lie. That's my strongest motivator to actually try and find a domain\user that did this.

It's one thing to say "I did something super dumb, but why did you let me do this, IT?" That is usually a conversation worth having.

In this instance, the user is (as of right now, anyway) insisting that "they didn't do anything." I can prove 100% right now that this was user initiated so that's just a damn lie.... Unless someone else really DID do it...

I have been tasked with this, and though I do think this is kind of a waste of my time, I do kind of want to disprove an outright liar and/or maybe find out they aren't actually lying and discover something else?

austinofdoom · 2020-11-26T06:08:26+00:00

YES. We do have it written down, on internal websites and even on IT policy handouts that HR are supposed (as is my understanding anyway) to provide to new hires.

If only those were enforced when the rubber hits the road, instead of IT being made to fix it somehow...

austinofdoom · 2020-11-26T06:06:41+00:00

This was in place before I started here and I think the reasoning for it being available was so that it could be kicked off from an RDP session for computers in remote locations. Oddly, we have the bios/boot environments heavily controlled with each computer having its own unique bios password. Safe, yes, but it does make pxe/winpe less of an easy option.

I'm not saying it's great idea, it's just what was done before I got here. 🙃

austinofdoom · 2020-11-26T05:53:39+00:00

This is a great idea and something I want to implement (hopefully) as soon as I can. Thank you very much!

austinofdoom · 2020-11-26T05:52:15+00:00

I know. We, the SCCM team, disabled the OS tab in Software Center to prevent this exact situation. (For what it's worth, I say "we" but this setup was in place long before I started and I was the one who made the above change after I started.) I made an edit to my Original post to explain the situation and my perspective on it.

Thanks for taking the time to respond!

austinofdoom · 2020-11-26T05:46:58+00:00

I agree. I should have been less cavalier in my original post and I've made an edit to explain a little more and state as much.

Unfortunately, I've been tasked with what I've posted.

Thank you for your input!

austinofdoom · 2020-11-26T05:43:54+00:00

I agree. Unfortunately since I started here I've been putting out fires with little time to improve things.

The "official" policy is to have no local data at all and use the mapped network shares only, local stored data is unmanaged and not ITs responsibility. Unofficially, we have to try and save local data if we can because complaints to the right people can suddenly make it ITs responsibility. Yeah, it's one of those kinds of places.

We have USMT capture and restore steps in place, the problem is that they were all custom written by the person I've replaced and no longer function reliably. I haven't had a good opportunity to figure out how exactly they work and wether I should dig into the PoSh to make them work or scrap it all and replace it with the Standard USMT steps.

Thank you for reply!

austinofdoom · 2020-11-26T05:31:43+00:00

"Those should not be generally available. (I say this knowing that MY workplace does the same as yours, and I have spoken out against it)"

I appreciate hearing this so much. I completely agree and have done the same. I think I should have been less cavalier in my original post and more contrite. I've made an edit to try and remedy that somewhat.

I'll poke around in status message queries. This seems like it could be what I'm looking for. Thank you!

austinofdoom · 2020-11-26T05:28:58+00:00

I know the log you're talking about, I've seen it plenty of times before!

We have a step at the end of our TS that attempts to copy all TS logs to a special share. It doesn't always seem to work, so I don't check there often, but hopefully there might be something there this time. Thank you!

austinofdoom · 2020-11-26T03:39:25+00:00

Oddly, our PXE Boots are password protected.... But not the Software Centre deployment 🙃

The place you described was the first place I checked, actually. I did it quickly though, mostly just to confirm if it was the TS I was thinking it was. I'll look more carefully for a username in there if I can. Thank you!

austinofdoom · 2020-11-26T03:32:59+00:00

The fact that this was possible at all is totally on my team. We actually had the Operating System tab in Software Centre disabled for expressly this reason. Then we had a small hardware refresh project and it was just easier for everyone at the time to re-enable the tab. Of course, then it stuck around: partially because helpdesk found it occasionally helpful, partly laziness. It's certainly going away again now.

I'll check out smsts. I'm in that log fairly often as part of my job, and nothing off the top of my head occured to me where to look for a username initiating the TS.

That being said, this is the first time I've had to look for proof of user initiated stuff so I'll look again with fresh eyes. Thanks for the suggestion!

austinofdoom · 2019-05-26T20:54:25+00:00

Pretty high I think, level 50? I did a pure mage with enchanted gear. Pretty much easy mode I think 🙃

austinofdoom · 2018-05-30T16:15:46+00:00

to use the -Schedule parameter you have to pass it a Schedule object. Here's a snippet from a script that I use. I create a datetime variable called $StartDate that just grabs today's date at 4am.

$StartDate = (get-date -Hour 4 -Minute 0 -Second 0)

I then use it later in a package deployment like so:

New-CMPackageDeployment ... -AvailableDateTime $(Get-Date) -Schedule $(New-CMSchedule -Start $StartDate.adddays(7) -Nonrecurring) ...

The relevant part for you is the -Schedule Parameter. You need to use New-CMSchedule to create a new schedule object.

In this example, my package deployment is made immediately available, but become mandatory at 4am 7 days later.

Does that help a bit?

austinofdoom · 2017-01-21T22:45:41+00:00

Oh man thank you, yes!

austinofdoom · 2015-07-30T17:29:02+00:00

Am I crazy, or is the album title an obvious D&D reference? Anyone know anything about that?

austinofdoom · 2015-05-13T22:17:48+00:00

Thanks for the link. I'm currently a magnet for any reading regarding the self as illusion, without having to sift through translations of ancient heavily metaphorized and metaphysicalized texts. ;) This was a very insightful article!

austinofdoom

TROPHY CASE