Welcome to Autodesk’s Installation and Licensing Forums. Share your knowledge, ask questions, and explore popular Download, Installation, and Licensing topics.
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
I have been trying to create a deployment for Land Desktop Companion 2008. Not pushed or anything fancy, just let the users run the setup from the network. It all seems to work except for the custom support paths. A couple of times I was able to specify a custom profile and that would include the printer configuration, toolpallete and template paths, but not the support paths. I was also unable to get it to create a custom launcher (shortcut icon).
glyons said the following on 9/24/2007 12:55 PM:
> I have been trying to create a deployment for Land Desktop Companion
> 2008. It all seems to work except for the custom support paths.
> Any suggestions?
Post process this by setting the support paths using "acad.lsp"
See:
http://rkmcswain.blogspot.com/2007/02/setting-support-paths-via-lisp.html
That was my intent, and I had already borrowed that bit o' code from your site. However, my acad.lsp is located in a directory on the server that I had hoped to include on the deployment. Without this, I have to add that directory to each station's support path manually for the post-processing to run. This is not a huge deal, as I have a small number of workstations to configure, but it would be nice if the deployment were to work as advertised.
glyons said the following on 9/24/2007 2:41 PM:
> That was my intent, and I had already borrowed that bit o' code from
> your site. However, my acad.lsp is located in a directory on the
> server that I had hoped to include on the deployment.
I think it's a vertical issue. We tried this back with LDT2005 and gave
up after a while and went to post-processing everything. This has ended
up working better for us since we don't have to remember to customize
each AdminImage the same way or anything (we have several). Each one
gets setup right OOTB.
Anyway, we use a BAT file for installing and configuring each system.
This BAT file WRITES the local "acad.lsp" for me (located in "C:\Program
Files\AutoCAD Civil 3D Land Desktop Companion 2008\Support"). The first
time LDT starts, it fires this "acad.lsp" which includes only this line:
(load "\\\\server\\share\\cad\\acad.lsp")
Once the network "Acad.lsp" fires, it sets the support file search path.
The path that contains the network "acad.lsp" is at the TOP of the new
support file search path - so it always loads.
It is frustrating that not only has that feature not worked in LDT for several releases but it hasn't been fixed nor do they let anyone know that it's broken and that they don't intend to fix it. It would be nice to see these "issues" made public by Autodesk in a single place, by release & vertical in an easy to find format. Yes you can search for a know problem if you know it exists but I would like to go to a "2008 LDT list of know issues and their status for resolution" site.
I've gotten around this issue by creating an arg the way I want & replacing the string in the icon to create a new company profile when you start LDT based off that arg which get's copied to the root program directory by the bat file which installs everything else. This is the way it used to work. The method works well although I will say that R.K.'s method is simpler to automate for multiple users. The method I describe, if you don't want to manually post-process, requires editing the msi and has produced consistently good results for me although in an AU network license class, I was told that Autodesk doesn't support or recommend it (even though it works and their out of the box solution doesn't)
drwdrwdrw said the following on 9/25/2007 7:40 AM:
> It is frustrating that not only has that feature not worked in LDT
> for several releases but it hasn't been fixed nor do they let anyone
> know that it's broken and that they don't intend to fix it.
They don't care....
> It would
> be nice to see these "issues" made public by Autodesk in a single
> place, by release & vertical in an easy to find format.
Not "by Autodesk", but a list...
http://www.texupport.net/bugslist/index.php
