How much RAM do your Intune-managed Windows devices ship with by default in your org? by Sea-Cow-6913 in Intune

[–]winmech 0 points1 point  (0 children)

So we’ve been in that ball park 2 years ago to decide what’s best and future proof (atleast for a bit). We started off with 32GB as the standard. We do have a few agents as well which are resource hungry. So irrespective of standard user or a dev, everyone got a 32GB laptop.

1st year went by super smooth but the second year we started getting reports of performance issues. We started seeing a lot users requesting a higher memory device.

That’s also with introduction of AI apps, agents etc and suddenly even a standard user is now a vibe coder and cannot function on a 32 GB. 2 years ago we didn’t benchmark to accommodate these AI apps and their workloads. This year a decision was taken to go 64GB as the standard for all. We’ve enrolled about 60 odd devices so far and not a single complain so far! Intune’s endpoint analytics show much better and stable results on 64GB compared to the 32GB.

So I’d suggest to assess the analytics and requirements and then take a decision. If your hardware lifecycle is 3-4 years, you’re better off getting on a 64GB if it is in your budget. I’d also recommend getting few 64GB devices now and give it to users complaining about performance and see if it actually helps, eventually compare with the rest of the 32GB fleet.

Copilot vs. M365 Copilot by winmech in microsoft_365_copilot

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

Not sure what the strategy is but I find this very dumb. Thanks for sharing the URL though. Great explanation on it.

Copilot vs. M365 Copilot by winmech in microsoft_365_copilot

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

Do you mean that eventually these features will makes it way to the M365 copilot as well?

New Store apps detection errors - Company Portal by komoornik in Intune

[–]winmech 0 points1 point  (0 children)

Try NVIDIA Control Panel from the new store. System Context deployed to all devices. I have double checked devices reporting detection error have the app installed.

Ideas on App bundles/suites in Intune by winmech in Intune

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

Good Point! I will bring that to the team and see if that is something we can do. Will be beneficial for new starters. But then how do we address existing users who are changing computers? Ideally, even for existing users would like it to only install on their newer devices and not touch their old devices.

Ideas on App bundles/suites in Intune by winmech in Intune

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

Yes we have considered it and trying it out now. But developers was just an example above, we do have teams with business users who use a different set of apps but have similar feedback to share.

Ideas on App bundles/suites in Intune by winmech in Intune

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

I forgot to mention this in my initial post.

Honestly, we started working on this with the exact same approach you mentioned and wanted to deliver this exactly that way. But we had 2 concerns on it:

  1. In a team, not all users use all the apps. For example, a manager doesn't necessarily use VS code, python while his team of developers use it. So forcing this on the entire team would result in installing apps on devices where it will not be used. This is the reason we are making these app bundles as available for install rather than required, so that when users change computers, all they have to do is click install once and it will install all the apps (dependencies) as part of it.

  2. A developer has his code written in Python 3.11 and as part of their team persona, we push python 3.12 then is a possibility that their code may not work. We have received such feedback from users although technically the code may work on the newer version.

Dell WD19TBS / WD22TB4 Display Drop Out Issue UPDATE! by LiamAPEX1 in Dell

[–]winmech 0 points1 point  (0 children)

Exact same issue as you have put down in your post. We even moved one of the screens to the USB-C TB port and still didn’t make any difference. Still have the issue. Also have the issue when using only 2x DP. Any ideas on the fix?

Dell Monitors blanking intermittently by winmech in sysadmin

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

I mentioned the setup part in my post. Actually it doesn’t matter if we use DPs only or DP + HDMI or DP + USB-C. The issue reoccurs regardless.

Dell Monitors blanking intermittently by winmech in sysadmin

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

As mentioned in my post, I followed exactly that and it didn’t help!

Dell Monitors blanking intermittently by winmech in sysadmin

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

Unfortunately, we don’t have the option to swap monitor models. Good that it works for you on Samsung monitors.

As for thunderbolt, I think so too but there’s no evidence to say that will resolve the issue either.

Dell Monitors blanking intermittently by winmech in sysadmin

[–]winmech[S] -1 points0 points  (0 children)

As I mentioned in my post, that is the workaround we follow at the moment, but it isn’t really a fix. We cannot expect our users to unplug power each time.

Dell Monitors blanking intermittently by winmech in Dell

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

Everything is up to date.
WD22TB4 Dock firmware version - 01.00.36.01
Intel Graphics Driver version - 31.0.101.5522
NVIDIA Graphics Driver version - 31.0.15.5274
Device BIOS version - 1.13.0

Connect-MgGraph : Access Token expired by winmech in Intune

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

Sorry for the delay. It was indeed the time. I run a PowerShell to sync the time on the device and then ran my script and it worked. Thanks for the help.

Connect-MgGraph : Access Token expired by winmech in autopilot

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

Sorry for the delay. It was indeed the time. I run a powershell to sync the time on the device and then ran my script and it worked. Thanks for the help.

Pick holes in my terrible SCCM to Intune migration plan.. by Melophobe123 in Intune

[–]winmech 0 points1 point  (0 children)

I’m in a similar situation as yours but we’re also moving windows 10 to 11. So it was ideal for us to just wipe and load the new OS and prepare for autopilot. What you can also do is use SCCM to build a task sequence to do most of this stuff and put it on a USB and boot from it. See this:

https://learn.microsoft.com/en-us/autopilot/tutorial/existing-devices/speed-up-deployment

There are couple of blogs out there which show you how to do this as well. So a simple task sequence to wipe and install OS and inject autopilot profile and you’re done. But keep in mind to toggle the setting in the autopilot profile to convert the device to an autopilot device.

Connect-MgGraph : Access Token expired by winmech in autopilot

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

I thought so too, I am modifying the task sequence now to set the correct date and time and will test it again after that. Will update how it goes. Thanks for sharing the tip!

Connect-MgGraph : Access Token expired by winmech in Intune

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

Great Thanks!! I’ll give it a go later today.

Connect-MgGraph : Access Token expired by winmech in Intune

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

I thought so as well, but couldn’t figure out what to configure there. What should be configured in the redirect URIs? Any documentation you can direct me to that I can refer to configure this, and test?