AdminStudio 2021 R2 is released today with several significant enhancements to some of the most impactful features. Package Backlog Management Enhancements: The Package Backlog Management feature, introduced in AdminStudio 2021, helps you manage your packaging requests and keep you up with the latest software updates. While you could leverage AdminStudio’s PowerShell Cmdlets and REST APIs to add several packaging requests at once to your backlog, with the new Add button in the Backlog tab, you can now add a single package request directly in the user interface. This should help you handle any ad-hoc or urgent package requests which come your way outside of the usual process. There are also new options added in the Backlog tab to edit a package request and customize a package directly in the Backlog tab. Automate Package Customization: The Package Automation feature, powered by the Package Feed Module, enables you to automate your packaging process by pre-configuring a set of actions to be automatically performed on a package when a new version of a subscribed application is made available in the Package Feed Module. To those sets of pre-configurable actions, AdminStudio 2021 R2 adds a new option to automatically create a transform file to the Import action. By checking this new option, the various options you selected in the customization wizard for a given version of a package will be retained and applied to generate a transform file for a new version of the package when made available in the Package Feed Module, all automatically.   Publish Intunewin (Win32) packages to Microsoft Intune: One of the common requests we heard from many of our customers was for AdminStudio to support the publishing of Intunewin packages – an Intune native package format for Win32 apps, to Microsoft Intune. At present, you can convert traditional package formats – MSI/EXE to the .intunewin package format, with AdminStudio 2021 R2, you can take a step forward and publish the .intunewin package formats to Microsoft Intune. Compatible with Windows 11: Today is also the release date for Microsoft’s new Operating System – Window 11. AdminStudio 2021 R2 is ready for the new Windows 11. AdminStudio 2021 R2 is installed, and all the major functionalities are successfully tested on Windows 11. Application compatibility testing of your packages against Windows 11 will very soon be supported in AdminStudio. Microsoft Updates: Our goal to continuously keep updating AdminStudio to support the latest versions of Windows 10/11 and Configuration Manager remains solid. AdminStudio 2021 R2 supports the latest Windows 10 21H1 for application compatibility testing and ConfigMgr 2107 for publishing the apps from the AdminStudio catalog.   AdminStudio 2021 R2 is available for download in Product and License Center. For more details please refer to the release notes here. To keep yourself updated with AdminStudio product releases and updates, please subscribe to this release blog!   ... View more

The monthly report for vulnerability insights for September 2021 is here. In September, a total of 461 advisories were reported by the Secunia Research Team for 307 unique products across 72 unique vendors. There were 14 Extremely Critical Vulnerabilities exposed through these advisories. Please see the attached report for detailed insights. ... View more

Summary When Software Vulnerability Manager (SVM) scans a device, which has Apache Tomcat webserver installed, the scan results do not show Tomcat to be installed on that device. Diagnosis Software Vulnerability Manager looks for exe, dll and ocx binary file extensions while scanning a device. The metadata in the PE header of these files is used to tie them back to their respective product and version. Apache Tomcat has two installer formats for Windows platform – ZIP and EXE. Upon installing the ZIP format installer on a device, it is seen that there are no exe, dll or ocx files in the install directory. It clearly appears that the ZIP format of the installer does not include any of the binary file formats which SVM can recognize therefore SVM fails to identify Tomcat during scanning a device which has ZIP format installed. The EXE format of the installer installs two .exe files in the install directory. However, the Product Version obtained from the PE header of these files does not match the actual version of Tomcat installed on the device, therefore SVM does not know which version of the product these files belong to and so cannot identify a version of Tomcat installed. As a result, Tomcat will not appear in SVM scan results. For instance: Tomcat.exe and Tomcat10w.exe are the two binary files installed by Tomcat version 10.0.5.0. However, the Product Version seen in the PE header of these two files is 1.2.4.0.   Conclusion The PE header meta data of the binary files installed by any product on a device plays a very crucial role in identifying the correct product name and the version installed. Tomcat’s either missing binary files, or (when present) offers unreliable identification data resulting in SVM’s failure to correctly identify the presence of any Tomcat versions on a device. If interested, we encourage customers to reach out to the creators of Apache Tomcat to fix the version information in binary files to align with the product version installed on a device. Currently there no work around available in SVM to address this deficiency. ... View more