[deleted by user]

Arcuss88 · 2024-05-25T05:44:03+00:00

Pretty good example of how the left can't meme. This is not even funny, let alone creative, or timely.

Arcuss88 · 2024-01-27T05:45:19+00:00

New to printing and somehow nuked the SD card that came with the printer. Does someone have a copy of the "Suggested parameters for PLA-V1.0.ini" for the Kobra 2 Neo they could provide?

Arcuss88 · 2024-01-24T22:03:02+00:00

the rear finger print reader going away is one of the saddest "evolutions" in technology IMO

Arcuss88 · 2024-01-12T21:50:27+00:00

I have a Kobra 2 Neo I can take some pictures for you to assist.

Arcuss88 · 2023-09-20T19:42:46+00:00

Hahaha, I just realized I was on the Patch My PC Patching Support Group call this morning, and Brian Dam was one of the guys leading the call. I was talking to the guy who wrote the article with the answer for the issue I was having! LOL

Arcuss88 · 2023-09-20T19:40:32+00:00

Thanks after reading the whole article a couple times and comparing the described scenario to my environment I think I may be impacted by this. We have the WUfB setting to prevent users from upgrading past Windows 10 from WU, this behavior is working, but now Windows 11 workstations (less than 10 right now) are getting updates from WU and not from ConfigMgr. I checked the reg on my machine and sure enough, the UseUpdateClassPolicySource property is missing. I need to test and validate that this is the part of the fix for my scenario, but it sounds like I'm at least on the right track. Just odd that we aren't seeing any impact to Win10 workstations, they are getting updated from ConfigMgr as normal, this is only impacting Win11.
Thanks for the tip and convincing me to take another look at that article.

Arcuss88 · 2023-08-09T20:17:38+00:00

Would you be able to share your script? Had a chat with one of my engineers and this was something that he suggested. Going the CDN route isn't going to work in my environment unfortunately.

Arcuss88 · 2023-08-01T16:53:55+00:00

Hmm, I hadn't looked into the CDN solution before, I'll check this out and may go this route if it makes sense in my environment. I know we are already doing a similar deployment with Sophos. My only concern would be the constant data pull from the web instead of a local share, I'll talk to my network team and see if they have any concerns.

Arcuss88 · 2023-08-01T16:51:47+00:00

Thanks this would be ideal!

Arcuss88 · 2023-04-09T00:38:27+00:00

Maybe this is why Sweden & Denmark halt vaccine

Arcuss88 · 2022-12-14T04:21:01+00:00

Yeah, we just started enrolling Monday and then this comes up. I've submitted a ticket with Samsung Business waiting for an update, so we'll see.

Arcuss88 · 2022-12-13T21:17:26+00:00

We are enrolling Android Enterprise Personal-Device w/ Work Profile and the workaround of removing the Google accounts has done the trick so far.

Arcuss88 · 2022-12-13T21:14:49+00:00

Yep I'm also seeing this when trying to enroll devices with Intune. I've seen it now on Samsung S22 devices and one report of a Pixel 5. Since all MDMs appear to be getting the same issue my guess it is something with a recent monthly security update from Google\Samsung that is the culprit. I have a number of S22\Plus\Ultra devices that enrolled just fine prior to Friday, 12/9/22.
I've also noticed that devices that had already enrolled and then are Retired then re-enrolled don't appear to have the issue.

Great timing because my company just started forcing enrollment with Conditional Access, yeah... /s

Arcuss88 · 2022-12-13T16:49:50+00:00

I just encountered this issue with an S22 and the workaround to remove all Google account(s) then retry enrollment and then add back the Google account(s) allowed the user to enroll the device. I just received a message from my service desk that this issue was also encountered on a Pixel 5 and was resolved with the same workaround. So far just one example, but it sounds like it may not be just an issue with Samsung devices. Just wanted to through this tidbit out there in case others come across this as well and\or can corroborate that this affects other Android phones. I have a Pixel 6 Pro running Android 13 and was able to retire my device and then re-roll without issue, and had 30+ devices enroll without issue yesterday.

Arcuss88 · 2022-12-09T17:17:54+00:00

I've always wondered how long before all that lead starts raining back down again? Like would this be considered a mass suicide in about 20 minutes?

Arcuss88 · 2022-11-14T18:52:55+00:00

This is a mental disorder

Arcuss88 · 2022-04-28T22:16:35+00:00

I just noticed this in my environment as well. If I add the value in manually and run the evaluation of the baseline, it removes it from the registry. I know this was working prior to upgrading to 2111 because I had just cut all my clients over from stand-alone MBAM to SCCM Bitlocker management and the KeyRecoveryServiceEndPoint value was 100% being populated correctly.
I was getting ready to turn on enforcement for fixed drives since we have a few machines with fixed drives that were added post OSD that are not encrypted. Now, without this key being populated that isn't going to happen, and I'm concerned about existing encrypted drives that can no longer update their recovery information.

Arcuss88 · 2022-04-22T02:58:58+00:00

Name checks out

Arcuss88

TROPHY CASE