ASPHostCentral.com SharePoint 2013 Hosting BLOG

All about Sharepoint 2013 Hosting articles

Microsoft Emphasizes Cloud-First with SharePoint 2013 Hosting

clock December 20, 2012 17:18 by author Administrator

As Microsoft showcased its new SharePoint 2013 and the SharePoint online upgrades to its Office 365 service this week, it raises the question of how far organizations are willing to go to phase out their premises-based software in favor of shifting everyday work to a service-based model.

That's not to suggest that organizations will or should scrap their SharePoint deployments in favor of Office 365 or some other instantiation of Microsoft's collaboration platform that's subscription-based or hosted elsewhere. It's not an either/or proposition. But Microsoft left little doubt it wants you to gravitate to the SharePoint Online component of its Office 365 service.

"We really recommend moving to the cloud for the best experience overall," said John Teper, the Microsoft corporate vice president known as the "father of SharePoint," speaking in his opening keynote at the annual SharePoint Conference in Las Vegas Monday. "We understand not everyone is there yet. This will take time. People who want to run their own servers, that's great. We have the best server release we've ever done in SharePoint 2013. The thing you should take away from our cloud focus is all we've learned about optimizing the system and deployment and monitoring, we've put into the server product and put into the deployment guidance."

SharePoint 2013's "Cloud-First" model follows in the footsteps of Microsoft's promise that it will deliver infrastructure software and applications as a cloud service first or simultaneously with the release of the on-premise version of its key products. That came to life with last year's CRM Online Dynamics CRM duo. Now Microsoft is employing the same approach with the latest version of SharePoint Online in the Office 365 service and SharePoint 2013.

One of many distinctive new cloud features in SharePoint 2013 and SharePoint Online is the new SkyDrive Pro, an evolution of the SharePoint Workspace. SkyDrive Pro raises the bar in synchronizing content between SharePoint Sites and workers' various devices. SkyDrive Pro is modeled after the consumer-based SkyDrive service, except it's built into SharePoint, which allows IT organizations to manage it.

Experts are predicting more rapid than usual uptake for the new release of SharePoint and Office 365, primarily due to the major overhaul of the SharePoint experience, which brings enterprise social networking to the forefront.

A Forrester Research poll of 153 clients who already have SharePoint found 68 percent of respondents planned to introduce the new version within two years (37 percent within the first year and 31 percent within the second). What's interesting about that finding is 70 percent of that sample said they already have upgraded to SharePoint 2010, which is unusual since organizations typically skip subsequent releases to amortize their investments.

"This is conjecture here but it could be around the social experience," said Forrester analyst Rob Koplowitz in an interview. "The feedback on the social facilities in SharePoint 2010 was pretty dismal. That might be the driver but others include the need for improved document and records management. Also, it could be they're trying to move to a more stable development environment."

Speaking of social networking, that's where Yammer comes in, the popular social networking company Microsoft just acquired for $1.2 billion. Microsoft announced it's bundling the popular cloud-based enterprise social networking service, into SharePoint 2013 and Office 365 in addition to offering it as a standalone offering and plans further integration.

In the annals of Microsoft's cloud transition, 2010 will be remembered as the year CEO Steve Ballmer proclaimed the company is "all-in." With the revamp of SharePoint and Office, we may get our biggest sense yet how many Microsoft's customers are all-in.

Currently rated 2.0 by 210 people

  • Currently 1.976189/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5


SP 2013 Hosting :: How to solve error message "Unable to retrieve topology component health states. This may be because the admin component is not up and running"

clock December 16, 2012 13:32 by author Administrator

Sometimes, when you are playing with SharePoint 2013, you will encounter this error message: “Unable to retrieve topology component health states.  This may be because the admin component is not up and running.” You will see this error message on your Central Administration page -> Application Management -> Manage Services on the server -> click on the “SharePoint Search Server”




This article provides resolution on SharePoint 2013 that is installed on Windows Server 2008 R2 SP 1 and SQL Server 2008 R2. The server is not a domain controller or hosting SQL either.
 
To resolve this issue, please download the following fixes on Microsoft website

KB 2554876
KB 2708075
KB 2472264

If after installing the above hotfixes and you still encounter issue, you need to run Windows Update and installing all patches/hotfixes reported as critical.

Once this had been done (and a reboot or two later), the problem will be resolved!

The updates in installed are below (so it’s one or more of them?)

 

Currently rated 2.9 by 204 people

  • Currently 2.857843/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5


SharePoint Foundation 2013 Hosting :: Setting up your App domain for SharePoint 2013

clock December 9, 2012 13:43 by author Administrator

The most important change in SharePoint 2013 for developers is the introduction of SharePoint apps. An app for SharePoint is a small and isolated application that provides a specific bit of functionality. SharePoint apps can and have to be added to or removed from a site by the site owner.  Apps have their own, isolated URLs, which are separate from the URLs of the sites where the app is being deployed to and where the app is being used. In order to provide isolation apps run in their own domain, instead of in the same domain name as your farm. Using a different domain name for apps helps prevent cross-site scripting between apps and SharePoint sites.

Each installation of an app has its own unique URL within the app domain. The app’s URL is based on a template “http://[app prefix][app hash].[app domain]/[relative site url]/[app name]. When you add an app to a site, a subweb of that site is created to host the app content. This subweb is not visible on the Site Contents page though.

Because apps run in their own app domain you will have to configure Domain Name Services (DNS) in your environment in order to be able to host apps. There is a page on TechNet that describes how to setup you DNS, but because it took me a while to get it all working I decided to write a step by step guide, which is what you’re reading now.

You can choose whether you want your app domain to be a subdomain of the domain that hosts the SharePoint environment (option B), or whether you want to create a completely new domain for your apps (option A). Creating a new domain specifically to host your apps in is a bit more secure, but it also requires a little bit more configuration. I will describe both approaches in this article. If you don’t have control over your DNS you will have to ask an administrator to perform these steps for you.

Option A: Create a new domain to host your apps in

- Go to “Start”
- Click on “Administrative Tools”
- Select “DNS”
- Right click “Forward Lookup Zones” and select “New Zone…”
- Click “Next”
- Keep the default and click “Next” again
- In most cases, especially if your development server is in it’s own domain you can use the default on the next tab again and can just click “Next”
- You now have to specify a zone name. It’s up to you what you choose here. My domain name is “solutions.com” and for my app domain I will use “solutionapps.com”
- Click “Next”
- Click “Next”
- Click “Finish”
- Right click on your new zone and select “New Alias (CNAME)…”
- Fill in a * for “Alias name (uses parent domain if left blank)”
- Click “Browse”
- Double click on your server name
- Double click “Forward Lookup Zones”
- Double click the domain of your SharePoint environment. In my case this is “solutions.com”.
- Select “(Same as parent folder)” and click “OK”
- Click “OK”.

* Note that selecting the FQDN of the domain in here will only work in single server scenarios. If you are using more than one server you should be pointing to the DNS record of the web server in here. This is either the DNS A record for the web server, or the DNS record of the primary cluster address for NLB environments.

You are now done setting up your DNS and it should look like this:

Option B: Create a subdomain to host your apps in

- Go to “Start”
- Click on “Administrative Tools”
- Select “DNS”
- Right click on the name of your domain and select “New Alias (CNAME)…”
- Fill in “*.app” for “Alias name (uses parent domain if left blank)”
- Click “Browse”
- Double click on your server name
- Double click “Forward Lookup Zones”
- Double click the domain of your SharePoint environment. In my case this is “solutions.com”
- Select “(Same as parent folder)” and click “OK”
- Click “OK”

* Note that selecting the FQDN of the domain in here will only work in single server scenarios. If you are using more than one server you should be pointing to the DNS record of the web server in here. This is either the DNS A record for the web server, or the DNS record of the primary cluster address for NLB environments.

You are now done setting up your DNS and it should look like this:

Configuring SharePoint

I’m assuming you already created an App Management and a Subscription Settings Service Application and that you already started the App Management and Subscription Settings services on your servers. If not this MSDN article will tell you how to. Note that you have to use PowerShell to create the Subscription Settings Service Application. There is no user interface for it.

- Go to Central Administration
- Click on “Apps” in the left side navigation
- Click “Configure App URLs”
- Fill in the URL of the app domain that you configured. If you choose to use Option A the url will be something like “solutionapps.com”, if you choose to use Option B it will look like app.solutions.com.
- Fill in an app prefix. This can be anything you like, although it is best to keep this short. I used “app” myself.

Beware of host headers

You are now ready to deploy your apps. Because of all this extra domain stuff though there are a few things you should know about your web applications and site collections.

If you are using a host header for your web application apps won’t just work for that web application. Because of how the redirect for the app domain works IIS will try to resolve the app url by using the default IIS web site, which of course doesn’t work. If you want to use host headers for your web applications you have to create an extra web application that is listening on port 80 (or 443 if you are using https) and that doesn’t have a host header.

This means that you have to create a web application like you normally would. You have to make sure that you select port 80 (or 443 if you are using https) and you should not fill in a host header. Note that you have to stop the Default Web Site in IIS in order to be able to do this. The web application will use the server name as its url. The web application can be empty except for a root site collection.

Another option is to use web applications without host headers and to create Host Header Site Collections. Be aware that Host Header Site Collections cannot be created via the user interface, they can only be created by using PowerShell.

Currently rated 2.9 by 179 people

  • Currently 2.938549/5 Stars.
  • 1
  • 2
  • 3
  • 4
  • 5


Sharepoint 2013 Hosting

ASPHostCentral is a premier web hosting company where you will find low cost and reliable web hosting. We have supported the latest ASP.NET 4.5 hosting and ASP.NET MVC 4 hosting. We have supported the latest SQL Server 2012 Hosting and Windows Server 2012 Hosting too!



Calendar

<<  August 2018  >>
MoTuWeThFrSaSu
303112345
6789101112
13141516171819
20212223242526
272829303112
3456789

View posts in large calendar

Sign in