![]() I've heard employees complaints about they don't connect right away it takes several tries it's slow it freezes it shuts down. ![]() I'm thinking about working from home, but the issues and complaints have made me leary. I am an employee, what steps should I take to make sure I have the minimal requirements to work from home? Is this a question the IT department can answer? That said, I continue to cram as much into asynchronous cloud services and avoid VPN and RDP as much as possible. We used to make house calls but it wasn't economically viable with the amount of variables involved (poor internet, various routers, employee entitlement, distance, etc.) If someone can't connect, I ensure our services and connection are up but past that it's up to the user. ![]() The only exception here is work travel, but even then our Marketing staff is wising up and avoiding places with junk wifi. If the user wants to be a dedicated remote employee, they demonstrate that they can handle it and purchase adequate office resources to do it right. If the user can't handle the perk of working remote, they show up to work. In either case the onus is on the employee to have their endpoint working, deal with limitations (occasional disconnect), and know some basics of troubleshooting. Working remote is either a perk or a job requirement. Normal SMB file transfers are virtually unusable though with my low upload speed. My speeds are 15mbps down and 1mbps up on a basic TWC cable package.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |