I now have SBS-E running with the newest 6.33 beta, and three "clients" in my test network. Runs fine.
I did all you said: C: - operating system only D: - Client backup (another hard drive -- there isn't room on the SSD for the back partition that SBS automatically installs, but I found a wizard that migrated that partition to another drive.) E: - Programs, including AC and MEDWARE. Now I find that after installing MEDWARE into the "company" partition and running it once as "administrator" it will run without admin privileges subsequently. So I no longer have to log in as anything but a normal user. So you were right all along, Bert - I have no clue what was going on in my system before, but it's fine now.
The system with SSD and Xeon CPU is remarkably fast, and even wireless to another machine by remote desktop, to contol a third machine by RD which is connected by Ethernet to the server is about as fast as connecting directly to the server!
The last hurdle is Quest lab. They have to install the lab connector, then I'm ready to go. I assume UpDox just installs their connector to SBS-E like it did to Win-7, but I haven't tried. If I can get them to come in Thursday, I'll be up and running this week!
Thanks for all your help and encouragement. This has been, and continues to be an interesting project.
There still are issues like remote Web access that I haven't addressed, but Remote Desktop seems to work well enough for now, and I'll figure that out eventually.
Backup works slick -- it is totally automatic. All those other bells and whistles you talk about -- Exchange, SharePoint, fax boards and the like. I'm sure that they might be useful, and I might look at them in the future.
However, UpDox works fine for faxing, and until we have a more computer-savvy patient group, we won't need much in the way of electronic communication with them.
