Specops Command

3.8.19148.1

Fixed Issues

• Failed to enumerate domains in multi-domain scenarios. This caused the Admin Tool to crash.

Released June 13, 2019

3.7.20705.1

New Features

• Support for clustered SQL server improved in Setup Assistant.
• Improved the way computer names are resolved to work with Windows 8 and Windows Server 2012.

Fixed Issues

• UserMode directory used for Tracing isn’t created if it doesn’t exist.
• The CSE logs error related to loading multiple PowerShell snap-ins.
• A full sync of Inventory removed previously reported information for Command.
• The processor target uses Current clock speed instead of Maximum clock speed.
• Error when running Specops Reporting on a Domain Controller.
• Error when a single cell contains large amounts of text and is exported to PDF.
• Live View values does not properly update when running over time.
• IFP messages are not properly processed on the Server when multiple threads are used on the IFP server.
• Last logged on user fails depending on order of installation for Specops Command .
• Server needs a dependency to the Windows Server Service in slow computers.
• NumberOfWorkerThreads registry key missing during server installation.

3.5.9153.27366

Fixed Issues

• Cmdlet log files ends up in the wrong directory: When enabling tracing for the cmdlets, the trace file ended up in C:\Specopssoft\. The Log files now are now written to the Specopssoft directory under the local application directory in the user’s profile.
• When using Prompt Filters in Specops reporting, very long strings are capped: When viewing a Specops Reporting report that contains a Prompt filter that contains long values in the drop down list, the last part is cut off. This meant similar long text that only differed in the end were impossible to differentiate. This is now changed so that the full text of any size will be displayed.
• The path to Program Files and Common Files are not localized for the Admin Tools: The Setup did not localize the path where both common Specops Software files and specific files are being stored, resulting in problems on all non-English computers. This is now changed and uses the correct paths on all languages.
• When Active Directory contains thousands of objects with explicit Access Deny for the user running the Setup Assistant, enumerating GPOs time out: In the step where the path to the setup files for PowerShell is set, all Group Policies in the domain are being enumerated, but when there are a massive number of objects in AD that are explicitly denied to the user, the time for the enumeration is too long and the operation times out. The search is now changed and the issue removed.
• Execution identity for user script not elevated: Even if the option to run a Script for the users with the System Credentials was set, the user’s personal settings were used. This is now fixed and the System credentials are used for all scripts that are configured to run with elevated privileges.