Roaming Profiles and LandDesktop 2005 Installation Woes

We are upgrading from AutoCAD 2000 to Autodesk Land Desktop 2005 and found
some woefully painful issues concerning application data and our user
profiles.

We are in a large institution in which a majority of the user base have
roaming profiles. The problem is that they only have 50MB of storage space
for both their roaming profile and netowk files (word, excel documetns,
etc...). One of the ways we help keep their space usage down is by not
saving certain portions of their profiles to the roaming profile. One of
those is the LocalSettings folder. Well, the new version of Autocad Land
Destktop (none of the other components added at this time) takes 20MB of
space alone in that exact location (templates, textures, support, etc.).
Also the roaming profiles are not stored locally after a user logs out as
well because there are approximately 400+ users using these systems at
random (we are in a University environment).

The Network Administrator Guide documentation does a very poor job in
describing installation alternatives and the only document that could be
found about roaming profiles and a newer version of the software is related
to the 2004 revision locat at

http://usa.autodesk.com/adsk/servlet/ps/item?siteID=123112&id=4376227&linkID=2475507

Is this still an issue with the Autodesk Land Desktop 2005? If so, has
anyone come up with a possible work around?

Increasing storage space for users is not an option (State budgets are at
rock bottom and there's no way to implement more drive storage for our
environment).

Is there a way to run it with the runas command but have the password
embedded so they do not have to type it in?

Thanks,
Ken

 

Roaming profiles or not, we've modified the settings in AutoCAD, (LDT2005),
profiles so that *all* support and other paths are the same for everybody,
so no localsettings folders are used for R2005. It first required a "master*
setup that was modified, and was the source for all the files that would
later be accessed in standard locations. Once we had this master
installation the way we liked it, we saved the LDT .arg profile, rolled it
into our network deployment images, and also copied the files originally in
localsettings to their new standard locations in the installation routines.
This has worked well for us so far, and should work the same whether roaming
profiles are used or not. It's a little work to set up in the beginning, but
allows us to easily update any standards, etc, since they're now in the same
location on all computers.

John