What do I need to consider when installing labview on a virtual windows machine?

[Hooovahh]

---

@PhillipBrooks wrote:

I would use the opportunity to design a test station using cDAQ/cRIO and LXI.

---

This is a great solution.  I can't use a Windows PC connected to your network?  Fine I'll make my own network with my own PC running my own software.

[Joseph_Loo]

In my world, it does not stop IT from interfering. Right now the only thing is to change the OS from other than windows.

[EWTech]

"I would use the opportunity to design a test station using cDAQ/cRIO and LXI."

Actually that is where we are headed here at our lab, at least for FieldPoint units. Since there are only drivers for Windows there is no point in not using Windows as part of the solution. We also inherited a heck of a server that has more resources than I've ever had in this lab so I'm going to vertuallize, test and if this works as expected deploy this onto our network. We eventually will be forced to use an RIO solution but since the hardware is able to continue to be maintained we'll stick with what we have.

[Esteban.R]

Hi EWTech

I think that I did not understand your question or issue; Could you provide us with more information?

I might recommend you to create a new thread so that your question might have more visibility.

Regards

Esteban R.

[EWTech]

For Ethernet connceted devices such as LXI and FieldPoint the virtualized machine seems to work fine for already working code. This allows us to virtualize the environment under RedHat for use for other infrastructure on the same hardware. We have a retasked Proliant Gen 65 rack-mount serverwith eight cores and 16 GB RAM that can take up this task rather nicely. It also allows for management of a single server rather than several at once. Assuming we can purchase a couple of Windows 2008 Server licenses for the guests we can add two separate virtual servers to do what we have been doing with much lesser hardware for the last 5 years.