Same here. We deploy the installs from the network (which is also a nice,
time saving feature when setting up new clients), with a full install onto
the client machine.
I would also like to add:
If you want "company standard customization" the best way for this is to do
the customizations and have all of those files located on a network share,
then have all of the clients pointing to them with that path at the very top
of their search paths. If you place these customizations on the local
drives then you really have to start worrying about version control of your
custom routines, borders, eco blocks, title blocks, etc. (the list goes on,
and on). Also, if you did copy all of these customizations to the local
machine how would you keep the user(s) from "accidentally" deleting or
changing the files (another version control issue)? Now if the network goes
down, who cares if you have standalone or networked versions of acad, nobody
can do any real work as all of the customizations that they so heavily
depend upon are no longer accessible.
As Mike stated you need stable, reliable servers and NOS; NT, Novell, UNIX,
Linux, whatever, just as long as it stays up for the users to access.
--
Kevin Nehls
remove -ns- for direct reply
"Mike" wrote in message
news:22BD527D398095A491119BBCFBAE8A12@in.WebX.SaUCah8kaAW...
(snip)
> We do not use a "network installation" of the software - all the LDD
> software is installed on the user's workstations. Drawings, details,
fonts,
> linetypes, etc are on server - so if the server is down, all CAD users are
> down too.
>
> Key is reliable server and network OS. We have much more lost production
> from workstation failures than from network problems.
>