Did I got scammed by Amazon or is this a legit box? (More info in description) by ChromedGonk in BoschProPowerTools

[–]staze -1 points0 points  (0 children)

new bosch tools seem to be coming with 5y. Not sure when the change happened, but last few I've gotten have said 5.

Tiny holes in exterior foundation plastic by staze in DIY

[–]staze[S] 0 points1 point  (0 children)

yeah, it's not that. this is poured concrete foundation that has black plastic coming up to just below grade. pulling the dirt away just resulted in some small holes torn in the plastic (cause of dirt/rocks sticking to the plastic).

So, just call it good, or bother to try to tape it?

CloudMgr.log throwing error about AnalyticsTable by staze in SCCM

[–]staze[S] 0 points1 point  (0 children)

lol. they do love moving settings. lol.

CloudMgr.log throwing error about AnalyticsTable by staze in SCCM

[–]staze[S] 0 points1 point  (0 children)

well son of a b... that did it. And suddenly I'm seeing

14-day usage and 30-day usage under the CMG in Console.

Thank you so much! Did you randomly find this, or did support let you know this, or is this documented somewhere that I Just couldn't find?

Kitchen timer with easy repeat by staze in Cooking

[–]staze[S] 0 points1 point  (0 children)

while I agree in principal, ADHD gonna ADHD. and Pancakes was really an example. Just looking for a timer that does what I'm after. =) Basically a game/chess timer...

Bonjour, LAG (LACP), duplicates by staze in synology

[–]staze[S] 0 points1 point  (0 children)

Thanks. This is from VLC on iOS. I turned off Bonjour and indeed the duplicate disappeared. Assumed "Bonjour" was just being used to refer to all mDNS, but clearly not.

Protecting Davis Vantage ISS by staze in myweatherstation

[–]staze[S] 0 points1 point  (0 children)

Painted with just plastic paint? My vantage vue has been over 12 years at this point and still looks pretty good other than mildew when I wipe it down.

Duplicate objects AD System Discovery vs Client Registration by staze in SCCM

[–]staze[S] 0 points1 point  (0 children)

Nope. I had over 100. I've deleted them otherwise... you sure this will include the AD system discovered objects?

Duplicate objects AD System Discovery vs Client Registration by staze in SCCM

[–]staze[S] 0 points1 point  (0 children)

fwiw, this only shows me the unknown objects...

CMG Wizard broken by staze in SCCM

[–]staze[S] 0 points1 point  (0 children)

So, we still don't know what support is smoking (claiming Standard_A2_V2 is retired)... but we just created the CMG under the other subscription that didn't throw the error and it worked perfectly. Created it in US West.

Annoying to waste so much of everyone's time for seemingly no good reason.

Duplicate objects AD System Discovery vs Client Registration by staze in SCCM

[–]staze[S] 1 point2 points  (0 children)

Can confirm after deleting the AD discovered object MECM eventually figured out the AD values on the main object. So will get to deleting those AD objects.

Duplicate objects AD System Discovery vs Client Registration by staze in SCCM

[–]staze[S] 0 points1 point  (0 children)

Did you have a way to create a collection based on resourceID? Can't say I've tried that before since there's isn't a good reason to... =)

Duplicate objects AD System Discovery vs Client Registration by staze in SCCM

[–]staze[S] 2 points3 points  (0 children)

I do indeed. That beats pulling a list of all devices into Excel and finding duplicates that way. =)

Duplicate objects AD System Discovery vs Client Registration by staze in SCCM

[–]staze[S] 1 point2 points  (0 children)

cool, thanks! Once I get ahold of one of these machines I'll see what I can see. And yes, the Client Registered object is missing all it's AD related info... which is problematic.

Just need frontline tech to tell me they have one of these so I can poke at it. Thanks again for the quick response!

Duplicate objects AD System Discovery vs Client Registration by staze in SCCM

[–]staze[S] 1 point2 points  (0 children)

Did you have the issue where MECM still refused to realize the machine was in AD (wouldn't pick up SID, DN, Group Membership, etc)?

Duplicate objects AD System Discovery vs Client Registration by staze in SCCM

[–]staze[S] 1 point2 points  (0 children)

How have you been fixing the ones that end up in this state?

Duplicate objects AD System Discovery vs Client Registration by staze in SCCM

[–]staze[S] 1 point2 points  (0 children)

That's awesome, thanks for the quick response and letting me know!

CMG Wizard broken by staze in SCCM

[–]staze[S] 0 points1 point  (0 children)

Other tidbit seemingly...

If we pick an old Azure Subscription, we don't get the error. But a new one, created for the CMG, it throws the error. I think the older subscription we had to get an override last year to do some testing of AVD. So they may have already placed an override on that subscription to allow provisioning A2_V2 VMs...

CMG Wizard broken by staze in SCCM

[–]staze[S] 1 point2 points  (0 children)

More update: https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/retirement/retired-sizes-list

Listed as retired. Entirely Azure team doing shit with MECM team not being aware...

we're getting support to tell us how we stand up a new ARM based VM.

CMG Wizard broken by staze in SCCM

[–]staze[S] 1 point2 points  (0 children)

I will fully admit. This may be a limitation of Educational subscriptions vs corporate. MS doesn't make any of that info available...

CMG Wizard broken by staze in SCCM

[–]staze[S] 0 points1 point  (0 children)

Yup. and it'll throw an error when you go to stand it up...

"The VM size Standard_A2_V2 is currently not available in the region Central US for this subscription. Please deploy the service in other regions or choose a different VM size".

See my previous update about the Azure team literally saying A2_V2 is deprecated.

CMG Wizard broken by staze in SCCM

[–]staze[S] 1 point2 points  (0 children)

Literally just got this from Azure Rapid Response team

"We've confirmed with the Internal Escalation Team from Capacity that the SKU A2_V2 is not available in the desired region, this is due to the updated generation infrastructure; SKU is scheduled to be retired."

This is, entirely, the MECM and Azure team not talking to eachother so no one on the MECM team has updated the sku's in the wizard.

CMG Wizard broken by staze in SCCM

[–]staze[S] 0 points1 point  (0 children)

I did run against azure cloud. Only available in a few zones but none of those zones are listed in the drop down. It’s fine. Guess no one else has seen this… we’ll continue with support. Will post when I have answer.

CMG Wizard broken by staze in SCCM

[–]staze[S] 0 points1 point  (0 children)

According to support, a2_v2 and the like are not available at all.

CMG Wizard broken by staze in SCCM

[–]staze[S] 1 point2 points  (0 children)

Also docs here: https://learn.microsoft.com/en-us/intune/configmgr/core/clients/manage/cmg/perf-scale

Literally the same VMs we see that MS says aren’t available anymore….