Inconsistent AIS (IV/ MDT) NLS setup.

[Anonymous]

Hi today I installed NLS versions of Inventor Series, that mean both Inventor R5.3 and MDT R6
PP.
I started with the FlexLM license Manager on the server, which went fine, without problems.

On the client PC's, I started with installation of the NLS version of Inventor, after Volo View
which is required offcourse, then I continued with MDT as next installation in the AIS_Setup
process.
It apeared that the MDT installation in this process is the C-Dilla version. I discovered that
because MDT asked for a autorisation with 15 days left. Inventor accepted the license from the
FlexLM server.

It is unlogical, if MDT in the same installation process defaults to a softlocked version,
despite the fact I choose NLS setup during the Inventor installation, the MDT installer in the
AIS_Setup didn't ask for NLS install, thats why I assumed that it was so since the entire AIS
package are expected to be treated as one license with one code: softlocked (c-dilla) or FlexLM
based.

As far as I could see after short reading is that I have to run "netsetup.exe" in the netsetup
dir on AIS CD2 (MDT). This is exactly the same procedure as MDT NLS installation in the old
Elan days, with deployment setup. Can it really be true that the installation process is so
inconsistent?

--
Best regards

Lars Sandberg
TechSolution
dba IMAGINiT Technologies

[Anonymous]

Hello,

Yes. If you want to use network version of MDT6, you must use the
netsetup.exe from the Netsetup directory.
Inventor ask if you want a standalone or a networked version.
This is the procedure...

; "TechSolution dba IMAGINiT Technologies" a
écrit dans le message news:
MPG.172ab957cb5ab4379896d4@discussion.autodesk.com...
> Hi today I installed NLS versions of Inventor Series, that mean both
Inventor R5.3 and MDT R6
> PP.
> I started with the FlexLM license Manager on the server, which went fine,
without problems.
>
> On the client PC's, I started with installation of the NLS version of
Inventor, after Volo View
> which is required offcourse, then I continued with MDT as next
installation in the AIS_Setup
> process.
> It apeared that the MDT installation in this process is the C-Dilla
version. I discovered that
> because MDT asked for a autorisation with 15 days left. Inventor accepted
the license from the
> FlexLM server.
>
> It is unlogical, if MDT in the same installation process defaults to a
softlocked version,
> despite the fact I choose NLS setup during the Inventor installation, the
MDT installer in the
> AIS_Setup didn't ask for NLS install, thats why I assumed that it was so
since the entire AIS
> package are expected to be treated as one license with one code:
softlocked (c-dilla) or FlexLM
> based.
>
> As far as I could see after short reading is that I have to run
"netsetup.exe" in the netsetup
> dir on AIS CD2 (MDT). This is exactly the same procedure as MDT NLS
installation in the old
> Elan days, with deployment setup. Can it really be true that the
installation process is so
> inconsistent?
>
> --
> Best regards
>
> Lars Sandberg
> TechSolution
> dba IMAGINiT Technologies

[Anonymous]

In article <0DE9D2A6FF952F674F45910A9600CBEA@in.WebX.maYIadrTaRb>, franck.hervet@aricad.fr
says...
> Hello,
>
> Yes. If you want to use network version of MDT6, you must use the
> netsetup.exe from the Netsetup directory.
> Inventor ask if you want a standalone or a networked version.
> This is the procedure...
>
Hi, thanks for your response. I must say that, in my opinion this isn't very smart or
consistant. I remember for some years ago (MDT R2/R3 or R4) it was possible to copy a file:
tcpip.sys (as I remember the filename) from the Elan dir on the installation CD. And voila the
software accepted to receive the license authorisation from either the NLS licensemanager or
the hw-lock. However in this case I didn't succeed finding a "workaround" for that.

So if anybody did take the time to analyse differences between MDT NLS vs. the C-Dilla locked
diito, whether it is files or registry, I would like to hear about that.

I will certainly wish, that the AIS installer are going to be more consistent in the future.
Just imagine the quite different approaches for MDT deployment-setup vs. Inventor's use of a
MSI based script.


--
Best regards

Lars Sandberg
TechSolution
dba IMAGINiT Technologies