Study Materials for 70-410, 70-411 and 70-412

I will be using the follow study material

We need 3 kinds of materials

1) Books

2) Video Courses

3) Labs Labs Labs


1) MVA (

Pre Req –

PreReq –

Pre Req –

2) TrainSignal Courses –

3) MCSA Windows Server 2012 Complete Study Guide by William Panek

4) Lab – TechNet Virtual labs for practice

Posted in WS2012 | Tagged , , , , , | Leave a comment

MCSA in Windows server 2012

MCSA Windows Server 2012

As we are aware Microsoft wants us to be certified in WS 2012 before achieving MCSE in SharePoint.

I am planning to work on this goal for this year.

I will post my experiences, study plan and books/reference material in this blog post series.

Make sure to follow my blog posts every Week to see latest updates/notes. Writing blog posts will encourage me to study and motivate others as well.

Posted in SharePoint 2013, WS2012 | Tagged , , , | Leave a comment

New Features in SharePoint 2013 – Part 7 (Service Applications)

Service Applications in SharePoint 2013

While SharePoint Server 2013 Preview provides a service application architecture consistent with SharePoint Server 2010, its new services are designed to maximize your investment and make information available to more people, in more formats, with more efficiency. In Microsoft SharePoint 2013 Preview, the service architecture model provides a framework in which you deploy and manage services across a farm or across multiple farms. A service application represents a deployed instance of a service that you can configure and manage centrally and that many web applications can consume. You can configure individual services independently and third-party companies can add services to the platform. Please see below for a list of service applications, new Service Applications in 2013 are highlighted in RED Rectangles.

As seen above, some new service applications are available in SharePoint 2013 and there are huge improvements in existing ones. For example, Office Web Apps is no longer a service application, it is separated as own product (so it can be used in Exchange 2013 and Lync 2013 and can be patched separately). Also, Web Analytics is no longer service application (it is incorporated into search service application). Deployed services are called as service applications.

Cross Farm Services in SharePoint 2013:

You can share some services across server farms. Services that support sharing across farms can be run in a central farm and consumed from other farms in the environment. For services to work in a consuming farm we first need to enable publishing within the service application on the master farm and then consume it on the child farm by creating a service end point or a service application connection proxy. Sharing across farms is currently supported only in below services. Some of which are not recommended in WAN environments because of latency issues.

  • Machine Translation Service (highly recommended in WAN Environments)
  • Managed Metadata Service (highly recommended in WAN Environments)
  • Search (highly recommended in WAN Environments)
  • Business Data Connectivity (moderately recommended in WAN, depending on situation)
    • Business Data Connectivity can be used in WAN depending upon the location of Line of Business Application and how the connectivity is actually done (performance implication).
  • Secure Store Service(Not recommended in WAN Environments)
    • Secure Store Service actually works in a WAN environment, but is not recommended as it could have performance impact of the service across WAN.
  • User Profile Service (Not recommended in WAN Environments)
    • UPS requires direct database access, which means there are some operations which do not follow service application proxy (this is to improve performance). If you still need to use UPS, then there is UPRE (User Profile Replication Engine – could be available as a separate download). UPRE could be utilized to replicate user profile entities across farms.

As seen above, each web application can be configured to use services from different farms. For example, you can share the User Profile Service across web applications in several server farms while using some services, such as the Excel service, locally.

In large environments, computing-intensive services can be run in a central farm to minimize administration overhead and to scale out easily and efficiently as requirements grow.

PS: Remote farms do not need direct permissions to the parent farm’s configuration or services databases.

How are Service applications deployed?

Service applications can be deployed using Initial Configuration wizard, Central Admin console and Windows PowerShell (Recommended). Deploying service application from PowerShell provides you with a flexibility to provide process isolation by deploying them in specific application pools. You can apply different service accounts to service application. You can assign database names and implement naming convention. You can implement custom settings when the service application is deployed.



Posted in Architecture, SharePoint 2013 | Leave a comment

New Features in SharePoint 2013 – Part 6 (Sharing)


Sharing a document or a site has significantly improved in SharePoint 2013. In this blog post, we will 1st look at all the problems in previous versions of SharePoint and see how the newer version solves those problems with new features. We will also discuss about all the new features in SharePoint 2013 in detail.

What are some of the problems with Sharing in previous versions?

Sharing in previous version (MOSS 2007, SharePoint 2010) had lots of problems that Microsoft wanted to solve. Some of them are listed below.

  1. Granting access to a site can be a bit convoluted
  2. Users don’t understand what permission level to grant to other users even if they had the right to grant
  3. Users generally don’t know who has permissions on a site
  4. Users can’t see the invitations that have been sent out to external users. They have no idea of what could have happened from that point forward.
  5. Users don’t understand what rights they are giving people when they add them to a SharePoint group
  6. Access requests in SharePoint 2010 are very limited. So for example, we can only request access if we have no access at all
  7. We have no obvious ways to ask for additional level of access
  8. We can’t share with others if we don’t have “Grant Permissions” right, which only Owners have by default.
  9. Even if users have submitted a request, there is no way of seeing the status of their requests
  10. Sharing is typically done for the whole site, when usually the only thing people want to share an individual element of the site collection such as a web, list or library
  11. Site owners didn’t have a page to see all pending requests to their sites and manage them
  12. Users can’t see the level of access they themselves have within a site collection

How do we solve those problems?

Sharing in SharePoint 2013 is designed to address the above limitations with the following new Sharing features:

  1. To address these concerns, a Sharing dialog which is used everywhere for adding users, distribution groups, and security groups to SharePoint sitecollection has been introduced
  2. An email invitation with a message that can be customized before it goes out
  3. A “request on behalf of” feature, where if we don’t have rights to add someone to the site, then we can send a request on someone else’s behalf.
  4. A requests management page where admins can view all the requests and respond to them. It also shows them a history of how these requests have been handled in the past
  5. A Personal Permissions page where users can request more permissions than they currently have
  6. A conversation component to requests has also been added, so admins and users can discuss about the request and it can be used for compliance purposes

How do we access these new Sharing features?

  1. Users can share a site from the Site Actions menu
  2. Users can also request access via the access denied page, like they did before
  3. If a user has the Grant Permissions right, they themselves can share the element to other users, otherwise the requests must be handled by an admin

NOTE: We MUST have configured the outgoing SMTP server for a web application or the “Share this site” menu option will not appear for anyone but site collection admins

Now let’s discuss how an admin would provide access in different scenarios.

If an admin wants to provide additional rights to an end user, he can click on “Share” link at the top of the page to provide additional rights.


After clicking on “Share” link, the “Share” dialog opens up. If we look at below sharing dialogs, we can enter the names of individuals and it will automatically start populating the list of users that match that name. It will also display “Show Options” label. When we click on Show Options, it displays all the groups with different permission levels (Edit, Full Control, Read and View Only).

The admin can also see a list of all the pending requests in the “Access Requests and Invitations” (http://…/Access%20Requests/pendingreq.aspx) page. We can accept or decline a request, or add comments to request additional details. A link also shows up on Site Permissions page when request are pending. Users can view all of their own pending requests from the Site Permissions page. They can also see and respond to admin comments

Sharing – Granting Rights:

Selecting a request gives us request details and lets us assign rights or decline, or ask for more info. And when we grant rights, it shows us what permission levels are associated with groups.




Posted in SharePoint 2013 | Leave a comment

Deployment guide for SharePoint 2013

Deployment guide for SharePoint 2013 ->

This serves as an excellent source of reference.

Posted in SharePoint 2013 | Tagged , , , | Leave a comment