Restriction by operating system change of behavior
When applying a restriction by operating system, only operating systems that are locally installed on a device will now be considered when applying the restriction. As a result, consumption numbers may reduce.
Prior to this change, for some devices, FlexNet Manager Suite was reporting software running on remote machines/virtualizations as installed applications on devices used to connect to the remote machine. For example, a common scenario would have been Microsoft Windows Server being reported as an installed application on any Microsoft Windows 10 device which was used to remotely access a VDI machine running Microsoft Windows Server. This effectively meant that a device running Microsoft Windows 10, with the Windows Server restriction by operating system setting applied, was able to consume from a Microsoft Windows Server license. This behavior is no longer the case. Now, FlexNet Manager Suite will only consider the local installation of Windows 10. Therefore, the Windows Server restriction will prevent the device from consuming and, as a result, consumption numbers (notably for Microsoft Server licenses) may reduce.
- Microsoft Server Processor
- Microsoft Server Core
- Microsoft Server/Management Core
- Microsoft SCCM Client Device
- Microsoft SCCM Client User.
- Non Windows Server
- Windows desktop
- Windows Server.
In all cases, devices will need a local installation of the operating system type specified in the restriction in order to be allowed to consume from the license. Consumption numbers may reduce if devices that previously consumed from that license have an operating system different to what is specified in the restriction.
For more information on restriction controls in FlexNet Manager Suite, see Restrictions Tab in the Online Help.
FlexNet Manager Suite (On-Premises)
2024 R1