![]() This can be isolated to only the Windows Installer and the Windows Registry. If they change from one to the other the INSTALLER of that new version can change the registry key. Therefore as a first pass release you ONLY have to add the IsESR (or something like) to your common registry key during the installation. ![]() This issue is explicitly to solve a problem for MICROSOFT Windows Administrators who use System Center Configuration Manager and System Center Updates Publisher. Linux and Mac in Enterprises have ways where using a text file to determine ESR or not is not an issue. Who said anything about Mac? This is a Feature Request/Bug WINDOWS. What we Windows Administrators are asking you is nothing different but to add a way to detect ESR via the Registry as well, just like we can currently detect your VERSION and LANGUAGE via the registry. Mac and Linux don't have registries however you are providing version, and language and installation path in the Windows Registry. Which makes the ability for Enterprises to meet their compliance requirements more difficult.Īlso this is for all platforms, not just Windows 7, that should be updated. ESR was supposed to be for Enterprises what need extended support of a specific version, however you are limiting the ability of Enterprises that use a very popular product provided my Microsoft to detect, and update your ESR product. I am not sure why this is not addressed after two years. Right now reading a text file is not useful. If the application changes subscription channels for updates then the registry entry can be flipped from true to false or false to true by the application itself. It seems like a simple thing to have an IsESR in the registry placed by the installer. Or for consistency having it always exist going forward wouldn't hurt anything. This could be set to one only when an ESR is installed and not even exist if on standard releases. To be safer you could add a new DWORD value like "IsESR" with a 0 being false and 1 being true. If you changed this value's data to be "27.0esr (en-US)" then that would be great however for some people this could be a breaking change. HKLM\SOFTWARE\Mozilla\Mozilla Firefox\CurrentVersion If you add the term ESR someplace under the Mozilla Firefox registry key this would be extremely useful going forward.Ĭurrently the following Key's Value data is in the format of example would be "27.0 (en-US)" Why can't it be a registry addition that the installer adds for ESR installs.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |