Know your network. The first step, which is not always easy, is to understand your network. At headquarters, the descriptions you have of how remote workstations are configured -- and used -- may be inaccurate. All the PCs may have to be checked, one by one, to get the information you need.
Educate. ESD software is a long way from plug-and-play. Train your staff to understand ESD and the complex LAN environment that encompasses protocol stacks, drivers, device management, and router management.
Standardize. Enforce your standards, especially in the area of workstation naming policy. If two workstations share the same name, it could scramble an ESD program. Also standardize as much as possible on the software used throughout your organization. The more standardization, the easier updates and upgrades will be.
Start small. Use a pilot project -- perhaps fixing a bug or updating a utility -- to get a clear picture of the strengths and weaknesses of your ESD software and any network quirks. Then you can move on to changing mission-critical software.
Protect your assets. Treat your code distributor as a corporate asset. Back it up frequently. Protect it with passwords, and limit access.
Be patient. Perhaps that's the best advice. The Gartner Group, a consulting firm, estimates that implementing ESD software takes from six to nine months, including the initial pilot project.
See also:
How to Pick the ESD Software You Need
ESD's Bright Future
Taking ESD to a New Level
NetView Distribution Manager