We are looking at upgrading our hardware and software associated with our data collection to a server 2008 platform running LoggerNet Admin.
Is this appropriate?
Is there any reason or consideration that we should be aware of?
Also the question has been asked of 32 vs 64 bit operating system. can loggerNet run on servers 2008 R2 (IT prefered system)?
cheers for comments or suggestions
The released LoggerNet 4.0 was not officially tested on Windows Server 2008 and thus is not officially supported on Windows Server 2008. I know of CSI customers that are successfully running it on Windows Server 2008 however. Based on CSI customer feedback, the more "hardened" the Windows Server 2008 platform is the more tweaking of the Windows settings is required.
I know this is an old thread, but just in case someone comes looking, I'll add my experience.
LN 4.0 works fine on Windows Server 2008. Most everything works fine on Windows Server 2008 R2, but RTMC tends to crash and hog the CPU. This probably has something to do with the fact that R2 only comes in a 64-bit version, whereas LN is a 32-bit application. I could be wrong here, but this is based on my observations.
I just installed WS 2008 R2 on my LN server, but I'm switching back to WS 2008 due to this issue with RTMC.
This thread is old...
I'm guessing by the lack of communication Windows Server 2008, probably 32-bit is the platform of choice.
Please let me know if there are any plans to rebuild for the newer 2008 R2 64 bit platform.
Just a follow up on this
I am still running on a windows server 2007 (32bit) OS
I just tried an install onto a virtual machine running servers 2003 R2 with a few downstream complications (not related to loggernet but likely to be 2003 associated).
Was asked the question again as to "why not 2008 R2"
any update on the support for the 64 bit OS?
I see a new update for loggernet is due, will this support such OS's?
looks like 2008 R2 should work given above comments and RTMC is not used on our system so might ive that a go
Just a follow up on this
I am still running on a windows server 2007 (32bit) OS
I just tried an install onto a virtual machine running servers 2003 R2 with a few downstream complications (not related to loggernet but likely to be 2003 associated).
Was asked the question again as to "why not 2008 R2"
any update on the support for the 64 bit OS?
I see a new update for loggernet is due, will this support such OS's?
looks like 2008 R2 should work given above comments and RTMC is not used on our system so might ive that a go
LoggerNet is a 32-bit application, but many people run it in a 64-bit environment (I have a work and a home computer, both running LoggerNet on a 64-bit OS -- albiet Windows 7). As previously mentioned, we do not specifically develop and test for Windows server computers, though we do have customers who run successfully in those environments and we occasionally will test those OSes.
If you run into issues on server OSes, it is often due to permissions inherited from the network.
There are no plans to move LoggerNet to a 64-bit application -- there are just too many 32-bit OSes available to make that move.
Dana
Yeah, I have Server 2008 32-bit hosting LoggerNet and it does work. I do have to say I'd recommend LOGGERNETADM from the start instead of just LOGGERNET, because the ADM version will run as a service, and does not need to run on a console in a logged in user account.
The people in the data center that have this system hosted in a virtual server environment were confused by the idea of a requesting a 32 bit environment, and that I think is the source of this question.. Basically if you're bringing loggernet into a large enterprise or organization that has an IT department, at this point the standard for a Windows Platform "host" is a 64-bit Server OS.
Update
Successfully running Loggernet Admin on Servers 2008 R2 but not without issues, all relating the servers 2008 permissions.... what a drama especially not been of IT background.
thanks for the replies
Server 2008 R2 is a 64-bit OS, hence LoggerNet will run in the automatic 32-bit emulation mode. As PPeters points out, installation of LoggerNet on 2008 R2 is not as simple as running the install program. Because of the way that the R2 OS is designed, you should consider the installation of LoggerNet to be a task for a Server Admin/IT professional or someone with a related background. The gist of things is that the server itself has to be configured into a web-enabled (TCP/IP enabled) mode, and then the "Roles" feature of R2 has to be utilized, as well as an update made to the DOTNET framework to a recent version that is compatible with LoggerNet. The DOTNET portion of Loggernet's installation therefore becomes a separate "Admin" task.
Of course, the user is "on their own" for all of this since this is not an OS officially supported by Campbell Scientific.
Has anyone had experience running LoggerNet LOGGERNETADM on Server 2012? Does anyone expect issues?
Thanks, -Mike
The prospect of the Linux version is looking more and more appealing.