If a committee has a narrow set of objectives, deadlines and strong leader, something may get done . Also, I recommend you start with one committee with one strong leader and have that group get too busy and need to spin off new subcommittees to tackle specific tasks . If you start with four and a couple of these start to drift, committee members will think the momentum behind intranet is failing. Leadership skills are much more important than technical skills for these intranet committees. It helps if the leader is immersed in the technology, but look for people that know how to prepare for and run a meeting, not somebody that can argue the merits of NT vs Unix.
Servers are usually setup by systems staff.
They are usually skilled at the setup of the hardware and software but they will shy away from the important task of enabling authors to access and use the servers. You need to find ways to encourage the owners of the servers to spend time coaching the authors. Also, when you get added resources for servers support, make sure you build into the job specifications a definition of administration of servers that includes helping the web authors . I work for a large bank and we have been testing a new design to our intranet using a frames design. Navigation frames use up precious real estate on your screen.