User Profile
ON2000
Brass Contributor
Joined Oct 18, 2017
User Widgets
Recent Discussions
Why is Remote Desktop app from MS Store not aligned with Windows Desktop app releases?
Hi, I recently struggled to login to some new "Azure Virtual Desktop" VMs, using the MS Store version of "Remote desktop". This app is, at time of writing, the version 1.2.1810 (https://github.com/MicrosoftDocs/windowsserverdocs/blob/a4b5827771360b24b69b567de2a3244a067c27df/WindowsServerDocs/remote/remote-desktop-services/clients/remote-desktop-clients.md) Unfortunately, if you try to connect to these VMs with your AAD account/UPN, you get a nice username/password incorrect (I am also connecting from a machine that is AAD-bound in same tenant). However, if you install the so-called "Windows Desktop" app (that is BTW also called "Remote Desktop" in your start menu...), then everything is fine. At time of writing, the app version is 1.2.2459. So while they were already few "Windows Desktop" recent revisions published by MS, the version from the Store is still the one from march 2021 (https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/windows-whatsnew) Beside this authentication annoyance, I am wondering why the "Remote Desktop" MS Store version has no feature-parity with the "Windows Desktop" app, and why the one from the Store (which is basically easier to install in 1-click, then playing with a MSI download/installation...), seems always lagging behind? When you look at https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/remote-desktop-features, there is here yet another naming scheme : Windows Inbox, Windows Desktop, Microsoft Store. Is there no way to harmonize the naming and articles?Re: Intune Management Extension not installing
This morning, everything went fine and thought I would pull all my hair off. It worked with any users (AD or AAD), scripts were installed sometimes after 7 to 10 min of uptime after OOBE, but there were installed at some point. But while writing this post, I did a last test with the same user I used during all my tests, and I hit the issue again : even the start menu icons (like for for XBox, Alarms, Weather, Sway,...) were not populated after 10 minutes, and were left with these "down-arrows" signs (see attachment), even if the Intune Management Extension MSI could already be seen in Settings/Apps pane. But at the exact moment, that "wsappx" process starts to re-eat your CPU (it did it first time shortly after landing on desktop to install my 7-Zip MSI, Arduino and Bitcoin Calculator apps from the Store... I flagged them in Intune as "Required"), my PS scripts were executed after exactly 20 min of uptime!, and 4 minutes later, the start menu icons for XBox&Co started to be all populated. So one thing is sure : you really have to wait until "omadmclient.exe" and this "State Repository Service" are really idle for long time, and you have to wait even few minutes more to be on safe side. It makes me believe there is now like an artificial throttling interval, that didn't existed before, and is why people believe "PS scripts do not always work", especially when your CPU/network/disk are fully idle for few min.93KViews0likes45CommentsRe: Intune Management Extension not installing
I also noticed the same since approx 2 weeks. This worked absolutely fine in the past (in Dec for example, I built internal docs based on these positive results). Unfortunately, I did not found any root cause so far : in "devicemanagement" event log, stuff seems to communicate to the Intune backed and no obvious errors. Hitting "Sync button" does not help. The file C:\ProgramData\Microsoft\IntuneManagementExtension\Logs\IntuneManagementExtension.txt and the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\IntuneManagementExtension\Policies\ are no longer created. Since that time (coincidence?), I have also problems with devices enrolled with on-prem users coming from "synched AD groups" (from an on-prem infra, and using ADFS), where neither apps, scripts, or profiles are applied, even if "devicemanagement" event log does also not show obvious errors. I will post here once I will progress in my tests.94KViews0likes49CommentsRe: Migration tool
I thought that if you offer co-management, then this can be seen as a "long transition phase", and you believe that one day, your customers will not stay with SCCM and Intune running in parallel forever, even if these "authority sliders" in SCCM 1710 let you choose what backend is doing what. Then sooner or later, the Data Importer tool and MMAT tools will need to translate the GPOs and other advanced SCCM options to their MDM equivalents...or you will somehow "simplify" things by dropping lot of SCCM options, no? ;-).6.4KViews0likes1CommentRe: Demo at Ignite
So it means once a machine is switched to being Intune-managed, even if the device is physically connected my company LAN, it will not be able to use our SCCM internal distribution points, to cache the updates files, and only the Intune "Delivery optimization download mode" options found in the "Update Ring" configurations will apply, right? Asking this, as we want to avoid all Internet links to collapse every 6 months :-).2KViews0likes1CommentMigration tool
hi, I heard of about this tool : https://docs.microsoft.com/en-us/sccm/mdm/deploy-use/migrate-import-data , which is supposed to migrate the SCCM content to Intune. You say that it migrates policies/packages/CIs/VPN or Wifi profiles, and stuff like this : I understand there are some limitations, explained in the documentation, but are you not afraid that vast majority of users will not be able to use this tool in a prod way, because of the various current Intune limitations like no PS script support yet available, not all GPOs are existing in the "LocalSecurityPolicies" CSP, packages that are EXE-based or contains several MSI files, and so on... ?
Recent Blog Articles
No content to show