I have been using Plant 3D with P&ID for several weeks. I now need to be able to work from home a few days a week. How would I be able to barrow the license?
Thanks,
Mark
type about in the command line
it should pop up the license info box and there should a borrow license button in that box
DarrenP
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
ThanksDarren.
Nowanew problem. I have attempted to installthe software on my PC at home. It gets to the end of installing & comes up saying failed.?
It doesn't give me a reason why. I have tried it entering the Ser # & Key and also as a 30 day trial. They both give me the same result. I need this at home because I will be working from home a few days a week.
Please help.
Thanks,
Mark
You cannot install a trial license and borrow a network license. You will need to install it as a network version with access to your NLM server first. Then you can borrow the license and take it home.
or if your on subscription you can request a home use license
DarrenP
Did you find this post helpful? Feel free to Like this post.
Did your question get successfully answered? Then click on the ACCEPT SOLUTION button.
So would I need to uninstall & re-install as a network installation?
I thought I could use the License Transfer Utility?
I thought this option was for those without a network install or without a network all together.
We have no network at out office. It's only my workstation that hase the Autodesk software on it.
I really need to get this resolved though.
True Autodesk rep?
Please get me an answer.
Thank you,
Mark
Your terminology led us to believe you had a network licensed copy. If you are using stand-alone, you can use the LTU, but you should instead ask for a home use license in this case.
Why don"t the error messages say what they really are? Wouldn"t that make all this a lot simpler? When I try to pull a license, it would be nice if it said "there aren"t any available " instead of some nonsesne about the server. I find this true with most of the error messages throughout the AD line.