Proper way to handle a remote user for Quickbooks login
-
@tiagom said in Proper way to handle a remote user for Quickbooks login:
Quickbooks install on his computer and vpn into the network that has the quickbooks data.
If he's the CFO, get him a company computer (or laptop) and have it setup to connect to the VPN. Host the database on the network, and configure the laptop to have QuickBooks open this file.
Save nothing locally.
Or, get the online version of quickbooks, and have the local installation on his laptop connect to that with user credentials.
-
Was going to mention that as well. Quickbooks online is always an option.
-
@krisleslie said in Proper way to handle a remote user for Quickbooks login:
I have a newly appointed CFO (never had one before) that will need to use Quickbooks in another state.
Can you still be considered a CFO if you use QuickBooks? That's like being called a race car driver while on a skate board.
-
@krisleslie said in Proper way to handle a remote user for Quickbooks login:
However, I'm not sure its legal to even virtualize a windows 7 desktop in the manner asked.
In what manner, no virtualization was mentioned.
-
@krisleslie said in Proper way to handle a remote user for Quickbooks login:
What would be the smart way to allow that person remote access since they won't have a desktop in house?
If it is really just for one user, either VPN and RDP over it is fine. Or TeamViewer, ScreenConnect, LogMeIn, etc. Lots of people use an RDS server for this, but that's for multiple users.
-
QB over straight VPN doesn't perform well. You'll want a remote viewer system to make it comfortable to use.
-
I would not connect to the DB via a VPN, I have seen to many VPN connects fluctuate and destroy data. A better solution would be to keep it in house by using a Terminal Server and publishing it. That way, should he be disconnected, it doesn't thrash the DB.
-
@gjacobse said in Proper way to handle a remote user for Quickbooks login:
I would not connect to the DB via a VPN, I have seen to many VPN connects fluctuate and destroy data. A better solution would be to keep it in house by using a Terminal Server and publishing it. That way, should he be disconnected, it doesn't thrash the DB.
For a single user, just TV to Windows 7 is just fine.
-
@scottalanmiller said in Proper way to handle a remote user for Quickbooks login:
@gjacobse said in Proper way to handle a remote user for Quickbooks login:
I would not connect to the DB via a VPN, I have seen to many VPN connects fluctuate and destroy data. A better solution would be to keep it in house by using a Terminal Server and publishing it. That way, should he be disconnected, it doesn't thrash the DB.
For a single user, just TV to Windows 7 is just fine.
True, There is nothing wrong with using TV for a single user. As long as you ensure all the proper security measures are taken. Don't want any breaches.
Sorry,.. been working with a DB software and remote users of late, and have the TS on the brain.
-
@gjacobse said in Proper way to handle a remote user for Quickbooks login:
@scottalanmiller said in Proper way to handle a remote user for Quickbooks login:
@gjacobse said in Proper way to handle a remote user for Quickbooks login:
I would not connect to the DB via a VPN, I have seen to many VPN connects fluctuate and destroy data. A better solution would be to keep it in house by using a Terminal Server and publishing it. That way, should he be disconnected, it doesn't thrash the DB.
For a single user, just TV to Windows 7 is just fine.
True, There is nothing wrong with using TV for a single user. As long as you ensure all the proper security measures are taken. Don't want any breaches.
Actually easier than securing it with RDS.
-
@scottalanmiller said in Proper way to handle a remote user for Quickbooks login:
@gjacobse said in Proper way to handle a remote user for Quickbooks login:
@scottalanmiller said in Proper way to handle a remote user for Quickbooks login:
@gjacobse said in Proper way to handle a remote user for Quickbooks login:
I would not connect to the DB via a VPN, I have seen to many VPN connects fluctuate and destroy data. A better solution would be to keep it in house by using a Terminal Server and publishing it. That way, should he be disconnected, it doesn't thrash the DB.
For a single user, just TV to Windows 7 is just fine.
True, There is nothing wrong with using TV for a single user. As long as you ensure all the proper security measures are taken. Don't want any breaches.
Actually easier than securing it with RDS.
That's because - Windows
-
I would vote for just using TeamVIewer if you have it. Keep it simple.
-
@scottalanmiller said in Proper way to handle a remote user for Quickbooks login:
QB over straight VPN doesn't perform well. You'll want a remote viewer system to make it comfortable to use.
Let's be honest here, Quickbooks doesn't perform well ever. Over a VPN, just forgetaboutit. How and what they actually do with company files is nothing short of crazy (you'd be transferring the entire company file over the VPN multiple times while opening/working/closing the thing.)
-
@tiagom said in Proper way to handle a remote user for Quickbooks login:
Quickbooks install on his computer and vpn into the network that has the quickbooks data.
You can't VPN with Quickbooks it doesn't work like that.
-
@gjacobse said in Proper way to handle a remote user for Quickbooks login:
I would not connect to the DB via a VPN, I have seen to many VPN connects fluctuate and destroy data. A better solution would be to keep it in house by using a Terminal Server and publishing it. That way, should he be disconnected, it doesn't thrash the DB.
Honestly that was my premise on moving to Enterprise 2015, but considering online seems to be better suited for the world now since it integrates better with apps, I'm considering the move.
-
@travisdh1 said in Proper way to handle a remote user for Quickbooks login:
@scottalanmiller said in Proper way to handle a remote user for Quickbooks login:
QB over straight VPN doesn't perform well. You'll want a remote viewer system to make it comfortable to use.
Let's be honest here, Quickbooks doesn't perform well ever. Over a VPN, just forgetaboutit. How and what they actually do with company files is nothing short of crazy (you'd be transferring the entire company file over the VPN multiple times while opening/working/closing the thing.)
[Exactly]
I've tried every form of VPN known to man and told Quickbooks support it doesn't make sense the way they built the app for it to be so critical and yet be so frail. -
@scottalanmiller said in Proper way to handle a remote user for Quickbooks login:
ar driver while on a skate board.
I didn't make the title, I just follow the instructions lol. She is a PhD I believe in finance and business so
-
@krisleslie said in Proper way to handle a remote user for Quickbooks login:
@scottalanmiller said in Proper way to handle a remote user for Quickbooks login:
ar driver while on a skate board.
I didn't make the title, I just follow the instructions lol. She is a PhD I believe in finance and business so
and yet shows how likely useless a PhD really is - because.... Quickbooks. Single sided accounting that's so easy to screw with the "books," ect.
-
If you're asking if you can host a Win 7 (though why not Win 10?) VM on XenServer - yes you can. Now the question is, what licensing do you need?
If you have Software Assurance for the laptop you gave the CFO, then you need nothing more. If not, you'll need a VDI license for her, something like $125/year.
-
Wow, not nearly as much QB vitriol as I expected in this thread.