Heres what we set up for one of our customers who has a shit ton of QB seats and remote access from some really crummy internet connections
The database for QB and the compliment software that uses the QB database sits on w2k8 server (it can sit on a w7 pro machine in a pinch with zero issue) multiple instances of w7 pro. There were always issues with windows RDP so we got them Blaze RDP http://www.ericom.com/ericom-blaze/ (cheap and perpetual license) Everything sits inside Vmvare, full image backups with file level restore using VEEAM Backup. the server instance has 8 cores assigned with 16 gb RAM and the w7 instances have 2x2 cores assigned with 8gb ram. This is a testimonial setup becuse they had so many instances of lost time due to the shitbox internet connections. The print driver virtualization with blaze is phenominal and it naitively suppors multiple monitors, where RDP alone is a cobblefuckery of spanned display hi-jinx that QB does not play well with On Tue, Nov 1, 2016 at 10:40 AM, Josh Luthman <j...@imaginenetworksllc.com> wrote: > +1 to Chuck. I've been running QB on Windows in a VM for a while now, > it's convenient to just RDP. If you need a keyboard/mouse/etc for this > person Maybe a Chromebox or NUC? I'd suggest Chromebox for the speed, but > NUC has Windows for all the compatibility. > > > Josh Luthman > Office: 937-552-2340 > Direct: 937-552-2343 > 1100 Wayne St > Suite 1337 > Troy, OH 45373 > > On Tue, Nov 1, 2016 at 11:22 AM, Chuck McCown <ch...@wbmfg.com> wrote: > >> I RDT into into the machining running a QB client all the time with a >> laptop. As a matter of fact, I use my laptop more than half the time with >> a docking booster so I can have a real monitor and keyboard. >> That screenshot was from my laptop logged into the headless system >> running the client talking to another server running the QB database. >> >> *From:* Lewis Bergman >> *Sent:* Tuesday, November 01, 2016 9:15 AM >> *To:* af@afmug.com >> *Subject:* Re: [AFMUG] OT : Small computer to run QB enterprise with RDP >> >> To be clear, This is not the machine running the DB. That machine will be >> on the network. this is just a box to RDP into so my sales person can run >> QB Enterprise remotely. Bill, do you RDP into QB? >> >> On Tue, Nov 1, 2016 at 10:08 AM Bill Prince <part15...@gmail.com> wrote: >> >>> We ran QB Enterprise on Windows 7 and Windows 10 (both 64 bit). 4GB RAM >>> is probably shy; would recommend 8 at least. The disk space is probably shy >>> too. >>> >>> bp >>> <part15sbs{at}gmail{dot}com> >>> >>> >>> On 11/1/2016 7:53 AM, Lewis Bergman wrote: >>> >>> This is a bright group so I wanted to see if this is something worth >>> doing or maybe worth avoiding. I really don't want to get Windows server >>> 2012 and try to figure out the while terminal services thing with >>> licensing. I was thinking it might just be easier since I only need one or >>> two people to remote in just to get some headless PC's and sit them in a >>> corner somewhere. >>> >>> Probably a bad idea but any thoughts? >>> >>> The specs from QB are: >>> >>> - Windows Vista SP2, 7 SP1, 8.1 Update 1, or Windows 10(32-bit & >>> 64-bit) >>> - Windows Server 2008 R2 SP1, 2012 R2 >>> - 2.4 GHz processor >>> - 4 GB of RAM >>> - 2.5 GB disk space recommended >>> - 1024x768 or higher screen resolution, extended monitor is >>> supported >>> - 4x DVD-ROM drive >>> >>> >>> > -- If you only see yourself as part of the team but you don't see your team as part of yourself you have already failed as part of the team.
