- Перерегистрация компонентов VSS (Volume Shadow Copy Service) в Windows Server
- Windows Server Essentials Connector
- Добавление пользователей до установки программы-соединителя
- Добавление пользователей
- Запустите программу установки Windows Server Essentials Connector.
- Windows SharePoint Services
- Contents
- Overview
- Downloads and Installation
- History
- Features
- Technical Details
- Use of ASP.NET web parts within SharePoint
- How web requests are handled in WSS 3
- SharePoint API overview
- Third-party packages for Windows SharePoint Services
- References
Перерегистрация компонентов VSS (Volume Shadow Copy Service) в Windows Server
Большинство решений для резервного копирования данных под Windows в том или ином виде используют возможности службы теневых копий (VSS — Volume Shadow Copy Service) для создания копий данных приложений или сервисов. В некоторых случаях, служба VSS или один из ее модулей записей начинают работать некорректно, в результате чего не удается выполнить нормальную процедуру резервное копирования данных. Я сталкивался с такой ошибкой на Exchange, MSSQL и Hyper-V серверах. Для быстрого восстановления службы VSS и ее компонентов я использую следующую инструкцию.
Чтобы определить сбойный модуль VSS, выведем список зарегистрированных в системе модулей записи VSS (Writers) с помощью команды vssadmin.
vssadmin list writers
В списке компонентов ищем те, которые находятся в состоянии Failed (для нормально работающих компонентов статус должен быть State: [1] Stable)
Writer name: ‘Microsoft Exchange Writer’
Writer Id: <76fe1ac4-6ded-4f4b-8f17-fd23f8ddcfb7>
Writer Instance Id: <31b56ab0-9588-412f-ae7b-cdc375347158>
State: [7] Failed
Last error: Retryable error
Как вы видите, в нашем случае модуль записи Microsoft Exchange Writer находится в сбойном состоянии (State: [8] Failed), поэтому резервное копирование Exchange выполнить не удастся. Как правило, чтобы исправить состояние такого компонента, достаточно перезагрузить сервер (что не всегда возможно по производственным причинам).
Чтобы починить модуль записи, нужно попробовать перезапустить связанную с ним службу (в таблице ниже содержится список соответствия типовых VSS Writer и связанных с ними служб Windows). Помимо остановки службы, иногда приходится руками завершать процесс зависшей службы.
VSS Writer | Имя службы | Полное имя службы |
ASR Writer | VSS | Volume Shadow Copy |
BITS Writer | BITS | Background Intelligent Transfer Service |
Certificate Authority | CertSvc | Active Directory Certificate Services |
COM+ REGDB Writer | VSS | Volume Shadow Copy |
DFS Replication service writer | DFSR | DFS Replication |
DHCP Jet Writer | DHCPServer | DHCP Server |
FRS Writer | NtFrs | File Replication |
FSRM writer | srmsvc | File Server Resource Manager |
IIS Config Writer | AppHostSvc | Application Host Helper Service |
IIS Metabase Writer | IISADMIN | IIS Admin Service |
Microsoft Exchange Replica Writer | MSExchangeRepl | Microsoft Exchange Replication Service |
Microsoft Exchange Writer | MSExchangeIS | Microsoft Exchange Information Store |
Microsoft Hyper-V VSS Writer | vmms | Hyper-V Virtual Machine Management |
MSMQ Writer (MSMQ) | MSMQ | Message Queuing |
MSSearch Service Writer | WSearch | Windows Search |
NPS VSS Writer | EventSystem | COM+ Event System |
NTDS | NTDS | Active Directory Domain Services |
OSearch VSS Writer | OSearch | Office SharePoint Server Search |
OSearch14 VSS Writer | OSearch14 | SharePoint Server Search 14 |
Registry Writer | VSS | Volume Shadow Copy |
Shadow Copy Optimization Writer | VSS | Volume Shadow Copy |
SMS Writer | SMS_SITE_VSS_WRITER | SMS_SITE_VSS_WRITER |
SPSearch VSS Writer | SPSearch | Windows SharePoint Services Search |
SPSearch4 VSS Writer | SPSearch4 | SharePoint Foundation Search V4 |
SqlServerWriter | SQLWriter | SQL Server VSS Writer |
System Writer | CryptSvc | Cryptographic Services |
TermServLicensing | TermServLicensing | Remote Desktop Licensing |
WDS VSS Writer | WDSServer | Windows Deployment Services Server |
WIDWriter | WIDWriter | Windows Internal Database VSS Writer |
WINS Jet Writer | WINS | Windows Internet Name Service (WINS) |
WMI Writer | Winmgmt | Windows Management Instrumentation |
Еще раз выполните команду
vssadmin list writers
Проверьте статус проблемного модуля записи. Если он не изменился на Stable и проблема не исправлена, можно попробовать перерегистрировать компоненты и библиотеки службы VSS.
Перейдите в каталог:
Остановите службы Volume Shadow Copy и Microsoft Software Shadow Copy Provider
Net Stop VSS
Net Stop SWPRV
Перерегистрируйте компоненты VSS:
regsvr32 /s ole32.dll
regsvr32 /s oleaut32.dll
regsvr32 /s vss_ps.dll
vssvc /register
regsvr32 /s /i swprv.dll
regsvr32 /s /i eventcls.dll
regsvr32 /s es.dll
regsvr32 /s stdprov.dll
regsvr32 /s vssui.dll
regsvr32 /s msxml.dll
regsvr32 /s msxml3.dll
regsvr32 /s msxml4.dll
vssvc /register
Теперь осталось запустить остановленные службы:
Net Start SWPRV
Net Start VSS
Проверьте, пропала ли ошибка у проблемного модуля записи VSS.
Данный метод перезапуска и перерегистрации компонентов VSS эффективен, как на Windows Server 2008 / 2012/ R2, так и на Windows Server 2016.
Windows Server Essentials Connector
Подключив ПК в своей сети к домену WSS NAS, вы сможете извлечь дополнительные преимущества от использования Windows Storage Server 2012 R2 Essentials,. Помимо упрощения обмена данными между пользователями в вашем офисе, устройство WSS NAS обеспечивает управление и автоматическое резервное копирование для ПК.
Программа Windows Server Essentials Connector совместима с ПК с операционной системой Windows 7 или выше.
Перед установкой программы Windows Server Essentials Connector убедитесь, что работа ассистента настройки Seagate WSS NAS завершена (см. раздел «Начало работы»).
Добавление пользователей до установки программы-соединителя
Мастер Windows Server Essentials Connector отобразит запрос пользователя в сети. Поэтому вы должны добавить пользователей в инструментальной панели Windows Storage Server 2012 R2 Essentials до запуска мастера Windows Server Essentials Connector на ПК.
Добавление пользователей
- Используя ПК в сети, подключитесь к своему устройству WSS NAS через удаленный рабочий стол.
- Запустите инструментальную панель.
- Выберите «Пользователи».
- На панели «Задачи пользователей» справа выберите «Добавить учетную запись пользователя».
- Введите учетные данные и нажмите «Далее». См. пример на рисунке ниже.
- Щелкните раскрывающееся меню, чтобы выбрать права доступа пользователя к совместно используемым папкам сервера.
- Нажмите «Далее».
- Подтвердите настройки пользователя по умолчанию и внесите изменения, если необходимо. Выберите «Создать учетную запись», чтобы добавить пользователя.
- Просмотрите страницу со сводкой. Проверьте URL-адрес для загрузки Windows Server Essentials Connector (http://[[server name]]/connector) и имя для входа в учетную запись пользователя.
- Выберите «Закрыть». Пользователь добавлен в устройство WSS NAS.
Повторите описанные выше шаги, чтобы создать дополнительных пользователей.
Запустите программу установки Windows Server Essentials Connector.
- Запустите Internet Explorer или браузер по умолчанию.
- Введите URL-адрес //[[WSS NAS network name]]/connect.«Имя сервера» — это сетевое имя устройства WSS NAS. Например, сетевое имя по умолчанию — seagate-wss-nas. Если после ввода URL-адреса перенаправление на страницу загрузки не произойдет, введите адрес //[[WSS NAS network name]].local/connect или //[[WSS NAS IP address]]/connect.
- Выберите «Загрузить программное обеспечение для Windows».
- Выберите «Запустить».
- Выберите «Да».
- Установите флажок для опции «Я прочитал и принимаю условия лицензионного соглашения», затем нажмите «Далее».
- Введите применимое имя пользователя и пароль, созданные в инструментальной панели WSS NAS.
- Нажмите «Далее». Завершение установки может занять несколько минут.
- Выберите «Перезагрузить».
- После перезагрузки появится запрос на указание количества пользователей, которые могут войти в систему на компьютере. Следует помнить, что настройка по умолчанию предназначена для переноса данных и настроек из локальных учетных записей пользователей ПК. Вы можете выбрать опцию пропуска переноса, установив соответствующий флажок в нижней части окна.
Теперь пользователи могут ввести свои учетные данные при входе в систему на ПК. Учетные данные должны быть созданы на инструментальной панели WSS NAS.
ПК, успешно добавленные в домен WSS NAS, отображаются в списке в меню «Инструментальная панель» > «Устройства». WSS NAS предусматривает выдачу уведомлений, относящихся к устройствам.
Windows SharePoint Services
Windows SharePoint Services (WSS) is a free add-on to Microsoft Windows Server 2003 and 2008 providing a fully functional web portal with the following features:
- Content Management system.
- Collaboration tools
- Shared calendars and contact lists
- Alerts (including e-mail alerts)
- Discussion boards
- Blogs and Wikis
- Document Management providing a central repository for shared documents
- Web-based collaboration, collaborative editing of shared documents, and document workspaces
- Content Publishing including publishing workflows
- Access control and revision control for documents in a library
- Browser-based management and administration.
- Help desk and bug tracking
- Room and Equipment Reservations
- Physical Asset Tracking
- Sales Pipeline
- Customizable web pages using dashboards, web parts, and navigation tools
- Network load balancing and web farm support
- Firewall and DMZ support
In addition to its portal functionality, installation of WSS on a server makes available the complete object model and APIs underpinning Microsoft SharePoint technology. This includes a collection of web parts that can be embedded into web pages to provide SharePoint functionality such as dashboards, document workspaces, lists, alerts, calendaring, contact lists, discussion boards, and wikis in a custom web site.
WSS is provided as a free download from Microsoft for Windows Server 2003 Service Pack 1 or later and is added to the Microsoft .NET Framework. WSS is only provided for Microsoft servers and cannot be deployed on any other OS. WSS 3 downloads includes the core package and a set of «Application Templates» to add functionality to the basic installation.
WSS technologies are at the core of several of Microsoft’s commercial portal technologies. Specifically, WSS 3 underlies Microsoft Office SharePoint Server 2007 (MOSS), and WSS 2 was the framework beneath SharePoint Portal Server 2003.
Contents
Overview
Windows SharePoint Services (WSS) includes several major components:
- An underlying framework including an object model, persistent storage of content and configuration in SQL server databases, and ASP.NET controls for presenting the content
- A management web site for managing a «web farm» consisting of one or more servers hosting one or more web sites
- Built in template sites and pages that can be used to quickly create your own sites and add pages and libraries to existing sites
- Site editing web controls that allow you to edit the structure of your web site, modify the layout and contents of individual pages, create new workspaces and lists, and edit the schema of existing objects
- An indexer that crawls content databases indexing their contents for fast searching
- A collection of additional template sites and pages, including additional logic in code, known as «Application Templates»
- A configuration wizard that helps you get an initial site set up within minutes
SharePoint serves content via IIS Web Sites. They can use either Microsoft SQL Server or the Windows Internal Database to store their data. The web sites can be configured to return separate content for Intranet, Extranet and Internet locations. In WSS website deployments have no licensing implications since the WSS software is free, but licenses are required to run Microsoft’s commercial portal products.
Multiple WSS servers can be configured as part of a «server farm», which allows them to share configuration and content databases. Server farms can consist of a single server or span hundreds or thousands of servers. Each server in the farm’s entire content — for load balancing scenarios — or just selected portions of the content. The data in the farm can be spread into up to 9,900 «content databases.» Replication of farm data is handled using SQL Server’s replication and clustering abilities.
SharePoint uses a similar LDAP permissions model to Microsoft Windows, via groups of users. This can be provided via Active Directory. Alternatively, other authentication providers can be added through or even HTML Forms authentication.
Downloads and Installation
WSS 3 can be downloaded for free from Microsoft and installed on a Windows 2003 Server Service Pack 1 or later [1] In May 2008, Bamboo Solutions published a way to install WSS 3 on Vista. [2] Windows SharePoint Services 3.0 Application Templates is a separate download on the Microsoft web site that installs additional templates. [3]
WSS 2 can still be downloaded for free from Microsoft and installed on a Windows Server 2003 or later. [4]
Special installation note for Windows Small Business Server (SBS) 2003 or SBS 2003 R2: There is a bug such that upgrading from WSS 2 to WSS 3 on these operating systems may cause some SharePoint features to fail. Microsoft only supports installing via a «side by side» installation on SBS 2003; this means creating a new SharePoint website and migrating the content across. Neither SBS 2008 nor any version of Windows Server is affected by this bug.
History
The first version, called SharePoint Team Services (usually abbreviated to STS), was released at the same time as Office XP and was available as part of Microsoft FrontPage. STS could run on Windows 2000 Server or Windows XP.
Windows SharePoint Services 2.0 was marketed as an upgrade to SharePoint Team Services, but was in fact a completely redesigned application [5] . SharePoint Team Services stored documents in ordinary file storage, keeping document metadata in a database. Windows SharePoint Services 2.0 on the other hand, stores both the document and the metadata in a database, and supports basic document versioning for items in Document Libraries. Service Pack 2 for WSS added support for SQL Server 2005 and the use of the .NET Framework 2.0.
Windows SharePoint Services 3.0 was released on November 16, 2006 as part of the Microsoft Office 2007 suite and Windows Server 2003. WSS 3.0 is built using .NET Framework 2.0 and .NET Framework 3.0 Windows Workflow Foundation to add workflow capabilities to the basic suite. By the beginning of 2007 WSS 3.0 was made available to the public. Windows 2000 Server is not supported by WSS 3.0.
WSS version 3 marked a significant maturation of the product. Version 3 supported more features commonly used in Web 2.0 solutions like Blogs, Wikis and RSS feeds.
Microsoft has changed the name beginning with version 4.0 to SharePoint Foundation 2010. [6] [7]
Features
A default WSS 3 farm contains the following features:
- Sites and Workspaces
- Document Libraries
- Document Workspaces
- Collaborative editing with Microsoft Office integration
- Calendars
- Contact Lists
- Task Lists
- Alerts
- Discussion Boards
- Blogs
- Wikis, including RSS feeds and an WYSIWYG editor
- Announcements
- Image Libraries
- Form Libraries
- Project Tracking (Gantt Charts)
- Issue Tracking
- Link Lists
- Workflows
- Revision Control
- Access Control
- Custom Pages
- Web Part Pages
- Dashboard
- Search
- Site Navigation
- Backup and Restore
- User Management
- Central Administration web site
After installing the packages from the separately downloaded Windows SharePoint Services 3.0 Application Templates the following additional features are also available:
- Absence Request and Vacation Schedule Management
- Help Desk
- Budgeting and Tracking Multiple Projects
- Inventory Tracking
- Bug Database
- IT Team Workspace
- Call Center
- Job Requisition and Interview Management
- Change Request Management
- Knowledge Base
- Compliance Process Support Site
- Lending Library
- Contacts Management
- Physical Asset Tracking and Management
- Document Library and Review
- Project Tracking Workspace
- Event Planning
- Room and Equipment Reservations
- Expense Reimbursement and Approval Site
- Sales Lead Pipeline
- Board of Directors
- Employee Training Scheduling and Materials
- Business Performance Rating
- Equity Research
- Case Management for Government Agencies
- Integrated Marketing Campaign Tracking
- Classroom Management
- Manufacturing Process Management
- Clinical Trial Initiation and Management
- New Store Opening
- Competitive Analysis Site
- Product and Marketing Requirements Planning
- Discussion Database
- Request for Proposal
- Disputed Invoice Management
- Sports League
- Employee Activities Site
- Team Work Site
- Employee Self-Service Benefits
- Timecard Management
Technical Details
Use of ASP.NET web parts within SharePoint
A SharePoint page is built by combining the web parts into a web page, to be accessed using a browser. Any web editor supporting ASP.NET can be used for this purpose, even though Microsoft Office SharePoint Designer is the preferred editor. The extent of customization of the page depends on its design.
WSS pages are ASP.NET applications, and SharePoint web parts use the ASP.NET web parts infrastructure, and using the ASP.NET APIs, web parts can be written to extend the functionality of WSS. In terms of programmability, WSS exposes an API and object model to programmatically create and manage portals, workspaces and users. In contrast, the MOSS API is more geared towards automation of tasks and integration with other applications. [8] Both WSS and MOSS can use the web parts API to enhance the end user functionality. In addition, WSS document libraries can be exposed over ADO.NET connections to programmatically access the files and revisions in them.
How web requests are handled in WSS 3
At the web server level, WSS configures IIS to forward all requests, regardless of file and content types, to the ASP.NET session hosting the WSS web application, which either makes a certain revision of a certain file available from the database or takes other actions. Unlike regular ASP.NET applications, the .aspx which contains the WSS (and MOSS) application code, resides in SQL Server databases instead of the filesystem. As such, the regular ASP.NET runtime cannot process the file. Instead, WSS plugs a custom Virtual Path Provider component [9] into the ASP.NET pipeline, which fetches the .aspx files from the database for processing. With this feature, introduced with WSS 3.0, both the WSS application as well as the data it generates and manages, could be stored in a database.
SharePoint API overview
Windows SharePoint Services includes an object model that allows programs to manipulate the structure of SharePoint Sites. The main hierarchy of API object classes is:
- SPWebApplication is an entire Web Application
- SPContentDatabase is a Content Database used within a web application and stored in a separate SQL database
- SPSite is a Site Collection that includes multiple sites, similar to an IIS virtual directory
- SPWeb is a Web Site or a web page, typically an .aspx file
- SPList is a List on a web site
- SPListItem is an item in a list
- SPField is a field of an item in a list
All of these classes are found in the Microsoft.SharePoint namespace in the assembly Microsoft.SharePoint.dll, which is located in the Global Assembly Cache.
SharePoint is built on top of ASP.NET, so it uses many familiar ASP.NET concepts such as .aspx files, master pages, and web parts. Within a .aspx page, the SharePoint objects can be accessed using the SPContext.Current object, for example:
== 的SPWeb currentWeb = SPContext.Current.Web;↵的foreach(子網站的SPWeb在currentWeb.Webs)↵的foreach(在subWeb.Lists SPList列表)↵↵. == Understanding SharePoint lists (SPList objects) is central to understanding how SharePoint manages information. Essentially everything that is managed by SharePoint will be in a list at some level. For example, the Quick Launch of a Windows SharePoint Services site presents a hierarchy of sites, subsites, and lists (including lists of lists), instead of pages as such. If you add a page to such a site, the new page appears in the Quick Launch as a new item in a list of shared documents, not as a child node under the home page or some other page [10]
Third-party packages for Windows SharePoint Services
SharePoint提供一種方式,公司發布的軟件包和模板可以加載到Windows SharePoint Services和用於添加自定義功能。許多這樣的套餐可供選擇,例如社區工具包的SharePoint ↵ ☃☃ ,包括增強了SharePoint的維基和博客的特點。
References
- ↑»WSS 3 Download from Microsoft» . http://www.microsoft.com/downloads/details.aspx?FamilyId=D51730B5-48FC-4CA2-B454-8DC2CAF93951&displaylang=en . Retrieved 2009-10-01 . .
- ↑»WSS on Vista» . http://community.bamboosolutions.com/blogs/bambooteamblog/archive/2008/05/21/how-to-install-windows-sharepoint-services-3-0-sp1-on-vista-x64-x86.aspx . Retrieved 2009-05-26 .
- ↑»WSS 3 Application Templates Download from Microsoft» . http://www.microsoft.com/downloads/details.aspx?FamilyID=5807b5ef-57a1-47cb-8666-78c1363f127d&DisplayLang=en . Retrieved 2009-10-01 . .
- ↑»WSS 2 Download from Microsoft» . http://www.microsoft.com/downloads/details.aspx?familyid=B922B28D-806A-427B-A4C5-AB0F1AA0F7F9&displaylang=en . Retrieved 2009-10-01 .
- ↑»WSS 3 completely redesigned» . http://msdn.microsoft.com/en-us/magazine/cc163578.aspx . Retrieved 2009-11-30 .
- ↑SharePoint Foundation 2010 : What’s in a Name (and New!)
- ↑SharePoint 2010 Lineup
- ↑»Use Windows SharePoint Services as a Platform for Building Collaborative Apps, Part 2″ . http://msdn.microsoft.com/msdnmag/issues/04/08/WebParts/ . Retrieved 2007-10-01 .
- ↑»Discover Significant Developer Improvements In SharePoint Services» . http://msdn.microsoft.com/msdnmag/issues/06/07/WSS30Preview/default.aspx . Retrieved 2007-10-01 .
- ↑»Understanding the Administrative Object Model of Windows SharePoint Services 3.0″ . http://msdn.microsoft.com/en-us/library/cc300138.aspx . Retrieved 2009-10-01 .
SharePoint Events: Synchronous Asynchronous
31b56ab0-9588-412f-ae7b-cdc375347158>