You can transfer stand-alone perpetual licenses from one computer to another using several methods, depending on when you purchased your software. You can also transfer a license to a different owner. Note: Subscription software does not require license transfer for activation on more than one computer. To easily use your software on more than one computer, consider a.
Jul 18, 2007 - Portable License Utility. I went through the help on PLU, and everything seems to include exporting to another computer. I want to upgrade my. The Portable License Utility (PLU) is an application for Autodesk software versions 2009 and earlier used to check out a license from one stand-alone, software-locked Autodesk product and use that license on another computer that has the same product and installation type.
Follow standard procedures for your software. See your for information about software usage rights. Transfer License to Another Computer Reasons and requirements for using the License Transfer Utility (2010 and newer products only) How to use the Portable License Utility (2009 and older products) Transfer License Ownership Transferring license ownership from one person or organization to another generally requires permission from Autodesk. How to transfer ownership from one organization to another.
'The computer identification code contained in this transfer code or file does not match this computer's identification code. Import this license on the correct computer. ' Error code: 17.1.88 I exported the license to my laptop, and when I went to add to my laptop I received this error, and now when I try to add the license back to my desktop I receive the same error. It will not let me add it to either computer. I've re-verified several times the computer names and identification codes, and they match. Any suggestions?
Most likely it's an error of using the wrong transfer file, or forgetting which way you went last time. One of the two ways will work: desktop to laptop, or laptop to desktop. On the desktop, export by file to the laptop, creating a file named 'ToLaptop.plu'. On the laptop, try importing that file. If that fails, on the laptop export by file to the desktop, creating a file named 'ToDesktop.plu'. Import that file on the desktop.
This should work. In the import dialog, click 'Browse' to navigate to the file you're importing. When you come back to the dialog from selecting the file, all the fields in the bottom of the dialog are filled in from the transfer file itself: the license name, the target computer ID, everything, so you can validate it yourself before you import.Cy- wrote in message news:[email protected]. 'The computer identification code contained in this transfer code or file does not match this computer's identification code. Import this license on the correct computer. ' Error code: 17.1.88 I exported the license to my laptop, and when I went to add to my laptop I received this error, and now when I try to add the license back to my desktop I receive the same error.
It will not let me add it to either computer. I've re-verified several times the computer names and identification codes, and they match. Any suggestions? Yes, call Support. Did you browse to the import file, and verify the data in it as I suggested? Can you export by code, or is this the first time?
-Cy- wrote in message news:[email protected]. That is what I did.
And am now stuck. I exported the license to my laptop, verifying the numbers were typed in correctly. I then tried to import it to the laptop and received the above message. I then tried to import it back to my desktop thinking maybe something didn't work right with the export, and I get the same message.
So basically I'm locked out of both computers and cannot work anymore. At this point do I just call Autodesk? Cy, Your method worked perfectly!
I like the idea of using ToLaptop and ToDesktop, too. A visual nudge always helps knowing which way to go. Initiall in my situation, there was only one user going back and forth. I got into the mix updating the laptop for him, and did so by adding my machine to go back and forth with. By using the default name for the license, I think I screwed things up (and probably not paying attention when going back to my machine and selecting the other machine in the process) Would an additional failsafe for having more than one source machine on the target be to add ' to the endo of the license name? In other words 'ToLaptopmel', or do you still have to be careful in selecting the correct host machine when going back? Glad it helped!
Yes, adding anything else to the filename can't hurt; may as well take advantage of the long names. All you need to track is the target PC; the source PC is irrelevant. It also helps to make the computer name as descriptive as possible in the PLU's computer list.
The important decision is in selecting the right target computer, not necessarily in naming the output license transfer file! Once you select it and hit 'Export', that's the only place the license can go. A few more tips: o You can always re-create the export file by going back to the source PC and exporting again.
You can only choose the same target PC as before, but if the export file or code is lost or corrupted, you can recreate it. O Sometimes the transfer code is more reliable than the file. Files can get corrupted during transmission (you can zip them for extra safety). You can use the code after the first time you transfer a license. O On the source PC, if you export a license just before going home, but suddenly find you have to do One More Urgent Thing, you can usually still run the product for 24 hours using the 'emergency license'. This is automatically activated by simply launching the product again, after export. The 24-hour period begins the moment the product is launched.
Note: this is for emergencies, so you can't use it every day; it's allowed something like once a month.Cy- wrote in message news:[email protected]. Cy, Your method worked perfectly! I like the idea of using ToLaptop and ToDesktop, too. A visual nudge always helps knowing which way to go. Initiall in my situation, there was only one user going back and forth. I got into the mix updating the laptop for him, and did so by adding my machine to go back and forth with. By using the default name for the license, I think I screwed things up (and probably not paying attention when going back to my machine and selecting the other machine in the process) Would an additional failsafe for having more than one source machine on the target be to add ' to the endo of the license name?
In other words 'ToLaptopmel', or do you still have to be careful in selecting the correct host machine when going back?
Comments are closed.
|
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |