Question
What are the best practices for the CLS instances which are no longer in use by any client but still present in FlexNet Operations (FNO).
Answer
One can follow either of below for the redundant CLS instances:
1) Obsolete the CLS instance can be done through webservices (ManageDeviceService, obsoleteHostRequest call) or UI
- The server id will be renamed with suffix to original ID(ex: WS2UFY6GDXXX-OBSOLETE-20230618213543).
- This will remove the licenses mapped and return the count back to the line item pool
- You can still see the history of the server in FNO UI.
- Details of the linked served devices in FNO UI until it makes call to new CLS.
- Cannot call CLS APIs for the obsoleted server as it gets deleted from the CLS database.
2) Deleting the Server(CLS) has to be done using webservices. (ManageDeviceService, deleteDeviceRequest call)
- This will remove the licenses mapped and return the count back to the line item pool.
- You cannot see the previous transaction history nor the served device details. The CLS and its related records are deleted from FNO and CLS database.
- Unless there is a need to retain the unused CLS instances details and it's history, we recommend to delete the instance which keeps the database less bulky.
Was this helpful?
Related Articles
Linux-based Docker Host support to run FNO onprem 6Number of Views Best Practices for Upgrading Commander® 392Number of Views Best Practice: Operating Within the Connection Threshold for Hosted CLS Instances 6Number of Views Error "Features are not available due to a rule rejection" While Checking Out a License from a Cloud License Server (CLS) 10Number of Views Error! "LFS Feature mixes concurrent and metered models" reported at LLS or CLS 7Number of Views
Revenera Assistant - Beta
Online
Hi, I am Reva - Ask me anything.
Updates
No new updates
Chat
Home
Updates
/**/
Thanks for the feedback!
Your feedback has been saved.Rate this response:
1
2
3
4
5
Add Additional feedback ( Optional )
0/240
English
English
Language changed successfully
Something went wrong
Email sent successfully
Something went wrong
Case create successfully
Are you sure you want to cancel
the case creation?
Please select a product to submit the case.
Please select a product version to submit the case.
0/255
Upload Attachment
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to cancel the case creation?
Case closed successfully
File Upload
Maximum file size allowed is 3 MB.
File type not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
File Upload
Maximum file
size allowed is 3 MB.
File type
not supported.
Supported file types:
Documents (.txt, .doc, .docx, .pdf), Images (.jpg, .png), Comma Separated Files
(.csv) Speadsheets (.xlsx, .xls)
© 2026 Flexera Software. All Rights Reserved.
Case id: 00001065
Activity: Status change: 2 hours ago