in Blog / Citrix / Containers / FSLogix / Outlook / Search / UPM / Windows
Windows Search challenges in Server 2019 and Windows 10 Multi Session
- Intro
- First Logon for the user
- User Logoff
- Restarting the search service
- Summary
Intro
As always in our industry, small changes in one platform can result in significant impact across what is “standard practice” in many other areas. This week’s lucky contender is Windows Search.
Update 25/10/2021: There is a new update from Microsoft available stating the fix as follows:
Addresses an issue that causes searchindexer.exe to keep handles to the per user search database in the path below after you sign out:
C:\Users\username\AppData\Roaming\Microsoft\Search\Data\Applications\{SID}
As a result, searchindexer.exe stops working and duplicate profile names are created.
Windows Search in both Windows Server 2019 and Windows 10 Multi-Session has changed how it operates, introducing the concept of per-user search natively into the Search Service. This is fundamentally different from previous versions (namely Windows Server 2016 etc) and changes how we need to think about search roaming with supporting technologies such as FSLogix Containers and Citrix UPM.
The biggest change is that the Windows Search index is now stored per user in the user profile, specifically
C:\Users\%Username%\AppData\Roaming\Microsoft\Search\Data\Applications\{UserSID}\{UserSID}.edb
On each login, the Windows Search process creates a new instance of the search database for the user based on the existing EDB. If no EDB file exists, a new one is created by the Operating System.
There are two components associated with the Search functionality split into individual processes:
- SearchIndexer.exe: This process runs under the
NT AUTHORITY\SYSTEMaccount and accesses the index database for each user (profile based) - SearchProtocolHost.exe: an instance of this process runs per user and is a child process of SearchIndexer.exe. This process handles amongst other things, the indexing of the Outlook OST file, not the searching of the index file, but the actual index creation of it making content available to search. Searching should be operational with or without this process running. When new items need to be indexed, the process will run, once finished, it will stop
The impacts here, should you have dealt with FSLogix or Citrix UPM Search roaming should start to become obvious when you think about how these solutions tackle the Search side of things (they rip out a component of the index and store them within a container). The long and short of it is as follows:
- For FSLogix environments, you must NOT enable search roaming within the FSLogix GPO. Specifically, you want SearchRoam set to 0 in the registry. This needs to be reversed in your master image should you have enabled it previously, in fact, given the what we know of Search challenges and the attempted hooks into it, I would be tempted to suggest that should you have enabled search roaming in either Windows Server 2019 or Windows 10 multi-session previously, then revert the setting, reinstall Microsoft Office and make sure that the event logs are clear from a Windows Search perspective
- For Citrix UPM environments, the following article has been released which is quite confusing. TLDR, the key it’s discussing should not be set to anything other than 0, and ideally shouldn’t exist as a whole in Windows Server 2019. Citrix UPM configurations will need to cater for the new location of the Search Index, however, the OST container can stay in place and do its thing. I haven’t had time to test, but I would assume that the new search location in the user profile is an ideal candidate for the UPM container feature
Unfortunately, Windows Search is an ongoing challenge and there is a fair number of customers who are experiencing issues with the native multi-user search capability in both Windows 10 Multi-Session and Windows Server 2019. Some are experiencing repeated crashing of the service others are finding that search index files are not released on logoff resulting in locked files and corrupt indexes.
In the below walkthrough, I will try and outline what happens with Windows Search in Server 2019, and where things fall apart, along with a temporary resolution which may help until the problems are properly addressed by Microsoft.
First of all, an outline of the environment I am using to demonstrate the situation
- Windows Server 2019 Datacenter, latest rollup at the time of writing
- FSLogix release 2.9.7237.48865
- Profile and Office Container configured
- Microsoft Office 365 ProPlus, x64, Semi-Annual channel
- No PVS or MCS provisioning
Secondly, below is an outline of some of the event log entries we will be referring to:
| ID | Detail | |
|---|---|---|
| 5 | Windows Search Service has created default configuration for new user KINDO\JKindon5 |
|
| 2 | SearchIndexer (4400,P,98) {S-1-5-21-2397015974-2202110191-2245630456-1134}: The database engine (10.00.17763.0000) is starting a new instance (3) |
|
| 102 | SearchIndexer (4400,P,98) {S-1-5-21-2397015974-2202110191-2245630456-1134}: The database engine (10.00.17763.0000) is starting a new instance (3) |
|
| 105 | SearchIndexer (4400,D,0) S-1-5-21-2397015974-2202110191-2245630456-1134: The database engine started a new instance (3). (Time=0 seconds) |
|
| 637 | SearchIndexer (4400,D,35) S-1-5-21-2397015974-2202110191-2245630456-1134: New flush map file C:\Users\JKindon5\AppData\Roaming\Microsoft\Search\Data\Applications\{S-1-5-21-2397015974-2202110191-2245630456-1134}\{S-1-5-21-2397015974-2202110191-2245630456-1134}.jfm will be created to enable persisted lost flush detection |
|
| 325 | SearchIndexer (4400,D,35) {S-1-5-21-2397015974-2202110191-2245630456-1134}: The database engine created a new database (6, C:\Users\JKindon5\AppData\Roaming\Microsoft\Search\Data\Applications\{S-1-5-21-2397015974-2202110191-2245630456-1134}\{S-1-5-21-2397015974-2202110191-2245630456-1134}.edb). (Time=0 seconds) |
|
| 103 | SearchIndexer (6672,T,97) {S-1-5-21-2397015974-2202110191-2245630456-1134}: The database engine stopped the instance (3) |
|
| 2 | Unable to remove Windows Search Service indexed data for user ‘KINDO\JKindon5’ in response to user profile deletion. Error code 0x80004002 | |
| 482 | SearchIndexer (3768,D,0) S-1-5-21-2397015974-2202110191-2245630456-1134: An attempt to write to the file C:\Users\JKindon5\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-2397015974-2202110191-2245630456-1134\S-1-5-21-2397015974-2202110191-2245630456-1134.jfm at offset 0 (0x0000000000000000) for 8192 (0x00002000) bytes failed after 0.000 seconds with system error 21 (0x00000015): “The device is not ready.”. The write operation will fail with error -1022 (0xfffffc02). If this error persists then the file may be damaged and may need to be restored from a previous backup |
|
| 492 | SearchIndexer (9200,D,0) S-1-5-21-2397015974-2202110191-2245630456-1134: The logfile sequence in C:\Users\JKindon5\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-2397015974-2202110191-2245630456-1134\ has been halted due to a fatal error. No further updates are possible for the databases that use this logfile sequence. Please correct the problem and restart or restore from backup |
|
| 439 | SearchIndexer (3768,T,97) S-1-5-21-2397015974-2202110191-2245630456-1134: Unable to write a shadowed header for file |
C:\Users\JKindon5\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-2397015974-2202110191-2245630456-1134\S-1-5-21-2397015974-2202110191-2245630456-1134.edb. Error -1022 |
| 104 | SearchIndexer (3768,T,97) S-1-5-21-2397015974-2202110191-2245630456-1134: The database engine stopped the instance (2) with error (-1022) |
|
| 103 | SearchIndexer (3768,T,97) Windows: The database engine stopped the instance (0) | |
| 300 | SearchIndexer (10076,R,98) S-1-5-21-2397015974-2202110191-2245630456-1134: The database engine is initiating recovery steps. |
|
| 301 | SearchIndexer (10076,R,98) S-1-5-21-2397015974-2202110191-2245630456-1134: The database engine has finished replaying logfile C:\Users\JKindon5\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-2397015974-2202110191-2245630456-1134\edb.jtx |
|
| 302 | SearchIndexer (10076,U,98) S-1-5-21-2397015974-2202110191-2245630456-1134: The database engine has successfully completed recovery steps |
|
| 326 | SearchIndexer (9808,D,50) S-1-5-21-2397015974-2202110191-2245630456-1104: The database engine attached a database (2, C:\Users\JKindon\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-2397015974-2202110191-2245630456-1104\S-1-5-21-2397015974-2202110191-2245630456-1104.edb). (Time=0 seconds) |
My findings here are an aggregation of existing posts, as well as feedback from colleagues in the World of EUC slack channel. Testing has been validated in my own environments.
First Logon for the user
On the first logon for a new user, the following event logs entries will occur, basically detecting a new user without an index, creating a new database, configuring and leveraging the new instance as below:
Event ID 5: Windows Search Service has created the default configuration for new user Kindo\JKindon5
Event ID 102: SearchIndexer (4400,P,98) {S-1-5-21-2397015974-2202110191-2245630456-1134}: The database engine (10.00.17763.0000) is starting a new instance (3)
Event ID 105: SearchIndexer (4400,D,0) S-1-5-21-2397015974-2202110191-2245630456-1134: The database engine started a new instance (3). (Time=0 seconds)
Event ID 637: SearchIndexer (4400,D,35) S-1-5-21-2397015974-2202110191-2245630456-1134: New flush map file C:\Users\JKindon5\AppData\Roaming\Microsoft\Search\Data\Applications\{S-1-5-21-2397015974-2202110191-2245630456-1134}\{S-1-5-21-2397015974-2202110191-2245630456-1134}.jfm will be created to enable persisted lost flush detection
Event ID 325: SearchIndexer (4400,D,35) {S-1-5-21-2397015974-2202110191-2245630456-1134}: The database engine created a new database (6, C:\Users\JKindon5\AppData\Roaming\Microsoft\Search\Data\Applications\{S-1-5-21-2397015974-2202110191-2245630456-1134}\{S-1-5-21-2397015974-2202110191-2245630456-1134}.edb`). (Time=0 seconds)
In summary, in a healthy operational state, for a new user, the following event log patterns will occur on logon:
- 5 = Search Creates a default configuration
- 102 = Search Indexer creates a new instance for the user
- 105 = Search Indexer starts the new instance for the user
- 637 = New flush map file created for the user
- 325 = Search Indexer creates the new database
User Logoff
When the user logs off for the first time, the following event entry is logged:
Event ID 103: Event 103: SearchIndexer (6672,T,97) {S-1-5-21-2397015974-2202110191-2245630456-1134}: The database engine stopped the instance (3)
And this is where things go pear-shaped, you will most probably find the 103 entry is quickly followed by this one:
Event ID 2: Unable to remove Windows Search Service indexed data for user KINDO\JKindon5 in response to user profile deletion. Error code 0x80004002
In this state, when the user next connects, they are going to be hit with a problem. What we are looking for, is a happy combination of the following events when the user logs on for the second time:
- 102 = Search Indexer creates a new instance for the user
- 105 = Search Indexer starts the new instance for the user
- 326 = Search Indexer attaches an existing database
What we end up with though due to the above event ID 2 on Logoff, is the following:
Event ID 482: SearchIndexer (3768,D,0) S-1-5-21-2397015974-2202110191-2245630456-1134: An attempt to write to the file C:\Users\JKindon5\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-2397015974-2202110191-2245630456-1134\S-1-5-21-2397015974-2202110191-2245630456-1134.jfm at offset 0 (0x0000000000000000) for 8192 (0x00002000) bytes failed after 0.000 seconds with system error 21 (0x00000015): The device is not ready. The write operation will fail with error -1022 (0xfffffc02). If this error persists then the file may be damaged and may need to be restored from a previous backup.
The root cause of this is due to the following handles still being kept open by the SearchIndexer.exe process
These files are held open; however, the physical files have gone (detached) and thus we loop.
If the user was to log back on at this point, we will experience some problematic symptoms and events:
Outlook indexing will present as below:
And no files in the %AppData%\Microsoft\Search\Data\Applications\{UserSID}` directories will be touched
Restarting the search service
If we restart the Windows Search Service, a few things happen:
All existing handles are closed for SearchIndexer operations, both for any logged off users in a fail state, and for any other user on the Server, and the following event logs are written
| ID | Detail |
|---|---|
| 439 | SearchIndexer (3768,T,97) S-1-5-21-2397015974-2202110191-2245630456-1134: Unable to write a shadowed header for file C:\Users\JKindon5\AppData\Roaming\Microsoft\Search\Data\Applications\S-1-5-21-2397015974-2202110191-2245630456-1134\S-1-5-21-2397015974-2202110191-2245630456-1134.edb. Error -1022. |
| 104 | SearchIndexer (3768,T,97) S-1-5-21-2397015974-2202110191-2245630456-1134: The database engine stopped the instance (2) with error (-1022) |
| 103 | SearchIndexer (3768,T,97) Windows: The database engine stopped the instance (0) |
| 102,105,326 | (happy combination representing success) |
| 300 | SearchIndexer (10076,R,98) S-1-5-21-2397015974-2202110191-2245630456-1134: The database engine is initiating recovery steps |
| 301 | SearchIndexer (10076,R,98) S-1-5-21-2397015974-2202110191-2245630456-1134: The database engine has finished replaying logfile |
| 302 | SearchIndexer (10076,U,98) S-1-5-21-2397015974-2202110191-2245630456-1134: The database engine has successfully completed recovery steps |
| 105,326 | (Search index is OK again) |
Outlook indexing is now OK
Along with successful alterations to the %AppData%\Microsoft\Search\Data\Applications\{UserSID}` directories.
Fixed it would seem. So, logically here, we know that the resolution is to restart the Windows Search Service based on the failure Event, which is represented by Event ID 2. Specifically:
- Event Log: Application
- Event Level: Error
- Event Source: Search-ProfileNotify
- Event ID: 2
- Event Data: Unable to remove Windows Search Service indexed data for user
KINDO\JKindon5in response to user profile deletion. Error code 0x80004002
By implementing a scheduled task with the above Event ID as the trigger, and a simple configuration of PowerShell to restart the search service as the action:
We can successfully clear the errors on log-off, release the files, and ensure that when the user logs back in, their index is good to go. The process will now look like the below when a user logs off:
| ID | Detail |
|---|---|
| 103 | for the user logging off |
| 2 | This triggers the restart of the service, which also triggers an Event ID: 103 for all other users on the Server |
| 102, 105, 326 | for all remaining user accounts on the server |
Based on testing so far, this process does not hurt user experience, inclusive of existing Outlook sessions with existing search indexes, however, your mileage will vary, and this is at the end of the day, simply a workaround for a problem that needs to be fixed.
Summary
There are multiple streams of issues associated with native multi-user search currently, a running an interesting stream is located here on the Microsoft forums which pointed to the end resolution of a scheduled restart of the Search Service on the specific Event ID trigger, however, there have been multiple discussions around the World of EUC slack channel with people willing to test and share results – namely Kasper Johansen, Mike Streetz, Dennis Mohrmann
Windows Server 2019 users find that when searching in RDS, the search indexing on the terminal server do not work while searching in remote desktop and in Outlook.
Symptom
Windows Server 2019 users reported that searching in Remote Desktop on the Terminal Server and searching in Outlook doesn’t showing any search results. The status “Indexing is not running” is displayed in the indexing options.
After checking the search indexing service “services.msc”, it is shown that Windows Search is running on the RDS Server 2019. When trying to Rebuild the index under Advanced “Rebuild”, the indexing remains unsuccessful even after this action.
Cause
Starting with Windows Server 2019, Microsoft has made changes to the Windows Search service. The per-user search index is now enabled by default. This search indexing also applies to RDS and Windows Server 2022.
That’s why, as an administrator, you won’t see any locations under Indexing Options > Change > Show all locations.
Administrators can disable the setting and restore the older indexing method for Windows Server and RDS by using the EnablePerUserCatalog registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Search
DWORD EnablePerUserCatalog 0Solution: Search Indexing for RDS server
The traditional indexing option “per user search indexing” is restored with the following action.
To do this, open a command prompt on the windows server as an administrator and execute the following command to add the registry DRWOD key EnablePerUserCatalog with the value 0.
REG ADD "HKLM\SOFTWARE\Microsoft\Windows Search" /v "EnablePerUserCatalog" /t REG_DWORD /d "0" /fNow restart the “Windows Search” service or Reboot the Windows Server.
Now all locations are displayed (such as Outlook and/or OneNote). In addition, the number of indexed items should increase significantly.
Note: In Indexing Options > Advanced, the locations of the index can be specified and Rebuild if necessary.
Windows Search Indexing in Server 2019, 2022 using Multi-Session
Now, the default Windows Search service is able to roam all Windows Search index data on a per-user basis. The most significant change of per-user search indexing is that the Windows Search index is now stored per user in the user profile, under the following path:
C:\Users\%Username%\AppData\Roaming\Microsoft\Search\Data\Applications{UserSID}{UserSID}.edbOn each login, the Windows Search process creates a new instance of the search database for the user based on the existing EDB. If no EDB file exists, a new one is created by the Operating System.
Enable Windows Search Service on RDS Server
Log in to the Windows Server 2019 or 2022 and launch the Server Manager. Click Manage and select Add Roles and Features. Select Role based or feature-based installation option and click Next, walk through until the Features page, select the Windows Search Service checkbox and click Next. On the Confirmation page, click Install.
Now the windows search service just needs to be started, this is done from services.msc, open windows search properties, select startup type Automatic (Delayed Start), then click the Start button.
Install Windows Search Service in PowerShell
Using PowerShell is probably the quickest way to install the Windows Search service on a server. Launch the PowerShell as administrator. Run the following PowerShell command to install the Windows Search service on Windows Server.
Install-WindowsFeature Search-ServiceOpen Windows Indexing Options
To access the indexing options, enter “indexing” in the search field.
Alternatively, you can press the key combination Windows-Logo+R.
A new “Run” window will then open. Type the command control srchadmin.dll and select OK.
Windows Search Indexing
Indexing is the process of looking at files, email messages, and other content on your PC and RDS Server and cataloging their information, such as the words and metadata in them. When you search your Computer after indexing, it looks at an index of terms to find results faster.
When you first run indexing, it can take up to a couple hours to complete. After that, indexing will run in the background on your PC or RDS Server as you use it, only re-indexing updated data.
Note. if you are considering using single user search roaming or multi-user search roaming, follow this Microsoft article.
Если в вашей организации несколько системных администраторов, у вас периодически может возникать вопрос “Кто перезагрузил сервер?”. В этой статье я покажу как найти определения пользователя, который перезагрузил или выключил компьютер/сервер Windows.
Информация об учетной записи, которая отправила команду перезагрузки Windows сохраняется в журнал событий.
- Откройте консоль Event Viewer (
eventvwr.msc
) и перейдите в раздел Windows Logs -> System; - Включите фильтр журнала событий, выбрав в контекстном меню пункт Filter Current Log;
- В поле фильтра укажите EventID 1074 и нажмите OK;
- В журнале событий останутся только события выключения (перезагрузки), откройте любое из них;
- В событии от источника User32 будет указан пользователь, который инициировал перезагрузку Windows. В этом примере это пользователь a.novak.
The process C:\Windows\Explorer.EXE (MSK-DC03) has initiated the restart of computer MSK-DC03 on behalf of user WINITPRO\a.novak for the following reason: Other (Unplanned) Reason Code: 0x5000000 Shutdown Type: restart Comment:
Рассмотрим еще несколько примеров событий перезагрузки/выключения Windows. В качестве пользователя, запустившего перезагрузку операционную систему может быть указан NT AUTHORITY\SYSTEM.
Это означает, что перезагрузку инициировала одна из служб или программ Windows, запущенная от имени SYSTEM.. Например, это может быть процесс службы
wuauserv
, который закончил установку обновлений Windows и выполнил перезагрузку согласно настроенной политике Windows Update или с помощью задания модуля PSWindowsUpdate.
The process C:\Windows\uus\AMD64\MoUsoCoreWorker.exe (WKS-PC11S22) has initiated the restart of computer WKS-PC11S22 on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Service pack (Planned) Reason Code: 0x80020010 Shutdown Type: restart Comment:
Если ваша Windows запущена внутри виртуальной машины VMware, то если выполнить Restart Guest из консоли управления VMware, событие (выключения) будет выглядеть так:
The process C:\Program Files\VMware\VMware Tools\vmtoolsd.exe (MSK-DC03) has initiated the shutdown of computer MSK-DC03 on behalf of user NT AUTHORITY\SYSTEM for the following reason: Legacy API shutdown Reason Code: 0x80070000 Shutdown Type: shutdown
В этом случае выключение Windows также инициировано NT AUTHORITY\SYSTEM, т.к. службы интеграции VMware Tools запущены от имени системы.
Вы можете получить информацию о событиях перезагрузки с помощью PowerShell. Следующая команда выберет все события с EventID 1074:
Get-WinEvent -FilterHashtable @{logname=’System’;id=1074}|ft TimeCreated,Id,Message
Команда вернула описания всех событий перезагрузки и выключения Windows.
Можно использовать следующий скрипт PowerShell, который возвращает более короткий список с последними десятью событиями с именами пользователей, и процессами, которые инициировали перезагрузку/выключение сервера.
Get-EventLog -LogName System |
where {$_.EventId -eq 1074} |select-object -first 10 |
ForEach-Object {
$rv = New-Object PSObject | Select-Object Date, User, Action, process, Reason, ReasonCode
if ($_.ReplacementStrings[4]) {
$rv.Date = $_.TimeGenerated
$rv.User = $_.ReplacementStrings[6]
$rv.Process = $_.ReplacementStrings[0]
$rv.Action = $_.ReplacementStrings[4]
$rv.Reason = $_.ReplacementStrings[2]
$rv
}
} | Select-Object Date, Action, Reason, User, Process |ft
Также с помощью PowerShell можно быстро получить имя пользователя, который перезагрузил удаленный компьютер. Получить доступ к журналу событий на удаленном хосте можно с помощью формата Get-EventLog -ComputerName или вы можете подключиться к компьютеру через PSRemoting с помощью командлета Invoke-Command:
Invoke-Command -ComputerName rds2-12 -ScriptBlock {Get-WinEvent -FilterHashtable @{logname=’System’;id=1074} |select-object TimeCreated,Id,Message -first 1}
По событию 1074 можно найти только причины корректных (штатных) перезагрузок сервера. Если Windows была перезагружена не штатно (например, при потере электропитания, или появления BSOD), тогда нужно искать события с EventID 6008.
The previous system shutdown at 4:34:49 AM on 1/17/2022 was unexpected.
И конечно, вы не сможете понять, кто перезагрузил Windows, если журналы событий были очищены, или старые события перезатерты более новыми (в домене желательно настроить увеличенный размер журналов событий с помощью GPO).
В этой статье мы рассмотрим базовые настройки Windows Server 2019, это AD, DNS, DHCP и лицензирование терминального сервера. Данные настройки актуальны на большинстве серверов и являются самыми необходимыми.
Как установить Windows Server и произвести первичные настройки по активации можете ознакомиться в нашей прошлой статье по этой ссылке.
1) Меняем имя сервера и его описание (если нужно). Переходим в свойства системы => изменить параметры => изменить. Задаем «Имя компьютера», и если нужно, то имя рабочей группы. После изменения параметров нужно перезагрузиться.
После перезагрузки можете проверить, все ли у вас прошло успешно с изменением имени.
2) Далее меняем сетевые настройки, IP, маску и шлюз ставите обязательно статичными, настройки производятся в зависимости от Вашей сети.
Переходим в свойства сетевой карты.
И далее в свойства IPv4
3) Следующим пунктом настраиваем Active Directory. Добавляем роли и компоненты. Для этого переходим меню «Пуск» => Диспетчер серверов.
Установка «Ролей и компонентов».
Соответственно выбираем нужный нам пул сервера.
В «Роли сервера» для всех наших настроек выберем «DHCP-сервер», «DNS-сервер», «Доменные службы Active Directory» и «Службы удаленных рабочих столов».
Идем далее до «Службы ролей» и выбираем пункты как на скриншоте ниже.
После так же идем «Далее» до пункта «Подтверждение» и устанавливаем все, что мы выбрали.
После установки в «Результатах» выбираем пункт «Повысить роль этого сервера до уровня контроллера домена».
В мастере настроек доменных служб выбираем «Добавить лес» и вводим имя корневого домена, это может быть любое имя, к примеру домен вашего сайта.
В параметрах контроллера нужно придумать пароль.
По каталогу настроек идем дальше, до дополнительных параметров, там нужно указать имя домена NetBIOS, если он у вас там уже стоит, то можете оставить как есть, либо поменять по своему желанию.
Далее идем до «Проверки предварительных требований», если проверка прошла успешно, то устанавливаем примененные настройки.
После полной установки необходимо перезагрузиться.
4) Производим настройку «Зона обратного просмотра».
На пункте «Зона обратного просмотра» => Создать новую зону.
Выбираем «Основную зону».
Для всех DNS-серверов, работающих на контроллерах домена в этом домене:
Зона обратного просмотра IPv4
Ну и соответственно выводим индефикатор сети.
Проверяем, что все установилось.
5) Переходим к настройке DHCP. Переходим в мастер установки.
После завершения установки => Диспетчер => Средства => DHCP
На DHCP => Имя вашего сервера => IPv4 — правой кнопкой мыши => Создать область.
Задаем любое имя области DHCP.
В диапазоне адресов задаем начальный и конечный интервал области IP адресов, который будет раздавать сервер.
Далее в дереве каталогов DHCP => Имя сервера => Область => Пул адресов. В списке должен быть указан начальный и конечный диапазон, который Вы указывали в настройках.
6) Теперь по настройкам лицензирования удаленных рабочих столов (терминального сервера). Пошаговую инструкцию как лицензировать терминальный сервер можете прочитать в нашей ранней статье на следующей странице.
Лицензионный ключ активации Windows Server 2019 от
Sometimes the Windows search bar stops working. Usually this is related to updates but there can be other causes as well. In this guide, we will show you a few methods to solve this problem.
Step 1. Restart Windows File Explorer
In the first method, we are going to restart the Windows File Explorer. File explorer is responsible for showing files and folders on your computer. To restart this, right-click on the Windows taskbar and select Task Manager or use the keyboard combination Ctrl + Shift + Esc.
Scroll down in background processes until you reach Windows Explorer. Select it and click on the restart button.
Step 2. Search and Indexing Troubleshooter
In the second method, we are going to use the search and indexing troubleshooter. To do this, use the keyboard combination Windows + R. This opens a run window. Here, you can enter ms-settings:
Click on Update & security. After that, click on Troubleshoot on the left of the settings menu.
Next, click on Additional troubleshooters. In this window, you get an overview of all of the available troubleshooters. Scroll a bit down and select Search and Indexing. Click on Run the troubleshooter.
Here, you have a few options to choose from. In this tutorial, the logical choice is Can’t start a search or see results. You can also check, Search or indexing is slow. After that, click on next.
In our case, it suggests trying to repair Windows search as administrator. So, we’ll select this option and wait a short bit for the repair to complete. It’s possible that you have a different suggestion. The best option is to go along with what the troubleshooter says.
In our case, it suggests trying to repair Windows search as administrator. So, we’ll select this option and wait a short bit for the repair to complete. It’s possible that you have a different suggestion or it will run automatically the troubleshooting. The best option is to go along with what the troubleshooter says.
Step 3. Restart Windows Search Service
Sometimes, it happens that wrong settings are set for the Windows search bar or that the search service isn’t running. We can check this by going to the services in the Windows taskbar. Use Ctrl + Shift + Esc if you need to reopen this.
Switch to the services tab. Here you can click on Open Services.
Scroll down until you reach Windows Search. First, make sure that the status is set to running. If not, right click on it and select start. If not, right click on it and select restart.
Restart your Windows server, then try again.
Step 4. Fix Windows Search with Indexing
We are going to rebuild the indexing feature. It might be that this is the cause that Windows search isn’t working properly. Use the keyboard combination Windows + R to open another run window. Type in Control panel and hit Ok.
Change the “view by” to small or large icons. After that, search for indexing options. The indexing options menu opens
Then click on Advanced.
This opens a new window, here you can delete and rebuild the indexing options. Keep in mind that this can take quite a bit of time especially if you have an older system. When you are ready, click on the Rebuild button. A warning from Windows that this might take some time. Click on Ok.
Wait for this to complete. You will know that it is done once it says indexing complete at the top.
Conclusion
In our case after performing the above steps, we did not see the error again.
Hopefully, this article will be helpful for you. Good luck!