Что есть в Атырау:
Atyrau Fitness (gym)
Orange (gym)
Renco (gym, pool)
Renessance (gym, pool)
Marriott (?)
ФОК (gym, pool)
Мунайши (pool)
Ardager (gym, pool)
Europa (gym, pool)
7KZ (gym, pool)
Infinity Armada (gym)
Что есть в Атырау:
Atyrau Fitness (gym)
Orange (gym)
Renco (gym, pool)
Renessance (gym, pool)
Marriott (?)
ФОК (gym, pool)
Мунайши (pool)
Ardager (gym, pool)
Europa (gym, pool)
7KZ (gym, pool)
Infinity Armada (gym)
Based on “Streamlined Topologies for SharePoint Server 2013” diagram from Microsoft (“Topology design guidance for maximizing system resources”),
Simplified for 4-servers high-available 3-tier farms:
Services | |
Front-End Servers Service applications, services, and components that serve user requests directly are placed on front-end servers. These servers are optimized for fast performance. Low and Very low latency. |
|
Batch-Processing Servers Service applications, services, and components that process background tasks are placed on a middle-tier of servers referred to as batch processing servers. These servers are optimized to maximize system resources. These servers can tolerate greater loads because these tasks do not affect performance observed by user |
|
The safest method to update a SharePoint farm is to take the entire farm offline, update all servers, and then bring the farm back online. This method requires a maintenance window that might not be practical for all organizations.
High availability updating involves more planning, testing, and coordination. The general outline for the process includes the following steps.
(the article is under development)…
In short, keeping SharePoint online means designing a fault-tolerant architecture, coding customisations & apps in a well designed and tested manner, and implementing good SharePoint governance. First though, the architecture…
(SharePoint PLA – Product Line Architecture)
References:
Distributed Cache should be patched separately from SharePoint (DC updatess will not come with SharePoint CUs…).
Do not use SharePoint Distributed Cache with your custom code.
Connect-AFCacheClusterConfiguration Get-CacheHost Get-AFCacheClusterHealth Get-SPServiceInstance | ? {($_.service.tostring()) -eq "SPDistributedCacheService Name=AppFabricCachingService"} |fl Get-AFCacheHostConfiguration -ComputerName XXX -CachePort "22233" $svc=$f.Services | ? {$_.Name -eq "AppFabricCachingService"} $svc.ProcessIdentity Get-AFCacheAllowedClientAccount #Stop-SPDistributedCacheServiceInstance –Graceful #Update-SPDistributedCacheSize -CacheSizeInMB 1024 #Add-SPDistributedCacheServiceInstance #Grant-AFCacheAllowedClientAccount -Account "domain\upsa_runas_account" get-command -module DistributedCacheAdministration
=======================
(see also Part1: SharePoint Workflow Manager Review)
Ensure hardware/software requirements. Ensure/configure your server (time, time zone, IP, hostname, domain, language, region, ESC, updates, event log).
Accounts you need (for example):
DNS: wfm.contoso.kz points to Workflow Manager Server (or load-balancer)
On an Internet connected machine:
SharePoint Apps
wildcard SSL cert (*.contosoapps.com) is needed
$trustCert = Get-PfxCertificate "c:\wfm.cer"
New-SPTrustedRootAuthority -Name "Workflow Manager Farm" -Certificate $trustCert
Configure App Management Service Instance and Service Application
purchase a domain name from a domain name provider for your apps, for example, ContosoApps.com
create a forward lookup zone for the app domain name (ContosoApps.com)
create a wildcard Alias (CNAME) record for the new domain name (*.ContosoApps.com -> Portal.contoso.com)
create a wildcard SSL certificate for app domain (*.ContosoApps.com)
Start App Management and Microsoft SharePoint Foundation Subscription Settings services.