There are apparently some issues with the NIW (Network Installation Wizard)
generating admin installations for distribution.
One of our primary issues were the inability for a standard user to login
and use the application due to default search paths pointing to the
administrative profile as a searchable path for the menu item, fonts and all
of the other stuff AutoDesk assumes a user wants dumped in their profile.
The primary culprit is the default setting in the NIW for setting the temp
path to C:\DOCUME~1\\LOCALS~1\Temp\. One would go on the
assumption that the line would be equivalent to the %username%
environment variable for MS Windows but no, it instead hard codes the
installation username in the LDDT.ARG and MAP.ARG search paths for startup.
Of course if you happen to be an administrator or are not using the NTFS
file system you can use the erroneous paths since there are no file security
limitations.
A brief overview of what needs to be corrected can be found in the knowledge
base document TS85103
http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=4494045&linkID=2475507
the best document to use is
http://www3.autodesk.com/adsk/files/4515408_LDT_Limited_User_Whitepaper_FINALV3.doc.
If it is no longer is available just do a keyword search on the Internet for
Land Desktop Limited User. There are several replications from other folks
who have had this issue and have made it easier to find than AutoDesk. They
do not even link it with the keywords from their Knowledge Base support
area. You have to either browse the Whitepaper section or search from the
main search link within their site or then sort through 100+ hits depending
on the keywords you use.
There are several other issues with the NIW just for the Land Desktop
installs. If you want the Express Tools available you have to manually copy
the files to the installation point even though you have selected to have
them included from the NIW. This is explained in the knowledge base document
TS84941
http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=4366039&linkID=2475507
We of course had the bonus problem of all of our users having roaming
profiles with a storage area of only 50MB for their roaming profiles and any
personal files. This issue was a main problem for us because the AutoDesk
Land Desktop 2004/5 product likes to dump 25MB of "support files" into each
user's profile. The excuse we got for this was "this is Microsoft's issue
because it is what we had to do to be WinXP compliant". This seems pretty
bogus since a standard user still has to have the modifications to the
installation that I mentioned above in Limited User comment in order for the
software to work correctly. In fact, we over came this issue by designing or
installation to run with a script that initializes the NIW MSI package and
then generates a profile directory in the program's default installation
directory and places all of the "unique" files required by each user in a
single directory and points the LDDT.ARG and MAP.ARG files to this directory
as the searchable path rather than the user's network profile path which we
limit what files are kept when they log out. We exclude the local settings
folder from their profile for the roaming profiles and so when they log back
in the application finds the search path is available and rebuilds the local
settings folder.
Since we are trying to teach engineers to be engineers and not AutoCAD/Land
Desktop users we have decided not to implement all of the other components
(Civil Design, Survey, Raster Design, Envision) so we have skipped the
issues that may be unique to those additions but I am sure there are as many
quirks in those as there are in just the base application.
-- Ken Young --
-- IT Resource Consultant --
-- University of South Carolina --
"Jon Houser" wrote in message
news:40c99fed_2@newsprd01...
> When I try to install Civil Design or Survey from an admin image on a
> Windows XP workstation, I recieve the following error message:
>
> MSI2EA - C:\DOCUME~1\jonh\LOCALS~1\Temp\Adsklicense.ini not found.
>
> Does anyone know how I can fix this problem?
>
> Thanks,
> Jon
>
>
