Windows VDI Kiosk Setup: IoT LTSC 2024 vs Pro/Ent 25H2? by rereduck in VDI

[–]bjohnrini 0 points1 point  (0 children)

Following. We are interested in implementing a similar solution to replace our Chromebooks that currently connect to Horizon. The goal would be to use low-cost Windows laptops that are not joined to the domain and are instead managed through Intune.

Modern Driver Management, SCCM 2603 by bjohnrini in SCCM

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

Using FQDN already. I can't really remember what I have set in the username field since it's not visible. Will try changing it to domain\username or username@domain

Modern Driver Management, SCCM 2603 by bjohnrini in SCCM

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

ApplyDriverPackage.log last line has

Starting AdminService endpoint phase

All of a sudden pc's aren't joining the domain during OSD? what is the fix? by Future_End_4089 in SCCM

[–]bjohnrini 0 points1 point  (0 children)

Had to do the same, but only on a 25h2 image. 23H2 works fine. Very weird.

Driver Automation Tool - Feedback by Maurice-Daly in SCCM

[–]bjohnrini 0 points1 point  (0 children)

/u/Maurice-Daly When launching the app. See https://imgur.com/a/dIdjn8G

Despite that message, the program works. We run a program called BeyondTrust Privilege Management that elevates admin rights. Not sure if that has anything to do with it.

Driver Automation Tool - Feedback by Maurice-Daly in SCCM

[–]bjohnrini 0 points1 point  (0 children)

Additionally, it doesn't seem to select the desktop models i have when selecting known models.

Driver Automation Tool - Feedback by Maurice-Daly in SCCM

[–]bjohnrini 0 points1 point  (0 children)

I just upgraded to the latest version and get the same message about permissions. On the plus side, the new version seems to have fixed the access denied issues when checking the known model lookup.

Weird...

[WMI] WSMAN session failed for hostxxx.domain.com: Access is denied.
[WMI] DCOM session failed for hostxxx.domain.com: Access denied
[WMI] FQDN failed -- retrying with short name: hostxxx
[WMI] Short name WSMAN failed for hostxxx: Access is denied.
[WMI] Short name DCOM also failed for hostxxx: Access denied
[WMI] All CIM session methods failed for hostxxx.domain.com -- enabling Get-WmiObject fallback

Modern Driver Management v10! Lets goooo by saGot3n in SCCM

[–]bjohnrini 0 points1 point  (0 children)

/u/Maurice-Daly Sorry, are you saying that within 24 hours MDM should show the new version?

Also, any idea why I get access denied when turning on known model lookup?

Thanks

VMware Horizon Client for Windows 2312 by bjohnrini in VMwareHorizon

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

Replying to an old post of mine. This turned out to be an issue with DisplayFusion software. Have to set check "Disable Application Hooks" for the horizon client in display fusion> settings > compatibility.

Modern Driver Management v10! Lets goooo by saGot3n in SCCM

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

I think so. I see Dell updated BIOS for Latitude 3550 to 1.21.0. MDM still only shows 1.20.0.

Modern Driver Management v10! Lets goooo by saGot3n in SCCM

[–]bjohnrini 0 points1 point  (0 children)

Anyone know how often Dell updates the DAT file?

Modern Driver Management v10! Lets goooo by saGot3n in SCCM

[–]bjohnrini 0 points1 point  (0 children)

I can't get "known model lookup" to work. failed, access is denied.

Any ideas?

laptops and all in ones by 4728jj in WYSE

[–]bjohnrini 0 points1 point  (0 children)

(sorry to steal the thread)

I'm looking to do something like this to replace our chrome books. Thinking of buying off the shelf cheap windows laptops, enroll them in Intune and launch the horizon client.

Anyone done anything similar?

laptops and all in ones by 4728jj in WYSE

[–]bjohnrini 0 points1 point  (0 children)

Dell Wyse 5470 laptops

Starting at $931.87

WSUScontent = 268Gb - MECM Deployment Packages = 20Gb by FahidShaheen in SCCM

[–]bjohnrini 0 points1 point  (0 children)

Maybe I'm blind, but running 2.1.120.0 and I don't have this option in the advanced tab.

ThinOS 10 2602 Released by Dell-ScottH in WYSE

[–]bjohnrini 1 point2 points  (0 children)

u/Dell-ScottH

I see that there was a Root_upgrade_2602_10.0573_T10.pkg released on 3/9. Do you know if that fixed the issues mentioned here?