|I want to have a domain server at home and then 2 sites with PCs just switching logon and connecting straight though to the domain pulling policys down etc. |
First consideration (as I see it).
This is exactly the wrong way to do this. You're going to clog up WAN links with unnecessary traffic. Put a DC in each location and let clients authenticate to it and receive policies from it. WAN links should only be used for syncronization traffic between DC's.
Also, doing this from home?!?! I'm sorry but, if these two remote sites are a business, then this should be setup in one or the other as you can't provide decent protection and bandwidth in a home environment. Do you have proper AC at home? How about UPS and power conditioning? Do you have a rack? Do you have a managed L3 switch at home?
Well I have done some VPN but not on this scale and I think they want it doing cheap!!!!
The way I've always seen it is, you have two choices:
1) Do it cheap
2) Do it right
Doing a job the right way means less hassles in the long run. With proper planning you leave yourself setup for growth and by employing the KISS principle, less problems troubleshooting issues that will arrise. Notice I said "will" and not "might", problems always crop up.
Once I broke it down I think it be easier but if yopu were me how would you go out it? like the setup VPN
If it were me, I'd be offering professional, mid-grade to enterprise level solutions. If they want "cheap" I'd refuse. I don't do cheap, I won't support "cheap" and, I won't even come in and fix someone elses "cheap" without charging an arm and a leg to do so. "Cheap" is just not worth the headaches and hassles IMHO
In all honesty, you'll probably find it very hard to do a mesh VPN on the cheap. I know of no SOHO level equipment that could provide reliable multipoint encrypted VPN's.
It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.