Installation & Licensing

Reply
*martin, jason
Message 11 of 13 (62 Views)

Re:

08-15-2000 10:08 AM in reply to: aekins
Inline
Kevin Nehls wrote in message
news:43CDF937A18D516AFADCFCAB35EBFE85@in.WebX.SaUCah8kaAW...
> jason martin wrote in message
> <142DE224ED10A37A22F69B24DC02067D@in.WebX.SaUCah8kaAW>...
> >If you're using an @ in the acadserver name it makes this a little more
> >complicated. Either you must go to each client and remove the @ from the
> >server name or, do like me and don't mess with the acadserver variable.
If
> >you have a large network it would be fairely easy to write a login script
> >that could change the variables on the local machines when they logged in
> >(assuming of course that they logged out the night before!!!).
>
> That's what I thought. The login script would be easy and simple if all
of
> the clients are on NT. But what happens if they are on Win9x and the
> ACADSERVER variable is set in Autoexec.bat? In that situation the
> Autoexec.bat file needs to be edited for each client.

Write a perl script (or vbscript for that matter) that can modify the
autoexec.bat files on each of the (W9x) client machines if you have access
to their hard drives over the network. If they don't have the drives shared
and depending on security settings it might be possible to send them an
email that will do all of the work for you (all they would have to do is
preview the email, depending on security settings). Worst case you email
them the compiled perl or vbscript and force them to run it. Just tell them
that they won't have autocad unless they run it and re-boot. As long as you
know what the current ADLM server is set to it would be easy to search for
and replace a given string within the autoexec.bat.

>
> >
> >Actually you might be able to get away with the server name game using
dns.
> >Since ADLM checks based on dns names and not netbios names you might be
> able
> >to simply set your dns server which was pointing at say 10.10.10.10 for
> >adlm.company.com to 10.10.10.11 for adlm.company.com. Works in theory,
but
> >I've not tried it this way. Maybe Jerry will confirm.
>
> This potentially sounds like the best option.
>
One gotcha on this method would be dns timeouts. If you're doing any dns
caching you would have to make sure that the updates get replicated before
the clients started trying to use autocad. As long as it's planned the day
before you could set you times outs to something like an hour and then let
it sit overnight after the change is made and the new dns names would be
replicated throughout the organization.

hth

jason martin
frankfurt-short-bruza
*milana, jerry
Message 12 of 13 (62 Views)

Re:

08-16-2000 04:22 PM in reply to: aekins
H1 All,

You could not have two systems on the network with the same hostname, that
can create disaster! So, that eliminates the idea of setting up the new
server then bringing down the old one and ending up with a AdLM server that
responds to the old hostname. Sorry, thats network physics ;}. If the @
symbol is being used OR if workstations are on remote sides of router(s)
from the AdLM server, you MUST change the ACADSERVER variable on the
workstations.

jerry

"jason martin" wrote in message
news:8BD5EABCB15CB73E6472BD683E496840@in.WebX.SaUCah8kaAW...
> Inline
> Kevin Nehls wrote in message
> news:43CDF937A18D516AFADCFCAB35EBFE85@in.WebX.SaUCah8kaAW...
> > jason martin wrote in message
> > <142DE224ED10A37A22F69B24DC02067D@in.WebX.SaUCah8kaAW>...
> > >If you're using an @ in the acadserver name it makes this a little more
> > >complicated. Either you must go to each client and remove the @ from
the
> > >server name or, do like me and don't mess with the acadserver variable.
> If
> > >you have a large network it would be fairely easy to write a login
script
> > >that could change the variables on the local machines when they logged
in
> > >(assuming of course that they logged out the night before!!!).
> >
> > That's what I thought. The login script would be easy and simple if all
> of
> > the clients are on NT. But what happens if they are on Win9x and the
> > ACADSERVER variable is set in Autoexec.bat? In that situation the
> > Autoexec.bat file needs to be edited for each client.
>
> Write a perl script (or vbscript for that matter) that can modify the
> autoexec.bat files on each of the (W9x) client machines if you have access
> to their hard drives over the network. If they don't have the drives
shared
> and depending on security settings it might be possible to send them an
> email that will do all of the work for you (all they would have to do is
> preview the email, depending on security settings). Worst case you email
> them the compiled perl or vbscript and force them to run it. Just tell
them
> that they won't have autocad unless they run it and re-boot. As long as
you
> know what the current ADLM server is set to it would be easy to search for
> and replace a given string within the autoexec.bat.
>
> >
> > >
> > >Actually you might be able to get away with the server name game using
> dns.
> > >Since ADLM checks based on dns names and not netbios names you might be
> > able
> > >to simply set your dns server which was pointing at say 10.10.10.10 for
> > >adlm.company.com to 10.10.10.11 for adlm.company.com. Works in theory,
> but
> > >I've not tried it this way. Maybe Jerry will confirm.
> >
> > This potentially sounds like the best option.
> >
> One gotcha on this method would be dns timeouts. If you're doing any dns
> caching you would have to make sure that the updates get replicated before
> the clients started trying to use autocad. As long as it's planned the
day
> before you could set you times outs to something like an hour and then let
> it sit overnight after the change is made and the new dns names would be
> replicated throughout the organization.
>
> hth
>
> jason martin
> frankfurt-short-bruza
>
*martin, jason
Message 13 of 13 (62 Views)

Re:

08-17-2000 05:43 AM in reply to: aekins
I wasn't talking about changing the name of the server itself, just
resolution from the clients using the dns server. Does the auth code for
adlm depend on the host name??? If not you could simply rename the existing
adlm host to something else and then rename the new server to the old
servers host name if needed, without a reboot. (I'm pretty sure you don't
have to reboot to change host names, only netbois names). If the servers
are sitting next to each other the host name change could occur in 30
seconds.

jason martin
frankfurt-short-bruza

jerry milana wrote in message
news:smileyvery-happy:8C2AF60D5F746F8BEA774E67DAD09DF@in.WebX.SaUCah8kaAW...
> H1 All,
>
> You could not have two systems on the network with the same hostname, that
> can create disaster! So, that eliminates the idea of setting up the new
> server then bringing down the old one and ending up with a AdLM server
that
> responds to the old hostname. Sorry, thats network physics ;}. If the @
> symbol is being used OR if workstations are on remote sides of router(s)
> from the AdLM server, you MUST change the ACADSERVER variable on the
> workstations.
>
> jerry
>

You are not logged in.

Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register

Announcements
Are you familiar with the Autodesk Expert Elites? The Expert Elite program is made up of customers that help other customers by sharing knowledge and exemplifying an engaging style of collaboration. To learn more, please visit our Expert Elite website.

Need installation help?

Start with some of our most frequented solutions to get help installing your software.

Ask the Community


Up & Ready Blog

Boldly Install, Configure and Deploy Autodesk Software.

AutodeskHelp Blog

Your one-stop shop for the latest solutions, breaking news, and behind the scenes access to the world of Autodesk support.

Connect with Us

Twitter

Pinterest

Blog

Youtube