Fórum Root.cz
Hlavní témata => Windows a jiné systémy => Téma založeno: ZAJDAN 27. 02. 2018, 12:59:55
-
Ahoj...
zajímalo by mne proč systém hlásí:
The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data.
když tuto službu nevyužívám/nekonfiguroval jsem, protože rozprostřené úložiště na více místech nemám. A v síti je jediný DC.
-
Prvni odkaz?
This occurs because the DFS Namespace service attempts to access Active Directory before it has completely initialized.
To resolve this issue, we simply have to force the DFS Namespace service to start after the Active Directory service has initialized. We can do this by setting the DFS Namespace service to depend on the Active Directory service as well as setting it to a Delayed Startup mode.
To make those changes, start regedit and make the following changes :
Navigate to the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Dfs
Modify the DependOnService value and add NTDS to the list.
Create a new DWORD value named DelayedAutostart and set its value to 1.
This entry was posted in Windows Server on September 5, 2009.
-
Prvni odkaz?
This occurs because the DFS Namespace service attempts to access Active Directory before it has completely initialized.
To resolve this issue, we simply have to force the DFS Namespace service to start after the Active Directory service has initialized. We can do this by setting the DFS Namespace service to depend on the Active Directory service as well as setting it to a Delayed Startup mode.
To make those changes, start regedit and make the following changes :
Navigate to the registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Dfs
Modify the DependOnService value and add NTDS to the list.
Create a new DWORD value named DelayedAutostart and set its value to 1.
This entry was posted in Windows Server on September 5, 2009.
ano to jsem take nasel, ale precijenom vime ze tam lidi pisou kde co...udelam snapshot a zkusim to
me by spise zajimalo proc se tak deje
-
Tak ted asi nechapu.
Jak "Proc se tak deje?"
DFS pro svoji funkcnost potrebuje sluzby AD.
Po startu Windows ruzne sluzby nabihaji ruzne dlouho.
Pokud neni nastavena zavislost, muze DFS nastartovat driv nez AD, a pak zahlasi chybu (zvlast kdyz je DC jenom jeden, pak se bude pravdepodobne rozcilovat vic veci).
Pokud to hlasi jindy nez po startu, videl bych problem v tom, ze stroj byl puvodne v jine domene a nebyl korektne odebran....jak uz tu bylo probirano v jinem tematu. V tom pripade bych videl jako cestu cistou instalaci DC
-
Tak ted asi nechapu.
Jak "Proc se tak deje?"
DFS pro svoji funkcnost potrebuje sluzby AD.
Po startu Windows ruzne sluzby nabihaji ruzne dlouho.
Pokud neni nastavena zavislost, muze DFS nastartovat driv nez AD, a pak zahlasi chybu (zvlast kdyz je DC jenom jeden, pak se bude pravdepodobne rozcilovat vic veci).
Pokud to hlasi jindy nez po startu, videl bych problem v tom, ze stroj byl puvodne v jine domene a nebyl korektne odebran....jak uz tu bylo probirano v jinem tematu. V tom pripade bych videl jako cestu cistou instalaci DC
tento stroj byl puvodne clenem jine domeny, a ted se stal sam Domenovym radicem
-
ok, provedl jsem tu změnu v registru a vypadá to, že to zabralo