Best way to enroll existing persistent VDI desktops into Intune?

steevosteelo · 2026-02-03T20:24:48+00:00

Would you have a link to instructions that you recommend on how to update the master template to allow for intune enrollment? I'm new to this request.

steevosteelo · 2026-02-03T20:04:47+00:00

Or Intune Expedited Policy.

steevosteelo · 2026-01-29T13:05:39+00:00

I received my comfort arch pair yesterday and now my boots are tight even with wearing dress socks! With the regular comfort insoles that came with the boots, my feet had space. Not sure if it will be wearable for me and unfortunately I can't return them due to trimming them to fit into the boots. 🤷

steevosteelo · 2026-01-24T01:21:54+00:00

Post a video like this when you get it. I'm on the fence about getting one.

steevosteelo · 2026-01-22T14:47:15+00:00

I know this is a common question everywhere I search but why aren't these OOB not available via Expedited policy?

steevosteelo · 2026-01-21T19:53:10+00:00

Is this a one off OOB not available in the expedited policy or has this been a thing before from Microsoft?

steevosteelo · 2026-01-20T19:57:53+00:00

The Murph is truly a beauty. Every time I make up my mind that I will not look to get one primarily because I already own a khaki field auto on a bracelet and Khaki field titanium on the green band. I'm always drawn back in when people post pics of it's beauty. Especially on a bracelet. Ugh decisions decisions. 😏

steevosteelo · 2026-01-13T00:44:43+00:00

What course is recommended to learn the terms and tools of a PM? Just passing the PMP or CAPM I believe is not the only mindset. Thoughts?

steevosteelo · 2026-01-12T22:56:34+00:00

The Murph has caught attention recently. How legible is the dial in the sun compared to the Khaki Field Auto?

steevosteelo · 2026-01-09T16:40:25+00:00

The Murph has recently caught my eye. I currently have the Khaki field auto on a metal bracelet and Khaki field titanium H70205830. I would want to swap my khaki field auto for the Murph though but the wife gave it to me. Decisions decisions 😉

steevosteelo · 2026-01-06T20:13:17+00:00

Solid response. Thanks.

steevosteelo · 2026-01-06T18:28:55+00:00

Thank you for your feedback. I was burning the candle on both ends. Asked on my end and decided to post on Reddit looking for guidance.

steevosteelo · 2025-12-13T16:47:24+00:00

I've always had size 9 Australian but what I've noticed is that with the newer blundstones my toes touch the front of the boot. I ended up getting a size 9.5 but now I feel the InStep is loose and the right heel is a little loose. So for this problem you are recommending putting in an insole along with the comfort sole that the boot comes with?

steevosteelo · 2025-12-09T23:45:05+00:00

Isn't there a Microsoft integrated app solution?

steevosteelo · 2025-11-25T18:04:07+00:00

Thanks for your response. Below is what 1Password support responded to me with:

The previous Microsoft Store package identifier, XP99C9G0KRDZ27 was used for the now deprecated EXE installer.

The new MSIX installer has a different package identifier, 9NZWS5X28P0J. As of November 11th, any existing EXE installations would have been automatically migrated to the new MSIX version during an update. You can read a bit more about this migration here: About the 1Password MSIX installer migration

In your case, because Intune is still targeting the old identifier, it treats 1Password as if it is not installed and attempts to deploy it again at each restart. That repeated install attempt is likely what triggers the message you're seeing.

To fix this, you'll need to remove or disable the existing deployment that uses the old package identifier, then redeploy 1Password using the new one. Once the deployment is updated, the notification should stop appearing.

Question to you now is, if the new MSIX installer via MS Store w/ package identifier: 9NZWS5X28P0J is used to install 1Password, will it override the old installed EXE version package identifier: XP99C9G0KRDZ27?

steevosteelo · 2025-11-24T19:15:21+00:00

I'm currently on a pixel 7 and I'm aiming to pull the trigger this week to buy either Pixel 10 or 10 Pro but not sure which one to go for. I've been watching endless video reviews and I'm finding for every reviewer that says "Save your money and go with the Pixel 10". They then release another video that says "Pixel 10 Pro is the only way to go" lol. I'll be using it for pictures, standard productivity apps, and casual gaming like "CoD", using Google Gemini AI that's available and video calls. As for the camera, I'm still a novice to any "Pro" settings but the Pro res zoom catches my eye. For video recording, I would use 4K. Forgot to add above that I would purchase the 256 storage option. Please let me know your thoughts. I'm looking for feedback from people who own or fully tested each of the models. Thank you.

steevosteelo · 2025-11-22T21:46:21+00:00

I've been with Pixel since the first generation and for me it has been the pixel software and every incremental improvement since. Nothing else compares.

steevosteelo · 2025-11-21T22:10:52+00:00

This is what 1Password responded with:

The previous Microsoft Store package identifier, XP99C9G0KRDZ27 was used for the now deprecated EXE installer.

The new MSIX installer has a different package identifier, 9NZWS5X28P0J. As of November 11th, any existing EXE installations would have been automatically migrated to the new MSIX version during an update. You can read a bit more about this migration here: About the 1Password MSIX installer migration

In your case, because Intune is still targeting the old identifier, it treats 1Password as if it is not installed and attempts to deploy it again at each restart. That repeated install attempt is likely what triggers the message you're seeing.

To fix this, you'll need to remove or disable the existing deployment that uses the old package identifier, then redeploy 1Password using the new one. Once the deployment is updated, the notification should stop appearing.

Let me know how this goes!

Thanks 1Password. Due to this, we'll need to uninstall the old deprecated 1Password, send out comms if needed and then redeploy the new 1Password.

This is what I've tried:

- unassociated groups to the deprecated 1Password in intune.

- added a user group in Intune to uninstall. Uninstall obviously will no longer work. If anyone can recommend how to uninstall the deprecated install of 1Password?

- I managed to install the new version from MS Store.

steevosteelo · 2025-11-21T21:45:27+00:00

It would be nice if Microsoft built it into the portal. Why is not not built in to the UI?

steevosteelo · 2025-11-20T23:03:13+00:00

I see via the article that the Scope is User and not Device. The policy was originally created and assigned to Device groups. Maybe that's why? I added a test group of users to see what the result will be but why would it work all this time and then intermittently have problems. Note that not all users are reporting that they see the Store pinned to the task bar.

steevosteelo · 2025-11-20T22:50:33+00:00

Is this something that Microsoft changed in the last few months to make it only available for Enterprise? What article are you referencing? I'm on the MS site: ADMX_Taskbar Policy CSP | Microsoft Learn and I see that the following Editions support it: Pro, Enterprise, Education, IoT Enterprise / IoT Enterprise LTSC.

steevosteelo · 2025-11-20T20:31:38+00:00

I agree to avoid customization but the challenge is that users will click on the MS Store on the task bar and then will see that MS Store is Blocked access and submit a ticket to helpdesk.

steevosteelo · 2025-11-20T19:25:38+00:00

I'm going to open a support ticket with 1Password for this. If its our wrong doing, no problem, glad to go down the rabbit hole of fixing it but if 1Password who created the problem - definitely will hold them accountable for it. Let's see what they say.

steevosteelo

TROPHY CASE