Re: sysvol folders missing

Tech-Archive recommends: Speed Up your PC by fixing your registry


The machine itself is a DC as it still has AD installed on it. But it is
listed in AD as a member server and now lives in the computers container. It
should be in the DC OU because its a DC. I don't know how it moved because it
wasn't demoted as far as I know.

Do I just move it back into the DC OU - is it as simple as that, or will I
break something else?

Thanks,
Taz


"Meinolf Weber [MVP-DS]" wrote:

Hello Taz1972,

When you demote a domain controller it automatically moves to the computers
container. The other way around occurs when a member server becomes domain
controller.

So it will not move itself to the computers container, either the DC is demoted
or moved to it. So is that machine a DC and listed also in the AD database?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


OK - we did an authoritative restore of sysvol from backup and this
seems to have solved the issue. GP's and scripts are now replicating
to all dc's as normal.

btw - we have one recently promoted DC, which at first was in the DC
OU but has now for some reason moved itself to the default computers
container. Why is this, and is it ok to just move it back to the DC
OU, or is there another procedure for this?

Thanks,
Taz
"Ace Fekay [Microsoft Certified Trainer]" wrote:

"Taz1972" <Taz1972@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9088532B-6E5B-44BD-AEAD-DF4561A11C28@xxxxxxxxxxxxxxxx

No, we didn't use sysprep, they were just iso images installed on
vmware.

Another thing I noticed was one of the DC's is showing up multiple
times
in
AD sites and services. A few days ago there were two computer
objects for
this DC, one had CNF with it, which I renamed to the proper DC name
and
other
object was deleted. But now I see multiple instances of the same DC
in AD
sites and services. So it looks like a SID issue.
So what is the best approach for solving this? Shall I do a AD
demotion on
the affected DC, metadata cleanup and removing the DC from AD and
dns
zones
etc? Or is there a better way?
Thanks,
Taz
Hi Taz,

See if you can run a dcpromo /forceremoval. If that doesn't work,
simply delete the duplicate images, and run a Metadata Cleanup to
remove references from the AD database as shown in the following
article. Also make sure the server objects are deleted in Sites and
Services. Go through DNS to make sure it's gone, including under the
Nameservers tab in DNS properties.

Cleanup (Metadata Cleanup) the AD database from the crashed DC - How
to
remove data in Active Directory after an unsuccessful domain
controller
demotion
http://support.microsoft.com/kb/216498
Then put your image on a machine or VM. Then run Sysprep on it using
the mini-setup switch. WHen it needs to restart, trap the restart and
Ghost it up or whatever you're using, to your image file. Then use
that image to put on a machine. During startup it will go through a
mini setup process where it will ask for a machine name, IP info,
etc. During this mini setup process, it creates a new SID for the
machine.

Here are some links on Sysprep

How to use the Sysprep tool to automate successful deployment of
....Describes how system administrators can use Sysprep to
automatically
deploy Windows XP on multiple computers. Describes how to set up an
initial
computer ...
http://support.microsoft.com/kb/302577
Updated System Preparation tool for Windows XP Service Pack 2 ...Use
Sysprep.exe to create images of operating systems, to duplicate
disks, to automate the mini-Setup program, and to perform many other
deployment tasks. http://support.microsoft.com/kb/838080

More results from support.microsoft.com »
How to Use Sysprep: An IntroductionNov 29, 2001 ... Sysprep is a tool
designed for corporate system administrators, OEMs, and others who
need to
deploy the Windows® XP operating system on ...
http://technet.microsoft.com/en-us/library/bb457073.aspx
I hope that helps!

Ace




.

Relevant Pages

  • Re: sysvol folders missing
    ... has now for some reason moved itself to the default computers container. ... and run a Metadata Cleanup to remove references ... Here are some links on Sysprep ... automate the mini-Setup program, and to perform many other deployment tasks. ...
    (microsoft.public.windows.server.active_directory)
  • Re: sysvol folders missing
    ... Check with ntdsutil if it is really a known DC in the AD database. ... is listed in AD as a member server and now lives in the computers ... and run a Metadata Cleanup to ... Here are some links on Sysprep ...
    (microsoft.public.windows.server.active_directory)
  • Sysprep Delay Question (15 minutes)
    ... Usually when I use the system preparation tool (sysprep) for resealing ... it almost always takes the proper 15 seconds or so to reseal the computer. ... if I let it go through the minisetup again and resysprep it then ... It happens on new computers and old computers. ...
    (microsoft.public.windowsxp.setup_deployment)
  • Re: Clone Disk
    ... Do we need to use Sysprep before we capture an image with Norton Ghost only? ... >> If i want to roll out computers with the same OS plus ... >> the hard drives, is it possible to then change the Windows Product Key. ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange Wizard not available in AD Users and Computers
    ... Computers on the member server. ... >Exchange CD run setup, select Custom and select just the ... >> Exchange 2003 on the member server then ran ForestPrep ... >> it OK for me to run the ForestPrep and DomainPrep from ...
    (microsoft.public.exchange.setup)