There may be instances where you need to move data from one server to another using a Windows service.  Typically your reasons for doing so are to keep certain files sychronized from a common source - for instance, a content management system may need to push files up to multiple web servers, or a BI engine may need file drops moved to a staging folder.  Whatever your reason, it isn't difficult to setup if you follow a list of basics that need to be accomplished:

1) Create your Windows service that can move files around locally.  If you can do this, then you can move files between servers too.

2) Assuming the above works, then you'll need to setup a common username/password on all servers.  When doing so, make sure the common username has access to all the folders where files are being read and written.

3) Install your service on one of your servers, ensuring that your service is running under common username/password

That's it.  Three steps, and you can move files around between non-domain servers. 

As part of my work, I must document everything.  Being a code monkey it is sometimes hard to change gears between coding and documenting.  When I do get around to documentation there are odd things that happen that make me realize I have been coding too much.  As a result, I've compiled the list below.

This is a list of things that happen to code monkeys when they try and write documentation:

- your sentences end with semi-colons

- you try and delete lines of text with shift-delete

- rather than ctrl+s to save your document you hit ctlr+shit+b to build

- you try and comment-out various parts of your documentation

- when someone asks you for a technical spec you send them the code

- your document headings start with "public void"