Though knowing that the "reasonable" assumption would be to look for the
drive with the most space on the Server environment, is an easy "out" as it
were John.
I agree with you though, it would be nice if the reseller responsible for
the client, would communicate with all the parties involved in this
endeavor.
So that once the "package" arrives, it would then seamlessly fit into the
client's Server system.
I wonder which Service Pack that might be on?
;0)
--
Don Reichle
"The only thing worse than training your staff, and having them leave is -
not training your staff, and having them stay."
😮
A reminder taken from Graphics Solution Providers' Calendar page
-------------------------- ------------------------------------------
!! Please discuss whatever we tell you with your SysMgr !!
!! They appreciate staying in the loop
🙂 !!
LDT-2K4
AMD Athlon64 2.2GHz 2GB RAM
XPPro 32bit SP2
WD Raptor 10K-rpm 37GB HD
Nvidia GeForce FX 5200 128MB
"The only Constant is Change".
"John Schmidt"
wrote in message
news:5580942@discussion.autodesk.com...
We finally resolved the deployment problem ourself. When creating the
depolyment image and taking the defaults, the installation program appears
to erroneously assign whatever drive on the "server* that has the most space
as the default client drive for LDT Projects. In our case, this was an F:
drive, which none of the clients have. Recreating the deployment and
manually changing this to the C: drive resolved the problem.
The routine should *not* assume everyone will have the same drive
arrangement as the deployment server and just automatically assign the
Projects folder to whatever big drive it finds on the server!
John
"Pat Trudeau" wrote in message
news:5575163@discussion.autodesk.com...
Maybe a solution in this thread (64 bit it won't load?):
Ok after contacting the reseller they had no clue what was wrong. I thought
about it overnight and this morning I've got it installing Hallelluh!!
Here's the deal I kept getting a message like my windows installer wasn't
working then it'd come back with a fatal error about the ldt.msi file. So I
really thought about what I did to my machine. First I backed up the
important stuff from my 2007 product. Then I uninstalled it. Then I cleaned
the registry. Then I had issues. So I found a little freebee program
called Dial A fix. I ran that this morning. It starts and stops all of the
standard windows services, and cleans out the temp files. AFter I ran that
little program, wouldn't you know it, it installed. AMEN!!. So if you run
into an issue with the LDD not wanting to install but Civil 3D did install
that's most likely what has happened, your windows installer service went
bad and needed to be restarted. Let me tell you what a head ache!
Thanks for all your support and helpful thoughts on this, and for letting me
Vent after a long day at work.
Heidi
"John Schmidt" wrote in message
news:5572663@discussion.autodesk.com...
I've created a deployment image for our standalone licenses, using ONLY the
Autodesk defaults. There were no problems creating the deployment image.
Installation on workstations fails with the following error in the logs:
MSI (s) (20:38) [11:44:50:695]: Product: AutoCAD Civil 3D Land Desktop
Companion 2008 -- Error 1324. The folder path 'Land Projects 2008' contains
an invalid character.
What is invalid??? I'm using the installation defaults, without changing
anything!! This happens at all computers I've tried.
Installation directly from the DVD works, but only about 10% of our
workstations have DVD's. And I expect the deployment functions to work
anyway - isn't that what we pay Autodesk the big bucks for anyway??
Thanks for any suggestions on resolving this issue.
John
![Autodesk Design & Make Report](https://forums.autodesk.com/t5/image/serverpage/image-id/1350519iCB55845EBFC43016/image-size/large?v=v2&px=999" "Autodesk Design & Make Report")