Friday, September 2, 2011

AutoCad LT 2011

AutoCad LT 2011

Creating a package for deployment over the network is significantly different from running the setup for a single user.  As a packager you'll probably get instructions on how to install the software but these will only be a guide to the requirements of the installation.  In reality you need to create a "deployment point" (DP) which you do be creating a sort of administrative installation and then arranging a call to the installation from there.

Chances are you've been given no license or a single user license for 1 installation, not much use if you're package maybe needed on unknown numbers of machines in the future.  The way to tackle this is to obtain at least 1 set of licensing numbers of the form: serial number 555-55555555 and product key XXXXX
Enter these details during the deployment point creation.  You HAVE to enter something, blanks are not possible.

Once the DP is created you'll be able to locate these values in the property table and remove the entire property.  This causes the installation from the DP to query the user at launch for their Autocad login (which has a license relationship) to validated the install OR enter a 30 day evaluation period.

The DP has a name that you set during the DP creation routine.  This becomes the name of a shortcut that can initiate the AutoCAD LT installation to a client.  If you look at the command of this shortcut you'll see that it references an ini file with a similar name that is also created with the DP.  This is the setup.exe configuration file and contains many setting that you may wish to modify including the DP share location.

Note that there may be problems with applying service packs (SPs) to the DP.  During the DP creation you can choose to download SPs and "merge" or "append" it to the DP.  Merging worked fine with an English DP, however only appending was possible when creating a German language DP.  Although the German Language DP was created with a merge selection, subsequent client installation attempts from it, failed.

http://docs.autodesk.com/ACDLT/2011/ENU/pdfs/acadlt_install.pdf

Note there is an earlier version of the above document with SCCM specific sections.