A schedule has been created but no reports are running Reports have not been added to the schedule. ... <div> </div> ... <ol><li>If necessary, create the schedule. ... For more information, see “Creating a Schedule ” section of the User Guide</li><li>On the Schedule tab, on the schedule card, click Schedule Report</li><li>Select the reports you want scheduled under this particular schedule</li><li>Click OK.
How to merge license files together, or request a new or updated license, for a Quest product you are currently licensed for. ... If you have license files which need to be merged together or you require a new updated license for a product that you are currently licensed for, please fill out the form on the following page to submit a request to the Licensing Team:
Does ER provides a report or a log to view when a discovery job was last modified and by whom? ... The Configuration Manager does not display any audit information on the modification of discoveries but we do log activity to the event log.
How to create a new database to replace the existing one in case of database corruption? <strong>IMPORTANT:</strong><br>You must RDP or login to your Enterprise Reporter Server using an account member of Domain Admins AD group and is a SYSADMIN on the target SQL Server.
Does ER hold any capability to capture password hash synchronization (PHS) data? ... Enterprise Reporter does not report on PHS specifically but it does collect on-premises sync status and last sync time.
When running AD discovery to collect data from other domains you may see an error like "The supplied credential is invalid”.<br><br>The service account is member of the administrator group on the target domains.
When trying to open Configuration Manager you may get the following error:<br><br>The Enterprise Reporter Server cannot connect to the database. ... Make sure it has an access to the Enterprise Reporter Database.
When creating a discovery for a nontrusted domain using alternate credentials, at the scope definition is not possible to reach the domain. ... Try to connect the domain using ADSIEdit or LDP.exe using the alternate credentials used on Enterpriser Reporter.
We have tested upgrading to the latest Microsoft SQL Server, ODBC and OLE DB Driver for SQL Server in a server running Enterprise Reporter version 3.5.1 and this did not affected functionality and all discoveries and reports worked fine afterwards.
ER Node deployments fails with the error message "The Node account should be a member of the group Reporter_Discovery_Nodes" even when the account is already a member of the group. ... The credentials of the account used to deploy the node are not being decrypted properly or they are corrupted.
All licenses requests from merge licensing to new license file.
This solution outlines the command and instructions to silently perform a node installation. ... A quiet node installation is possible. ... However, the Node cannot be associated with a Cluster when it is installed via command line, or when it is installed manually on the remote location.
The ER Server establishes unencrypted SQL connections.<br>We need to enforce TLS for SQL from the ER Server without having to explicitly enforce TLS on the SQL Server.<br>We have not explicitly installed the public keys of the certificates on our ER server, as we operate an Enterprise PKI and the ER server trusts the root certificate of the SQL certificates.
The Node logs show the following error: "Your app has been throttled by AAD due to too many requests. ... To avoid this, cache your tokens. ... See https://aka.ms/msal-net-throttling." ... Throttling issues on the Microsoft side To mitigate throttling issues for all our cloud discoveries, you can provide multiple credentials for the discovery.
This solution outlines the commands to silently install the Configuration Manager and Report Manager. ... <p>The below examples are for version 3.2.2.11000 x64 but should work for other versions too, just change the MSI file name:</p>
When creating a Registry discovery, the Add scope using a query option is not available.
Having an issue with Enterprise Reporter delivering reports with old data even though the status for the cluster is showing as finished without failures in Configuration Manager. ... Verify the status of the Discovery Node linked to the cluster that execute the Active Directory discovery.
Either “Sign In” if you have already registered in the portal, or register. ... Next, enter the product name in the “Enter your product to find support” section, select the product and click the "Go" button.
Is there a way to exclude this information? ... IP address is basic information that is collected from a server or computer and can not be excluded from Computer Discovery. ... However, there is an option to modify the Computer Information report for not showing IP address data.<br><br>1- Copy the Computer Information to your "My Reports".<br>2- Select the report, then click "Edit".<br><br><img id="Picture_x0020_1" border="0" height="439" src="https://questsoftware.lightning.force.com/sfc/servlet.shepherd/version/download/0686R00000iQf7J?asPdf=false&operationContext=CHATTER" style="width: 702px;height: 393px;" width="783"></img><br><br>3- Click &
Is it possible to run a report to find duplicate files on a server or share? ... There is a report in the builtin library on Report Manager under the NTFS > Files folder called "Duplicate File Details" which should show duplicate files data:
How to install a node manually when installation from the console fails or not possible? ... alt="image.png" src="https://questsoftware.file.force.com/servlet/rtaImage?eid=ka06R000000BySI&feoid=00N6R00000J0qH8&refid=0EM6R000005XrBs"></img><br><br>4- The installation wizard should pop up.
Reporter node service stops suddenly, status in Configuration Manager stuck at "initializing" when adding it to cluster. ... The service account for the Reporter Node Service on the node computer is not a member of the local administrators group.
Azure Active Directory Privileged Roles for User report only displays the roles assigned to a user during the discovery execution and it is not collecting additional roles that can be dynamically assigned to users.
All discoveries for two clusters are stuck on Resolution task with status Dispatching. ... The same credentials that are failing on this cluster discovery is working on several other clusters. ... The SQL server authentication account used on the node is a windows authentication account.
Reporter_Discovery_Nodes ... Solution ... This can be done in two ways: ... As part of the Update process ... Follow the wizard until prompted for the Group Names ... By running the Database Wizard
© 2025 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center