Downgrade NILM from 4.4 to 4.3, possible? To resolve issue with VLM still at 3.1

[DavidBoyd]

Crossposting from the Volume License Management forum, in case this is really more of a package installation problem.)

Found the article here which describes how the local license manager (NILM) release 4.4 is not compatible with Volume License Manager 3.1.

Unless/until I can get our admin to update the license server, I would like to downgrade NILM to 4.3, so I can get my LabVIEW installation out of eval mode.  NILM 4.3 is available for download (as a zip of a standalone installer) but it refuses to install with 4.4 present.  And, in turn, NIPM won't remove NILM without removing most of LabVIEW and tools.  Sigh.

Is there a NIPM-compatible package for NILM 4.3 (and if so I'd fiddle with nipkg CLI to force a downgrade), or some other way I can trick the installers to do what I want here?

Thanks,

Dave

[cflory]

Some NI product packages have dependencies on other product packages with specific version requirements. If a particular product has such a version-specific dependency, then it is intended to be removed when one of its dependencies is removed, since it won't run without it.

[DavidBoyd]

cflory,

I get that there are version dependencies, and it is pretty obvious that a development environment installation (LabVIEW plus addons) requires a license manager to be present.

But just look at the present predicament.  NI released an updated LM and apparently testing missed that its functionality with existing VLM was broken. So they released a patch to VLM (3.1.1) followed by a new release (3.2).  But end users aren't always in control of the volume license administrator role.  (Well, I'm not, anyway.)

A package release of NILM 4.3 with the ability to downgrade an installed NILM 4.4 is really what is needed here until all VLM installations are upgraded.

Dave

[GreyGrey]

What IDEs are you using? Also, which version of those IDEs are you using?

[DavidBoyd]

Brandon,

LV 2019 (32 bit).

I changed employers recently, so I'm starting over in terms of getting my development environment set up.  Though I preserved my NI profile by swapping out email addresses, I ended up downloading the current release of everything as an eval (no other choice when you don't have an identity as an SSP holder).  I got connected to Abbott's enterprise license server after the fact.  Unless/until Abbott's admin upgrades VLM on the license server, I'm stuck in eval mode... or else I must uninstall everything and download a release with the older version of NI license manager.

This would've been easier when I *was* the VLA, back at the prior employer.

[BoKnows · Accepted solution]

David,

Brandon asked that question mostly hoping you wouldn't provide the LabVIEW 2019 answer.  LabVIEW 2019 is reliant upon NILM 4.4.  

Would it be alright if I sent you an email to see if we can find a resolution that gets you out of eval mode?

[DavidBoyd]

I'm happy to take any solutions under consideration at present.  If you can't get it from my profile, my work email is now david.boyd1 at abbott.com.

If LV2019 requires NILM 4.4, and NILM 4.4 (under a VLA) requires VLM 3.1.1 or 3.2, then logically anyone under volume/enterprise licensing who installed LV2019 would experience this issue, unless and until their license admin also updated VLM.

Dave

[kpitts27]

How about if you are still using LabVIEW 2018? Is there an easy way to downgrade the License Manger?  Our IT says I have uninstall all of LabVIEW 2018 and that it isn't easy.