• subscribe
February 01, 1999 12:00 AM

The Right Tool

Windows IT Pro
InstantDoc ID #4792
Personal Access Devices and PCs

My next-door neighbor Tom has the right tool for any conceivable job, and he's always willing to help me get a job done and lend me his tools. Whether we need an odd-sized wrench or a special chisel made in the 1920s, Tom has it. His tools are simple, reliable, and well adapted for their intended purpose.

Unlike Tom, we in corporate IS try to use one tool, the PC, to do everything, and PCs are anything but simple, reliable, or well adapted. No wonder end users are purchasing a variety of personal access devices (e.g., PalmPilots, the Franklin Rex Pro PC Card Organizer, hand scanners, Windows CE devices, and computerized watches and phones) for specialized tasks. These devices are proliferating in IS environments. Microsoft's Gordon Bell predicts that by the year 2000, the number of such personal access devices will approach the quantity of all corporate PC desktop systems. The number of these devices will grow 30 to 40 percent faster than PCs, and by the year 2003, they will outnumber corporate desktop systems.

Even Windows NT is following the trend toward specialization and getting into the embedded market. As Windows 2000 (Win2K—formerly Windows NT 5.0) approaches 40 million lines of code, embedding a small portion of the OS into a dedicated device makes sense. The antidote to bloatware is simplicity and reliability. Network Engines, for example, makes a Web server in a box that includes embedded NT Server, Internet Information Server (IIS), replication, and clustering hardware and software. You can connect up to 256 servers into one cluster and manage all of them from one location. To add a server to the cluster, you just connect it. Replication and clustering services start automatically. This product provides true linear scalability in a simple, reliable form that is adapted to users' needs.

Providing Support
So how do IS professionals deal with specialized and personal devices? Ignore them and hope they go away? Refuse to support them and ban them? Perhaps the best way to deal with personal devices is to incorporate them into our hardware strategy.

If we want to provide support for these new devices, we first need to require a solid replication strategy to prevent users from stranding islands of important business data on their personal access devices. If Microsoft Outlook is your corporate groupware standard, you can replicate changes to PalmPilots or Windows CE Personal Digital Assistants (PDAs) by using Puma Technologies' Intellisync software, for example. This product replicates data from the corporate network to the laptop and then to the personal device. No data ends up stranded, and users have a backup of all data.

Next, we need to ensure network connectivity. Each device must connect easily to the corporate network or to a device (such as a laptop) that is currently connected. (Soon, we'll probably have to provide wireless connectivity to all these devices. Can you imagine surfing the Web while driving on the freeway?)

Third, we need to make sure that we can update applications easily. Accessing all the PCs around an organization for upgrades is hard enough, let alone accessing all the personal devices sitting in users' pockets. But where there's a will, there's a way. With a PalmPilot, for example, users download a new application to the PC first; then, the next time the user does a normal synchronization, the application loads onto the user's PalmPilot.

What Do You Need?
So what is the best device strategy for your network? At Windows NT Magazine, we want to know what type of coverage this issue requires. Like my neighbor Tom, who always has the right tool, I want to give you all the tools you need to do your job.

Do you want us to ignore all these personal devices, or do you want articles and product reviews about them from an administrator's point of view? How can we help you manage these adaptive devices? If you need a strategy or if you already have one, I would love to hear from you. Perhaps your letters will result in an article about best practices. Meanwhile, we'll keep you posted on our discoveries, focusing on NT connectivity and administration.



ARTICLE TOOLS

Comments
  • Claude Albertario
    13 years ago
    Aug 06, 1999

    In February’s editorial, “The Right Tool,” Mark Smith asks whether readers need articles and product reviews from a systems administrator’s point of view about personal access devices. Asking this question is like closing the barn doors after the horses are out!
    I’m the technical director of the
    Pulmonary and Critical Care Medicine department of a teaching hospital on Long Island. I see the medical field as overripe for the use of Personal Digital Assistants (PDAs) and the like. We’ve been using 3Com’s (formerly U.S. Robotics’) PalmPilots since their introduction in 1995, and presently we’re using them in a Microsoft Exchange Server environment with Microsoft Outlook clients on all departmental desktops and laptops. This setup lets us share doctors’ schedules and resources via public folders. We use Chapura’s PocketMirror (similar to Puma Technology’s Intellisynch) for each doctor in the group. All laptops in the field connect through either America Online (AOL) or AT&T Worldnet via a firewall port that MIS has enabled. This setup requires Windows NT-level passwords for access, so it remains secure. Users with Pilot modems can RAS in to the server for Point-to-Point Protocol (PPP) network synchronization using 3Com’s HotSync. These users end up with synchronization across all levels for email, contacts, schedules, tasks, and notes. My information manager is adding the finishing touch: Microsoft Access feeds from each PDA through Pendragon’s PilotForms, with synchronization of all PDA and desktop info.
    Soon, we’ll be shuttling this whole scenario to the patient-management side of the office and abandoning a Macintosh system that we implemented more than 6 years ago using QUALCOMM’s (formerly Now Software’s) Now Up-to-Date. Our desire for information has grown since the PDA-Outlook-Exchange implementation, and we want a truly contact-centric system to handle our patient data.

    --Claude Albertario

  • Eric Campbell
    13 years ago
    Aug 06, 1999

    I’m a new subscriber to Windows NT Magazine, and I’m very happy I signed up. In February’s editorial, “The Right Tool,” Mark Smith asks readers whether they need information about managing personal access devices in their role as systems administrators. I’d welcome articles on best practices.
    I’m an IS manager in charge of NT, and personal access devices are the main source of my headaches. Our users are property and acquisitions managers who are constantly on the road. Secretaries edit the users’ calendars, and users dial in for information and new email. What makes my job so difficult is that the machines aren’t under my control at all times. (I lock down PCs and laptops so that users can’t change everything.)
    Another frustrating problem is synching between 3Com’s PalmPilots, Puma Technology’s Intellisync, and Microsoft’s Outlook 98. (We jump back and forth between using Intellisync and Chapura’s PocketMirror.) The job is more difficult when I have roaming profiles and a user tries to log on to Outlook 98 and synch at a satellite office.
    Personal access devices are here to stay, and as much as I hate having to support them, I welcome any additional information I can get. One of my best sources for finding solutions is the Deja News Web site (http://www.dejanews.com). I can usually find solutions there more quickly than I can get solutions from Puma, Microsoft, or 3Com.

    --Eric Campbell

  • Mark Smith
    13 years ago
    Aug 06, 1999

    Looks like “The Right Tool” struck a nerve. Look for coverage of personal access devices and solutions to management problems concerning these devices in upcoming issues of the magazine. Send article ideas to Amy Eisenberg at articles@winntmag.com.

    --Mark Smith

  • Tim Davidson
    13 years ago
    Aug 06, 1999

    My company lets employees use PalmPilots for Day-Timer functions and Windows CE devices for laptop-lite needs. The company does not purchase these devices with IS funds; users (or a user’s department) purchase them. The IS department supports synchronizing a user’s device with the user’s desktop in Microsoft Outlook or the native PalmPilot application. We need articles about how to manage the administrative challenges these devices present.

    --Tim Davidson

  • Brian Minnie
    13 years ago
    Aug 06, 1999

    I welcome articles and reviews about integrating Personal Digital Assistants (PDAs) and other personal access devices into a Windows NT environment. My company’s IS department has decided to support at least two types of devices: 3Com’s PalmPilot and HP’s handheld PCs that run Windows CE.
    Although both products promise to be productivity-enhancing tools for our users, the products have caused major headaches for IS. The main problem is remote connectivity and synchronization with our network. We use Microsoft RAS servers to let these devices dial in, but to synchronize data and email, the user’s desktop system must be logged on to the user’s account. This arrangement is not always possible or desirable, and I would appreciate finding out how other systems administrators deal with this problem. In a corporate environment, a server-based data storage system would be best for personal access devices, but companies that sell these devices seldom address the synchronization issue. I hope you start including articles about this topic in the magazine soon. I’m one administrator who would welcome the help.

    --Brian Minnie

You must log on before posting a comment.

Are you a new visitor? Register Here