We have migrated our datacenter to AWS on the 17th of August, 2019. As a result of this move, we have changed the SSL certificates of https://csi7.secunia.com. The certificate chain is different and the CRL - Certificate revocation list's distribution points have changed as well with the new certificates.
If you require to whitelist the URLs explicitly on your proxy and firewall, then we recommend to whitelist below mentioned URLs to continue using SVM products.
New CRL Distribution Point URLs:
If you require explicit URLs then allow below URLs:
http://crl.rootca1.amazontrust.com http://crl.sca1b.amazontrust.com http://crl.rootg2.amazontrust.com http://s.ss2.us
Product URLs: (Not changing) https://csi7.secunia.com https://agent.csi7.secunia.com https://dl.csi7.secunia.com https://*.secunia.com
A complete list of system requirements can be found in the technical user guide at the Flexera Helpnet.
For further information, please contact SVM Support Center at Flexera.
Welcome to Flexera – we’re glad you joined us. With the implementation of a new product comes new processes and tools. Here is a rundown of our recommended practices to ensure your team members have what they need, when they need it.
Get set-up for success
Determine who from your company would benefit from our online training, accessing cases, participating in forums and downloading products.
Invite these employees to join the community. Include the account ID and product ID in your message so they get the correct level of access.
Document who is your product and license center administrator and who are your general users.
If you have a team of employees submitting cases, we recommend you agree upon any standards you have. For instance, some companies will detail what to include in the case, how to title cases, how quickly to respond to tickets and what emails to add as case watchers. Be sure to document the decision.
Train employees: To ensure your team is taking advantage of all offerings, have each member view these brief training items:
Using the case portal
How to submit a case
How to find the case portal
Best practices on submitting a case
How to filter a case by status
Adding a case watcher
How to view all cases from your company
How to access the Product and License Center
Subscribe for updates
We post our release notes for products. How to subscribe.
Access training via our Learning Center (If they don’t see the options you do, they will need to connect their account to your organization— have them follow the above step.)
Grant Access: Direct employees to request access to the Product and License Center. The PLC admin will receive a notification and need to approve access.
Aim to review your access list once a year. This additional step helps you manage access. If you have employees who no longer need access or who have left the company, submit a case.
Have them join the community. If you don’t have your account & product IDs handy, you can submit a support case asking that the user be added to your account. (Connecting your account to your organization or the view the video How to update your account)
Have them follow the training steps outlined above.
We’ll periodically check with you to ensure we have the right information, but it works best when customers make this part of their onboarding and offboarding procedure.
To deactivate a user, please submit a case (or email firstname.lastname@example.org) and provide the email, name and last date of employment for the individual. Our team will take care of the rest.
A note about the PLC admins – every account must have a PLC admin. If your PLC administrator is leaving your company, please include the name and email of the new staffer who will serve as the PLC administrator. We recommend new PLC admins read this brief knowledge base article on using the tool.
Have additional best practices you’ve seen work for your company? Please share them here.
You may find you need help beyond community forums, our documentation and learning opportunities. Read on for case best practices.
Submitting a detailed case helps everyone act more quickly toward a resolution. So be as thorough as possible when filling out case information.
Our support cases have five key areas to complete. An optional sixth area is detailed at the end.
Case Summary: This serves as your support case title and will appear in your email subject lines. Write titles detailing the action needed. This helps narrow the scope, so our support team can quickly triage and identify tickets. For instance, “Adding billing content for AWS clients” versus, “Billing content issues.”
Description: We recommend each description includes:
What: What is specifically happening within the system. Please try to be as specific as possible with the exact area of the system, links you've clicked, etc.
Who: The specific user or users first and last name who have reported this problem and/or who you have noticed this problem affecting.
When: When the request/problem happens. For instance, did it start at a certain time of day or geographic location? What was being done prior to it occurring?
How: Detail the steps to reproduce the error. When possible, include attachment videos or screenshots of the journey.
Why: What is the expected outcome versus what actually happens.
Product: Please select the appropriate product to quickly route your case.
Version: The drop-down menu will adjust based on the product you select. Please choose the version to quickly route the case.
Severity levels: There are 4 severity levels used to classify a case:
Severity 1 – Critical: Production use of the cloud software is stopped or so severely impacted that authorized end users cannot reasonably use it. Flexera will work continuously to resolve the support request until it is closed. Severity Level 1 issues must be reported by telephone.
Severity 2 – High: Major cloud software documented features are unavailable with no workaround. Use of the cloud software can continue; however, productivity is significantly decreased. Flexera will work continuously to resolve the support request until it is closed. Severity Level 2 issues must be reported by telephone.
Severity 3 – Medium: Major cloud software documented features are unavailable, but a workaround is available, or less significant cloud software documented features are unavailable with no reasonable workaround.
Severity 4 – Low: Authorized end-user requests information about the cloud software or an enhancement to the existing cloud software specifications. Use of the cloud software is available without being materially and adversely impeded.
Optional: end customer: Our partners use this field to detail their clients affected by the case issue.
BONUS: Case Watchers
After you create your case, you can add case watchers to the field. Case watchers receive email updates on case progress so adding key staff help keep your team apprised of progress. Details on adding case watchers are here.
If you run into any issues or want additional information, let us know in the comments.
After applying the 5.5.20 patch, the User Console UI is not accessible through IE/Edge browser.
There is no error message on the User Interface, but it appears as though the user was logged in for just a second and the page refreshed back again showing the same Login prompt.
This is caused by a security enhancement in 5.5.20 to store the JSESSIONID in Cookies instead.
This change will require the browser to support Cookies.
Engineering is working on a permanent solution.
1. Login via any browsers other than IE or Edge. Tested with Chrome and it works fine.
2. Using HTTPS protocol instead of HTTP.
IBM’s x86 Server Business has been acquired by Lenovo.
Please refer to the following link: https://news.lenovo.com/pressroom/press-releases/lenovo-set-to-close-acquisition-ibms-x86-server-business/
Technopedia has made these changes accordingly. Related products and mappings under IBM (manufacturer ID: 6517) have been migrated to Lenovo Group (manufacturer ID: 7053).
IBM will be retaining its System z mainframes, Power Systems, Storage Systems, Power-based Flex servers, PureApplication and PureData appliances. Therefore IBM (manufacturer ID: 6517) will stay active.
We have compiled a complete list of the hardware products displaying lineage and relationships affected by this acquisition. Please refer to the list attached to this article.
We have an expert team of professionals available to answer questions and to assist you with technical issues with Flexera products. To contact Support for technical issues, please use our online system to log a case. In addition to our online submission system, you can contact Support using the following information.
+1 630-332-5957 (toll) +1 877-279-3781 (toll-free)
+44 1925 944368 (toll) +44 800 047 8643 (toll-free)
+61 1800 560 584
The 5.5.* Normalize Mapping cube, Unmatched Package report, and Unmatched Files report are disabled by default. This is due to the MatchAddremove and MatchExe configuration settings being disabled in order to improve performance. Please see below if you want to re-enable them.
To enable these, you need to change the following parameters and make them true in Norm.configuration.config (This file can be found under ..\BDNA\Data Platform\Conf)
By default the above values are set to false.
After you change the parameters, you need to rerun the Normalize tasks and then you should see the Normalize Mapping cube with both the Unmatched Package and Unmatched Files report showing up.
If you need to force a full Technopedia catalog sync please follow the steps below:
In the BDNA database run the following:
update BDNA.dbo.TECHNOPEDIA_VERSIONS set PKG_ID=-1 where '_src' = 'TECHNOPEDIA';
The next time you run a Technopedia catalog sync the full catalog will be downloaded and synced with your system.
Please note as this is a full catalog sync this will take some time to complete.
Download the Spider 6.3 Technical Reference Manual here.
Table of Contents
1 General 1.1 Typographical conventions 1.2 Help 1.2.1 Support 1.2.2 Documentation 1.2.3 Training
2 Introduction 2.1 Chronological order for new installations
3 Spider 3.1 System requirements 3.1.1 Application server 3.1.2 Database - Microsoft SQL Server 3.1.3 Indexing - OneSearch 3.1.4 Hardware requirements 3.1.5 Clients / Browser 3.1.6 Implementation system 3.1.7 Permission requirements 3.1.8 Hardware-Scaling
3.2 Installation 3.2.1 Software to be installed in advance 3.2.2 Start of the installation 3.2.3 License agreement 3.2.4 New installation or update 3.2.5 License file 3.2.6 Installation directory 3.2.7 Start menu item 3.2.8 Database server 3.2.9 Index proxy server 3.2.10 Web Logins 3.2.11 Database names 3.2.12 Language and format settings 3.2.13 SMTP settings 3.2.14 Administration account 3.2.15 IIS configuration 3.2.16 Transfer directory 3.2.17 Installation 3.2.18 Activate the license
3.3 Update 3.3.1 Start of the update 3.3.2 Update 3.3.3 Selection of the Instance 3.3.4 Database server 3.3.5 Index proxy server 3.3.6 Select updates 3.3.7 Installation
3.4 Advanced configuration 3.4.1 Operation with domain account 3.4.2 Subsequent setup of the index proxy 3.4.3 Conversion to SSL operation 3.4.4 HTTP(S) Redirect 3.4.5 Setup of Active Directory login 3.4.6 Info page - support.config 3.4.7 Available languages - culture.config 3.4.8 Settings in the Config table
3.5 Troubleshooting 3.5.1 Display of advanced error messages
3.6 Encryption of the configuration
3.7 Additional information 3.7.1 Error handling system
4 Software catalog 4.1 System requirements 4.2 Import of the catalog 4.2.1 Start of the installation 4.2.2 Database server 4.2.3 Select the database 4.2.4 License file 4.2.5 Summary 4.2.6 Installation
5 Recognition 5.1 System requirements 5.1.1 Application server 5.1.2 Database server
5.2 Installation 5.2.1 Start of the installation 5.2.2 License agreement 5.2.3 License file 5.2.4 Installation directory 5.2.5 Database server . 5.2.6 Database & Data Receiver 5.2.7 SQL login, service user 5.2.8 Summary 5.2.9 Installation
5.3 Update 5.3.1 Start of the update 5.3.2 License agreement 5.3.3 License file 5.3.4 Installation directory 5.3.5 Database server 5.3.6 Summary 5.3.7 Installation
5.4 Advanced configuration 5.4.1 Data Receiver 5.4.2 EDC Monitor 5.4.3 Operation with domain account
6 Log files 6.1 Brainware.log 6.2 Smart-Inspect log files (*.sil)
Download the Spider 6.3 User Manual here.
Table of Contents
What is new in 6.3
What is new in 6.2
Active Directory Login
Structure of the home page
Spider Asset home page
Spider Licence home page
Spider COntract home page
OneSearch: Indexed Search
Search on the object level
The search results
Save a search (My queries)
IT Management with Spider Asset
Glossary of terms
Software/Software shopping cart
Assign legal entity
Manage software of the asset
Create function unites
Assign legal entity
Edit function units
Functions at the asset
Result overview and settings
Status of the SDC connections
Manual software management
Software/Software shopping cart
Active Directory groups based Software assignments
License metrics procedures (LMP)
Software meterings for the Software object
Detailed metering evaluation
Software metering for the Asset object
Asset master data
License management with Spider Licence
Glossary of terms
Assign legal entity
The license allocation ribbon
Assign legal entity
The Products ribbon
The Licences ribbon
Maintenance wizard for updating licenses
Subdividing a license
Article change wizard
Selection of the products
Selection of manufacturers
Selection of the language
The Product versions ribbon
The Maintenance ribbon
Create product versions
Edit product versions
The Licenses ribbon
Software product version assignments
Product version change wizard
Oracle inventory data
Create product groupings
Edit product groupings
Manage product assignments
Product version compliance
Product grouping compliance
Contract Management with Spider Contract
Glossary of terms
Contractual parties assignment
Assign legal entity
Contract structure / Structure view
Contractual parties assignment
Create contractual parties
Edit contractual parties
Create reference objects
Edit/delete reference objects
Contract - Reference object assignment
Employee Change Wizard
Edit the document
Full text search
Cost center history
Automated E-mail reports
Show and filter reports
Loading a search query
The search result
Settings ribbon - Customize search queries
Creating new search queries
Saving search queries
Publish and authorize search queries
Cost centers/Cost center master
Edit cost centers
Create cost centers
Edit legal entities
Create legal entites
Structure of legal entities
Authorize legal entities
Move legal entities
Search in selection lists
Edit entries for the selection list
Create entries for the selection list
Assign Active Directory
Edit password rules
Test cases ribbon
Create password rules
Edit test cases
Create test case
Test password rules
Edit user roles
Active Directory groups ribbon
This article provides information regarding how to connect to Workspace ONE distribution system from Application Manager.
While trying to configure the workspace ONE distribution system in Application Manager one can encounter with an error message Unable to establish a connection with Workspace ONE server. For more information, see the log. Connection to <url of the Workspace one distribution system> Failed: A required process for this task failed
Valid Site code is not provided / if it is empty in the distribution plugin configuration window, the required process for this task failed error will be logged.
Steps to Reproduce:
Provide a valid Site code which is nothing but tenant id of the Workspace one along with the valid user credentials to resolve the connectivity issues.
This article provides information regarding generic questions in the activated version of AdminStudio using Application Catalogs like How many folders can be created in the application catalog, what is the maximum number of packages/applications that can be added to each folder if multiple Catalogs are created, how do you delete a Catalog, etc.
Steps to Reproduce
Q1. How many folders can be created in the catalog?
If it is only creating independent folders, there are no limitations as such. But if a hierarchical folder structure needs to be created, which is same as the windows default supported file path limitations (Maximum path length should not exceed 260 characters based on the Operating System on which AdminStudio is Installed)
Q2. What is the maximum number of packages/applications that can be added to each folder?
As long as the database has enough space there are no restrictions on the number of packages or applications which can be imported into the application catalog.
Q3. If multiple Catalogs are created, how do you delete a Catalogue? (ie: Is there anywhere in the AS UI to delete a Catalogue? Or can this only be done by an SQL Server DBA?)
No there is no UI option available currently to delete the catalog from Application Manager. One has to connect to the database server and delete the catalog by using SQL server management Studio or by running SQL scripts to delete the databases over there. This only is done by a SQL Server DBA.
AdminStudio Evaluation Restrictions:
This article describes how to activate verbose logging for the Software Vulnerability Manager 2019 Daemon service (installs as "Flexera Corporate Software Inspector Daemon"). This can be very helpful to debug technical problems with "System Center Inventory Import" schedule executions, or any other activity that is being delegated and therefore executed by the Daemon service.
Logging is useful for troubleshooting purposes. A log file can reveal if the Flexera Daemon service is working correctly and performing all scheduled tasks at regular intervals. By modifying and/or creating registry keys it is possible to enable logging for the Flexera Daemon service.
To enable logging of the Daemon service, follow the steps outlined below:
1) Open Regedit with elevated administrative account.
2) Browse to "HKLM\SYSTEM\CurrentControlSet\Services\Flexera Corporate Software Inspector Daemon\".
3) Modify the ImagePath value, and append logging arguments -d "C:\<folder>\<logfile.txt>" -v -v -v
For instance: "C:\Program Files\Flexera Software\Corporate Software Inspector Daemon\daemon.exe" --service-launch -d "C:\Logs\MyDaemonLog.txt" -v -v -v
4) Restart the Flexera Corporate Software Inspector Daemon service.
Restarting the service should work out-of-the-box and it should complete without errors. If you encounter an error, review the ImagePath string and make sure you haven't missed quotes, etc. Once the service restarted without errors, the log file you specified in the ImagePath should be created. You will need to leave the Daemon for a few hours in order to collect data from its own executions.
To enable enhanced logging for the SVM Daemon service, take the following steps:
1) Open Regedit.
2) Navigate to "HKCU\Software\Secunia\Daemon".
3) Create the following registry keys (if not present already):
a) Create String Value named LogFile and enter the path of the log file, e.g. C:\Enhanced Daemon Log\Daemon.log.
b) Create DWORD (32 bit) Value named LogFileMax and enter the maximum size of the log file, e.g. 8000000 (8 MB).
c) Create DWORD (32 bit) Value named Logging and enter the level of logging 1-4, recommended level is 3.
4) Restart the Flexera Daemon service.
Possible reasons of why the Flexera SVM Daemon service might fail include:
The Run-as-User account for the Flexera Daemon service does not have the appropriate permissions to connect to the SCCM database via ODBC (SQL permissions; Select and Connect).
The Secunia Daemon service is unable to fetch the configuration script from the back-end server due to incorrect CSI User authentication (HTTP 400 errors).
The Proxy information provided during Daemon service installation is currently being incorrect.
This article provides a list mapping the external App Portal version names to the version numbers.
This article provides a list mapping the external App Portal version names to the version numbers
Product Internal Version
Customers receive an error " Specific user account has no candidate group for the Management Group" when configuring User Console v5.5.13
This issue has been reported in the following scenario:
1)LDAP Authentication is used.
2)Customer license key does not contain Analyze.
Fix : This issue has been fixed in v 5.5.17
For customers performing a fresh v 5.5.13 install:
Download and unzip the attachment: BDNA -31044 Patch for 5.5.13.zip
Install 5.5.13 User Console
Backup and replace the Configure User Console.exe in the User Console/Bin directory with the one provided in the attached zip.
Run User Console Config Wizard.
In order to have access to our Support Portal, Product and License Center and customer-only Learning Center courses, customers must have their individual community accounts tied to their organization. There are two ways to do this connection:
1. At the time of registration
You can link to your individual community with your account by adding your account ID and product ID during registration. These sources of data may be found on your order confirmation emails.
Sample registration screen
If you registered for our community and didn't have your account and order IDs on hand, or had an account prior to becoming a customer, you may still add your organization. Please email email@example.com and include your full name and organization name and request to connect your community account with your organization.
How do I tell what organization I am tied to?
Sign in to the community
Click on your avatar (upper right-hand corner)
Select My Account. The organization is listed at the bottom of the form.
Sample account screen
Please contact firstname.lastname@example.org for instructions.
When using LDAP authentication you may experience the below ("Connection Reset") error when attempting to log in to the User Console:
This issue is caused by using HTTPS binding in IIS with the 'Require Server Name Indication' option selected.
To resolve this issue:
Close the User Console and launch IIS
Go to ‘Sites’ then click on the site being used for Data Platform
Then click on ‘Bindings’
Select the ‘HTTPS’ binding and click ‘Edit’
Uncheck the option for ‘Require Server Name Indication’
Click ‘OK’ then ‘Close’
Launch the User Console and attempt login
If your account is tied to a company with a maintenance contract, you have permission to view all cases your company has submitted.
To see all cases:
Click on "Get Support"
Select and Click on "My Cases"
Click on the "Filter" button
Check the "All Company Cases" checkbox
Click on the "Apply Filters >" button