Here we will go through the process of installing VMWare Workstation 7, creating a Virtual Machine and installing Windows Server 2008 64 bit edition on it. Once we have the Win Server installed, we will go about configuring it as per our needs(keeping in mind the requirements for the installation of Microsoft Office SharePoint Server 2010).
VMWare Workstation 7 offers a 30 Day Trial while Microsoft Windows Server 2008 as well as MOSS 2010 offers a 180 Days Evaluation period.
I have made a Video Tutorial of my installation process of VM Ware Workstation, creating Virtual Machine, and also the initial configuration of Windows Server 2008.
In the second part of the video, I will be taking you through the step-by-step process of configuring Windows Server 2008 further, with the installation of SharePoint Server 2010 in mind.
By this point, I hope everyone has successfully installed Windows Server 2008, and done with the initial configuration. In this part, we will see how to add the necessary roles, features, create an Active Directory Domain Controller, and also create the necessary Active Directory Users.
1. Enable Virtual Memory
– Start –> Control Panel –> Advanced System Settings –> Performance(Advanced) –> Settings –> Virtual Memory(Advanced)
2. Enable ‘File and Printer Sharing’
– Start –> Control Panel –> Network & Sharing Center –> Change Advanced Sharing Settings –> Turn ON File & Printer Sharing(for Domain)
3. Enable Remote Desktop
– Start –> Control Panel –> System and Security –> System –> Remote Settings –> Allow Connections(for Remote)
4. Turn OFF Windows Firewall for Domain Networks
5. Disable Internet Explorer Enhanced Security Config
– Start –> Server Manager –> Configure IEESC (Turn OFF)
Before we continue further, lets make sure that we have a Static IP address if we plan to use the system as a Domain Controller. If we are using a Dynamic IP, we might need to change it to a Static IP.
6. Add Roles & Features
a) Active Directory Domain Services
– Start –> Server Manager –> Roles –> Add Roles –> Server Roles –> Active Directory Domain Services
It will also prompt us to add the required features for the server role we have selected, we will continue with that. Once it is done,
goto Start –> Type in dcpromo in the search field (or) goto run –> Type in dcpromo there.
That will take us through the installation process of Active Directory Domain Services as well as creating a new Domain.
b) Application Server
– Start –> Server Manager -> Roles –> Add Roles –> Application Server
• .Net Framework 3.5.1
• Web Server IIS Support
• TCP Port Sharing
• Windows Process Activation Service Support
c) Web Server(IIS)
-Start –> Server Manager –> Roles –> Add Roles –> Web Server(IIS) Roles
• Common HTTP Features
• Application Development
• Health and Diagnostics (Custom and ODBC logging not necessary)
• Security –> Performance
• Management Tools –> IIS 6 Management Compatibility
7. Install the downloaded ‘KB979917 – QFE for Sharepoint issues – Perf Counter fix & User Impersonation’.
8. Add Features Windows Powershell Integrated Scripting Environment
– Start –> Server Manager –> Features –> Add Features –> Windows Powershell ISE
9. Create Accounts in Active Directory
Once we have added the required Roles & Features, we will need to create three important Active Directory Users. It is a good practice to create it now inorder to avoid any unnecessary hassles in the future. The three accounts needed are
• SQL Service Account (sql_svc) – This account is used to run SQL Server and it should be a Domain Account.
• SharePoint Set Up Admin (sp_admin) – This Account has to be a member of Administrator’s Group of every server SharePoint will be installed. It should also be there under SQL Server Administrator with roles of ‘dbcreator’ and ‘securityadmin’.
• SharePoint Farm Account (sp_farm) – The permissions for this will be automatically assigned by SharePoint 2010.
While creating accounts, it is really important to know about their roles, permissions, and privileges. The below blog provides you with a wonderful explanation regarding those.
– Least Privilege Service Accounts for SharePoint 2010
So, this ends the Part 2 of setting up SharePoint 2010. Again, I have provided a Step-by-Step Video Tutorial of the process. Hope you all find it useful.
I have been Googling(if that can be used as a term) for must know definitions and questions in SharePoint. After going through a lot of questions in various sites, I finally decided to just improvise a little on them and gather them in a single place. For people who want to download the word file, I have provided a link in the bottom of this post. So, here we go
What is SharePoint?
– Microsoft SharePoint is a browser-based collaboration and document management platform from Microsoft. A Content Management System which allows groups to set up a centralized, password protected space for document sharing. Documents can be stored, downloaded and edited, then uploaded for continued sharing.
Differences between SharePoint Portal Server and WSS?
– Windows SharePoint Services 2.0 is a collection of services for Microsoft Windows Server 2003 that you can use to share information, collaborate with other users on documents, and create lists and Web Part pages. You can also use Windows SharePoint Services 2.0 as a development platform to create collaboration applications and information-sharing applications.
SharePoint Portal Server 2003 is a scalable, enterprise portal server that is built on Windows SharePoint Services 2.0.
In addition to the features of Windows SharePoint Services 2.0, SharePoint Portal Server 2003 includes the following features:
- News and topics
- My Site, with personal views and with public views
- Information that can be targeted to specific audiences
- Index functionality and search functionality across file shares, across Web servers, across Microsoft Exchange Public Folders, across Lotus Notes, and across Windows SharePoint Services 2.0 sites
- Alerts that notify you when changes are made to relevant information, documents, or programs
- Single sign-on functionality for enterprise application integration
- Integration with Microsoft BizTalk Server
What is a Document Library?
– Document Libraries are collections of files that you can share with team members on a Web based on Microsoft Windows SharePoint Services. For example, you can create a library of common documents for a project, and team members can use their Web browsers to find the files, read them, and make comments. Users with Microsoft Office 2003 can check out and edit the files as if they resided on a local or network drive.
By default, your team Web site comes with a built-in document library named Shared Documents, which is listed on the Quick Launch bar as well as on the Documents and Lists page.
What is a Meeting Workspace?
– A Meeting Workspace is a Web site for gathering all the information and materials for one or more meetings. If your meeting materials — such as agendas, related documents, objectives, and tasks — are often scattered, a Meeting Workspace site can help you keep them all in one place.
It provides a place where your meeting attendees can go for the most up-to-date information about the meeting, whether you are managing a year-long project with recurring meetings or planning a small event.
What is a Document Workspace?
– A Document Workspace site is a Microsoft Windows SharePoint Services site that is centered around one or more documents. Colleagues can easily work together on a document — either by working directly on the Document Workspace copy or by working on their own copy, which they can update periodically with changes that have been saved to the Document Workspace copy.
What is a Site Hierarchy?
– When you configure a report server to run in SharePoint integrated mode, the SharePoint Web hierarchy is used to address items that are processed and managed on a report server.
The following elements of the Web hierarchy can be used to access and secure report server content. Other objects such as lists and pages are not used to access report server content and therefore are not described below.
- SharePoint Web Application: A SharePoint Web application can be installed as a stand-alone server or under a farm that contains a collection of virtual servers. A Web application has a URL (for example, http://servername) and can contain multiple sites.
- Site: A site is either a parent site for a Web application or a sub-site.
- SharePoint Library: A library contains documents or folders. A library or folder in a library is the only site object that can store reports, report models, shared data sources, and external images.
- Item: Report server items that you can reference in a URL include a report definition for a report or sub report, a report model, a shared data source, or an external image.
What is a Web Part?
– Web Parts are the building blocks of Web Part Pages in SharePoint sites. They can be added to Web Part Pages in SharePoint sites to offer users increased functionality. The Web Parts that are loaded within a site’s Web Part zones usually determine how popular a site truly will become.
List view Web Parts
- Shared Documents
- Team Discussions
Apart from these, there are also some miscellaneous Web Parts, namely Content Editor Web Part, Form Web Part, Image Web Part, Page Viewer Web Part, Relevant Documents Web Part, Site Users Web Part, User Tasks Web Part and XML Web Part.
Difference between Document Library and Form Library?
– Document libraries in SharePoint consist of your main/core documents. For example a word document, excel, PowerPoint, Visio, pdf, csv, notepad etc.
– A Form Library provides a simple way for you to share and track XML-based forms that are used to gather information. For example, you can create a form library for your team’s expense report forms. In a form library, you can use the versioning and approval features to manage your forms, just as you manage files in other types of libraries. You can keep track of versions, so that you can view a version history and restore previous versions if necessary. You can also specify that forms remain in a pending state until they are approved or rejected by someone who has permission to do so.
What is a Web Part Zone?
– Web Part Zones are containers of Web Parts that are used to group and organize Web Parts on a Web Part Page. Web Part zones also have a set of properties that serve a dual-purpose. You can use one subset of properties to organize the layout and format of Web Parts on the Web Part Page. You can use another subset of properties to provide an additional level of modification protection (or “lock down”) of the Web Parts within the zone.
The Web Part zone properties each have default settings or behaviors. As you add Web Parts to the Web Part page, you automatically set some of these property values. Although these property values are not designed to be edited in the browser, you can modify them by using an HTML editor compatible with Microsoft WSS , such as Microsoft Office FrontPage 2003.
How is Security managed in SharePoint?
– Security can be handled at the Machine, Domain, or SharePoint level.
SharePoint can run under various IIS modes to authenticate its users. The modes include: Anonymous, Basic, Integrated Windows or Certificates Authentication (over SSL).
SharePoint security facilitates the regulation of access privileges of users and groups as well.
.NET Impersonation which is utilized by SharePoint allows an application to run under the context of the client accessing an application.
Deployment and Code Access Security:
.NET Code Access Security (CAS) provides a security model. It can restrict the operations that can be performed as well as the resources that can be accessed by managed code.
How are Web Parts Developed?
– Web parts are developed in Visual Studio.Net. It offers many web parts and page templates, and can also be downloaded from the Microsoft site.
What is a SharePoint Farm?
– In the context of SharePoint, the term ‘Farm’ is used to describe a collection of one or more SharePoint Servers and one or more SQL Servers that come together to provide a set of basic SharePoint Services bound together by a single Configuration Database in SQL.
Differences between WSS and MOSS 2007?
– Windows SharePoint Service (WSS) is included with Windows Server, and Microsoft Office SharePoint Server 2007 (MOSS) is a separately purchased product that offers richer features for business.
– If your company has Windows Server, you can use the extensive features of WSS. If it isn’t set up for your company, you’ll have to ask your IT manager to set it up, turn it on, or whatever verbiage will get WSS in your hands.
WSS 3.0 offers all the standard site templates to build team sites, document workspaces, blank sites, blogs, wikis, and meeting workspaces.
– You can also use WSS 3.0 to create people and group lists. You can integrate WSS 3.0 sites with Access 2007, Excel 2007, Outlook 2007, Word 2007 and PowerPoint 2007. You can create RSS feeds and set up alerts to notify you when content changes on a site. Version control, task notification and alerts all come with WSS 3.0
– MOSS 2007 offers all of the features included in WSS 3.0. In addition, MOSS 2007 offers business intelligence features that allow you to track key performance indicators and build BI dashboards into your team site. The dashboards can assemble and display business info using Excel spreadsheets, SQL, or integrate with line of business applications. Excel Services in MOSS go beyond simply displaying Excel spreadsheets, you can actually stream parts of a spreadsheet, showing or hiding various parts. Workflow can also be integrated into MOSS 2007 and WSS 3.0. And don’t get me started on slide libraries – a much needed and unique way to share and reuse slides that is available in MOSS 2007.
– MOSS 2007 also offers My Sites, which are individual mini-sites that can be set up to show who in your company you’re connected to, what your tasks and skills are, your contact information, and more. When I worked at a consulting firm, we used our My Sites to let co-workers know what we did so that they knew whom to call on for a new project. We used the My Sites to ‘advertise’ ourselves.
– One of our team members was given the task of putting together a team site for my group that summarized our My Sites and provided other links and resources. He had about one month to build the site, but a big project prevented him from doing it. He asked me to take his place at a presentation of the site to a larger group in the company, giving me two hours notice. Now, while I don’t recommend doing a site in two hours, I was able to do this in less than two hours – more of a tribute to how easy SharePoint is to use than to my skills.
– The features that are included in WSS 3.0 are easy for anyone to use and set up. You can create your own team site, set up a blog in minutes, create wikis, use Word to post your blog entries, create slide libraries so that all your employees can find and reuse different slides from different presentations and lots more. But first you have to plan your site and decide how to organize it to help your team be more productive.
Definition of Site in SharePoint?
– A site definition is a group of files that reside on the Web server and that define a unique type of SharePoint site. Each SharePoint template that appears on the Web Site tab of the new dialog box is based on a site definition. For example, one site definition defines the Team Site, Blank Site, and Document Workspace templates, and another site definition defines the Basic Meeting Workspace, Blank Meeting Workspace, Decision Meeting Workspace, Social Meeting Workspace, and Multipage Meeting Workspace templates.
What is a Template in SharePoint?
– A template is a pre-defined set of functions or settings that can be used over time. There are many templates within SharePoint. Site Templates, Document Templates, Document Library and List Templates.
Custom templates are a way of packaging up a set of changes to an existing site definition and making those available for new sites and lists. Every custom template is based on a site definition. Custom templates are stored in the database and made available through the central or site collection template galleries.
How do we install Web Parts?
– Web Parts are the building blocks of Web Part Pages in SharePoint sites. They can be added to Web Part Pages in SharePoint sites to offer users increased functionality. The Internet Platform and Operations group chose to install Microsoft Office Web Parts and Components, but you could install any Web Parts compatible with Windows SharePoint Services.
Web Parts can be installed only after Windows SharePoint Services is installed and configured on the server.
To Install Office Web Parts and Components:
- On the first front-end Web server, open the folder that contains the Office Web Parts and Components files.
- Double-click Setup.exe.
- Repeat steps 1 and 2 for each front-end Web server.
Difference between Web and Site?
– SharePoint Web Application could be defined as an IIS Web Site specifically configured to run WSS sites. A Web application is the logical & physical partition/container within IIS to create portals.
IIS Web Site could be defined as an entry point in the IIS Web Server infrastructure. The Site-Collection and Sites are the logical & physical in the context of SharePoint’s content database. Ultimately sites and site-collection live in content database.
A single web application could have multiple site collection within it and each site collection has a top level site and could have multiple sub sites in it. A WSS site collection acts as a container of WSS Sites.
Differences between WebPart Page Gallery, Site Gallery, Virtual Server Gallery, Online Gallery?
– Users can include Web Parts from any of the following sources by default:
• Online Gallery: A set of Web Parts that is available over a Web service that permits many servers to share access to a common, centrally maintained gallery of Web Parts. The URL for this Web service is specified in the Online Library element of the web.config file for a site. This gallery provides a way for the IT administrator to deploy Web Parts.
• Site Web Part Gallery: Contains Web Parts that is available to a particular site. By default, when you run Stsadm.exe to install a Web Part, Stsadm.exe adds the Web Part to the Virtual Server Gallery. This gallery provides a way for the SharePoint Administrator to deploy Web Parts.
• Virtual Server Gallery: Lists Web Parts that is available to all sites on the server. This gallery provides a way for a server administrator to deploy Web Parts
• Web Part Page Gallery: Contains Web Parts that are already added to the current page. This gallery, unlike the other galleries, is generated dynamically. It contains Web Parts that are added to the page but are closed. The Web Part is still associated with the page by an entry in the SharePoint database, which also stores any shared or personalized property settings for the Web Part. To bring back a closed Web Part, select it from the Web Part Page Gallery.
What is GAC?
– The Global Assembly Cache (GAC) enables you to share assemblies across numerous applications. The Global Assembly Cache is automatically installed with the common language runtime. Components are typically stored in C:\WINNT\Assembly. It is one of the two locations where we can deploy a Web part assembly within a SharePoint Site, the other being a Bin Directory.
What is DWP?
– Dashboard Web Part (.dwp) is a Web Part description file. The .dwp file can be stored on and referenced from any computer, and contains XML metadata that describes an instance of the Web Part.
To create and export a simple Web Part, you can open any Windows SharePoint Services or SharePoint Portal Server page that you have permission to modify, configure any Web Part on that page, and then export the .dwp file. Because the .dwp file is a description of a Web Part instance, you can edit the file in any text editor on another computer and then import the .dwp file again to show a modified Web Part.
What is CAML?
– Collaborative Application Markup Language (CAML) is the XML-based language that is used to build and customize Web sites based on SharePoint.
CAML can be used to do the following:
- Provide schema definition to the Web site provisioning system about how the site looks and acts.
- Define views and forms for data and page rendering or execution.
- Act as a rendering language that performs functions in the DLL like pulling a value from a particular field.
- Provide batch functionality for posting multiple commands to the server using protocol.
– Themes represent a collection of graphics and cascading style sheets that can modify how a Website looks, to spice up the look and feel of a Website. It allows users to easily customize the look of their personal sites from the Site Settings page for each site. Themes are applied automatically to the entire personal site, except for the public view. Applying the theme to the public view requires additional steps by the portal site administrator.
– A Presence indicator is appended to every person in your contact list in the Launch bar and in the member list in each workspace. A person’s presence is determined by a collection of attributes that describe the person’s status, activity, location, willingness to communicate, and contact information. Presence information helps you to contact others and helps others to reach you.
Presence indicators in SharePoint Workspace correspond to those you see for contacts in Microsoft Office Communicator. If a contact is not running Communicator, you see a subset of these presence indicators.
Can Web Parts be connected? If so, how?
– Yes. You can connect Web Parts together by passing data, such as a row or filter, from one Web Part to change the display of the other Web Part’s data. By connecting Web Parts, you can synchronize their behavior and manage data in dynamic and interesting ways. Traditionally, the chore of connecting sets of data from different data sources has not been easy and has often required programming skills. But with Web Parts, making data connections is as simple as using menu commands. By connecting Web Parts, you can, for example, present data from two Web Parts in alternate views, perform related calculations between two Web Parts, and filter a Web Part using values from another Web Part – all on one Web Part Page.
What is Personal View and Shared View?
– When a Web Part page is in Shared View, all users see the same page and any changes you make in shared view are intended for all users to see. When a Web Part page is in Personal View, you see any personal changes you have made and any changes you make in this view are intended just for you to see.
When a Web Part page is in Personal page view, you:
- Can usually view and modify the Layout and Appearance common Web Part properties, but not the advanced ones. In some cases, the developer of a Web Part may decide not to display some or all common properties or you may not have permission to see them.
- Can view and modify custom Web Part properties. In some cases, the developer of a Web Part may decide not to display some or all custom properties or you may not have permission to see them.
- Can view and modify, but not delete, shared Web Parts with appropriate permission. Once you modify a shared Web Part, however, it becomes a personalized Web Part.
- Can view and modify, but not delete, personalized Web Parts. The modified property values of these Web Parts apply only to you.
- Can view, modify, and delete private Web Parts. These Web Parts only apply to you, no other users can see them, even in shared view.
When a Web Part page is in shared view, you:
- Can view and modify common as well as custom Web Part properties. Changes you make apply to all users.
- Can view, modify, and delete shared Web Parts. Changes you make apply to all users.
- Cannot view, modify or delete private Web Parts. You can only view, modify, and delete private Web Parts in personal view.
- Cannot view or modify personalized Web Parts, either your own, or for another user.
What is a STP File and FWP File?
– Site templates are stored into the site collections site template gallery as STP (.stp) files, whereas SharePoint sites which have been backed up are stored as FWP (.fwp) files.
How does SharePoint support Microsoft Outlook integration?
– The Document Library has syncing capability that allows us to easily access, preview, search and edit our SharePoint Document Libraries in Outlook. In order to do that, we just need to navigate to a SharePoint Document Library in our web browser, click on the ‘actions’ dropdown menu and select ‘connect to Outlook’.
We can even access our SharePoint documents in Outlook. We can preview a Document, or search it using Outlook’s Instant Search, and even better, we also can access and edit it Offline.
Explain Document Versioning in SharePoint Document Libraries.
– Document Versioning allows us to keep multiple versions of a document. If a change needs to be reversed, we can restore the previous version and continue working. When versioning is turned on, a Version History command is added to the drop-down list that users see when they click the arrow next to a document name (and the toolbar) in the Edit Properties page for the document.
When versioning is enabled, versions are automatically created whenever a user updates a document in a document library. Versions are created in the following situations:
- When a user checks out a file, makes changes, and checks the file back in.
- When a user opens a file, makes changes, and then saves the file for the first time.
If the user saves the file again, without closing the file, a new version is not created. If the user closes the application he or she is using to edit the file, and then opens it and saves the file again, another version is created.
- When a user restores an old version of a file (and does not check it out).
- When a user uploads a file that already exists, in which case the current file becomes an old version.
Also note that,
- When a file is deleted from a library, all previous versions are deleted as well.
- Versions can be created for all file types except HTML files that contain images or embedded objects. If you want to create versions as HTML, you must use the MHTML format (often saved as .mht) when saving to this Web site. This also applies to those files on the Web site that you check out and modify.
Where are Web Part Resources contained?
– Web Part Resources are contained in the SharePoint File System, SQL, and the Global Assembly Cache (GAC) folder. They are also referenced in the web.config folder.
Different Installation methods for deploying Web Parts and its PROS/CONS.
– Microsoft SharePoint Foundation requires that a Web Part be deployed in the Web Part gallery before it can be added to a Web page.
There are multiple locations within a SharePoint site where you can deploy a Web Part assembly.
- Solution Gallery – The Solution Gallery is the recommend placed to deploy a Web Part by using a sandboxed solution. It provides monitoring and security for your Web Parts by default.
- Bin Directory — The bin directory is a folder stored in your Web application root directory. The location of this folder is determined when the Web site is created in Internet Information Services (IIS). In SharePoint Foundation, this can happen either through the Central Administration site, or by manually creating a new Web site in IIS manager. (If a bin directory does not exist you must add one manually. Do not store Web Parts in the local _app_bin directory, which is reserved for use by Microsoft.)
- Global Assembly Cache — A global location where signed assemblies can be deployed. The global assembly cache enables you to share assemblies across numerous applications. The global assembly cache is automatically installed with the .NET runtime. Components are typically stored in C:\WINNT\Assembly folder.
|Code deployed to the Solution Gallery is run in partial trust, by default. Codes in the Solution Gallery also have resource usage monitoring to ensure the health of the farm. The Solution Gallery is specific to a site collection.||All of the object model in SharePoint Foundation is not available in the Solution Gallery.|
|Assemblies run with partial trust, by default. Code that runs from this directory has a low level of code access security (CAS) permissions. Because administrators must explicitly raise permissions that have been granted to a Web Part so it can function properly, they often prefer that assemblies run in the bin directory with a known set of required CAS permissions.
A bin directory is specific to a Web application. This makes it possible to isolate code to a particular Web application.
|In order for the Web Part to run in multiple Web applications, you must deploy it to the global assembly cache.|
Global Assembly Cache
|Assemblies run with full trust by default. They are globally installed, so they will work in any Web application. The global assembly cache can contain multiple versions of the same assembly.
|Generally there are no CAS restrictions on code installed to the global assembly cache.
Also, an assembly deployed to the GAC is cached, so if the assembly is rebuilt, it is not automatically updated on the SharePoint site. You must force SharePoint Foundation to reload the assembly by resetting Internet Information Services (IIS).
What are Ghosted and Unghosted Pages in SharePoint?
– Ghosted Page: Ghosted means that the Site Definition pages have Not been Customized (Ghosted means Un-Customized) and the pages in your Site Definitions run directly from the file system (cached of course). You can check this out by going to a page like the default.aspx page in the STS Site Definition and typing “Hello” in the body somewhere. Run IIISRESET to clear the cache, and you’ll see that “Hello” shows up immediately on all sites that were created using that Site Definition.
Unghosted Page: Unghosted means that the site has been Customized (Unghosted means Customized). When you customize a v2 site in FrontPage or a v3 site in SharePoint Designer, or you add custom fields to a Doc Library, or you customize a site in the UI and then save it as a Template – upload it into a Template Gallery – and then create sites using that template; then the changes that you made are stored in the database as a diff and that is referred to as Unghosted (Note that all Unghosted sites are based on a Site Definition).
A request for a Customized (Un-Ghosted) page returns a response which is a combination of data from both the file system and the database. In v2 this was a performance hit, and you wanted to avoid having a large number of sites that were Un-Ghosted. In v3 – caching etc. has been improved, and you are encouraged to use SharePoint Designer to do as much customization as you want.
How are Site Data stored in SharePoint?
– SharePoint sites are Data, not Application Codes, but Data.
A SharePoint site, at its core, is a set of lists. Document libraries, users, event calendars, surveys, tasks, discussions, Web Part galleries, template galleries — they’re all lists. Even the instancing of Web Parts on specific pages in a site (zones, properties, etc.) is effectively a list. For every list, we store data and Metadata, including views.
The set of sites/lists (Site Data) are maintained in SQL Server or Microsoft SQL Server Desktop Engine (MSDE). Access to SQL Server is constrained to stored procedures. Access to those stored procedures happens via ISAPI (for WebDAV, FrontPage RPCs, and static HTTP GETs) or via a managed API. We call that managed API ourselves, inside ASP.NET-authored SOAP Web services, as well as by our ASP.NET-based Dynamic HTML interface.
Architecturally, the DHTML interface we provide via ASP.NET is really just one way of getting to a SharePoint site. A nice way, an important way, and a way you can extend with Web Parts to pull in non-site data or new views of site data. But ultimately, it’s not the star of the show, but rather a much-loved supporting cast member.
How do we deliver the DHTML interface?
– For each site, and for each list, there are database-defined ways to render it (e.g., Edit Item, Add Item, View List), and for each one, we effectively store the location the ASP.NET page used to do that rendering in the database. Those pages are usually stored in localized resource directories on the Web server’s file system, but if you edited a page in FrontPage, we store the edited page directly in the database itself as a BLOB.
It’s only at this point that Web Parts enter the picture. Those ASP.NET pages involve extra code to provide the infrastructure for hosting Web Parts.
And to bring it all back to lists (i.e., data), the most important Web Part we provide in the box is the List View Web Part, whose job it is to grab a list’s CAML XML data and view rendering meta data and apply the latter to the former to generate HTML. It’s much, much, much faster than iterating through object model collections in loops and building up the HTML that way. Every time you create a list, we add an instance of the List View Web Part preset to point to that list into the site’s Web Part Gallery. It is, however, one piece of code we use over and over and over again to render every list in every site.
This architecture is what enables the scalability, availability, manageability, and extensibility of the WSS platform.
What is an Audience and describe its use.
– Audiences are groups of users determined by their memberships in Microsoft Exchange distribution lists (DL) or SharePoint groups, or by rules configured by a portal administrator.
Audiences allow organizations to target content to users based on their job or task, as defined by their membership in a SharePoint group or distribution list, by the organizational reporting structure, or by the public properties in their user profiles.
Where is Metadata for a Web stored?
– Metadata for a Web is found in the Content Databases stored in SQL.
What are the Trust Levels and what is the default Trust associated with SharePoint?
– SharePoint Foundation is a Partial Trust Application by default. SharePoint Foundation can use the ASP.NET built-in trust levels but defines two trust levels of its own:
These trust levels extend the ASP.NET Minimal and Medium trust levels for use with SharePoint Foundation. Trust levels are defined in policy files that can be found on the file system of each Web server.
Important: By default, the built-in SharePoint Foundation policy files in SharePoint Foundation, named wss_minimaltrust.config and wss_mediumtrust.config, are found in %ProgramFiles%\Common Files\Microsoft Shared\web server extensions\14\CONFIG directory.
By default, SharePoint Foundation applies the WSS_Minimal trust level for the virtual server. This trust level grants all of the permissions in the ASP.NET Minimal trust as well as Web Part connections. The WSS_Minimal policy restricts the Web Part from accessing many resources for advanced operations, including the object model and file operations.
The WSS_Medium trust level grants greater access to the environment. Also, WSS_Medium allows access to the SharePoint Foundation object model and file operations including read, write, append, and path discovery. This trust level also allows access to environment variables.
What functionality does owssup.dll provide for client side activities?
– The owssup.dll provides ‘Open with’ and ‘Export to’ functions for Access, Outlook, Excel, and other Microsoft Office and third-party applications. It is a WSS Export Database Object for client side activities.
What are the differences between a SharePoint Server Administrator, SharePoint Site Collection Administrator, and SharePoint Site Owner?
– SharePoint Server Administrator: They are responsible for the physical servers, software installation, backup, etc.
SharePoint Site Collection Administrator: The user responsible for the entire site collection. They have access to Site Collection wide features in several places including Site Settings, and typically is the person responsible for a department or a group’s entire site collection.
SharePoint Site Owner: A user with ‘full control’ rights to a single site, its lists, libraries and content, and any sub sites and workspaces created below it, i.e., responsible for a ‘branch’ of a site collection.
Here’s a list of what a Site Collection Administrator can see that the Site Owner (Full Control User) can’t:
Site Actions & Site Settings
Users & Permissions: Site Collection Administrators (Only an option when at a Top Level Site)
Site Administration: Content and Structure Logs
Site Collection Administration: The entire column is missing which means that a Site Owner can’t access the 2nd level Recycle Bin.
Interestingly enough, a Site Owner is not trusted with the above mentioned features but they can delete the site.
STSAdm and its uses?
– The command line tool stsadm.exe is the IT Pro tool for doing a few things that aren’t exposed through the web UI. It’s also great for scripting operations that are repetitive. It enables many administrative operations in Windows SharePoint Services that cannot be done with the Central Administration application. There are a number of commands and lots to do though.
Can WSS search Sub Sites?
– WSS 3.0 has a basic search feature that will allow users to search for content. This is a big change from previous WSS versions, which required WSS to be configured to run on SQL Server 2000, using its Full-Text Indexing engine. Another important change is that WSS 3.0 will search in sub sites, while the previous version of WSS only searched in the current site. The following list summarizes the search functionality in WSS, when combined with SQL Server:
- Finds information of any type, stored in the current site, or a sub site.
- Provides free-text searching in documents, files, and all list content.
Can we register alerts for users?
– Alerts are an e-mail and Short Message Service (SMS) notification service in SharePoint Foundation. Users can create alerts to notify them of changes to list items (item-level alerts), documents, lists (list-level alerts), or document libraries.
Alerts in SharePoint Foundation are quite flexible; when you create an alert you have options such as when to be notified and what kind of changes trigger the alert. You can also select whether the alert for a particular list, item, or library will be sent by e-mail or by SMS message. Users and administrators can manage alerts, and developers can customize alerts.
Are PDFs searchable?
– Out of the box only the metadata collected in the upload form is search able. Unless you download and install the Adobe iFilter.
Describe a Large Deployment.
– Many front-end web server with a SQL cluster with the possibility of multiple international locations.
How can you synchronize custom Active Directory attributes to SharePoint?
– Via the Profile Importer.
If it is anticipated that our organization would need to store 1 terrabyte of documents, what is the recommended configuration and storage requirement?
– Multiple front-end web servers with content databases across the server farm. The amount of web-servers can depend on how many users you have and what the typical size of a document is.
Explain how you would deploy SharePoint on an extranet.
– Usually servers that are accessible from external sources are housed in DMZ’s. Depending on the requirements and the workflow for publishing content you could go with Multiple Servers hosting the same information. One server would reside inside with the SQL Cluster while the external server resides in the DMZ simply calling data. Security would be handled by the same or different active directory domain clusters as well increasing security.
What are the migration strategies for moving sites around?
– You could use the SharePoint Portal Server backup and restore tool as well as the STSADMIN and GUI STSAMIN tools. We have migrated database from the SQL Level and have simply reconnected the front end.
Download: SharePoint – Must Knows
Before we actually decide on which direction to head when it comes to SharePoint, we need to find out where our strength lie. If we are someone with an IT Admin experience, or someone with fair knowledge of Servers, IIS, SQL, etc, then preparing ourself to be a SharePoint Admin would be a good start. For someone whose strength lie elsewhere, like developing and coding, and are well versed with C#, VB, ASP.NET, then they might want to concentrate on being a SharePoint Developer.
We have talked about the Admins, we have talked about the Developers, now lets talk about the confused. As far as I am concerned, I have decided to get into the Administration part of SharePoint. I have to admit that I have no prior knowledge or experience as an IT Admin.
There is an amazing blog by Saed which explains the learning curve for SharePoint beginners in great detail, and I am sure it will be of great help to anyone who is undecided about SharePoint.
For developers, there is a terrific blog by Paul Galvin. Paul actually gives us an insight from a developer’s perspective, explaining his road map towards success in SharePoint.
Most of you would have seen the above two blogs. But if you haven’t already, then I strongly recommend them.
Training & Tools:
Even before I installed MOSS and began working with it, I decided to read lots of materials and watch Video Tutorials on the basics of SharePoint. There are lots of amazing books and video tutorials out there and the ones I have followed are
Once we have a fair understanding of both WSS(Windows SharePoint Servers) and MOSS(Microsoft Office SharePoint Server) theoretically, it is time for us to actually dirty our hands with the product. The best part is that Microsoft offers a free 180 days evaluation for both Windows Server 2008 R2, as well as MOSS 2010.
My affair with SharePoint began when I met a Premier Field Engineer from Microsoft some 6 months ago, in Dubai. We had a lengthy conversation regarding almost everything which finally ended up in SharePoint, triggering an interest in the subject deep within me.
I am aware that there are many amazing SharePoint blogs for everyone out there, be it for Developers or Administrators, Beginners or Advance Level users. What I really aim from this blog is to how to get started from an Administrator’s perspective(because I am too good at coding to be a developer), beginning with the very beginners, and making it as simple as possible.
I hope to share my self-training plan from the very beginning to the way up, and also will be regularly updating with must know definitions, questions and solutions from a MCTS certification perspective, the problems I run into and the workarounds I find for it.
Hope this proves useful for every beginner SharePoint enthusiasts out there.