Saving a Site Template with activated Publishing Feature is not possible in SharePoint 2013 (menu link missing).
When using the direct browser link (which worked perfect in SharePoint 2010) http://YourSharePointSite/_layouts/15/savetmpl.aspx you get the error The "Save site as template" action is not supported on this site.
Modify the SaveSiteAsTemplateEnabled property in your SPWeb object via PowerShell.
# Store your Site in a variable: $SiteToModify = Get-SPWeb http://YourSharePointSite # Display the current value of the property: $SiteToModify.AllProperties["SaveSiteAsTemplateEnabled"] # Set the property to true: $SiteToModify.AllProperties["SaveSiteAsTemplateEnabled"] = "true" $SiteToModify.Update()
When now trying the savetmpl.aspx link again, you can save your template: http://YourSharePointSite/_layouts/15/savetmpl.aspx
When it comes to monitoring application administrators often disagree with system administrators on what to monitor and which thresholds to configure. By nature system administrators focus on system related counters and objects to monitor. They do not care about application related monitoring as those information's are out of scope of their daily work. Vice versa the same is true for application administrators.
Therefore there is no and will never be a single monitoring solution to combine totally different interests in information. On the other hand the business is highly interested in implementing a single monitoring solution to reduce the overall licensing cost (priority 1), reduce the number of servers required to host monitoring solutions (priority 2) and to eliminate the need for technical training (priority 3).
System monitoring and application monitoring systems sometimes share an intersecting set of “things” they are able to monitor. The fact is that both monitoring approaches have totally different procedures on how to monitor.
The following diagram illustrates the system monitoring approach, where a probe connects to a target and queries data using a dedicated protocol supported by the target (e.g. SNMP, WMI, SSH, etc.).
The solution illustrated uses PRTG which is a network monitoring solution that supports all standard protocols for monitoring. It can be enhanced by individual scripts, programs and libraries. You can find a link to PRTG at the end of this post.
In comparison to system monitoring the application monitoring approach looks very different, as the following figure shows:
Application monitoring relies on the existence of agents installed locally on the servers hosting the applications. This approach provides the ability to monitor from an application perspective. The agent itself performs checks depended on the application running on the same server. For example the agent checks that DNS name resolution works using the configured DNS servers on the server. If DNS resolution does not work the agent responds with an error to central management even when the DNS server itself is reachable by the system monitoring probe.
In the current IT landscape where messaging and collaboration solutions provide business functionality at a large scale and are setup in high-availability configurations the monitoring of such implementations from an application perspective is crucial. In a world where “always on” is the business goal for a mobile work force downtime of messaging and collaboration systems is an issue.
The ENow Management Suite supports your monitoring efforts for:
Mailscape is the part of the ENow Management Suite which helps you to monitor the messaging infrastructure components like Exchange Server, Blackberry Enterprise Server and SMTP relay servers.
Mailscape 365 is part of the ENow Management Suite which monitors your Exchange Online and Hybrid Exchange deployment inclusive of required hybrid components like AD FS and DirSync.
Compass is the part of the ENow Management Suite which monitors domain controllers and Active Directory specific topics.
ForeSite is the part of the ENow Management Suite which monitors your SharePoint farms and the related SQL database servers.
Besides monitoring the vitals of the application components and the infrastructure requirements (network, AD, etc.) the solution provides an extensive reporting functionality. The default set of reports fits most reporting requirements, but you can set up your own reports as well. A significant feature is the ability to provide the reports to different groups of stakeholders.
Monitoring servers should not be a time consuming task for an application administrator. Therefore the interface of the ENow Management Suite is quite handsome, as it displays all statuses in a dashboard. As long as all statuses are green the application administrator can focus on other work. When using all parts of the ENow Management Suite you act within one single dashboard, but each part utilizes it’s own security groups for access the dashboard.
How does a SharePoint administrator work with ForeSite?
The follow screenshot shows the ForeSite dashboard:
If the dashboard uses a traffic light approach to signal good, warning and error states. This makes it really easy to focus on section of the application infrastructure where some is not in a healthy state. It cannot be any more intuitive.
By just clicking on the signaling rectangle you dig deeper to the next level of information:
It seems as if there is something wrong with a SharePoint timer job. But what is going on?
Ok, it is not the SharePoint timer service itself. It is just one of the timer jobs itself.
The Application Addressed Refresh Job is offline since 3.4 days. That is a valuable information and the SharePoint administrator knows where to start to solve this issue.
This is a basic example how an application monitoring solution can help to identify the error.
The reporting functionality of ForeSite helps to gather a lot of different data from a SharePoint farm. Those reports can be executed manually or be sent automatically by email on a recurring basis. The reports overview displays a list of different reports which are available by default:
With the proactive monitoring of critical SharePoint services, like Site Availability, Timer Jobs, Search and Index, and content databases ForeSite helps the application administrator to focus on daily work. The alerting functionality helps to reduce the response time in the case of an error and therefore helps to reduce the overall business impact to a minimum.
The classic system monitoring solution is the interface of the administrative personnel responsible for the IT infrastructure itself. The application monitoring solution is the main interface for application administrators and runs on top of the IT infrastructure. Even when some components (disk, memory, CPU, …) are measured by both components.
Besides monitoring of different important aspects of the application an application monitoring solution provides the ability for application specific reports. Those reports and even the dashboard itself can be made available to different groups of stakeholders in the company using Windows credentials.
An application monitoring and reporting solution is a valuable addition to classic system monitoring.
What are your thoughts on system and application monitoring? Leave a comment.
Get your free 21-day trial of the ENow Management Suite today: http://www.granikos.eu/en/Products/ENowManagementSuite
Need more professional consulting on Exchange Server, Office 365 or Exchange configurations? Do not hesitate to contact us by email: info@granikos.eu
Vor Office 365 gab es bereits eine Cloud Productivity Lösung von Microsoft. Die Business Productivity Online Services (BPOS) haben Dienste auf Basis der Produkte Exchange 2007 and MOSS 2007 bereitgestellt.
SharePoint Sites wurden in BPOS unter der Domäne microsoftonline.com erstellt und sind bis heute in Nutzung.
Ab dem 1. Januar 2017 werden SharePoint Sites, die noch der *.microsoftonline.com Namenskonvention entsprechen, zu *.sharepoint.com überführt.
Administratoren können dies bereits vor dem 1. Januar 2017 durchführen. Microsoft hat hierzu einen Support-Artikel veröffentlicht.
Neben der reinen Änderung der Url für die SharePoint Sites ergibt sich ein zusätzlicher Vorteil. SharePoint Sites unter der Url *.sharepoint.com können das neue SharePoint App Modell nutzen. Dies ist unter *.microsoftonline.com nicht möglich.
Viel Spaß mit Office 365.
Welche Möglichkeiten bieten Site Mailboxes und welche Vorteile und Nachteile birgt der Einsatz von Site Mailboxes?
Ein erfolgreiches Team benötigt die passenden Werkzeuge, um die Projektkommunikation und die Projektdokumente sinnvoll zu verwalten. Site Mailboxen, eine Funktion von SharePoint Server 2013 und Exchange Server 2013, bringen eine neue Option ins Spiel.
Unsere neue Präsentation bietet einen schnellen Überblick, sowohl für Entscheider wie auch für Administratoren.
Sie möchten mehr über die Möglichkeiten von Exchange Server 20013 erfahren? Mit unseren Workshops helfen wir Ihnen Vorort und geben Ihnen die richtigen Informationen für Ihr Unternehmen.
Kontaktieren Sie uns über info@granikos.eu
Das Blog Cumulative Update für Juni 2017 (CU0617) fasst interessante Themen rund um Cloud Sicherheit, Exchange Server, Office 365, Azure und Skype for Business (aka Lync) des Monats Juni 2017 zusammen.
Gerne unterstützen wir Sie bei der Planung und Durchführung Ihrer Exchange Server Implementierung oder Migration.
Sie denken über einen vollständigen Wechsel zu Office 365 oder eine Hybrid-Konfiguration mit Office 365 nach? Wir beraten Sie umfassend und neutral über die Möglichkeiten der Office 365 Plattform.
Sie möchten mehr über Exchange Server 2016 erfahren? Gerne erläutern wir Ihnen die technischen Änderungen und Chancen für Ihr Unternehmen in einem individuellen Workshop.
Weitere Informationen zu unseren Dienstleistungen finden Sie auf unserer Website (https://www.granikos.eu) oder Sie kontaktieren direkt unser Vertriebsteam: info@granikos.eu
Das Blog Cumulative Update für März 2019 (CU0319) fasst interessante Themen rund um Cloud Sicherheit, Exchange Server, Office 365, Azure und Microsoft Teams des Monats März 2019 zusammen.
Sie denken über einen vollständigen Wechsel zu Office 365 oder eine Hybrid-Konfiguration mit Office 365 nach? Wir beraten Sie umfassend und neutral über die Möglichkeiten der Office 365 Plattform und Microsoft 365.
Sie möchten mehr über Exchange Server 2019 erfahren? Gerne erläutern wir Ihnen die technischen Änderungen und Chancen für Ihr Unternehmen in einem individuellen Workshop.
Die Installation des Windows Features Active Directory Domains Services (AD DS) kann fehlschlagen.
Bei der Installation per PowerShell kommt es zu folgendem Fehler:
Install-WindowsFeature -Name AD-Domain-Services Install-WindowsFeature : The request to add or remove features on the specified server failed. The operation cannot be completed, because the server that you specified requires a restart. At line:1 char:1 + Install-WindowsFeature -Name AD-Domain-Services + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : DeviceError: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature], Exce ption + FullyQualifiedErrorId : DISMAPI_Error__Failed_Reboot_Required,Microsoft.Windows.ServerManager.Commands.AddWindow sFeatureCommand Success Restart Needed Exit Code Feature Result ------- -------------- --------- -------------- False No Failed {}
Das ganze sieht erstmal danach aus, dass es sich um ein VMWare Problem handelt. "+ CategoryInfo: DeviceError: (@{Vhd=; Credent...Name=localhost}:PSObject) [Install-WindowsFeature], Exception" und das noch ein Reboot aussteht "because the server that you specified requires a restart."
Dem ist leider nicht so. Auch nach mehrfachem Neustart des Servers, bleibt es bei der gleichen Fehlermeldung.
Ein Blick ins EventLog zeigt, es gibt eine Abhängigkeit zwischen dem Dienst "DFS Namespace" und "Remote Registry".
Der "Remote Registry" Dienst konnte nicht gestartet werden, da dieser deaktiviert war.
Dieser Dienst war in der VM Vorlage deaktiviert.
Nach Umstellung auf Automatisch und einem Reboot ließ sich das Windows-Feature AD DS fehlerfrei installieren und der Server zum Domain Controller hochstufen.