So I started as the new SharePoint administrator at Trek Bicycles (in Waterloo, WI for those of you keeping score at home) last Monday. It's been quite the whirlwind thus far. The biggest learning curve I ran into was setting up our development environment with a snapshot of production data. In all my prior gigs other people were responsible for that. Here at Trek I'm the lone ranger. So I foraged ahead with my admin handbook, navigated to my dev environment's Central Admin, and clicked on "manage web applications."
Note: This post assumes you've got an available (and functioning) SharePoint 2010 environment, a breathing database administrator, and working knowledge of Central Admin.
Click New in the Ribbon and you'll get this
mean nice form.
You see 10 sections and you think "Gee, how hard could this be." Well, it's not hard per se, but it ain't easy either.
Depending on your scenario, you'll generally pick Classic Mode Authentication.
IIS Web Site
On to the IIS Web Site section. Here it is important to note that you need to have your domain (i.e. your web address) already setup and have it pointed in the right direction (i.e. pointed to the right IP address). In my case, I only have 1 Dev server so it's not that complicated. I e-mailed the person in charge of IP addresses, told her I needed a new A Record (the web address), gave her the IP address of the server, and we were off and running. You'll want to create a new IIS web site. Name it something you'll easily recognize in IIS. Use port 80 (http) or 443 (https). If you use any other port you'll have to add it to the end of the URL. For example, if you use port 4455 and your address is https://www.getaclue.com, you'll need to have users add :4455 to the end of their URL in order to hit the site correctly (https://www.getaclue.com:4455). Shout out to Brian Winkers for the help on that.
Next you'll need to add a host header. Using the example above you would add [www.getaclue.com] (note: no brackets). You can leave the Path alone. In fact, I recommend you don't touch it. Once that's done you've completed the IIS section. Moving on . . .
Next half of the form:
These are 3, subtle, yet oh-so-imporant radio buttons. For now, let's just leave the first 2 alone. Kerberos is a beast and if this is for an internal network you wouldn't want anonymous access. If you're using port 443 it's probably a good idea to use SSL, especially if it's internal. You'll need to buy an SSL certificate from an external vendor (I recommend RapidSSL). The certificate is installed on the server(s) in your environment via IIS, but that's a topic for another blog article.
Here you put in your URL. Pretty straightforward here. I don't know what Zone does, and I'm sure it's important, but this blog is called SharePoint Rookie; not SharePoint Expert.
The rest of the form
For the rest, I would just leave it alone unless you do not have an Application Pool account in the App Pool section. Again, topic for another blog.
Now hit OK at the bottom of the form and wait for SharePoint to work it's magic. It'll take 30 seconds or so, but once it's done the Web Applications page will refresh with your brand-spankin new web app provisioned.
Last step is to connect the copy of production's database to your newly minted Dev web app. Contact your Database Administrator (DBA) and ask him/her to put a copy of the production content database on the Development SQL server. It's important to have a good idea of what's in Production because you're going to reproduce it on a different server. Depending on where you work or where you're doing this, this may be a bad idea. Check with whoever (boss, director, higher-power) you may need to and make sure this is okay. Once you get the go ahead, do the following:
- Click on Application Management in the left-hand navigation
- Click Manage content databases
- Make sure the correct web application in the dropdown is selected (This would be the one you created above)
- Click "Add a content database"
- Add the correct database server name and the correct database name
Now if you and your DBA did everything right (and I didn't forget to mention anything here) you should have a production copy of your team site(s) now running in dev. Cheers!