Digger, yeah, that's what I'm figuring too (about accounts). Only reason I tried it was cause as I was reading some documentation on HomeGroups (some part of the Windows 7 help file, don't remember where), it mentioned using HomeGroups with Remote Desktops. Seemed odd to me for reasons you mentioned in last post, but thought I'd give it a try. Was only reason I even setup a HomeGroup on my LAN actually. Since I couldn't get it to work, I thought I was doing something wrong. Your insight backs up my own initial concerns and now I'll consider my curiousity satisfied.
Jimbo, I could share the burner across the network and then use burning software on the local computer to use it.
However, that would still require me to run the burning software on the local machine.
It would require me not to reboot or power down the local machine.
Depending on how resource intensive the software is, it could impact performance enough to matter to me. Remember, my local machine is my gaming rig which has had every possible tweak done to it to gain performance. I don't even install Adobe Reader on here cause of the very small launcher process it loads at boot. I just remote into the other PC and read PDFs there. With the newest 7 build, I found out I can actually play videos on the remote machine and watch them with equal FPS as if I played them locally.
And then there's the network clog. The files I want to burn are local to the burning computer. If I made the burner shared, and the drive with files shared, I'd be pulling the files to this computer, then pushing them right back again to the burner.
I agree to simply access resources, network shares are the way to go. Absolutely. In this case, the resource I want to access is the processing power of the other machines. Remote Desktop is the network share I'm using for this.
I'm liking this discussion with you though, Jimbo. It's giving me ideas for a few other projects. Any other advice or suggestions you can give?