Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Save to My Library
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1




|Views: 953 |Likes:
Published by Indrajit Banerjee

More info:

Published by: Indrajit Banerjee on May 21, 2008
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





Installing, Configuring and Managing SharePoint ServicesBySysnetadmin.co.nr 
Windows Server 2003 R2 includes Windows SharePoint Services. In this post,we will cover the basic installation and configuration steps needed in order to geta standalone Windows SharePoint Service 3.0 installation up and running onWindows Server 2003 system.1.Install the Application Server (IIS) role on your Windows Server 2003system.2.Install the Mail server (POP3, SMTP) role on your system.3.Downloadand install the Microsoft .NET Framework 3.0. Make sure todownload the version (32-bit or 64-bit) that matches your operatingsystem.4.Verify that ASP.NET v2.0.50727 is allowed by opening the InternetServices Manager, choosing Web Services Extensions, choosing ASP.NET v2.0.50727, and clicking the Allow button.5.DownloadWindows SharePoint Services 3.0 from Microsoft. Don't installWindows SharePoint Services through Add/Remove Programs, becausethis is not the latest version of the service. For the x64 version of SharePoint, gohere.6.Execute the downloaded file named SharePoint.exe.7.When asked, choose a Basic installation. The Basic installation alsoincludes a run-time database.
Figure 1
Choose an installation type.
8.Windows SharePoint Services 3.0 will install using the defaultconfiguration.9.The Windows SharePoint Services configuration wizard will run. This step,among other things, creates a SharePoint configuration database, installsservices, and creates sample data.
To utilize your new SharePoint site, open a Web browser and browse toyour server's name.
Figure 2
The SharePoint Team Site window
This is a very short introduction of the installation procedure. A detailedExplanation, Installation and Configuration method is as follows.What is Windows SharePoint Services?Windows SharePoint Services is the little brother of Microsoft's SharePoint PortalServer. Although Windows SharePoint Services isn't quite as powerful asSharePoint Portal Server, it can really go a long way toward helping your company become better organized.In addition to helping to archive documents, this Windows Server 2003component also allows employees to build their own collaborative Web sites.Employees can use these Web sites for retrieving commonly used documents,discussing things going on within the department, and having online meetings.Perhaps the best part of Windows SharePoint Services, though, is that it's freefor anyone running Windows Server 2003.Before you beginAs you can see, Windows SharePoint Services is as powerful as it is useful.Before you can install the component, however, you need to do a little prep work.For starters, you must locate a suitable server. The server must be runningWindows Server 2003 Standard, Enterprise, Datacenter, or Web Edition. Theserver must also be running Microsoft's ASP.NET and IIS 6.0. As you may know,IIS has a lot of optional components. You must therefore verify that the commonfiles, the Simple Mail Transfer Protocol (SMTP) Service, and the World WideWeb services are all installed and running. None of these components is installedby default.It's very important to note that you should not install Windows SharePointServices onto a server that is already hosting a Web site or running a Webapplication, including Microsoft Exchange. Previously existing Web applicationswill be disabled during the SharePoint Services installation. Furthermore, theinstallation process will also disable Kerberos authentication for IIS. Windows
SharePoint Services uses NTLM authentication in lieu of Kerberos.To install the necessary components, select the Add/Remove Programscommand from Control Panel. When you do, Windows will display the Add Or Remove Programs dialog box. Click the Add/Remove Windows Componentsbutton. When you do, the Windows Components Wizard will appear.At this point, scroll through the list of components until you find ApplicationServer. Select Application Server, then click the Details button to reveal theindividual Application Server components. Select ASP.NET. With the ApplicationServer screen still open, select Internet Information Services (IIS) and click theDetails button.You'll see a list of the various IIS components. The Common Files and the WorldWide Web Service should be selected by default, but you'll have to manuallyselect SMTP Service and click OK to return to the Application Server screen.Click OK again to return to the Windows Components Wizard screen. Click Next,and Windows will install all of the necessary files.Another requirement is that the server must be running a version of SQL Server 2000. Before you stop reading the article, I should tell you that Windows Server 2003 comes with it's own SQL Server engine. This means that smaller organizations don't have to go out and buy SQL Server. The built-in engine iscalled MSDE (Microsoft Database Engine). It is just like SQL Server, but it hassome major limitations.First, MSDE is designed to slow down significantly if it's used by more than fiveusers simultaneously. In this way, it will work well for small offices, but bigger organizations will want to use a full-blown version of SQL. A second limitation isthat it doesn't support databases over two gigabytes in size. This may sound likea big database, but if your users index a lot of documents, the database cangrow to be larger than two gigabytes fairly quickly. The final limitation is thatMSDE does not offer any administrative tools. If you want to do anyadministrative work at all on MSDE, you'll have to do it from either a commandline or a script. As you can see, MSDE is great for small offices or for development environments, but larger organizations should use SQL Server. For the purposes of this article, we will use a normal copy of SQL Server 2000running Microsoft SQL Server 2000 Developer Edition with Service Pack 3A.Once SQL Server or MSDE is installed, there are a few other minor requirements. The server must be a part of a Windows NT, 2000, or 2003domain, although it doesn't necessarily have to be a domain controller. Theserver must also have a Pentium III or higher processor, 512 MB of RAM, and550 MB of free disk space.Keep in mind, however, that these are only the requirements for installingWindows SharePoint Services. There is a good chance that the databases couldgrow to be several gigabytes in size, so plan your disk space requirementsaccordingly.Finally, the clients will be accessing Windows SharePoint Services through aWeb browser. It is therefore important that the clients are running a supportedWeb browser. Supported Web browsers include:
Internet Explorer 6
Internet Explorer 5.5 with Service Pack 2
Internet Explorer 5.01 with Service Pack 2

Activity (7)

You've already reviewed this. Edit your review.
1 hundred reads
1 thousand reads
dayooyefuga liked this
vykuntavasu liked this
nomi4me liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->