Intune/Set-WindowsDesktopWallpaper.ps1 at master You can find the updated script that works in a modern world in our GitHub repo, at the following URL: That was something that was not performed by the previous version, and should be considered a very much important task. Something worth mentioning that also has been improved with this new script, is that it now restores the required changes made to NTFS permissions on the desktop wallpaper image files that’s replaced using this approach. A shift towards the cloud, more specifically a Storage Account in Azure for instance, makes much more sense.Īdditionally, new functionality have also been added to the script, where as support for replacing theme related desktop wallpapers (the files located in C:\Windows\Web\Wallpaper\Theme1), as highlighted below:Īlso, the new script can now replace any of the default 4K wallpapers, more specifically the image files that reside inside the C:\Windows\Web\4K\Wallpaper\Windows folder: One of the core changes is that the desktop wallpaper cannot be stored in any sort of package and be delivered to the device along side with the script that is responsible for configuring the desktop wallpaper. In order to utilize the script when provisioning a device using Windows Autopilot to be managed by Intune, the script needed some changes. The script mentioned in the other blog post referenced above, was originally created to work in an on-premise world where devices was deployed using ConfigMgr. Looking at the options we have available today, the scripted approach still makes the most sense, as it can be customized to the max and essentially only your imagination sets the limit, and not intrusively lock the desktop wallpaper for the user. Set custom wallpaper in Windows 10 during OSD with ConfigMgr – MSEndpointMgr There are also a bunch of resources out there, that uses various script-based methods to replace the famous img0.jpg file, which is an approach that I’ve taken myself several times over the years, even so that I wrote a script about and posted it here on the blog: For myself, I don’t see an issue with the company that I work for would want to ‘brand’ their equipment, however they should at least provide me with the means to be able to change it. Some organizations would not have an issue with that, others might see that differently. a Storage Account in Azure or similar, as shown in the picture below:Ī downside of using this method, could of course be that the end user cannot change this desktop wallpaper set by their IT department. With Microsoft Intune, the option to set a desktop wallpaper can easily be performed by using a ‘ Device Restriction‘ policy, pointing to an image file stored in e.g. In a modern world, this hasn’t really changed, however the methods to use are slightly different than what was commonly used in the past. Type one of the following in the box and press Enter or click “OK.Every organization to some extent configures the desktop wallpaper for their users, it’s something that’s been common in the industry for ages and it’s also a way to brand it’s managed devices. To get started, use the Windows R keyboard shortcut to open the Run menu. In general, you’ll want to put shortcuts in this folder, not EXE files. Programs that are put in these folders will launch when the PC is started. One is for determining the apps that start up on your personal account, the other is for all users. There are two locations you’ll need to know to find the “Startup” folder. RELATED: How to Manage Startup Programs in Windows 10's Settings App How to Open the Startup Folder It works well and shows some apps that won’t appear in the Startup folders, but you can still access them.įor example, if you want to make an application start every time you sign into your computer, you can add a shortcut to it to the Startup folder. To stop apps from starting when you sign in, you should probably use the Startup Apps screen in Windows 10’s Settings app. This is where you can toggle on or off apps that want to run at startup.
0 Comments
Leave a Reply. |