Installation & Licensing

[#1]

Custom.lst Limitations:
1. Can only create new folders within the root directory of the application
program.

If you want folders outside of the application program you will have to use
a different approach, like PictureTaker.

Bud Schroeder wrote in message
news:3A07A02C.AC8B6F80@sonic.net...
> Hi Chris,
>
> Custom.lst will let you create a list of custom files you can copy with
your
> Deployment. Take a look in the Install guide for more information on this
and
> how it works.
>
> As far as Administrator rights go, any application that needs to write to
the
> registry and replace core System files needs to have Administrative
rights.
> Once you have installed and ran AutoCAD once, you can change the rights
back to
> say power user. You could use VBScripts to do this. You could have them
run at
> login. One question I have though is why do you need to lock down the
systems?
>
> As far as doing a push or pull, you may want to look at programs like SMS
do
> this. There are also a lot of things you can do with VBS script files as
well.
>
> Hope this helps.
>
> Bud
>
> Custom.lst help file information:
> =====================================
> The AutoCAD setup application enables you to customize AutoCAD files or
> supplement the installation with files of your own. You must add a file
called
> custom.lst to the Image directory in the client deployment location
created by
> the Network Setup Wizard. If this file exists, the AutoCAD setup
application
> will overwrite or add the files listed in custom.lst to the installation
> directories on the client workstation.
> The custom.lst file is a text file which must be placed in the Image
directory.
> Each line contains a source file name and an optional destination file
name,
> separated by a "greater than" sign (>). The file name can also contain a
fully
> qualified path. Blank lines are acceptable, and spaces are ignored at the
> beginning and end of each line. If you do not include a fully qualified
path,
> source file names are relative to the Image directory. You must copy the
> directories and files you reference in custom.lst into this directory.
> Destination file names are relative to the directory where AutoCAD will be
> installed. If no destination is provided, the source file base name with
> extension is assumed.
>
> When specifying source filenames, wildcard characters can be used.
However, you
> cannot rename files using wildcard characters.
> The following is a sample custom.lst file.
> data\test.lsp > test.lsp
> t3.lsp >
> t4.lsp > t5.lsp
> MyCustomFiles\*.* > Support\*.*
> MyDrawings\*.* >
> MyLSP\Special.lsp >
> In this example, the custom.lst file causes the following operations to be
> performed:
> 1. The test.lsp file is copied from the Data directory in the Client
deployment
> location to the AutoCAD directory.
>
> 2. The t3.lsp file is copied from the Client deployment location to the
AutoCAD
> directory.
> 3. The t4.lsp file is copied from the Client deployment location to the
AutoCAD
> directory and renamed to t5.lsp.
> 4. The contents of the MyCustomFiles directory in the Client deployment
location
> are copied to the AutoCAD\Support directory.
> 5. The contents of the MyDrawing directory in the Client deployment
location are
> copied to the AutoCAD directory.
> 6. The MyLSP directory is created in the AutoCAD directory and the
Special.lsp
> file is copied into it.
>
> The AutoCAD directory is the directory that contains the acad.exe file.
> =====================================
>
> Chris Plensdorf wrote:
>
> > I have seen this question in past posts with no response. Has anyone
> > experience with modifying files in the ACAD1.CAB file to affect a
'custom'
> > deployment of AutoCAD 2000i. Or can I modify the *.LST files to have
> > Windows Installer 'pull' additional files to the client? What do these
> > (*.LST) files accomplish?
> >
> > I am having serious issues with the viability of network deployment
if.....
> >
> > 1. I must install as an administrator. I do not want to grant
> > administrative priveledges to all CAD users. This means an
administrator
> > must log on locally on every machine. This is eased somewhat in W2000 if
I
> > can 'Run As' the Install Executable. I must still grant 'loose'
permissions
> > to execute the program.
> >
> > 2. I must still customize every single workstation after installing
2000i
> > because I can not 'push'/'pull' custom menus, etc during the deployment.
I
> > can not even modify a profile file and have the deployment modify the
path
> > automatically to point to it. With 200+ users, having all files on the
> > network causes network traffic issues, therefore having files local is a
> > plus. Inclusion in a logon script could assist.
> >
> > Am I missing something? Has anyone 'solved' this dilema?
> >
> > Chris Plensdorf
>

[#2]

Chris

I looked for it too and it must be buried real deep. It was in the network
deploy docs. for release 14 but I haven't seen it since. If you get an
answer can you let us know!

Shawn Romkey
Noranda Mining
Chris Plensdorf wrote in message
news:3CB21098AC98B0E0B35AFF9425EF0E28@in.WebX.SaUCah8kaAW...
> Bud,
>
> Where did you find the hlp on custom.lst? That is exactly the kind of
info
> I am looking for. Am I blind or has it been buried pretty deep?
>
> Chris
>
> "Bud Schroeder" wrote in message
> news:3A07A02C.AC8B6F80@sonic.net...
> > Hi Chris,
> >
> > Custom.lst will let you create a list of custom files you can copy with
> your
> > Deployment. Take a look in the Install guide for more information on
this
> and
> > how it works.
> >
> > As far as Administrator rights go, any application that needs to write
to
> the
> > registry and replace core System files needs to have Administrative
> rights.
> > Once you have installed and ran AutoCAD once, you can change the rights
> back to
> > say power user. You could use VBScripts to do this. You could have
them
> run at
> > login. One question I have though is why do you need to lock down the
> systems?
> >
> > As far as doing a push or pull, you may want to look at programs like
SMS
> do
> > this. There are also a lot of things you can do with VBS script files
as
> well.
> >
> > Hope this helps.
> >
> > Bud
> >
> > Custom.lst help file information:
> > =====================================
> > The AutoCAD setup application enables you to customize AutoCAD files or
> > supplement the installation with files of your own. You must add a file
> called
> > custom.lst to the Image directory in the client deployment location
> created by
> > the Network Setup Wizard. If this file exists, the AutoCAD setup
> application
> > will overwrite or add the files listed in custom.lst to the installation
> > directories on the client workstation.
> > The custom.lst file is a text file which must be placed in the Image
> directory.
> > Each line contains a source file name and an optional destination file
> name,
> > separated by a "greater than" sign (>). The file name can also contain a
> fully
> > qualified path. Blank lines are acceptable, and spaces are ignored at
the
> > beginning and end of each line. If you do not include a fully qualified
> path,
> > source file names are relative to the Image directory. You must copy the
> > directories and files you reference in custom.lst into this directory.
> > Destination file names are relative to the directory where AutoCAD will
be
> > installed. If no destination is provided, the source file base name with
> > extension is assumed.
> >
> > When specifying source filenames, wildcard characters can be used.
> However, you
> > cannot rename files using wildcard characters.
> > The following is a sample custom.lst file.
> > data\test.lsp > test.lsp
> > t3.lsp >
> > t4.lsp > t5.lsp
> > MyCustomFiles\*.* > Support\*.*
> > MyDrawings\*.* >
> > MyLSP\Special.lsp >
> > In this example, the custom.lst file causes the following operations to
be
> > performed:
> > 1. The test.lsp file is copied from the Data directory in the Client
> deployment
> > location to the AutoCAD directory.
> >
> > 2. The t3.lsp file is copied from the Client deployment location to the
> AutoCAD
> > directory.
> > 3. The t4.lsp file is copied from the Client deployment location to the
> AutoCAD
> > directory and renamed to t5.lsp.
> > 4. The contents of the MyCustomFiles directory in the Client deployment
> location
> > are copied to the AutoCAD\Support directory.
> > 5. The contents of the MyDrawing directory in the Client deployment
> location are
> > copied to the AutoCAD directory.
> > 6. The MyLSP directory is created in the AutoCAD directory and the
> Special.lsp
> > file is copied into it.
> >
> > The AutoCAD directory is the directory that contains the acad.exe file.
> > =====================================
> >
> > Chris Plensdorf wrote:
> >
> > > I have seen this question in past posts with no response. Has anyone
> > > experience with modifying files in the ACAD1.CAB file to affect a
> 'custom'
> > > deployment of AutoCAD 2000i. Or can I modify the *.LST files to have
> > > Windows Installer 'pull' additional files to the client? What do
these
> > > (*.LST) files accomplish?
> > >
> > > I am having serious issues with the viability of network deployment
> if.....
> > >
> > > 1. I must install as an administrator. I do not want to grant
> > > administrative priveledges to all CAD users. This means an
> administrator
> > > must log on locally on every machine. This is eased somewhat in W2000
if
> I
> > > can 'Run As' the Install Executable. I must still grant 'loose'
> permissions
> > > to execute the program.
> > >
> > > 2. I must still customize every single workstation after installing
> 2000i
> > > because I can not 'push'/'pull' custom menus, etc during the
deployment.
> I
> > > can not even modify a profile file and have the deployment modify the
> path
> > > automatically to point to it. With 200+ users, having all files on
the
> > > network causes network traffic issues, therefore having files local is
a
> > > plus. Inclusion in a logon script could assist.
> > >
> > > Am I missing something? Has anyone 'solved' this dilema?
> > >
> > > Chris Plensdorf
> >
>

[#3]

Chris,

If you are using a Windows 2000 Server with Active Directory, you can use Group
Policy to assign AutoCAD to groups of users and have these installation run with
elevated priveleges. In other words, you don't have to make everyone an
Administrator.

Alternatively, you can try assigning the package to the Computer itself, and A2K
will install when the machine boots up, before a logon occurs.

I'm currently evaluating about 2 different deployments methods, and will post
results in about a week when I get it all sorted out.

Matt
stachoni@bellatlantic.net
mstachoni@beyerdesign.com

On Tue, 7 Nov 2000 13:23:02 -0800, "Chris Plensdorf"
wrote:

>Thanks for the info.... and to answer your question, we prefer to lock down
>our workstations to keep a 'basic' set of applications on the desktop. When
>supporting several hundred stations, there are always a few (hundred?) that
>prefer to install their own programs that cause problems with our standard
>palette of application, (i.e. Napster, Real Player, shareware) Most of the
>common apps we have being removed at logon, but locking the station simply
>makes supporting any one workstation that much more consistent.

[#4]

Hello Bud,

> Custom.lst will let you create a list of custom files
> you can copy with your
> Deployment. Take a look in the Install guide for more
> information on this and how it works.

I also like to customize the client deployment made with Netsetup, but I don't know how. I've been searching all documentation about Cusatom.lst, but haven't found anything? We use the locked (english) version of AutoCAD 2000i. Are there any guidelines, tools or documentation on this subject?

Greetings,

Simon Weel