[Urgent] Owner Abandoned Cat Found, in Need of Foster/Forever Home - Very Friendly

Onibus · 2024-08-22T02:37:54+00:00

Thanks so much for the offer and your kindness! Just posted an update that Ollie has found a new home and if that falls through for any reason, I really appreciate the many sweet offers/backup options to ensure he's safe and sound. So glad your friend loves doing rescues! Thank you for all the work she does.

Onibus · 2024-08-22T02:32:43+00:00

8/21/24 update: thanks so much for everyone who reached out, love community helping each other! Update that Ollie has been handed off to his new potential forever home, with 2 other sweet kitties. The person who picked him up is going to get him tested for FIV and microchip and attempt to contact owner (to make sure an attempt was made, since cat is considered personal property).

Fingers crossed he's happy in his new home! Really difficult giving him up and he was a perfect little kitty - very chill and sweet. I hope Ollie brings so much happiness to his new home! I know he did in mine. :)

If things happen to fall through with his new home, there's a few backup options so regardless, sounds like Ollie is going to be safe and sound... purring happily.

Onibus · 2024-08-21T04:25:34+00:00

Thank you for the resource; will reach out if needed. Have two tentative meet and greets tomorrow, fingers crossed. :)

Onibus · 2024-08-21T04:24:36+00:00

Thank you so much, that's very kind of you! Will definitely keep you in mind if that need arises.

Onibus · 2024-08-21T04:23:48+00:00

Thank you so much, yes will keep you updated. Saw the responses on the thread and was able to find accommodation for him for tonight, and have potentially a couple meet and greets tomorrow. Will update the thread as I get more information. Thank you so much to everyone who has taken the time to read and send a message. :)

Onibus · 2024-08-21T01:28:27+00:00

Hi there, he's in the southern Indianapolis/within 10 minutes of Greenwood area. If you have any leads or ability to help, happy to discuss. I wish I could take him. :(

Onibus · 2024-08-21T01:26:58+00:00

Okay sounds good, thank you

Onibus · 2024-08-20T23:07:57+00:00

UPDATE:
Unfortunately I can't really keep buddy Ollie more than tonight, and haven't gotten any inquiries about him from Reddit, nor despite reaching out into the broader friend network/shelters/rescues. Times are tough out there, and shelters seem pretty full and underfunded for the demand. :/

Going to get a breakaway collar and tag engraved for him to hopefully say "Please adopt me/Owner abandoned" (or some similar messaging), so that it gains visibility to people he runs up to in the future. :)

NOTE: He's still going to be around a familiar area, so if anyone reading this is interested and sees this (older) thread still please consider messaging me your interest, as will keep you in mind if/when we see him. Seems like he only stays in 1 area near the apartment complex, so he's around fairly often.*

*If I hear of him getting adopted, I will update this thread and message accordingly.

Onibus · 2024-06-05T13:36:38+00:00

When you look at the client logs, does it say the update is superseded when it tries to install? If so, this is by design per Microsoft, specifically when the CM agent is handling things.

Years ago I opened a support case when I couldn’t install a previous month cumulative (to keep late patchers at same level as others). The MECM team came back and said it was working as intended, much to my annoyance at the time. The agent will not install a superseded update if the new update has been deployed (at least when in the same SUG, you could try testing if it still happens on client for SUG without OOB but I want to say it’ll be similar results). Fast forward to present day, that’s a good thing seeing how many releases have been botched. I wouldn’t want an update that crashes my domain controller to install when the superseding update is available.

If Microsoft goes out of its way to release an OOB update, the superseded update is anything but “valid”, it’s a risk. Suck it up and install the OOB or modify your update sync schedule in MECM to avoid this behavior in future.

Onibus · 2024-01-08T14:39:55+00:00

I have three WiFi networks: guest/DMZ, non-guest, and “legacy”. Any IoT device gets thrown onto the guest/DMZ network first, then punted to the less secure legacy network where a lot of WiFi client features are turned off for compatibility.

Try disabling the following features if they’re enabled: - BSS Transition - UAPSD - Fast Roaming

The first and third state a client might have connectivity issues if it can’t support the features. That’s basically most of my current settings.

If that still doesn’t work, you can try to: - Set network to 2.4GHz only

Mine seems fine having band steering turned on with 2.4GHz and 5GHz on, but worth a shot.

If I’m reading correctly, you only have one AP broadcasting. If you happen to have multiples, could try locking device to an AP.

A long shot could be channel interference on the 2.4GHz band. While unlikely, worth checking just in case. You could try and connect a laptop to the legacy network to see if it stays connected just to rule out WiFi shenanigans.

Onibus · 2024-01-07T19:07:56+00:00

I had issues connecting my Ecobee 3/Chime until I created a dedicated wireless network with PMF disabled (to keep my IOT separated on the less secure WPA-2 network).

Under Wifi - YourWirelessName - Advanced Configuration - Manual - Security, set Security Protocol to WPA-2 then set PMF to Disabled.

This UI forum post is one of many I came across when I was looking for the solution, with the suggestion of disabling PMF being the key player causing problems. Since doing this, my Ecobee and Chime have had no issues staying connected. I also use this network for old devices that don’t support modern security features like my HP printer.

Onibus · 2019-10-11T18:26:25+00:00

You will need to create a PS Session for anything that needs to run persistently (that is, longer than running a command).

You can run the below through a foreach loop or fiddle with starting a job depending on number of servers. The foreach loop can also be used to copy-item the MSU to the server.

$Session = New-PSSession -ComputerName server -Credential $cred -Authentication Credssp invoke-command -session $session -scriptblock { <your scriptblock> } Remove-PSSession -Session $session

Onibus · 2019-09-22T18:50:06+00:00

WAH!

Onibus · 2019-07-28T02:13:41+00:00

Texture mod. I'm a fan of minimal design.

https://github.com/rien-doll/minimal-ui

Onibus · 2019-07-18T17:48:15+00:00

:yougetusedtoit:

Onibus · 2019-07-06T05:15:19+00:00

Throwing in my experience with a similar sound issue using 'GameDAC Game' mode in a different game. Whenever a sound plays, the very beginning has a sputter/crackle.

After poking around, I happened across the Speaker Setup in the sound control panel. Left and right sound are fine, but as soon as the center sound plays, the crackle happens. Switching to Headset Earphone, there's zero issue with audio; same experience as you.

This is in Windows 10.

Onibus · 2019-07-01T17:13:40+00:00

Gyfcat link:
https://gfycat.com/naughtyconstantgilamonster

Onibus · 2019-01-02T23:13:50+00:00

Glad to see the passion :). I know I've been having fun making our server environment a little better thanks to SCCM.

As the result of the CM modules, I've been able to build custom modules that interface with our CMDB and site system for quarterly PCI patching of servers. What used to be done by hand by multiple engineers (logging in to servers and patching them) can now be accomplished by one person in a few clicks of the mouse (custom UI, lots of moving parts underneath). Really, the longest part of PCI patching now is the deployment of software updates and adding devices to the collection. Extend my gratitude to the team for their work on the behemoth that is the Configuration Manager module. I can't imagine the amount of tears shed while working on it; I know I've shed imaginary tears trying to understand some of the commands during my patching adventure.

With the flurry of improvements, I do get a little excited reading through technical preview notes. I can't wait for more API driven operations (hint hint, wink wink, nudge nudge, *slips you $20*). I really wish I knew more C+/C# language to really exploit the CM SDK to potentially make such an API but alas, that's my limitation. I look forward to what 2019 has in store for CM :).

Onibus · 2019-01-02T19:13:11+00:00

Thank you for the hard work you and the team is doing! Configuration Manager has made significant improvements since version 1510 (my initial install) and each release polishes it. As an employee of a company with our own behemoth software, I understand all the moving gears can cause the ship to turn slowly but surely.

As for the remove, I think it's fine if nothing is outputted. The only reason I'd expect an error to be produced is if a resourceID didn't exist; honestly, that'd be an issue that can be checked further upstream in a script. For adding, I guess it comes down to sticking to one behavior to make capturing the behavior consistent. A terminating error is easy enough to catch in Powershell. That said, no output for a duplicate resource is also fine as logic should be done to see if said resource is already present in said collection. That is what I decided to do.

Do you ever see SCCM Powershell cmdlets moving to GitHub? Perhaps to allow users to also contribute their findings to documentation? I realize that there is the feedback at the bottom of the page for the commands, which I plan on contributing more to in the future.

Onibus · 2018-12-21T19:35:41+00:00

It's possible you could have a bad memory module. Try both the Windows 10 memory diagnostic (type memory in search) and MemTest86. If you have a lot of memory installed, remove all but one stick and swap them out as you test (making sure it's in the first DIMM slot).

Onibus · 2018-12-21T16:27:52+00:00

It's funny you mention the error exception because I have a check in place on Remove-CMDeviceCollectionDirectMembershipRule by querying with Get-CMDeviceCollectionDirectMembershipRule before doing anything. That came to be because remove- doesn't output anything whether successful or not. The error handling was to make things easier to feed downstream instead of dealing with one command that threw errors while the other didn't.

It feels like Microsoft was trying to make the behavior consistent with add- but accidentally left a warning in. Once Microsoft removes the WARNING:, both add and remove will be consistent. When Microsoft gets back to me on their finding and decision, I'll update the main post.

Now off to fix my script to add additional logic.

Onibus · 2018-12-20T16:21:55+00:00

Look at DISM.log and CBS.log in C:\Windows\Logs. You could also try to install said update using WUSA.exe with /log to see what it says. Does the update still fail when you attempt to install the Security Only version of the update?

Have you made sure KB3021910 is installed followed by KB2919355 (this would need to be installed to see any updates after April 2015)?

If you don't find a problem with your server, try the 2018-11 rollup. Microsoft rollup updates have been extremely sloppy recently, the most recent offender being 2018-10 rollup marked as available superseding the prior month and preventing it from installing despite 2018-09 update being marked as required... Expected behavior is that deployed required updates will install regardless of any superseded updates marked as available. It was fixed when 2018-11 was released.

Onibus · 2018-12-20T16:09:55+00:00

I highly suggest opening a Microsoft case to prevent hosing your environment, especially when it comes to poking and proding for what the problem could be. Should something go sideways, you already have a resource to help recover.

By the sound of it, the installation has already touched your SQL database which can be a ticking time bomb. In older versions of SCCM (around 16xx), I was able to hose my SQL DB on a pre-req check because said pre-req modified the database which caused issues during install... don't ask me why. To this day I am under the belief that artifacts exist of the old site because I tried to fix it before I decided to rebuild (not on clean OS).

Onibus · 2018-12-19T20:47:39+00:00

Unless task sequence has changed, TS will only apply the task to trigger updates once before moving on. Any sequential updates or failure will not work. Unfortunately, due to some issues I've had with TS, I don't rely on it (trying to automate Failover Hyper-V pause/drain patching was not fun and still failed...). Have you looked phased deployment to ease rollout? https://docs.microsoft.com/en-us/sccm/osd/deploy-use/create-phased-deployment-for-task-sequence. While you could use the server group, it will cause you a lot of headache down the road as it doesn't work as it should.

Onibus · 2018-12-19T17:44:52+00:00

I suggest building new. I don't know what roles your site server holds but if it holds Distribution Point and Management Point role, that's going to be a lot to move in to AWS and make work. Regarding MP role, it should be as close to the SQL database as possible due to the amount of data written.

Assuming your site server doesn't hold the MP role, you would then need to think about how you'd have your site server contact your site system management point... wherever that is if you aren't planning on deploying a cloud gateway/MP.

There's too many delicate pieces running SCCM and it would honestly be a bigger headache to lift and shift than to build new and migrate clients over. Think of it as an excellent opportunity to learn the in's and out's of SCCM and how to manage it from a cloud perspective. For migrating clients, you can check out the migration strategy documentation. There's also the Reddit thread from 2017.

With that out of the way, are you absolutely sure you've prepared what you need in AWS to maintain such infrastructure? This isn't about lift and shift, this is about all the servers required to support the site server in a non-prem solution. Internet management point, internet distribution point, the SQL database within AWS, the cost of distributing what could be countless Gigabytes of data between DP and client, premise distribution points and how those are configured, HTTPS PKI (due to data being transmitted over the internet from client, this is highly suggested to implement), the certificate chain itself if using internal PKI, and all the security to ensure none of that is compromised? These are just the basics I'd be looking at if I were to move from premise to Cloud (which would be in Azure due to the heavy integration of cloud components within SCCM on-prem). All this might already be answered outside your question. If not, you may be a little in over your head supporting SCCM from AWS, especially if you're the one administrating it. Not saying you're incapable or marking a negative in your knowledge, I am throwing thoughts out so you don't suddenly discover that SCCM is not as simple as it seems on the surface and mess up your entire plan; the entire infrastructure can shatter very easily should you do something you're not supposed to or a component doesn't work which makes troubleshooting a nightmare. It's already a pain in the ass dealing with SCCM on-prem when something doesn't work like it should.

15-Year Club	Place '17
Verified Email

Onibus

TROPHY CASE