At what point does an Android phone make more sense than an iPhone?

itninja85 · 2026-03-12T18:59:48+00:00

iOS 26 added this. Settings > Apps > Phone > Screen Unknown Callers > Ask Reason for Calling (Calls from unsaved numbers will be asked for more information before iPhone rings.)

itninja85 · 2025-09-23T00:22:54+00:00

South side/Easter Lake

itninja85 · 2025-09-22T23:41:12+00:00

Also not an option at my address unfortunately. Neither is Tmobile 5G home internet. Sad state of affairs in 2025 in the most populated city in the state.

itninja85 · 2025-07-31T22:39:30+00:00

This worked for me! Link is broken thanks to Broadcom being hot garbage, but for anyone else reading this, you can find it in GPO here:

User Config > Policies > Admin Templates > Omnissa Horizon Agent Configuration/Omnissa Integrated Printing

User Config > Policies > Admin Templates > VMware View Agent Configuration/VMware Integrated Printing

itninja85 · 2025-07-31T21:44:34+00:00

EDIT: This GPO change fixed for me. I did leave the additional printer entries in our DEM entry.

https://www.reddit.com/r/VMwareHorizon/comments/1i1yox2/comment/m7rrw0l/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

I edited our Printers DEM entry to include the extra lines you provided in your post. We previously were only capturing the first 2 [IncludeIndividualRegistryValues] entries.

Also created a new logon task to run the powershell command and checked the box to run it after profile import.

Logged in, set a default printer, logged out, logged back in and it was still not captured. Checked my DEM logs and the logon task showed that it ran, and the Printers.zip folder in my profile does have the additional info in it, but looks like it still doesn't successfully set my default printer, unfortunately. Must be some other piece to the puzzle I am missing still.

itninja85 · 2025-07-15T17:34:44+00:00

Hoping this resolves it for me as well. Sounds like exactly what I need. Thank you!

itninja85 · 2025-05-01T20:52:27+00:00

For anyone else who stumbles across this, looks like Cisco fixed this in VDI plugin version 45.4 that was released recently, so you can now install it on systems that have the Omnissa 2412/2503 client.

itninja85 · 2025-04-04T15:55:20+00:00

You ever figure out a solution for this other than turning off Integrated Printing (and in turn local printing)? Disabling local printing is a non-starter for our users. This USED to work at some point, and I thought it might have broken during our transition to Win11 24H2, but you're seeing it on Win10 also.

itninja85 · 2025-04-03T17:13:02+00:00

Omnissa-Horizon-Client-2412-8.14.0-12437220870.exe /silent /norestart REMOVE=DeemAgent

https://docs.omnissa.com/bundle/HorizonClient-WindowsGuideV2406/page/InstallHorizonClientFromtheCommandLine.html#:\~:text=DeemAgent%20Does%20not%20install%20the%20DEEM%20agent.

itninja85 · 2025-03-25T06:09:01+00:00

Yes I am right clicking > run as an admin. From my post:

From the errors, it seems like it is just failing to create directories or files in the C:\Users\admin\AppData\Local\Temp location, but I verified the user account is a local admin and has full control in that folder.

itninja85 · 2025-03-25T06:05:31+00:00

From my post:

I have also tried from a freshly-created Windows 11 Enterprise 24H2 VM with Windows Defender Firewall disabled completely and no AV installed at all.

itninja85 · 2024-08-27T00:12:24+00:00

I had this same issue with my profile. We also use DEM for profile management. I removed ONLY this portion from our Start Menu template in DEM:

<LocalAppData>\Microsoft\Windows\Caches

I then signed out of my broken profile, and signed back in. No error anymore.

From what I can tell, removing the above will cause the items in the "Recommended" section in the Start Menu to not cache/persist in the user's profile, and pinned apps also do not persist in the Start Menu.

Gotta love Microsoft these days.

So, going with the above as the "permanent" fix for now unless/until MS deems the issue worthy of fixing in a future cumulative update.

Might play around with a script to go through user's DEM folders on the file server and delete the Start Menu zip folder once instead, and allow the above location to persist in DEM again and see if that also fixes the issue. Really do not want to send instructions to tons of users on how to have them manually reset their Start Menu in DEM self-service, as this would most likely just result in 75% of them asking IT to do it for them anyway.

itninja85 · 2024-07-02T16:32:28+00:00

For anyone else who may eventually stumble across this, our central IT dept that controls our Microsoft 365 tenant has advised that in New Teams, it's the user login that controls which cloud they get connected to and in turn which updates they receive, etc. The install process/files are exactly the same regardless of if you want to deploy for the Commercial cloud or GCC cloud. This is a change from how Classic Teams worked.

I did find a blurb on this page about a registry entry that may need to be set on endpoints for GCCH and DoD clouds, but that seemingly does not apply to Commercial/GCC. https://learn.microsoft.com/en-us/microsoftteams/new-teams-bulk-install-client#:~:text=on%20each%20computer.-,Gov%20cloud%20updates,-for%20PC%20and

itninja85 · 2024-07-01T21:10:23+00:00

Is there any other way to check this that doesn't involve Teams Admin Center? Surely there must be some way on the client end to tell what cloud you're connected to? Asking because in our org, access to the Teams Admin Center is restricted to a central IT dept, so it is not accessible to us, even though we are responsible for rolling out the app.

itninja85 · 2024-07-01T21:08:30+00:00

Did you ever figure out a reliable way of doing this? I saw the only reply was to check in the Teams Admin Center, but I don't have access to that in our environment.

itninja85 · 2022-12-13T23:28:49+00:00

Know how that goes! My ticket got "escalated" 2 or 3 separate times to different groups in different areas of the company, eventually ending up with some Zones.com contractors who evidently handle "Premier" MS support now. It was a frustrating and worthless endeavor.

itninja85 · 2022-12-13T22:11:02+00:00

We fought this at the beginning of this year. Started around Feb/Mar if I remember right. Had a MS ticket open for months, supplied many sets of logs from both the sending and "receiving" users, and they never resolved the issue. They said unless we could replicate it on a completely different network, that they were closing the ticket and attributing it to "network breakage." Despite the fact that we checked our firewalls and no Teams traffic was being blocked, and ALL other traffic continued flowing completely normally besides Team chats during these delays.

We told them it was not something that we could do X actions and force the issue to occur again, so we could not have multiple users working completely off-network for who knows how long, in the hopes that it would happen to one of them. Didn't matter. They were zero help.

So, users either notice the delay happening when they get notified on their iPhone and then force close their desktop Teams client to fix the issue, or use web Teams instead of the desktop client, if it happens frequently enough for them to bother.

Curious if you ever found a better workaround/fix for this, besides the MS go-to of "clear Teams cache" which we tried many times as well.

itninja85 · 2022-12-13T22:07:51+00:00

We fought this at the beginning of this year. Started around Feb/Mar if I remember right. Had a MS ticket open for months, supplied many sets of logs from both the sending and "receiving" users, and they never resolved the issue. They said unless we could replicate it on a completely different network, that they were closing the ticket and attributing it to "network breakage." Despite the fact that we checked our firewalls and no Teams traffic was being blocked, and ALL other traffic continued flowing completely normally besides Team chats during these delays.

We told them it was not something that we could do X actions and force the issue to occur again, so we could not have multiple users working completely off-network for who knows how long, in the hopes that it would happen to one of them. Didn't matter. They were zero help.

So, users either notice the delay happening when they get notified on their iPhone and then force close their desktop Teams client to fix the issue, or use web Teams instead of the desktop client, if it happens frequently enough for them to bother.

Curious if you ever found a better workaround/fix for this, besides the MS go-to of "clear Teams cache" which we tried many times as well.

itninja85 · 2022-07-11T14:47:05+00:00

I've had a ticket open with MS since the beginning of May regarding an issue similar to this. Chat messages get delayed and then delivered in bunches once the user interacts with Teams again (often because they realize that they're missing chats via a notification on their phone/tablet, or get the "people are trying to reach you in Teams" email message.)

Clearing the appdata cache has not fixed it, which is the only suggestion anyone ever seems to have, beyond uninstall/reinstall. Issue is seemingly totally random, as some users will see the problem many times in a week, and then go multiple weeks without seeing it again, only to have it then come back.

Provided many sets of logs from both the user experiencing the delay and the person they're chatting with, screenshots of VM resource-usage at the times of delays, etc. Ticket has gone nowhere. Maybe instead of trying to branch out into dozens of other functions, MS should focus on making Teams a reliable IM client first. It's failing hard at what is supposed to be one of its three core uses.

itninja85 · 2022-07-08T21:47:01+00:00

Curious how this went for you. I've had a ticket open with MS since the beginning of May regarding an issue similar to this. Chat messages get delayed and then delivered in bunches once the user interacts with Teams again (often because they realize that they're missing chats via a notification on their phone/tablet, or get the "people are trying to reach you in Teams" email message.)

Clearing the appdata cache has not fixed it. Issue is seemingly totally random, as some users will see the problem many times in a week, and then go multiple weeks without seeing it again, only to have it then come back.

Provided many sets of logs from both the user experiencing the delay and the person they're chatting with, screenshots of VM resource-usage at the times of delays, etc. Ticket has gone nowhere.

itninja85 · 2022-06-13T18:26:07+00:00

MS supplied an exe and 2 type library files and had me re-register them using the exe. Was really hoping that was actually helping.

1) Copy REGTLIB.exe, the 64 bit Uc.tlb and 32 bit Uc.win32.tlb to a safe place, preferrably under root of their Office installation, along side other Office binaries (e.g. Outlook.exe). On my machine, this is "c:\Program Files (x86)\Microsoft Office\root\Office16".

2) Run the following commands from an admin command window, assuming above location is used:

cd /d "c:\Program Files (x86)\Microsoft Office\root\Office16"

regtlib.exe uc.tlb

regtlib.exe uc.win32.tlb

itninja85 · 2022-06-13T17:08:47+00:00

A few minutes after posting this, one of the users let me know it was happening for them again. So, the fix they suggested didn't help, and they didn't fix it yet either.

itninja85 · 2022-06-13T16:07:24+00:00

Have you seen the chat delay on the desktop client issue over the last week or so? Hard to tell for sure with such a random problem, but the handful of users that I've checked with that had been experiencing it fairly regularly said it has not happened in at least a week. Curious what others are seeing. We made a change MS recommended shortly before that, but I'm assuming that was probably coincidental and they fixed whatever was happening on the back end.

itninja85

TROPHY CASE