these all are valid upto v4.1 , aastra has changed licensing procedures in v5....we have to to execute some scripts then it will show the hardware id on which lic should be ordered ( i read these things in cpi) ... but i dont knw wat is that script and where to execute....
Here you see a copy from the aastra-document:
- License is tied to Server 1 as before
- A new way of license binding has been implemented
- Creation of the HW fingerprint is different with MX ONE 5.0 compared to former versions
- ”license_status –s” shows different HW IDs for 5.0 compared to former Versions
- No problems will appear with new installations
- A new fingerprint has to be taken before upgrade to 5.0
1) Upload the file Hardware ID to the server which is to become the Server 1 from a MX-ONE 5.0 System e g. to /home/eri_sn_admin
2) Change the file property to ‘execution rights’ for the relevant user
3) Execute the file such as ./HardwareID
4) Note the shown Hardware ID and use this ID for ordering a MX-ONE 5.0 license
5) Further license handling is done as before
6) Once the system is upgraded to MX-ONE 5.0 the result of ./HardwareID and “license_status –p”will show the same result again.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.