Your approach sounds awfully bad. Multiple processes means considerable overhead not justified by anything; you really should prefer threads. Also, I'm not sure you should have many separate threads; threads are also should be reused, but I know too little about your goals and required operations to advice on further detail.
Why console application is bad? Because of… console. Why would you need it? It's not a problem: you can create a non-console application, without any windows at all. But do you need the process to execute when the user logs off? If the answer is "yes", you need to develop a Windows Service.
See also my past answer on development of dual-mode applications, behaving as interactive application or as the service, depending on how you host it:
Configure Windows Service with UI[
^].
Why doing so? Debugging! Debugging of the service is much harder, so you can move most of the debugging in interactive mode. How about this idea?
See also my past answers:
Configure Windows Service with UI[
^],
Windows services Error[
^],
http://msdn.microsoft.com/en-us/library/zt39148a.aspx[
^],
How to install windows service programmatically[
^],
How to start the application before user login to the System[
^],
Automatically start my c# application when i start my computer[
^].
—SA