Re: SYSVOL Doesn't appear as shared in a Secondary Domain Controll
- From: mosquito_hippy <mosquitohippy@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 23 Jul 2009 13:12:05 -0700
You are right but...
But it could work isn't it?
Any way i won't waste anything but time, if it does work it would be faster
than pass through all the diagnostic process, don't you think?
Thanks in advance
"Paul Bergson [MVP-DS]" wrote:
Evevn if you repromote it may not work. Find out why it is broke..
Run diagnostics against your Active Directory domain.
If you don't have the support tools installed, install them from your server
install disk.
d:\support\tools\setup.exe
Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
-> ntfrsutl ds your_dc_name > c:\sysvol.log
-> dnslint /ad /s "ip address of your dc"
**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take into
account slow links to dc's will also add to the testing time.
If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests without
having to learn all the switch options. The details will be output in
notepad text files that pop up automagically.
The script is located on my website at
http://www.pbbergs.com/windows/downloads.htm
Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)
When complete search for fail, error and warning messages.
Description and download for dnslint
http://support.microsoft.com/kb/321045
--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009
http://www.pbbergs.com
Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.
"mosquito_hippy" <mosquitohippy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D03A0FF3-E698-425E-9DE1-2BEA4108DFA1@xxxxxxxxxxxxxxxx
Hi
I have read a lot possible solutions for this issue but i'm wondering if
it
is not a better idea, since it's a secondary domain controller, simply
demote
this secondary domain controller and then promote it as domain controller
again so this shared can be recreated.
What do you think?
Thanks in advance
- Follow-Ups:
- Re: SYSVOL Doesn't appear as shared in a Secondary Domain Controll
- From: Jorge Silva
- Re: SYSVOL Doesn't appear as shared in a Secondary Domain Controll
- From: Paul Bergson [MVP-DS]
- Re: SYSVOL Doesn't appear as shared in a Secondary Domain Controll
- References:
- SYSVOL Doesn't appear as shared in a Secondary Domain Controller
- From: mosquito_hippy
- Re: SYSVOL Doesn't appear as shared in a Secondary Domain Controller
- From: Paul Bergson [MVP-DS]
- SYSVOL Doesn't appear as shared in a Secondary Domain Controller
- Prev by Date: Re: AD on XP/Limit Activities - MMC Issues
- Next by Date: Re: Only boots in to AD recovery
- Previous by thread: Re: SYSVOL Doesn't appear as shared in a Secondary Domain Controller
- Next by thread: Re: SYSVOL Doesn't appear as shared in a Secondary Domain Controll
- Index(es):
Relevant Pages
|
