How do I change my license on Sco Unix 3.2v4.2

I have an old legacy system running on 3.2v4.2 SCO Unix.  I recently had to reload it all after a disk crash, unfortunately I installed it with my 16-user license instead of my unlimited license.

Can anyone tell me the best way to change the license number without having to reinstall?

Secondly, is there a way to tell how many users a license handles?  I have a choice of 5, and I am not sure which one is the unlimited.

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SCO Unix 3.2v4.2 is very old (>15 years) now, consider update your OS to a current SCO release to get better support. (BTW, If I were you, I would change the OS to Solaris 10 x86 or Linux).

Now to get back to your question, from my memory you can run
to replace the license, to unlicense and then put the new license in. Make sure you have the new license paper on hand, put the new license number in straight after you unlicense it, don't exit from sysadmsh until you have put the new license in.

PS: I'm not 100% sure sysadmsh allow to to change the license (have not use it for long time). But I'm 100% sure if your are runing SCO 5.x you can run scoadmin to replace the license.

please read

MortimerCatAuthor Commented:
As I mentioned, this is a legacy system. The actual software will only run on this OS, unless I spend a lot of money on a new platform version, that will only be used for the rest of this year.  I know updating is the obvious answer so I wanted to explain my reasons for not doing that.

I cannot find a license section when I run sysadmsh.
try the "custom" command to see if it can help.

I have not use SCO 3.x for too long, can remember the exact command to use.

Have a nice holiday, cheers!

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Build an E-Commerce Site with Angular 5

Learn how to build an E-Commerce site with Angular 5, a JavaScript framework used by developers to build web, desktop, and mobile applications.

MortimerCatAuthor Commented:
Thanks for the suggestions so far.

custom looks like it will reinstall the entire operating system again. The question is how much will I have to reconfigure afterwards.

May be you can try to manually edit the license files to change the license key.

Please make a emernency boot FDs (Root and Boot disk), use "mkdev fd" command, incase you need to restore from
original settings. make a backup of the file(s) before you edit

Check the following files to see if you can modify the license key:
also: (for other package license details)
(or /etc/perms/packagename if you know it).

reboot the system after your modify the file. if you have problem after reboot, boot up from the emerency FD, mount
the filesystem and put the original file back.

Good luck, you needed!
See if there is a command named "brand".  Do a "man brand" and read through that if it comes up.  You might try going to SCO's Technical Article database and run a search there.  Just make sure you select "retired products" and "SCO 3.2/OpenServer3" products

Good Luck
MortimerCatAuthor Commented:
Thanks again for the further comments.

I found the files that were mentioned, but the license key appears to be in an encrypted format, so I cannot edit those.

brand does exist, however man gives the result "undocumented function - some useful function are not documented, such as brand".   I unsuccessfully searched for further information on the command.

My plan is still to run custom, reinstall Unix, and see what happens. Maybe this weekend.

If you can access SCO Technical Article Database you should take a look at TA#102626.  It may be of some help.

Try this link:

Good Luck
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.