Developing LabVIEW without Windows 10 OS Admin Rights

[Mark_L]

Our IT department is transitioning us from Win 7 to Win 10 OS. As part of the update, we will no longer have admin rights to our PC's due to security reasons.

Some of you may have already gone through this and found some answers. One answer that is not acceptable of course is to give all the engineers admin access.

I am thinking we can work a way out to install LabVIEW and the Tool Kits (and VIPM,...).  These can be well known and on a list that IT can track.

What I am also concerned with is running various test executables that we make.

Does anyone have some helpful feedback for me?

[Mancho00]

My only input would be that, yes you'll need admin rights to install LabVIEW, toolkits, etc., but I have yet to run into a situation where I needed admin rights to build or run any executable I've developed.

[Yamaeda]

It works fine, mostly. Once LV is installed no admin is needed, the next time you'll need it is when running any Installer you've done. 🙂

/Y

[RTSLVU]

Frankly the best plan is to just beat them at their own game. 

A day of troubleshooting a new executable involving calling our IT department 20+ times in one day to have them send someone over to install the new executable on the target machine quickly brought a similar Windows 10 lockdown policy to an end at my company.

Now we have a whole separate class of computers labeled "Lab Computers" these computers all have the same login user and password, with administrator privileges, and none of the corporate security policies are pushed on them. They also can not login to the corporate domain or access any of the network resources or sensitive company data.