Dedicated SharePoint 2013 or Hosted SharePoint 2013, SharePoint 2013 hosting overview, SharePoint Collaboration

PlexHosted – Dedicated SharePoint 2013
Dedicated SharePoint 2013 Hosting, Hosted SharePoint 2013

Dedicated SharePoint 2013 Hosting
Dedicated SharePoint 2013 Hosting
Dedicated SharePoint 2013 Hosting, SharePoint Site Hosting, SharePoint Dedicated
Dedicated SharePoint 2013 or Hosted SharePoint 2013
SharePoint 2013 is a platform for effective business and collaboration. Many companies prefer using it as a tool that increases productivity, saves money and time. It has an easy and familiar interface, so there is no need in additional education of employees, and it is flexible for some specific needs.

When choosing this platform customer have two options – purchasing dedicated Dedicated SharePoint 2013 or hosted in multi-tenant enironment. This choice usually depends on several factors, like a size of the company, its specific business needs, space requirements and other. If the company need to have a full administration control of SharePoint, SQL servers – it is better to choose the dedicated environment for the SharePoint service hosting.

Dedicated SharePoint 2013

Dedicated SharePoint 2013 provides customers with more fundamental control of their SharePoint 2013 farms. Developers or other employees have an ability access to the Central Administration and to the servers via RDP (Remote Desktop Protocol) as well. Also the space storage is rather large – started from 100 GB. This is the best solution for IT professionals and developers, as it allows any ways of customization sites, like deploying custom web parts, apps etc. Users also can appreciate developing and adaptation of business solutions and applications using familiar tools – Microsoft Visual Studio 2012 and SharePoint Designer 2013.

Hosted SharePoint 2013

Hosted SharePoint 2013 is a SharePoint solution that stored in the multi-tenant (shared) environment. It allows users to subscribe a suitable plan without installing and deploying Microsoft SharePoint Server on-premises, which saves time and money and give the opportunity appreciate abilities of Microsoft SharePoint 2013. It is the hosting company that performs root control of the servers. And the data storage may be much smaller – from 500 MB.

The best way of using SharePoint 2013

So, depending of what you need, you can find the best way of using SharePoint 2013. But firstly you should consider that not all of hosting companies offers both services and not all of subscription plans are available in the hosting companies. It is the better way to find a reliable hosting company that offers secure and flexible services, backups and high level of support. At PlexHosted your support is key to our business. A highly reliable and knowledgeable hosting partner is critical to your hosting success. PlexHosted support engineers are available 24/7/365 – when you have questions, we will more than likely have answers.

Dedicated SharePoint 2013
Multi-tenant SharePoint 2013

How to clear the Windows SharePoint 2010 Services configuration cache

There were many common issues that could occur in WSS v3 and MOSS that would require you to clear the configuration cache on your servers. While less common, these issues can still turn up occasionally on SharePoint Server 2010 (And Foundation). While the resolution for these issues might be the same, the steps are a bit different. The main thing to note is that the Configuration Cache is located in a different directory on Windows Server 2008 then it was in Windows Server 2003. The new path for the Configuration Cache under Windows Server 2008 is: %SystemDrive%ProgramDataMicrosoftSharePointConfig The overall steps remain largely the same:

  1. Stop the Timer service. To do this, follow these steps:
    • Click Start, point to Administrative Tools, and then click Services.
    • Right-click SharePoint 2010 Timer, and then click Stop.
    • Close the Services console.
  2. On the computer that is running Microsoft SharePoint Server 2010 and on which the Central Administration site is hosted, click Start, click Run, type explorer, and then press ENTER.
  3. In Windows Explorer, locate and then double-click the following folder:
  4. %SystemDrive%ProgramDataMicrosoftSharePointConfigGUID
  5. Notes
    • The %SystemDrive% system variable specifies the letter of the drive on which Windows is installed. By default, Windows is installed on drive C.
    • The GUID placeholder specifies the GUID folder. There may be more than one of these.
    • The ProgramData folder may be hidden. To view the hidden folder, follow these steps:
      • On the Tools menu, click Folder Options.
      • Click the View tab.
      • In the Advanced settings list, click Show hidden files and foldersunder Hidden files and folders, and then click OK.
      • You can also simply type this directly in the path if you do not want to show hidden files and folders.
  6. Back up the Cache.ini file. (Make a copy of it. DO NOT DELETE THIS FILE, Only the XML files in the next step)
  7. Delete all the XML configuration files in the GUID folder (DO NOTE DELETE THE FOLDER). Do this so that you can verify that the GUID folders content is replaced by new XML configuration files when the cache is rebuilt.
    Note When you empty the configuration cache in the GUID folder, make sure that youdo NOT delete the GUID folder and the Cache.ini file that is located in the GUID folder.
  8. Double-click the Cache.ini file.
  9. On the Edit menu, click Select All.
  10. On the Edit menu, click Delete.
  11. Type 1, and then click Save on the File menu. (Basically when you are done, the only text in the config.ini file should be the number 1)
  12. On the File menu, click Exit.
  13. Start the Timer service. To do this, follow these steps:
    • Click Start, point to Administrative Tools, and then click Services.
    • Right-click SharePoint 2010 Timer, and then click Start.
    • Close the Services console.
  14. Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
  15. Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.
  16. Check in the GUID folder to make sure that the xml files are repopulating. This may take a bit of time.