O Windows demora tanto no primeiro login no CentOS SAMBA DC

0

Eu configurei o SAMBA 4.7.0 DC no CentOS 7.4, referindo-me a este link . Tudo correu bem como diz. Eu configurei o DNS Back-end como SAMBA_INTERNAL e o DNS Forwarder como 8.8.4.4, embora eu não tenha configurado nenhuma configuração ou configuração de DNS antes da configuração do SAMBA.

Após concluir a configuração do SAMBA, criei alguns usuários administrativos. Eu coloquei o cliente Windows que está na mesma LAN sob o domínio SAMBA. Tudo corre bem e um reinício é processado.

Eu tentei fazer o login com nome de usuário e senha do domínio. Um círculo BEM-VINDO continua a girar por cerca de 8 minutos e ocorreu o seguinte erro.

The Group Policy Client service failed the sing-in. The universal unique identifier (UUID) type is not supported.

Eu cliquei em OK e tentei o mesmo processo novamente. Desta vez, o Windows efetuou login da mesma forma que o normal e o login continua bem até novos logins de novas contas.

Não gosto de esperar mais de 8 minutos após novos logins. Como posso consertar por favor?

Por favor, edite este post para uma melhor explicação, pois o meu inglês é ruim AF.

    
por Aung Myat 15.11.2017 / 04:55

1 resposta

0

Ah Windows 8.1. Existe um erro # 2890783 chamado - Incompatibilidade entre os perfis de usuário móveis do Windows 8.1 e aqueles nas versões anteriores do Windows

O problema é causado por: Perfis de usuários móveis no win8 ou win2012 são incompatíveis com perfis de usuários móveis em outras versões do Windows.

Para citar a solução da Microsoft:

Resolution

Update information To prevent this issue, before you deploy roaming, mandatory, super-mandatory, or domain default profiles in an environment where users will be using earlier versions of the operating system in addition to Windows 8.1 or Windows Server 2012 R2, follow these steps:

  1. Install update rollup 2887595. For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base: 2887595 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: November 2013
  2. Create a new registry entry by following the steps that are described in the "Registry information" section.
  3. Restart the computer.

    Note: If the roaming user profile is corrupted, you cannot use this update to resolve the issue. To recover from profile corruption, restore the roaming user profile from a backup.

Registry information

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 How to back up and restore the registry in Windows After you apply this update, you must create a registry key before you restart the computer.

  1. Swipe in from the right edge of the screen, and then tap Search. Or, if you are using a mouse, point to the lower-right corner of the screen, and then click Search.

  2. In the search box, type regedit, and then tap or click regedit. note: UAC If you are prompted to enter an administrator password, type the password. If you are prompted to provide confirmation, provide confirmation.

  3. Locate and then tap or click the following registry subkey: HKEY_LOCAL_MACHINE\System\CurrentControlset\Services\ProfSvc\Parameters

  4. On the Edit menu, point to New, and then tap or click DWORD Value.

  5. Type UseProfilePathExtensionVersion.
  6. Press and hold or right-click UseProfilePathExtensionVersion, and then tap or click Modify.
  7. In the Value data box, type 1, and then tap or click OK.
  8. Exit Registry Editor.

After you configure the UseProfilePathExtensionVersion registry entry, you have to restart the computer. Then, Windows 8.1 creates a user profile and appends the suffix ".v4" to the profile folder name to differentiate it from version 2 of the profile in Windows 7 and version 3 of the profile in Windows 8. Windows 8.1-based computers that have update rollup 2887595 installed and the UseProfilePathExtensionVersion registry entry configured use version 4 of the profile.

Notes

  • You can disable this feature by setting the value of the UseProfilePathExtensionVersion registry entry to 0. However, user profile corruption occurs if you continue to mix roaming user profiles from Windows 8.1-based computers with those from other operating systems.
  • You can use the Group Policy Preference (GPP) Computer Configuration Registry Preference item to populate the registry key on multiple computers. For more information about this, go to the following Microsoft website: Configure a registry item
  • You can safely apply this update on all operating systems. If these profile types are not being used, the registry setting is ignored.
    
por 15.11.2017 / 09:33