There are workgroups and domains. Once you install SBS Essentials and connect to it using the Connect feature, you are now part of a DOMAIN. That small network is now a client/server domain. This is why I constantly say that client/server is simply P2P with a fancy OS until you connect to it with Active Directory and make it a domain, hence the name TEST.domain.local. I hope the .local is at the end. As Steven says, he uses his as P2P, not a domain.
You can't go back and forth. Well you can by changing to a workgroup and rebooting, but then you are back to your plain computer and on your other network.
Once you connect the way you did (the correct way), you essentially have two different networks.
The whole idea of connecting to Essentials and having a domain is to have all the benefits of being on a domain. In this instance, no offense -- but in order to explain it, P2P 1 point, domain 100 points. THIS IS NOTHING AGAINST P2P JUST AN EXPLANATION. And, it certainly makes it a little more difficult, at first.
This is why I said (I think) to add a client to it. Remember, this is a test. To install Essentials only would be to see it, play with it and at least see what it feels like. To add a client to it USING THE CONNECT METHOD, as you did correctly, is to make a network that you can see. You can always go back by going to:
System Properties | Computer Name tab | Change | Click Workgroup (unchecking Domain) | Type in Workgroup name of your network | Follow the prompts and reboot (MAKE SURE YOU HAVE THE PASSWORD TO THE WORKGROUP COMPUTER.)
WIN 7 now has a wizard above that. I haven't used it, but it looks like it would work much smoother.
One thing you should do just for fun is bring up a command prompt and type >ipconfig /all and compare it with an ipconfig /all of a workgroup. They will be different, and you will see you are on a domain with the domain name and the domain info of your server.
I think we misled you a bit and will hear back from the naysayers. Installing Essentials is relatively simply. Making your network is considerably harder. Actually, that isn't fair to say. Making your network is easy. Look how easily you used Connect and made a domain network. You now do have a domain network (if you stop switching back and forth). This is a TEST. You test it like you did, kick the tires, just see what it is like and get the hell out. LOL. This is also why I, personally, would never suddenly change from a peer to peer to a domain by myself for the first time. And, I didn't. I used someone with considerable networking experience. I had to be set up properly, because while it is MUCH easier to use in the long run, things like DNS and Active Directory are tricky in the beginning.
CURIOUS:
Do you not have email at your office? Why would your patients be any more likely to be able to email you on Exchange than on your current email. Email is email. tomastoria@youroffice.com works just as well as tomastoria@yourdomain_name.com
You don't need Exchange. But, it doesn't make you more vulnerable; it makes you more secure.
PS All in all, I think you did fine. I think all you did wrong was to panic when you say that the client computer was now on a domain and not on your P2P network. But, you would NOT want to change over to a domain network by yourself. It's not that hard, but there are just things you need to know. IF you were going to try it (which I highly think you shouldn't), then get TRAIN SIGNAL. You can also use Sandeep's videos, but research it.
