Betsy Terrell 31.Jul.08 12:26 PM a Web browser Administration 2.0 Windows
When using the new "typical" install with Connections 2.0, all features are installed to a single physical WAS server profile as individual servers. THis is not using WAS DM, just base WAS.
By default in the WAS install, Server1 is configured to be a windows service and can be set to start with the restart of the box. Can the same be done with the Connections feature servers? I've tried using the Process Definition part of WAS admin to see if I could make this happen, so like as Server1 comes up the other severs also come up. This did not have the desired outcome.