![]() Many have traditionally used the Citrix Receiver/Workspace app to do this, but a) you may not be in a Citrix environment, or b) using the Workspace App in this way often feels clunky, drawn-out and messy – you’ve got to wait for the app to launch and kick in, at which point it then injects its own shortcuts into a pre-existing Start Menu. I’ve always been a fan of building a dynamic Start Menu when the user logs in based around their entitlements. Up to Windows 7/2008 R2, these additional features were quite simple and could be manipulated by Group Policies, Registry items and special folders – but with Windows 8 and upwards, we were introduced to wonderful things like the Start Tiles, Start Screen, UWP apps, WinX menus and many others that have made our management of this area of the UI much harder.īefore we start and dive in, let’s be clear what we are talking about here – we’re not referring to the Start Tiles (which are shown below) However, as operating systems moved on this became less a pure filesystem and was supported more by other items in the interface. The Start Menu has always been a combination of filesystem shortcuts that were applied to the user (from %APPDATA%\Microsoft\Windows\Start Menu) and the device (common start menu items were stored in an area that now maps to %ALLUSERSPROFILE%\Microsoft\Windows\Start Menu). How can we manage it so that it updates dynamically based on user entitlements so that we have security and flexibility, but also is easy to manage and doesn’t require a lot of updating? History The Start Menu in Windows used to be a user-customizable area of the filesystem, but ever since Windows 8, new functionality has been added here that has made it much more tricky to manage. Earlier versions of Windows ignore this setting.Let’s sort the Start Menu out…and find a nice, secure, simple way of managing it. Windows 7 introduced support for this setting. In the Do Not Highlight as New setting, select Yes. lnk file could be locked by a different process.įor InstallScript projects, use the Do Not Highlight as New setting. ![]() In the aforementioned message, is the name of the Shell property that Windows Installer is attempting to set, and. Property for shortcut ’.lnk’ could not be set. Note that for Windows Installer–based installations, some end users have reported run-time warnings or errors with a message such as the following one when Windows Installer is installing a shortcut that configures Shell properties: Earlier versions of Windows Installer ignore this property. Windows Installer 5 introduced support for this shortcut property. ![]() To enable the Start menu entry to be highlighted, find the Key Name setting that has a Property subsetting with either of the following, and click the Delete this shortcut shell property button in the Key Name setting: InstallShield adds a new Key Name setting, plus additional rows of related settings under it, and configures them as needed. In the Shell Properties setting, click the Add New Shell Shortcut Property button, and then click Do Not Highlight as New. The shortcut’s settings are displayed in the right pane. In the Shortcuts explorer, select the shortcut that you want to configure. In the View List under System Configuration, click Shortcuts. To prevent the Start menu entry for a shortcut from being highlighted as newly installed: 1. Instructions for Windows Installer–Based Projectsįor Basic MSI, DIM, InstallScript MSI, Merge Module, MSI Database, MSM Database, and Transform projects, use the Shell Properties setting to prevent the highlight behavior. Note that the method for preventing the highlight behavior varies, depending on the project type that you are using. By default, the property is not set for new shortcuts. If you specify that you want to prevent the highlight functionality for a shortcut, the installation sets a Windows Shell property. You may want to set this property for shortcuts that are for tools and secondary products that are part of your installation. This has the same effect as clearing the Highlight newly installed programs check box in the Customize Start Menu dialog box for an individual item on a target system. InstallShield lets you optionally prevent a shortcut on the Start menu from being highlighted as newly installed after end users install your product. Project-specific differences are noted where applicable. This information applies to the following project types:.Preventing a Shortcut on the Start Menu from Being Highlighted as Newly Installed Preventing a Shortcut on the Start Menu from Being Highlighted as Newly Installed
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |