Secure Desktop Access from Anywhere - continued

The fine print
To use uRoam, browsers must have access to port 443 (SSL); this is typically not a problem. But desktops must have inbound access to ports 443 and 661 (the uRoam Host Control Protocol). This can be an issue for desktops located behind firewalls; some companies have policies against opening or forwarding inbound connections.

uRoam is compatible with dynamic IP addressing and network address translation—it even assigns temporary hostnames to facilitate access. But desktops must be reachable through public addresses, and many corporate LANs use private addresses. Some users may circumvent this by forwarding ports from a public router or firewall to a private desktop. Those who cannot do so must wait for uRoam's Enterprise service, scheduled for release at year end.

uRoam can wake a "sleeping" desktop and arbitrate simultaneous local and remote use. However, when a remote user unlocks the desktop, anyone back at the office can watch the PC's monitor or use its mouse and keyboard. This can be a concern for companies that require password protection against unauthorized access to unattended PCs. Running uRoam desktop software as a service will address this problem—a planned, high-priority addition, according to Sokolsky.

Expanding the target market
uRoam's initial service is designed for small to medium businesses requiring secure, roaming access to entire desktops and networked shares. By leveraging the ubiquity of Internet access and browsers, and adapting to the peculiarities of wireless PDAs and smart phones, uRoam caters to the net-aware corporate traveler. As my colleague David Strom, an early beta user, said, "uRoam really solves the 'but I left that file on my other computer' problem easily and elegantly. Especially these days, when may people have broadband connections, uRoam makes it simple to move around the world without having to tote along all your data."

uRoam plans offer additional services, based on the same technology. In mid-October, I took the new Guest Access service for a test drive. Now in beta, this service grants one-time access to the entire desktop or just one folder - again, from any device with a browser. The desktop owner enumerates guests by email address, specifying access rights and connect time. A temporary URL and password are generated for each guest. Guests connect to the desktop over SSL. The desktop owner can monitor connected guests and terminate sessions at will.

Guest Access is a promising variation on uRoam's initial service. It might be used to make an on-line presentation or collaborate on a document with a business partner. I'd tweak this beta by adding read-only guest access and discouraging temporary password distribution via clear-text email. Additional weblets and refinements are likely before this service is released at year end.

uRoam is also developing an Enterprise service to facilitate large scale corporate deployment. This service will eliminate the requirement for public IP access to desktops, and will support centralized software administration, control, and monitoring. In other words, adapting single-user uRoam for deployment by IT organizations.

Service rollout
According to Finnerty, "uRoam's initial play is to channel partners—broadband providers, ISPs, and CLECs who want to resell our branded service to their own SMB customers, either standalone or as a bundled offering." uRoam also licenses its technology to strategic partners—for example, desktop and wireless device suppliers.

The uRoam value proposition: Partners can expand service offerings to generate incremental revenue, differentiate themselves from competitors, and reduce customer churn. Partners determine their own packaging and pricing, but uRoam provides accounting data sufficient to charge by session or connect time.

uRoam generates revenue through licensing, setup, and hosting fees, negotiated with each partner. During setup, the partner's brand is added to uRoam web pages. A scheme is implemented to redirect requests from the partner's server to uRoam's server for session establishment. Sales and product training are provided by uRoam. "A 45- to 60-day rollout timetable is expected to be typical, although the uRoam portion of this is nominal," said Finnerty.

uRoam elected to go B2B rather than B2C so that it could focus on meeting partner needs—for example, by creating new weblets and supporting additional browsers. "uRoam may eventually sell direct to consumers, but that's at least 12 months down the road," said Finnerty.

The first uRoam partner: RCN
On August 21, 2000, uRoam announced its first channel partner, the RCN Corporation (http:www.rcn.com). RCN is a facilities-based provider of bundled local and long distance telephone, CATV, and high-speed Internet services. Its high-capacity broadband fiber optic Megaband Network targets 44 percent of the US residential communications market. RCN licensed uRoam's technology to create a private label service offering.

Finnerty expects to announce further uRoam partners by year end, including a top-tier ISP, two CLECs, and a major computer manufacturer who plans to ship uRoam-ready handheld devices.

uRoam leaves the starting gate with proven, innovative technology. As it transitions from a nine month field test to commercial deployment, the pressure is on to perform—and to deliver promised extensions. To say that diverse challenges may be encountered during large enterprise deployment is an understatement. The next six months will be especially telling.

If uRoam were simply riding the WAP wave, I'd be less enthusiastic. But uRoam stands to benefit from growth in broadband access, an increasingly mobile workforce, a generation obsessed with peer-to-peer computing, and—above all—our ever-present thirst for convenience and simplicity.

—End

return to page one