Step 1 – ensure you have all relevant downloads and service patches, as well as your license key to hand. Nothing causes stress during an urgent installation like suddenly having to find a disk or try to locate a activation key!!!
Step 2 – If you’re installing onto a SQL server in a different domain, make sure you create a SQL user with sufficient rights. This is actually a pretty common requirement, and matches Microsofts own DMZ diagram, so it’s quite puzzling why SharePoint makes this option so hard.
Step 3 – Make sure you have created all of the appropriate accounts, and granted them the appropriate rights. See this post for a suggested list.
Step 4 – edit the registry to disable the IIS web server protection again loopbacks … otherwise all of the search functionality will work for a few hours after installation before being disabled. See this post for the details of this fix.
Step 5 – change the default path on the box to include
c:\program files\common files\microsoft shared\web server extensions\12\bin
If you don’t, you’ll need to manually change to this path for mot of the later configuration steps.
Step 6 – Find out the required functionality first! This sounds obvious, but I’ve found that sometimes things like the need for server side RSS pulls sometimes don’t get mentioned, and the need for http access for a server can need quite a lot of firewall changes! Make sure that the network works before beginning the installation, as troubleshooting network problems mid install is extremely difficult.
You should now be ready to install the product.
Recent Comments