Some interesting feedback from folks on how to get people to run the CEICW - most people seem to say “just run it for them”. <sigh> If only we could do that.
There are several issues around forcing a user to run a configuration wizard after the setup - most of them are user interaction and psychology issues than technical:
- Many servers are installed off-site and then taken to the business. Forcing the wizard to run after setup would be of no or little value to these customers.
- Today, users are so over-prompted with security warnings that they just click through that I don't want the value of the wizard to be brushed away. I was not a fan of Office's decision to put up an “OK” textbox for every time you open an Office doc from a Sharepoint site. To be honest, to this day I can't tell you what the hell the damn thing says, and I must see it 10-20 times a day.
- The install of SBS is so long as it is (unless you've purchased an OEM server), that to add in more required steps after you've just finished installing it risks entering into what I call the AFW effect (or “Another <bleeping> Wizard”)
We've gone round several times on thinking about making ICW required, but the wizard as it exists today is still probably too complicated and long to force all users to run through right away. Now, if we can take the functionality of ICW and just place it into the setup experience, that may be more interesting....