Slashdot Mirror
Creating A Virtual Office?
Fubar asks: "My small company of 10 employees is considering letting our lease run out on our office space and is thinking about having everyone work from home (or wherever they want). I have been tasked with putting a plan together to provide voice and data connectivity to each employee. What sort of solutions have you implemented?"
I'm considering the following for providing voice service:
+ Order an extra analog line for each employee
+ Reimburse each employee for a second line on their cell phones
+ Host our current phone system in my home office, add a VoIP card and provide an endpoint for each employee
+ Use third-party VoIP hosting service" What options have you used to create a virtual office, and what suggestions would might you give to anyone else attempting to do the same?
+ Order an extra analog line for each employee
+ Reimburse each employee for a second line on their cell phones
+ Host our current phone system in my home office, add a VoIP card and provide an endpoint for each employee
+ Use third-party VoIP hosting service" What options have you used to create a virtual office, and what suggestions would might you give to anyone else attempting to do the same?
I would create my virtual office in second life but I'd be afraid that giant wieners would run through my lobby and scare away my customers.
Want to improve your Karma? Instead of "Post Anonymously", try the "Post Humously" option.
Those employees had better be damned dedicated to the company if no centralized physical space exists anymore. You will find yourselves meeting in a lot of places. Maybe just downgrade the space to something like a meeting room you can rent a few times a week.
Communications:
1. VoIP (something like Packet8) or company-paid cell phone, probably a nextel group plan. Actually, Skype conferencing should work good enough.
2. Workstations - Windows Server 2003 Terminal Services Server. Then you don't care about what their workstations are like and the environment is manageable so you have no backup headaches.
3. In-person lunches at least once a week. It can get really boring to work from home!
I implement virtual offices all the time, so feel free to contact me through my website.
Good luck.
Leonid S. Knyshov
Find me on Quora
By isolating people you make social workings of the company impossible. You can't have face to face meetings, you can't casually walk up to someone and sketch a diagram or two, you complicate things that don't have to be complicated. IMO, you will lose far more in productivity than you gain in giving up the office space. How many companies do that? Hardly any; even one-man companies often maintain an office which is their public face - where they have an address, where they meet visitors, where they make phone calls, where they are a business. And at home they are at home - relaxing, reading, having family etc. Mixing work and home is bad. It's even difficult to work at home, where other distractions are present.
I wouldn't do it as many people remote work as goof off work. My experience is at most 25% of the people really work at home, and they are the ones absolutely passionate about what they do. Traits successful to work at home:
If the person can't demonstraight the above at the office, it will only become worse working at home.
So your major question should be are your staff suitable? My guess is some are, and many not. I am going through this with a consultant right now, he shows a low connect time, no results and is precisely a day away from being fired. Be prepared to do this for a lack of performance.
First of all, consider to rent a cheaper place.
Personally, I don't like having my whole office at home. In my case it's not about children or other sources of noises but I don't feel "at work" sitting in front of my PC. I would require a separate (and quite) working room to be productive.
Continuing with noises - if some employees have a quick question they'll call each other. This may be very disturbing.
Next, consider putting in cost for connectivity. Not only phone lines and a phone server, you will need a central VPN server to share files.
Then, think about security. You don't have any control about the employees PCs anymore. I could bet that there are an easy target for malware. Think about that the computers may be used by other people, like their kids. Don't wait for a "Cool I ownz sensitive data of that company - letz put on myspace to show how coolz I am!" to happen.
Last point is, where to meet up with customers? Tell them you not have an office and meet at Starbucks?
Seriously, have a look around for a cheaper office.
Tech support uses it sometimes with remote control yielded by a customer (through their Java client) to check the reported problems with our apps and their system config. One can even look, with customer permission, in real time into remote threads (Dr. Watson style hex dumps), all windows (a la SDK Spy++), apps, dll's, memory heaps (layout and hex dumps). These latter low level features are usually done when tech support guy has to conference in a programmer into his tech support session to help out with some trickier problem. In 1990s, I used to travel to customer locations to do this kind of troubleshooting.
I have set up and supported remote sites and home based telecommuting. Listen to my advice, listen very carefully and save your sanity.
If your organization is large enough then it is likely that you will have a few older desktop PCs that have been or are due for replacement during an upgrade cycle. PCs that are inadequate for Microsoft XP and Office2003 are more than powerful enough for many current versions of Linux, especially for the role of server. Also second hand PCs with the required specifications are very cheaply acquired.
1) Find an older PC, at least a PII 300 with 256 MB memory, to set up as a headless ( no display or keyboard ) server and firewall. A simple web based interface ( or even an external hardware push button ) can be used by the local users to start/stop the server and internet connection. All other maintenance should be handled remotely via ssh, webmin and VNC.
2) Install a second NIC or connect the modem directly to the server. Connection to the Internet should be through the server and connection to the Office should be through a VPN on the server. Use a dynamic IP service for each site so you can remotely log on to the local server via ssh.
3) Install a new IDE hard drive in a 3.5" removable rack and tray. The drive should be than big enough for the operating system (Linux of course) and copies of some of the local desktop partitions. A telecommuter can shut down the server and bring in the drive during the day to resync and repair.
4) Install a DHCP demon on the local server to allocate local IP addresses, DNS and gateway settings. If the desktops are network boot capable then install TFTP to remotely boot and use Knoppix via PXE and the network. If the desktop OS is constantly crashing, or is infected by malware, the user can select PXE/network boot via the BIOS, and boot into Knoppix. The user can then be instructed over the phone to enable the ssh server to allow remote scan,repair and reimaging of the desktop partitions. The user can use the Knoppix desktop to continue working with full access to files while the the remote administrator fixes/reimages the drive in the background.( Consider hiring someone who knows how to customise Knoppix or another live Linux system for your setup )
5) Partition the desktops with as small as required C: partition ( or in the case of Linux the root partition ) for software. When software is install, use dd and netcat via live Knoppix to copy/clone a snapshot of the partition to the server. You can allocate the remaining free space as a persistent partition where documents are stored.
6) Install and enable remote VNC service on all the platforms, but only allow incoming connections from the local server ( which is redirected over a SSH tunnel ).
7) For local backup, create share directories on the desktop accessible by the server. On the local server create loopback encrypted file systems, unmount and copy the images to the desktops shares in chunks, using redundancy if enough space is available on the desktops. Checksum ( MD5 is enough ) each piece.
8) If the network load to the Office is taking up all the available internet bandwidth or the connection is just too slow then install proxy servers on the local server. You can also consider using a distributed filesystem ( OpenAFS is still the best ) wi
If you are near a community college, you might have more meeting options. Many community colleges support small local businesses directly. While I cannot guarantee that the closest college to you has all this, these are fairly commonly available:
Meeting rooms in their libraries or other facilities that can be used for free or rented for a nominal fee.
Rooms with podiums, video projectors, and even computers that can be used or rented.
Small business support centers with specialized facilities and support options.
Access to costly online research databases available to community patrons.
Cafeterias that can internally cater meetings.
With more than 3,000 community / technical colleges across the US, there might be something near you. Many times, even though the college itself might be distant, it might have a local campus or branch with some of the options above.