That should allow us to cover all the wonderful things users are likely to pin to their Start Tiles. An “expandable” Tile with three web shortcuts in it (Windows 10 only, not supported on Server 2016 yet). A UWP app shortcut (on Windows 10 only, UWP apps not available on Server 2016).A pinned folder from the local filesystem.To cover all eventualities, we are going to do our persistence testing on the following items: Methods #1 and #4 only apply at first user logon, whereas method #3 will add the “enforced” icons to whatever you have saved. The methods we used for supplying default layouts in the first part of this article will all work with the techniques/tools specified here for saving and persisting, with the obvious exception of method #2, which enforces a non-customizable layout every time you log in. Because in a non-persistent VDI or RDSH environment, one isn’t very useful without the other! Also, whether you’re in a non-persistent environment or not, you may want to save and roam them anyway. Now, the second part of the conundrum we set ourselves was not just how to deliver customized default Start layouts, but also how to save and persist them once the user had elected to make changes. The primary focus of part #1 was delivering a pre-arranged Start Tiles layout to the user, in a number of different ways to meet different requirements. The first part of this article is available here. This is the second part of the article on Windows 10/Server 2016 Start Tiles management.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |