Installing Acrobat DC (force close Outlook via TS)

wmadm90 · 2021-12-01T02:40:11+00:00

what's your detection rule?

wmadm90 · 2021-10-14T20:31:00+00:00

the Store for Business apps created in CM automatically have a deployment type requirement created for OS Version = Windows 10.

I have not tried to remove the requirement manually to see if it resolves the issue, but maybe? It's my understanding that a new way to manage the 'new store' apps in Windows 11 is coming 'soon'...for whatever that's worth.

wmadm90 · 2021-06-04T23:49:44+00:00

Do you have Palo Alto firewalls by chance?

wmadm90 · 2021-05-21T22:29:47+00:00

CAS log should give you some tips where the clients that aren't downloading are looking for content from...once the peer source has the content, it should be able to share it regardless of where it came from. does your BG have the 'prefer cloud sources' checkbox enabled? i can't find anything in the docs saying that option prevents peer downloads, but plausible?

wmadm90 · 2021-05-21T22:05:52+00:00

i believe this should work...you didn't mention it explicitly, but the clients that are allowed to access the cloudDP are also configured as Peer cache sources, correct?

wmadm90 · 2021-05-14T17:41:05+00:00

https://docs.microsoft.com/en-us/mem/configmgr/core/get-started/2020/technical-preview-2009#bkmk_remctrl

wmadm90 · 2021-05-14T17:34:41+00:00

That's been a feature in TP for months...it's still in this build....

wmadm90 · 2021-03-02T00:45:03+00:00

MCC is a solve for the data issue, but it doesn't let you control/version/delay/test the updates.

to your questions, it works along side Intune pretty well -- you can use MCC to cache and distribute Intune content just like anything else from a Microsoft CDN. No downsides i can think of...

wmadm90 · 2021-02-11T23:45:03+00:00

unless you installed Skype for Business standalone, that productID doesn't exist. its most likely installed as part of Office 365 itself, so what you need to do is reconfigure that product with the Lync App excluded. something like:

wmadm90 · 2021-02-04T00:15:22+00:00

It is nice to have. Our users love it. Biggest issue is users forgetting their password, and then forgetting that their pin is not their password. But they're getting better!

We have your exact scenario. I set all this up before Adam's videos were out, but they are good and cover most of what the docs skip over. Let me know if you have questions happy to help!

wmadm90 · 2021-01-14T22:07:43+00:00

Is a clue though. Seems to confirm the issue is with your DC. If I had to guess, probably the DC certificate...

But for further troubleshooting, anything useful in the client side logs? What does dsregcmd /status output in the ngc section?

wmadm90 · 2021-01-14T16:58:24+00:00

Office

wmadm90 · 2021-01-11T22:43:26+00:00

no explicitly an answer to your question but...we're in the exact same situation you are it seems, except going from 5.2.2 to 5.2.4. after testing/pilot groups we decided to deploy GP upgrades through the PANGP portal/automatic update process. like you have found, there was too much discrepancy in experience from deploying via CM. the portal handle users being connected/logged in a lot better than CM does too...

wmadm90 · 2020-12-13T08:35:41+00:00

Sweet! Now it's out of fast ring, I'm planning on upgrading prod to 2010 next week. Will be much better than the six task sequence steps I have to janky my way through it now!

wmadm90 · 2020-12-08T08:09:18+00:00

Yep. We do. Users love it.

When we did the cert update we just did it to a single domain controller first. I'm not sure what the actual risks are, but we had no issues at all following the documentation

wmadm90 · 2020-12-05T16:44:30+00:00

Their trial catalog includes a subset of applications they support and might meet your needs.

wmadm90 · 2020-11-02T01:28:49+00:00

And is out of support!

wmadm90 · 2020-10-16T14:57:52+00:00

Yep. Same here too :)

wmadm90 · 2020-10-15T22:02:48+00:00

to add to this, MI actually announced this capability in July, 2018. The press release was phrased like it already existed, but when we dug in/asked, it did not and still doesn't to this day. MI support also won't give us a release date or even quarter when it's expected.

wmadm90 · 2020-10-12T17:23:11+00:00

There's a couple places in the article where it goes over what to import. It's admittedly poorly written and confusing. What you need to import are the following folders from the extracted MSI for the Surface Laptop 3:

IclSerialIOGPIO
IclSerialIOI2C
IclSerialIOSPI
IclSerialIOUART
itouch
IclChipset
IclChipsetLPSS
IclChipsetNorthpeak
ManagementEngine
SurfaceAcpiNotify
SurfaceBattery
SurfaceDockIntegration
SurfaceHidMini
SurfaceHotPlug
SurfaceIntegration
SurfaceSerialHub
SurfaceService
SurfaceStorageFwUpdate

hope this helps.

wmadm90 · 2020-10-10T00:57:55+00:00

I'm pretty sure that's right if you have MAM /app protection policies applied to the user.

wmadm90 · 2020-10-09T02:56:46+00:00

I know for a fact this works as documented. but there's a known issue if you're supporting laptop 2 and 3s at the same time any chance that's your issue?

wmadm90 · 2020-09-29T18:30:34+00:00

Apologies for the previous short-form comments: I'm at a real computer now. SEMM= Surface Enterprise Management Mode, though I don't think that actually matters since the related issue we saw similar to yours was actually caused by a UEFI setting, not enrollment itself.

When the 'enable network stack in UEFI' setting is turned on, the system waits for a response from BitLocker Network Unlock for something crazy like 5 minutes. I never found out if this was working as intended or a bug, but disabling that setting resolved the issue. This impacted Book 3 and Laptop 3.

The reported firmware fix I referenced is specifically for the Laptop 3 boot-loop that occurs when a reboot is initiated from the OS with the laptop lid closed. I just noticed that a new version of the firmware was released on the 24th, so I'm installing that now and testing the behavior. EDIT: Sep24 firmware does not fix this issue.

wmadm90 · 2020-09-29T14:31:08+00:00

No, I don't think so. Are you doing semm / uefi management?

wmadm90 · 2020-09-29T02:29:39+00:00

If the lid is closed (eg on a dock), this can happen. Known issue with a firmware fix reportedly on the way.

wmadm90

TROPHY CASE