My vote is to keep it together. As we move forward, I would imagine we will do some branching and it would be easier to branch say a .5 version with everything, rather than have to go to separate repositories and do it.

Hmm, perhaps it makes sense to keep as much of the interrelated things together as possible for now, so that breaking changes are more readily apparent? Exceptions to this may be if the things being broken out would require additional installation steps that would otherwise slow down the setup for the main server, or if it really makes sense to separate the ownership to the extent that different people will be maintaining/fixing breaks that are incurred from other peoples' submissions, or if a branch is needed because pending changes are significant enough to warrant checking in something known to be broken as refactoring/experimentation continues.

However, upon reading again, it sounds like the main motivation here is to have a second .sln which houses the Remote Admin Console. If this is the case, I'd recommend just having another .sln file housed in the same repo for simplicity.