If this is still the case then you need a tool which can search the registry and report back the matching value. Thanksįrom what I remember about Autodesk products, the serial number can be accessed several ways, one being the registry e.g. I’m also not looking to pay thousands of dollars for software either.
I’ve tried a bunch already with not much luck. Autodesk’s own Asset Locator won’t do the job as you can’t customize it per domains or IP addresses. I am looking for is software that is client-less, that I can use for our customers (AUTODESK Software ONLY, i.e., Autocad, Inventor, Showcase, Vault, etc) to scan and audit to return serial numbers that can be exported out to an Excel file or similar to help them with their SAM programs. Looking for a SAM tool that will full Autodesk serial numbers, AAL doesn’t work well – I need a 3rd party tool Thank you to everyone that contributed and sorry for the upheaval in moving things around. Below are some edited highlights of some of the discussions from the old forum. To run the silent install: From the command line, run the install using this format: C:download folder ToadforOracle90Setup /S Note: The trailing S must be a capital letter.The ITAM Review forum now has a new home within the Virtual User Group. Running the Silent Install Once you have created your configuration file and saved it in the same folder as the executable, you can run the silent install. If performing an upgrade (UPGRADE=B) the LICENSEKEY and LICENSEMSG values will be ignored.
Upon initial launch, Toad will then copy this file locally.
KXPERT A - Install Knowledge Xpert for PL/SQL Blank - Skip installation of Knowledge Xpert SQL OPTIMIZER A - Install SQL Optimizer Blank - Skip installation of SQL Optimizer TOADSHORTCUT YES - Places a shortcut on the desktop Blank - Do not make a shortcut LICENSEKEY Your Quest-issued license key number LICENSEMSG Your Quest-issued license key message (site message) Note: If this is a Citrix install (install type 'D') the LICENSEKEY and LICENSEMSG values will be copied to a file called 'QSAuth11.key' in the subfolder 'ClientFiles' on the server.
0 kommentar(er)
