Anders Björk Posted March 20, 2013 Report Share Posted March 20, 2013 Do any of you have any experiances on running LabVIEW on 2012 or 2008R2 Server? Quote Link to comment
JackDunaway Posted March 20, 2013 Report Share Posted March 20, 2013 The problem domain of deploying to and developing on a remote Server instance has challenges and nuances not present on desktops and local VMs; yet I have not run into inherent problems or incompatibilities between LabVIEW and Windows Server 2012 (or 2008, when i used that). Are you concerned about something in particular? Quote Link to comment
Anders Björk Posted March 21, 2013 Author Report Share Posted March 21, 2013 (edited) The problem domain of deploying to and developing on a remote Server instance has challenges and nuances not present on desktops and local VMs; yet I have not run into inherent problems or incompatibilities between LabVIEW and Windows Server 2012 (or 2008, when i used that). Are you concerned about something in particular? Which challenges and nuances have you encountered? We will be very seldom physically at the machine for instance, almost every will be done of remotely. Edited March 21, 2013 by Anders Björk Quote Link to comment
Anders Björk Posted March 22, 2013 Author Report Share Posted March 22, 2013 In addition, we are aiming almost exclusively to run prebuilt executable on windows server and also only have one user/administrator account. Jack do you believe we will run into the nuisances that you have encountered then? Quote Link to comment
JackDunaway Posted March 22, 2013 Report Share Posted March 22, 2013 Which challenges and nuances have you encountered? We will be very seldom physically at the machine for instance, almost every will be done of remotely. The most real challenge has been simply interrupted cognition and lost time waiting for things to happen -- connections over RDP are oftentimes klunky -- it feels like I'm always switching between engineering and devops mindsets, and this thread swapping is inefficient -- these are purely anecdotal issues, YMMV. My best advice is to jump right in with what you're trying to do, and post specific issues as you run into them. (Also, it sounds like you're making the good choice to develop locally, then deploy the executable remotely. After walking down the path of attempting to develop remotely, this was far too burdensome due to the latency of RDP -- I could never get into 'the groove') Quote Link to comment
Anders Björk Posted March 24, 2013 Author Report Share Posted March 24, 2013 Thanks Jack for your input! I have made changes (and some rather large) to some systems over RDP on XP. I agree can be real challenging with the delays when developing. Quote Link to comment
Steen Schmidt Posted March 30, 2013 Report Share Posted March 30, 2013 Ditto to what Jack says. Almost no compatibility issues between Windows Server and LabVIEW anymore it seems, except for one: A few times on 32-bit 2008R2 we've had to disable PAE on the server to get the LabVIEW application to execute without errors. TestStand can be more tricky, if you ever want to use that on Windows Server. But development is not possible over a remote connection. I think that's universal unless you're a very peculiar developer ;-) /Steen Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.