nework deployment issues

I manage about a dozen workstations that are all network licensed. We use
Civil series 2004 so you have about 3 different profiles on each machine.
We keep our pc3 files and customized plotters on the server. I don't want
to go to every machine and change 3 path's on 12 computers. Can someone
give me a good idea to automate this process.

Also is there a trick to get Sam report lite to work?

Thanks

 

THere's a couple of ways to bundle custom profiles with custom shortcuts. You can open and modify the MSI transform files (MST files) created by the NIW using something like InstallShield or Wise. Or you can build a script or batch file to wrap the deploy.exe package within and create a sequenced batch process that first installs the client deployments, and then downloads files and creates/replaces shortcuts to control the /p profile arguments. This can be pushed in a login script, "pulled" from a email link or web page link or pushed via something like MS-SMS packages.

 

Export your profiles to the network.

Import them into each machine.
Chris

You can open and modify the MSI transform files (MST files) created by the
NIW using something like InstallShield or Wise. Or you can build a script
or batch file to wrap the deploy.exe package within and create a sequenced
batch process that first installs the client deployments, and then downloads
files and creates/replaces shortcuts to control the /p profile arguments.
This can be pushed in a login script, "pulled" from a email link or web page
link or pushed via something like MS-SMS packages.

 

Hi Chris -

Would you change your posting name away from
discussion.autodesk.com so that you aren't confused as posting
from Autodesk? Thanks.

 

We use Kixtart (kixtart.org) during the logon script to import REG files
that are pieces of the exported profiles. Changes are made to files in a
central folder on a network share, so the users see them the next time they
login. This way, everytime the user logs in again, they are set back to a
standard. Pathing, settings, whatever. We also repoint the default menu to a
custom one on the network and let a MNL file deal with the inside autocad
issues. Single point of control.

Whatever can be exported in a ARG can be imported into the same profiles in
the registry, but you will have to write some kixscript to deal with the way
autocad profile ARG paths are abbreviated paths that go into user profile
directories. Autodesk uses a "non-registry-compliant" syntax to refer to
these directories. The ARG will show the "variable" name for the path, while
the same item in the registry will be expanded. You cannot make a single REG
file apply to all users for these paths, unless you move the user profile
directories back to the "acad" directory.