Installation & Licensing

[#1]

Greetings,

Can anyone suggest a directory and share permission profile that I could
copy or reference to setup a networked version of AutoCAD Map 2000 on an NT
server?

Thanks,

David Booth
CAD Manager
RCN Westwood

[#2]

Simply put, Read-only. Then save a copy of your "standard" profile to their
local drive. Also, if you would like the user to be able to customize
toolbars then create an empty MNU file with a menu group name of your
choosing, then load that MNU to create the MNS, MNR, and MNC files. Now
delete the MNU file to keep the user from accidentally reloading an blowing
away any of their toolbar changes. Now when they go to create custom
toolbars they can create them in that "Personal" menugroup, they will
receive a few messages (depending on how many other menus are loaded stating
that they can't write to the MNS files, but it will be able to write to the
"Personal" (Local) MNS file. I would also move the MNU files on the server
to a location that the users don't have access to. This would eliminate the
"desire" for the users to edit the "standard" MNU files when they can edit
their local MNS files.

On my network, I also have the Acad.lsp and Acaddoc.lsp files compiled to
.fas files and the lsp files move to another location. I have the
Acaddoc.lsp file loading a "MyAcad.lsp" file that the user can have saved to
their local drive to change any variables or load any other routines that
they want. BTW, the loading of the "MyAcad.lsp" file is done in the
S:TARTUP section.

Hope this helps.

--
Kevin Nehls
remove -ns- for direct reply
David Booth wrote in message ...
>Greetings,
>
>Can anyone suggest a directory and share permission profile that I could
>copy or reference to setup a networked version of AutoCAD Map 2000 on an NT
>server?
>
>Thanks,
>
>David Booth
>CAD Manager
>RCN Westwood
>

[#3]

Kevin,

Thanks for the reply. Is it really true then that there's no files in the
acad executable or supporting directory that users need write or change
privledges to? And how about the ADLM license server directory?

Kevin Nehls wrote in message
news:ef08912.0@WebX.SaUCah8kaAW...
> Simply put, Read-only. Then save a copy of your "standard" profile to
their
> local drive. Also, if you would like the user to be able to customize
> toolbars then create an empty MNU file with a menu group name of your
> choosing, then load that MNU to create the MNS, MNR, and MNC files. Now
> delete the MNU file to keep the user from accidentally reloading an
blowing
> away any of their toolbar changes. Now when they go to create custom
> toolbars they can create them in that "Personal" menugroup, they will
> receive a few messages (depending on how many other menus are loaded
stating
> that they can't write to the MNS files, but it will be able to write to
the
> "Personal" (Local) MNS file. I would also move the MNU files on the
server
> to a location that the users don't have access to. This would eliminate
the
> "desire" for the users to edit the "standard" MNU files when they can edit
> their local MNS files.
>
> On my network, I also have the Acad.lsp and Acaddoc.lsp files compiled to
> .fas files and the lsp files move to another location. I have the
> Acaddoc.lsp file loading a "MyAcad.lsp" file that the user can have saved
to
> their local drive to change any variables or load any other routines that
> they want. BTW, the loading of the "MyAcad.lsp" file is done in the
> S:TARTUP section.
>
> Hope this helps.
>
> --
> Kevin Nehls
> remove -ns- for direct reply
> David Booth wrote in message ...
> >Greetings,
> >
> >Can anyone suggest a directory and share permission profile that I could
> >copy or reference to setup a networked version of AutoCAD Map 2000 on an
NT
> >server?
> >
> >Thanks,
> >
> >David Booth
> >CAD Manager
> >RCN Westwood
> >
>

[#4]

I think acad2000.cfg has to be set to rw.

--
Best regards: Jimmy B
CAD coordinator at Emtunga International AB
http://hem.fyristorg.com/cadman/
www.emtunga.com
David Booth skrev i diskussionsgruppsmeddelandet:ef08912.1@WebX.SaUCah8kaAW...
> Kevin,
>
> Thanks for the reply. Is it really true then that there's no files in the
> acad executable or supporting directory that users need write or change
> privledges to? And how about the ADLM license server directory?
>
> Kevin Nehls wrote in message
> news:ef08912.0@WebX.SaUCah8kaAW...
> > Simply put, Read-only. Then save a copy of your "standard" profile to
> their
> > local drive. Also, if you would like the user to be able to customize
> > toolbars then create an empty MNU file with a menu group name of your
> > choosing, then load that MNU to create the MNS, MNR, and MNC files. Now
> > delete the MNU file to keep the user from accidentally reloading an
> blowing
> > away any of their toolbar changes. Now when they go to create custom
> > toolbars they can create them in that "Personal" menugroup, they will
> > receive a few messages (depending on how many other menus are loaded
> stating
> > that they can't write to the MNS files, but it will be able to write to
> the
> > "Personal" (Local) MNS file. I would also move the MNU files on the
> server
> > to a location that the users don't have access to. This would eliminate
> the
> > "desire" for the users to edit the "standard" MNU files when they can edit
> > their local MNS files.
> >
> > On my network, I also have the Acad.lsp and Acaddoc.lsp files compiled to
> > .fas files and the lsp files move to another location. I have the
> > Acaddoc.lsp file loading a "MyAcad.lsp" file that the user can have saved
> to
> > their local drive to change any variables or load any other routines that
> > they want. BTW, the loading of the "MyAcad.lsp" file is done in the
> > S:TARTUP section.
> >
> > Hope this helps.
> >
> > --
> > Kevin Nehls
> > remove -ns- for direct reply
> > David Booth wrote in message ...
> > >Greetings,
> > >
> > >Can anyone suggest a directory and share permission profile that I could
> > >copy or reference to setup a networked version of AutoCAD Map 2000 on an
> NT
> > >server?
> > >
> > >Thanks,
> > >
> > >David Booth
> > >CAD Manager
> > >RCN Westwood
> > >
> >
>

[#5]

That's true, but if you are doing a network deployment with A2K (maybe R14
as well) during the install on the client the CFG file is saved to the
directory that you specified to be created (or used) on the client when you
setup the image directory.

In my so far limited testing there are no program files that the user needs
to have write access to. When I set my directories to read-only the only
messages that popped up stated anything about not being able to write to a
file was when I modified toolbars. The messages stated that the changes
would not be kept since they could not write to the MNS files. This can be
fixed by creating the "Personal" MNS file on the local drive as I stated in
my first post.

Also, the users should not have ANY need to EVER access the AdLM server.
This will eliminate the potential for them burying other clients so that
they can get a license. They also don't even need to know where the
directory is on the AdLM server. The ACADSERVER environment variable points
to the AdLM server and the service that is running on the AdLM server takes
care of the requests for licenses. When I setup my AdLM server I did not
create a share to that directory and it installed to the C drive of the
server, which is hidden (by default) and inaccessible to the clients. I
have had no problems getting licenses.

--
Kevin Nehls
remove -ns- for direct reply
Jimmy B wrote in message ...
>I think acad2000.cfg has to be set to rw.
>
>--
>Best regards: Jimmy B
>CAD coordinator at Emtunga International AB
>http://hem.fyristorg.com/cadman/
>www.emtunga.com

[#6]

Just to clarify a point Kevin is making. You do not have to share the AdLM
directory but the adlm\log and adlm\key directories and their contents must
NOT be write protected, AdLM will fail if they are.

Jerry Milana,
Autodesk Product Support

"Kevin Nehls" wrote in message
news:ef08912.3@WebX.SaUCah8kaAW...
> That's true, but if you are doing a network deployment with A2K (maybe R14
> as well) during the install on the client the CFG file is saved to the
> directory that you specified to be created (or used) on the client when
you
> setup the image directory.
>
> In my so far limited testing there are no program files that the user
needs
> to have write access to. When I set my directories to read-only the only
> messages that popped up stated anything about not being able to write to a
> file was when I modified toolbars. The messages stated that the changes
> would not be kept since they could not write to the MNS files. This can
be
> fixed by creating the "Personal" MNS file on the local drive as I stated
in
> my first post.
>
> Also, the users should not have ANY need to EVER access the AdLM server.
> This will eliminate the potential for them burying other clients so that
> they can get a license. They also don't even need to know where the
> directory is on the AdLM server. The ACADSERVER environment variable
points
> to the AdLM server and the service that is running on the AdLM server
takes
> care of the requests for licenses. When I setup my AdLM server I did not
> create a share to that directory and it installed to the C drive of the
> server, which is hidden (by default) and inaccessible to the clients. I
> have had no problems getting licenses.
>
> --
> Kevin Nehls
> remove -ns- for direct reply
> Jimmy B wrote in message ...
> >I think acad2000.cfg has to be set to rw.
> >
> >--
> >Best regards: Jimmy B
> >CAD coordinator at Emtunga International AB
> >http://hem.fyristorg.com/cadman/
> >www.emtunga.com
>

[#7]

So do those directories need change permission for the user account that is
requesting a license, or for the Administrator account, or just for the
system account (since it is just a service running on NT). Currently in my
test environment I have AdLM installed on a test bed NT server that is using
FAT instead of NTFS and I have just created a hidden share to where I have
change permissions through.

I have just ran a test in where I have changed the permission for the share
that I go though to the AdLM directory to NO ACCESS, I was able to open up
AutoCAD without a problem. Which account exactly needs to have the change
permissions to that directory, the Administrator or the system account?

Thanks
--
Kevin Nehls
remove -ns- for direct reply
jerry milana wrote in message ...
>Just to clarify a point Kevin is making. You do not have to share the AdLM
>directory but the adlm\log and adlm\key directories and their contents must
>NOT be write protected, AdLM will fail if they are.
>
>Jerry Milana,
>Autodesk Product Support

[#8]

Kevin,

What we recommend is that the permissions on the file level be wide open on
these directories and files. If you choose to share these files for remote
administration, restrict access at the share level.

Jerry

"Kevin Nehls" wrote in message
news:ef08912.5@WebX.SaUCah8kaAW...
> So do those directories need change permission for the user account that
is
> requesting a license, or for the Administrator account, or just for the
> system account (since it is just a service running on NT). Currently in
my
> test environment I have AdLM installed on a test bed NT server that is
using
> FAT instead of NTFS and I have just created a hidden share to where I have
> change permissions through.
>
> I have just ran a test in where I have changed the permission for the
share
> that I go though to the AdLM directory to NO ACCESS, I was able to open up
> AutoCAD without a problem. Which account exactly needs to have the change
> permissions to that directory, the Administrator or the system account?
>
> Thanks
> --
> Kevin Nehls
> remove -ns- for direct reply
> jerry milana wrote in message ...
> >Just to clarify a point Kevin is making. You do not have to share the
AdLM
> >directory but the adlm\log and adlm\key directories and their contents
must
> >NOT be write protected, AdLM will fail if they are.
> >
> >Jerry Milana,
> >Autodesk Product Support
>