Installation & Licensing
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Problems using AutoCad LT 2012 on VmWare Virtual-De sktop Infrastruc ture
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Hello,
we are a small customer from Germany and we tried to use Auto CAD LT 2012 on our VmWare Virtual-Desktop Infrastructure.
We tried to build an App of AutoCad LT 2012 with VmWare ThinApp 4.7.0
Building the App was no Problem, but after the installation has finished, it's impossible that AutoCad works.
After starting the application, it suspended by checking the license.
We bought a one user-license for that product.
I hope you have some Ideas to solve that problem.
Solved! Go to Solution.
Re: Problems using AutoCad LT 2012 on VmWare Virtual-De sktop Infrastruc ture
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
While you wait you may want to explore this Forum:
Installation and Licensing Forum:
http://forums.autodesk.com/t5/Installation-Licensi
Please mark any response as "Accept as Solution" if it answers your question.
__________________________________________________
CSHADEDESIGN|AUTOCAD LT|LT-KB|DYNAMIC BLOCKS
Please mark Accept as Solution if your question is answered. Kudos gladly accepted. ⇘
Re: Problems using AutoCad LT 2012 on VmWare Virtual-De sktop Infrastruc ture
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Couldn't find anything about that Problem in the license-Forum.
And we still found no solution for that problem so far.
Is there no troubleshoot to fix that problem?
Re: Problems using AutoCad LT 2012 on VmWare Virtual-De sktop Infrastruc ture
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
Program works fine now!
There was a problem with the proxy-configuration....
