Showing posts with label SharePoint 2013. Show all posts
Showing posts with label SharePoint 2013. Show all posts

Thursday 4 October 2012

Break Permissions Inheritence for a docuemnt library in Sharepoint 2013


No comments:
Breaking the Inheritence Option is a little hidden in SharePoint 2013. So here we have a trick on how to Break Inheritence and Set unique permissions for a docuemnt library.

Click on the "Library" tab  in the Ribbon and the click on "Share with"
Next click on "ADVANCED" in the pop-up.

 
Next Click on Stop Inheriting Permissions to set unique or Item level permission for the library.


Thursday 27 September 2012

Site Policies in SharePoint 2013


No comments:
A site policy specifies the conditions under which to close or delete a site automatically. There are the following four options:
  • Do not close or delete the site automatically
  • Delete the site automatically
  • Close the site automatically and delete the site automatically
  • Run a workflow to close the site, and delete the site automatically



  • Do not close or delete the site automatically. If a policy that has this option is applied to a site, the site owner must delete the site manually.

  • Delete the site automatically. If a policy that has this option is applied to a site, the site owner may close the site manually, but the site will be deleted automatically. A policy that deletes the site automatically specifies a rule for when to delete the site, and has the following options:
    • What action triggers the site to be deleted, and how long to wait after the trigger occurs before deleting the site. The trigger can be either site creation or site closure. For example, you can create a policy that deletes a site three months after the site is closed, or a policy that deletes a site one year after the site is created.
    • Whether to have SharePoint 2013 send a notification email message to the site owner a specified amount of time before the site is scheduled to be deleted.
    • Whether to allow site owners to postpone deletion of the site.

  • Close the site automatically and delete the site automatically. This option gives the same choices for how to delete the site automatically, and also requires you to specify how long after its creation time the site will be closed.

  • Run a workflow to close the site, and delete the site automatically. This option gives the same choices for how to delete the site automatically, and also requires you to specify a workflow to run. When the workflow finishes running, SharePoint 2013 closes the site. You specify the name of the workflow, how long after the site is created to run the workflow, and whether to rerun the workflow periodically until the site is closed.
    A site policy can also specify that if it is applied to the root site in a site collection, when the root site is closed, the root site and all sub-sites become read-only.

Tuesday 25 September 2012

SharePoint 2013 the New Continuous crawl


No comments:
A new Crawl Option "Continuous crawls" has been Introduced in Search's Crawl Schedule category. Continuous crawls help to keep the search index and search results as fresh as possible.Continuous crawls run every 15 minutes by default although you can configure crawl schedules for SharePoint content sources so that crawls are performed continuously.Setting this option eliminates the need to schedule incremental crawls and automatically starts crawls as necessary to keep the search index fresh. Administrators should still configure full crawls as necessary.

When running, the crawler gets changes from SharePoint sites and pushes them to the content processing component.The document will get processed by the content processing component on the fly. No index has to be merged. Items appear in the search results right after they have been crawled.

Enabling continuous crawl has the following advantages:

  • The search results are very fresh, because the SharePoint content is crawled frequently to keep the search index up to date.
  • The search administrator does not have to monitor changing or seasonal demands for content freshness. Continuous crawls automatically adapt as necessary to the change rate of the SharePoint content.

Sunday 23 September 2012

SharePoint 2013 - New Feature "Content Recommendation"


No comments:
Another awesome fetaure of SharePoint 2013 is "Content Recommendations". The new Analytics Processing Component in SharePoint Server 2013 runs different analytics jobs to analyze content in the search index and user actions that were performed on a site to identify items that users perceive as more relevant than others.

By including these recommendations on a page, you can guide users to other content that may be relevant for them. You can do this by adding Recommended Items and Popular Items Web Parts in the SharePoint 2013 site. You can configure the Web Part to display recommendations for the document or item that a user is viewing. For example, these recommendations can be displayed under the heading Users who viewed this document also viewed.


You can use the Popular Items Web Part to display the most popular items that satisfy a set of criteria. For example, these recommendations can be displayed under the heading Most popular items in this category.

The search recommendations framework works in the following way:

  • User actions produce usage events. When users interact with a SharePoint Server 2013 website — for example, when they click a link, press a button, or view a document — their actions are stored as usage events.
  • Usage events are counted and analyzed. The recommendations algorithm in the Analytics Processing Component counts and analyzes the usage events.
  • Information is added to the index.
    After processing in the Analytics Processing Component, the information is added to the search index and the Reporting database.

Thursday 20 September 2012

SharePoint 2013 - Unfollow SharePoint sites


No comments:
I found this little tricky so I am writting a blog post about it. So how do you unfollow any site once you start following it.

To unfollow the site navigate to My sites (under NewsFeed) and click on “I’m following”. This will take you to the screen where it shows you all the “Sites you’re following”.




click on star next to the site to unfollow it.

What Language will you use for SharePoint 2013 Apps


No comments:
So the question in the user group meeting was What Language will you use for SharePoint 2013 Apps?
Answer - It depends. here is the Chart that will help you decide.

  • Representational State Transfer (REST): For scenarios in which you need to access SharePoint entities from client technologies that do not use JavaScript and are not built on the .NET Framework or Silverlight platforms, SharePoint 2013 Preview provides an implementation of a REST web service that uses the Open Data (OData) protocol to perform CRUDQ (Create, Read, Update, Delete, and Query) operations on SharePoint list data. In addition, nearly every API in the client object models has a corresponding REST endpoint. This enables your code to interact directly with SharePoint by using any technology that supports standard REST capabilities. To use the REST capabilities that are built into SharePoint 2013 Preview, your code constructs a RESTful HTTP request to an endpoint that corresponds to the desired client object model API. The client.svc web service handles the HTTP request and serves a response in either Atom or JavaScript Object Notation (JSON) format.

  • .NET Framework client object model (.NET client OM): Almost every class in the core site and list server-side object model has a corresponding class in the .NET Framework client object model. In addition, the .NET Framework client object model also exposes a full set of APIs for extending other features, including some SharePoint Server 2013 Preview-level features such as ECM, taxonomy, user profiles, advanced search, analytics, BCS, and others.

  • JavaScript client object model (JS client OM):SharePoint 2013 Preview provides a JavaScript object model for use in either inline script or separate .js files. It includes all the same functionality as the .NET Framework and Silverlight client object models. The JavaScript object model is a useful way of including custom SharePoint code in an app, because custom server-side code is not allowed in apps for SharePoint. It also enables web developers to use their existing JavaScript skills to create SharePoint applications with a minimal learning curve.
When you want to access data in your app from SharePoint, you have to use the APIs that the app provides.

Monday 17 September 2012

SharePoint 2013 - Apps Related Errors


4 comments:
I am documents some the error that you can get while trying to Download and Install SharePoint Apps from the App store.


Error - "Sorry, there is a Problem with your Download"
Fix - Verify App Management Service is running on your WFE/app server.


Error -"Sorry we Couldn't determine which Apps to Show you. Please choose an available language from the options in the upper right corner."
Fix - Select the Laungage on the (no language selected) drop-down on upper right.


Error - "Sorry, apps are turned off. If you know who runs the server, tell Them to turn on the App Shared Service Management."
Fix - Verify App Management Service Shared service is running. Also Configure the Subscriptions setting service

Error - "Error occurred in deployment step 'Uninstall App for SharePoint' Value cannot be null. Parameter name value"
Fix - App has not Installed properly.Open the root site of your SharePoint website and click 'View Site Contents'. Here you will see your app installed.You need to remove the app by clicking on the ECB of the App and click the option Remove. After this you will get an error, just click retry. The app is now being uninstalled. After the uninstall try to remove the app again.


Error - "App domain must be configured prior to completing this operation"
Fix - You need to Configure an Isolated application domain to Install and run SharePoint 2013 App. Read more SharePoint 2013 App Error "App domain must be configured prior to completing this operation"


Error when you Turst an App - "Sorry, there was something wrong with the download. Try adding it again."
Fix -


Saturday 15 September 2012

SharePoint 2013 App Error "App domain must be configured prior to completing this operation"


No comments:
If you get the below SharePoint 2013 App Development

Error "App domain must be configured prior to completing this operation"

You need to Configure an Isolated application domain to Install and run SharePoint 2013 App. Ofcourse the application domain has to be added into the bypass list and trusted sites list to avoid authentication prompts.

Also you need to disable loopback check to avoid authetication issues.

Disabling Loopback Check:

1. Backup registry of the target machine.
2. Open registery editor(by typing regedit.exe or regedt32.exe in Start->Search program and files)
3. Add DWORD registry value DisableStrictNameChecking HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters and set it to 1 with base type Decimal
4. Add DWORD registry value DisableLoopbackCheck at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa and set it to 1 with base type Decimal
5. Close registery editor. Restart the machine
6. Deploy the app again.
7. Launch the app locally.


Using Poowershell -

New-ItemProperty HKLM:\System\CurrentControlSet\Control\Lsa -Name “DisableLoopbackCheck” -Value “1″ -PropertyType dword

Wednesday 12 September 2012

SharePoint 2013 - What's Friendly URLs?


3 comments:
New Concept of Friendly URLs has been Introduced.With this you can set URLs without the "/pages/" and even ".aspx".

Please Note - Using managed navigation enables this experience. Managed navigation provides a scheme for friendly URLs that is consistent across site, category, and item pages. Any page, including your site's Welcome Page, can have a friendly URL. Depending on how you configure your site, most pages using managed navigation automatically gets a friendly URL.

 Publishing Pages that have friendly URLs can still be requested using their physical URLs. If not dealt with properly this can lead to content duplication, particularly as in SharePoint 2013 Preview the canonical URL changes alongside and renders the physical URL of the page.

How to Create one?
 
1. Select “Managed Navigation” in Navigation in Site Settings.
2. Next Create Navigation Items in the Term Store with "Term Store Management Tool”.
3. Create a Term Set, Create Terms to reflect your desired navigation.
4. For each Term (navigation links) that you created, use the tabs at the top to manage “Navigation” and “Term-Driven Pages”.
You can choose between two Navigation Node Types:
-Simple Link or Header
-Term-Driven Page with Friendly URL
5. Next we will set the Friendly URL by moving to the next tab for the term, Term-Driven Pages. There you will find options to change the friendly url as well as setting the target page for the hyperlink.
 

Saturday 8 September 2012

SharePoint 2013 Now you can Cut and Paste from Word


No comments:
In addition to few awesome SharePoint 2013 Content Management Improvements MS in SharePoint 2013 has improved the output of the text that you Cut and Paste from Word in any Text Editor.

This is a huge Change as I know a lot Content editors would like to Paste directly from the Document into the Blog Body or Announcement description field. Lets look at how it looks

Word Document -



When you copy it in a Description Field of a Announcement it looks like below






Wednesday 5 September 2012

SharePoint 2013 Improvements in Excel Services


1 comment:
Excel Services provides users with a rich experience and new capabilities when working with web-based workbooks.

• Power View now empowers users to visually explore data, quickly create interactive visualizations, and easily present and share reports—all with the familiarity of Microsoft Excel 
• Users have the ability to mash-up and analyze data from virtually any source and rapidly create compelling analytical applications using PowerPivot in Excel and publishing to SharePoint Server.

• New data navigation features make it easier to drill into data displayed in Excel Services reports and dashboards.

• Timeline controls render in a browser window similarly to those in the Microsoft Excel client.

 • Context menus in a browser window resemble right-click menus in the Excel client.

• In a browser window, users can add, change, and remove items from rows, columns, values, and filters in PivotChart and PivotTable reports. • With Excel Services, users can publish workbooks that contain calculated measures and members.

These capabilities can help your organization achieve better business outcomes by increasing the effectiveness and efficiency of users, while reducing IT cost and complexity. Plus, because the IT department maintains control over security and policies, these benefits can be attained in a highly secure manner.

Tuesday 4 September 2012

Disable Content Follow and Site Follow Fetaure in SharePoint 2013


1 comment:
How to disable Content Follow and Site Follow Fetaure in SharePoint 2013 -

You can simply disable the corresponding Features in "Manage Site Features".

To disable Follow of Documents and other Content simply

1. Navigate to Site Actions and click on "Manage Site Features".

2. Next Deactivate the "Following Content" feature.




3. Deactivate the "Site Feed" feature here.


Monday 3 September 2012

SharePoint 2013 Content Management Improvements


No comments:
Some of the Improvements in the area of Content Management that Microsoft has made in the new SharePoint 2013 version are :


Preview Content - A very powerful preview feature has been Introduced where you can see Preview of each document that you upload in SharePoint 2013 document library.


Digital Asset Content Types (Audio, Video Content Types) - In SharePoint 2013 MS has introduced a new set of content types called “Digital Asset Content Types” for better use of Audio, Video, Images as Web content. These content types can be added to any library and be used as a one of the items\files.

Embed Docuemnts\Images\Videos -  Now you can embed documents, Videos and Images on the page itself with the Embed code available for each of them.

Insert an IFrame in HTML field (Content Editor, Description Field) - In SharePoint 2013 admins can now Insert an iframe element into an HTML field like Content editor webpat on a page. This will let users Embed dynamic content from other sites, such as videos or map directions on any SharePoint site page.

Image renditions - Image renditions let you display different sized versions of an image on different
pages. When you create an image rendition, you specify the width and height for all images that use that image rendition. For example, if the site has a news article page layout that contains an image field, you can create an image rendition named Article_image to display the full-sized image in the article page.

Wednesday 29 August 2012

Whats New at SharePoint 2013 and PerformancePoint Services 2013


No comments:
Whats New with SharePoint 2013 and PerformancePoint Services 2013. The Architecture and general model has remained the same but they have made some good enhancements that I am going to Point out here.

Dashboard Designer -  Dashboard Designer is now an Ribbon button. Clicking on the Dashboard Designer Ribbon button launches the dashboard designer The appearance of the PerformancePoint ribbon tab is based on content type. So it appears in document libraries where the "Web Part Page" content type is present, and it appears in lists where any of the PerformancePoint content types have been added. This whole feature is great because now you can launch the designer without having to navigate to the old, BI Center landing page.

Integrated Themes - PerformancePoint 2013 Services now Inherit SharePoint 2013 Themes. The Dashboards will look now be prettier than ever before. The background Images from the themes actually bleed through the elements on your dashboard.

New BI Center -   The ppssample.aspx page that you may have used in SharePoint 2010 product (Site Contents --> Pages) has been changed to make the Componenets simpler.

Filter Enhancemnets (Cascading Filters) -  
You can now
  •  show sub selections in tree filters by bolding each parent in the hierarchy.
  • dynamically size the tree filter height based on the number of visible items in the tree.
  • select different tree filter actions by
    • selecting all
    • clearing all
    • resetting to default
    • selecting children
    • getting all filter items (when 5,000 limit is reached)
  • create a filter based off a measure
  • see significant performance improvements
PerformancePoint 2013 support on iPad

Dashboard Migration - Now you can Migrate the Dashboard that you Created in SharePoint 2010 to SharePoint 2013.

Monday 27 August 2012

What got Removed in SharePoint 2013


1 comment:
A list of what got Removed in SharePoint 2013 -

Web Analytics - The SharePoint 2010 Web Analytics system is being removed and will no longer be available or upgraded. This service was not available for Office 365, and so this change affects only the on-premises SharePoint 2013 Preview product.
Benefits -
Replaced by a new analytics system that is a subcomponent of the search system. Every click in SharePoint is still logged and still provides a hit count for every document in SharePoint, but user data is made anonymous early in the process and is made scalable to the service.

The data is used as follows:

  • Drive new item-to-item recommendation features.
  • Show view count embedded in various SharePoint and Search UIs.
  • Provide a report of the top items in a site and list.
  • Influence the relevancy algorithm of search.
Editing workbooks in a browser that has external data connections -
Workbooks that have external data connections that require Windows Authentication cannot be edited in the browser. Users who attempt to open them are prompted to open the workbooks in the client. Workbooks that have database credentials stored in the Secure Store or in the connection string can still be edited.
Benefits -
Users can get better scale-out and management by using Office Web Apps Server Preview instead of Excel Services.

PowerPoint Broadcast hosted on SharePoint 2013 Preview -
In Office 2010, the PowerPoint Broadcast feature can be configured to use a SharePoint 2013 Preview site to host broadcasts, in addition to a free public service hosted on Windows Live. In Office 2013 Preview, the SharePoint 2013 Preview capabilities are removed.After a user upgrades to SharePoint 2013 Preview, PowerPoint client users will no longer be able to select a SharePoint 2013 Preview site as a host for broadcasts.
Benefits -
Lync offers a fuller experience, for example, integrated audio, chat, telecommunications integration. Broadcast provides only a small portion of what is required in a remote collaboration scenario. In Office 2013 Preview, the broadcast technology is integrated into the Lync client so that the overall quality of document rendering is the same as in previous broadcasts, and also includes the Lync features.
Modify search topology by using the Search Service Application User Interface -
UI for changing search topology is no longer supported. Search topology can be changed only by using Windows PowerShell.
 
SharePoint Designer - Removing Design and Split Views of Page editing Earlier versions of SharePoint Designer had both code and design view for editing ASPX/HTML pages in SharePoint Server. In SharePoint Designer 2013 Preview, the design view is removed.
Benefits - The design view technology is not as up-to-date as the current Internet Explorer. In addition, code view is much more widely used than design view. Design view cannot support the new tags in HTML5 and new cascading style sheets that are used in SharePoint 2013 Preview.
 
Site Templates - Document Workspace -  Removing the ability to create new Document Workspace sites.
Benefits - Reduces any confusion about which site template to use to create a new site.
 
Site Templates - Personalization -  Removing the ability to create new Personalization sites.
Benefits - Reduces any confusion about which site template to use to create a new site.


Saturday 25 August 2012

Add an Audio or Music file in SharePoint 2013


No comments:
SharePoint 2013 now has a Content type for Audio,Video,Image and more these are called "Digital Asset Content Types". You can use these content types as you use any other the only thing is that these content types has its own set of Site columns that are specif to these types.
In this post we will see how to add a Audio file in a SharePoint 2013 site and then add it to a page.


Steps -

1. Naviagate to your library where you want to upload the Music file.
2. Add a Audio Content type in your library.
3. You either add your New Audio file by "New Document" or Drag and drop the music file in your library.
This is how it gets Added


If you Noticed the Preview pane you have Full Screen, Embed Code and Play buttons.

4. Get the Embed Code to this Music file to add to a new page.




Copy the embed code and we add add to a Script Editor WebPart on any SharePoint page.

New Master Pages Introducted in SharePoint 2013


No comments:
A quick list of all new Master Pages Introduced in SharePoint 2013

App.master -

Location: \TEMPLATE\GLOBAL\app.master
belltown.master

Location : \TEMPLATE\GLOBAL\belltown.master

belltown.preview

Location : \TEMPLATE\GLOBAL\belltown.preview

mwsdefaultv15.master

Location: \TEMPLATE\GLOBAL\mwsdefaultv15.master

overlay.master

Location : \TEMPLATE\GLOBAL\overlay.master

overlay.preview

Location : \TEMPLATE\GLOBAL\overlay.preview
v15.master

Location: \TEMPLATE\GLOBAL\v15.master

v15.preview
Location : \TEMPLATE\GLOBAL\v15.preview

Thursday 23 August 2012

SharePoint 2013 - New eDiscovery


No comments:
eDiscovery in SharePoint 2013 includes new ways to reduce the cost and complexity of discovery. These include:

  • The eDiscovery Center, a central SharePoint site used to manage preservation, search, and export of content stored in Exchange and SharePoint across SharePoint farms and Exchange servers.
  • SharePoint In-Place Hold, which preserves entire SharePoint sites. In-Place Hold protects all documents, pages, and list items within the site but allows users to continue to edit and delete preserved content.
  • Exchange In-Place Hold, which preserves Exchange mailboxes. In-Place Hold protects all mailbox content through the same UI and APIs used to preserve SharePoint sites.
  • Query-based preservation allows users to apply query filters to one or more Exchange mailboxes and SharePoint sites and restrict the content that is held.
In SharePoint Server 2010 MS delivered eDiscovery functionality and APIs as part of its records management feature set.


Key new features include:

Site-based management and collaboration for eDiscovery cases with statistical tracking. Each case has its own site with an “eDiscovery Set”—the universe of search resources and their search filters (as well as action options).
  • All sites are accessed through a common portal (the eDiscovery Center) for search, preservation, query and export of relevant materials. Search results are displayed based on the user’s permissions.
  • Multiple Exchange mailboxes, SharePoint sites/farms and file shares can be associated with cases and then preserved in their entirety or queried to refine the pool of preserved content.
  • Content holds include a new “in-place hold,” a feature that enables users to continue working with the preserved content from Exchange mailboxes and SharePoint sites. Users can change the content, but a content snapshot is recorded at the time of preservation and stays in hold, even if the user deletes the content. All held material is indexed in a preservation hold library visible only to Administrators and other authorized individuals.
  • Query-building enables authorized users to define a scope for searching held resources, with additional filtering by message type or file type. Users can then view statistics about the items, preview results (documents; lists; pages; Exchange objects) and export (into the Electronic Data Reference Model format) the items for separate review, if desired.

Monday 20 August 2012

SharePoint 2013 - Retrieve List Items using REST


No comments:
A simple example of how to Retrieve List Items using REST that will be useful while creating a SharePoint apps.
 




//This method retrieves all items from a specified list.
  private void RetrieveListItems(Guid listId)
  {
            TokenHelper.TrustAllCertificates();

            string contextTokenString = TokenHelper.GetContextTokenFromRequest(Request);

                contextToken =
                    TokenHelper.ReadAndValidateContextToken(contextTokenString, Request.Url.Authority);

                sharepointUrl = new Uri(Request.QueryString["SPHostUrl"]);

                accessToken =
                    TokenHelper.GetAccessToken(contextToken, sharepointUrl.Authority).AccessToken;

              if (IsPostBack)
            {
                sharepointUrl = new Uri(Request.QueryString["SPHostUrl"]);
            }

              //Add pertinent namespaces to the namespace manager.
            xmlnspm.AddNamespace("atom", "http://www.w3.org/2005/Atom");
            xmlnspm.AddNamespace("d", "http://schemas.microsoft.com/ado/2007/08/dataservices");
            xmlnspm.AddNamespace("m", "http://schemas.microsoft.com/ado/2007/08/dataservices/metadata");

            //Execute a REST request to get the list name.
            HttpWebRequest listRequest =
                (HttpWebRequest)HttpWebRequest.Create(sharepointUrl.ToString() + "/_api/Web/lists(guid'" + listId + "')");
            listRequest.Method = "GET";
            listRequest.Accept = "application/atom+xml";
            listRequest.ContentType = "application/atom+xml;type=entry";
            listRequest.Headers.Add("Authorization", "Bearer " + accessToken);
            HttpWebResponse listResponse = (HttpWebResponse)listRequest.GetResponse();
            StreamReader listReader = new StreamReader(listResponse.GetResponseStream());
            var listXml = new XmlDocument();
            listXml.LoadXml(listReader.ReadToEnd());

            var listNameNode = listXml.SelectSingleNode("//atom:entry/atom:content/m:properties/d:Title", xmlnspm);
            string listName = listNameNode.InnerXml;

             //Execute a REST request to get all of the list's items.

            HttpWebRequest itemRequest =
                (HttpWebRequest)HttpWebRequest.Create(sharepointUrl.ToString() + "/_api/Web/lists(guid'" + listId + "')/Items");
            itemRequest.Method = "GET";
            itemRequest.Accept = "application/atom+xml";
            itemRequest.ContentType = "application/atom+xml;type=entry";
            itemRequest.Headers.Add("Authorization", "Bearer " + accessToken);
            HttpWebResponse itemResponse = (HttpWebResponse)itemRequest.GetResponse();
            StreamReader itemReader = new StreamReader(itemResponse.GetResponseStream());
            var itemXml = new XmlDocument();
            itemXml.LoadXml(itemReader.ReadToEnd());

            var itemList = itemXml.SelectNodes("//atom:entry/atom:content/m:properties/d:Title", xmlnspm);

            TableRow tableRow = new TableRow();
            TableCell tableCell1 = new TableCell();
            tableCell1.Controls.Add(new LiteralControl(listName));
            TableCell tableCell2 = new TableCell();

            foreach (XmlNode itemTitle in itemList)
            {
               // itemTitle.InnerXml + "<br>";
            }
 
        }

SharePoint Apps Error - "Error occurred in deployment step 'Uninstall App for SharePoint': Value cannot be null. Parameter name: value"


1 comment:
If you are getting the below error while adding an SharePoint App you probably hit a bug in Office 365 developer site.

 Error - "Error occurred in deployment step 'Uninstall App for SharePoint': Value cannot be null. Parameter name: value"

I got this error thrice at different times and in different Apps... Microsoft says its a bug as per the Discussion Here but I am still looking for a good explanation.