#LENOVO WINDOWS 10 START MENU NOT WORKING KEYGEN#
The name is misleading I would say.Īt the end, as far as I understand, the difference will be only that via Local Policy you would still be able to revert it back whenever you want it. That is the same for taskbar when you add PinListPlacement="Replace", even if is set as "Device Restriction". Yet, according with my researches at the time when I was creating this policy, you can lock an specific group by specifying in the XML the LayoutCustomizationRestrictionType="OnlySpecifiedGroups" and still leave the customization of the remaining start menu. Unfortunately now that this has been scoped for more than 100+ devices, I found out that this policy is those tattooed ones. Remove-Item -Path "C:\Users\DefaultLayout.bin" -Force Import-startlayout -layoutpath C:\Users\DefaultLayout.bin -MountPath C:\ Set-Content -PassThru "C:\Users\defaultlayout.bin" ' New-Item "C:\Users\defaultLayout.bin" -ItemType File At least this has been my experience from testing this pretty extensively the last few weeks. One thing to remember, if you set taskbar via XML, the pins are not changeable by users regardless of your method but using import-startlayout does allow the users to pin/unpin the start menu. This will set the start menu with your layout before the users profile can be created, and should overwrite any default the OS is setting for users. I never liked pushing things via policy with the intent they be changeable. You may have defective battery or power supply module (yes, laptop has a PSU. It sets it but users are able to change it if they so desire. There are many possibilities as to what causing the problem in this question. I've added our XML file below just for reference.ĭeploy this as a script to a device group instead of using a device restriction policy for the XML data. I've manually erased it from the user AppData, All User, Default0, etc. Lenovo startmenu group comes back again and again. I've already tested to erase the XML file that is not pushed by Intune in "%LocalAppData%\Local\Microsoft\Windows\Shell" directory, but it does not seem to work. Whenever I managed to clean the start menu, Lenovo succeeds to pin it again after a reboot. End-user choses to unpin the group, nothing happens. This group seems to be locked/buggy somehow. This happens in more than one device in our company, so it's not an isolated case. It works on most devices, yet in Lenovo it seems that a custom group starts to duplicate itself more than once. The deployed XML file would simply add a group of applications and fix some other apps in the taskbar. We have a Device Restriction policy (device assigned) which defines the Start Menu layout with a set of applications (nothing of another world). Most of our policies works just fine with the OEM image, with exception of Lenovo.
As we all know, any OEM image comes with tons of bloatware and custom configurations. Our first approach with MEM is to manage all policies and settings to in a second phase move forward with App management.Īll our devices are AADJ devices, no hybrid environment.Ĭoming to the point.
Our company decided to enroll devices with manufactory's OEM image and we are still in the early phase of managing the life cycle of our applications via Intune with PatchMyPC (in case this info is of any value). So we are having an strange behavior with Lenovo's machines.
0 kommentar(er)
