Steven, you can not build on one machine and move a build to your Windows server. With meteor you can do ‘meteor deploy’ which will build and deploy to a server hosted by meteor.com. If you want to host on your own server you can use Meteor Up (mup). Meteor Up does not support Windows, it supports only Debian/Ubuntu flavours and Open Solaris.
So what am I doing? I develop on my Mac computer. I’ve installed Meteor on my Windows server. I then move the source files to the Windows server and start the app there. Yes, it’s running in “development” mode but that’s not an issue for my application. If running with ‘meteor run --production’ the source files are minified.
The meteor application should always be running and it should be able to start and stop it in a controlled way, therefor I made a Windows Service (running as Local System account).
In the Windows Service a thread pool worker thread is started. There I start a System.Diagnostics.Process (a window-less local process, acting like a cmd-console) and the application I start in that process is a .bat-file containing ‘meteor run --production’. All output from the process (what meteor will write to server-side console) will be piped to a file (to a rolling file using log4net).