| Author |
Message |
hvymtlfan
Guest
|
 Posted:
Mon Sep 20, 2004 8:04 pm Post subject:
AdminImage's EULA did not Install |
|
|
Installing the 2005 client deployments for Network for multiple
ADSK products. On one (Land Desktop), the EULA directory
is completly empty, i.e. no AdskLicense.ini exists so the deployment image will not install to workstations.
Has anyone had this happen when creating the network deployments on the server ? Then do you just "reinstall" over
the deployment image, or should you REMOVE the entire
deployment image and in a sense start over for that product.
In checking all the other products, the AdskLicense.ini and
associated files are present. For some reason, the LDDT product just did not register it's EULA directory components.
Appreciate the info. (now if I can only figure why after combining license files with 2002, our 2005 products are not
reading the updated lic. file, while our older products are ok?)
|
|
| Back to top |
|
 |
hvymtlfan
Guest
|
| Posted:
Mon Sep 20, 2004 9:00 pm Post subject:
Re: AdminImage's EULA did not Install |
|
|
Just a "personal" post update.
Found the below info Posted by: Mark Castle
Date: May/23/04 - 00:11 (CDT)
2. The initial deployment image for Land Desktop 2005 contained an empty
EULA folder, which caused the install to abort with an error. I searched the
newsgroups and found a thread about this problem occurring in 2004 if an
apostrophe was included in the personalization information. I did not have
any but I did include parentheses in the support phone number which I
removed when I re-created the image. Same result. Finally I just manually
copied the contents of the EULA folder on the CD to the folder in the
deployment and the install proceeded without problems.
Had the idea to simply copy off CD, yet was not sure.
Sounds like very SAME problem, yet again, we had only a
"1" as the number, and no other text, and still failed.
Sure it will be fine. |
|
| Back to top |
|
|
jerry milana (Autodesk Co
Guest
|
| Posted:
Mon Sep 20, 2004 9:53 pm Post subject:
Re: AdminImage's EULA did not Install |
|
|
Creating an admin image does not cause files to be registered, installing
the admin image to workstations does. Try copying the contents of
\BIN\Installer\EULA on tour LDD CD to AdminImage\EULA on your deployment
server.
--
Jerry Milana,
Autodesk Consulting
"hvymtlfan" <nospam@address.withheld> wrote in message
news:14348377.1095696327246.JavaMail.jive@jiveforum1.autodesk.com...
| Quote: | Installing the 2005 client deployments for Network for multiple
ADSK products. On one (Land Desktop), the EULA directory
is completly empty, i.e. no AdskLicense.ini exists so the deployment image
will not install to workstations.
Has anyone had this happen when creating the network deployments on the
server ? Then do you just "reinstall" over
the deployment image, or should you REMOVE the entire
deployment image and in a sense start over for that product.
In checking all the other products, the AdskLicense.ini and
associated files are present. For some reason, the LDDT product just did
not register it's EULA directory components.
Appreciate the info. (now if I can only figure why after combining
license files with 2002, our 2005 products are not
reading the updated lic. file, while our older products are ok?) |
|
|
| Back to top |
|
|
hvymtlfan
Guest
|
| Posted:
Wed Sep 22, 2004 1:37 am Post subject:
Re: AdminImage's EULA did not Install |
|
|
Jerry,
Again, appreciate the response.
Maybe I should have not used the word "Register" so loosely,
since understood contents were just a copy from the CD, yet wanted to make sure before accepting at face value.
Simply checked a couple other product (CD) sources, and
EULA dir. was just as noted.
I know some people are having (some) instances with LDDT, and the support options detail the problem if an "apostrophe" (or "other(s)" text noted in some past threads), yet was unclear that the EULA contents were just the admin image=CD. Hopeful, it's clear to all who experience same. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in