Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Active Directory » Re: sysvol folders missing
Re: sysvol folders missing [message #156871] Thu, 25 June 2009 08:52 Go to next message
meiweb(nospam)  is currently offline meiweb(nospam)  Germany
Messages: 1307
Registered: July 2009
Senior Member
Hello Taz1972,

Check this article:
http://support.microsoft.com/kb/315457

Did you restore one or more DCs from backup before, maybe a snapshot? Or
are they installed from images that are not sysprepped?

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


> Hi,
>
> I found out that in the sysvol\domain folder, everything is gone
> except the folder DO_NOT_REMOVE_NtFrs_PreInstall_Directory, which is
> itself empty. The sysvol share itself is still there though.
>
> This occurs on most DC's including the root which holds the fsmo roles
> (all DC's are server 2003, fully functional and also host dns/dhcp)
> but on a few of the DC it is not a problem. This problem started to
> happen when we added more 2003 DC's in our environment...
>
> Obviously somewhere something has gone wrong, and of course I cannot
> even open group policies. When I try to open the gpmc snapin I get the
> error:
>
> 'failed to open the group policy object the system cannot find the
> path specified'.
>
> So how do I repopulate the sysvol share again with the scripts,
> policies folders etc?
>
> Please help as this is urgent.
>
> Thanks,
> Taz
Re: sysvol folders missing [message #156885 is a reply to message #156871] Thu, 25 June 2009 10:43 Go to previous messageGo to next message
Taz1972  is currently offline Taz1972
Messages: 18
Registered: October 2009
Junior Member
Hi Meinolf ,

No, we haven't restored any DC from backup, as far as I know. Some of these
machines were installed the normal way (CD etc) and we have some image based
DC's that are installed on VMware.

Thanks,
Taz

"Meinolf Weber [MVP-DS]" wrote:

> Hello Taz1972,
>
> Check this article:
> http://support.microsoft.com/kb/315457
>
> Did you restore one or more DCs from backup before, maybe a snapshot? Or
> are they installed from images that are not sysprepped?
>
> 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
>
>
> > Hi,
> >
> > I found out that in the sysvol\domain folder, everything is gone
> > except the folder DO_NOT_REMOVE_NtFrs_PreInstall_Directory, which is
> > itself empty. The sysvol share itself is still there though.
> >
> > This occurs on most DC's including the root which holds the fsmo roles
> > (all DC's are server 2003, fully functional and also host dns/dhcp)
> > but on a few of the DC it is not a problem. This problem started to
> > happen when we added more 2003 DC's in our environment...
> >
> > Obviously somewhere something has gone wrong, and of course I cannot
> > even open group policies. When I try to open the gpmc snapin I get the
> > error:
> >
> > 'failed to open the group policy object the system cannot find the
> > path specified'.
> >
> > So how do I repopulate the sysvol share again with the scripts,
> > policies folders etc?
> >
> > Please help as this is urgent.
> >
> > Thanks,
> > Taz
>
>
>
Re: sysvol folders missing [message #156892 is a reply to message #156885] Thu, 25 June 2009 11:12 Go to previous messageGo to next message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Taz1972" <Taz1972@discussions.microsoft.com> wrote in message
news:05088FB7-A085-45F9-8D87-35E5CCCEFC59@microsoft.com...
> Hi Meinolf ,
>
> No, we haven't restored any DC from backup, as far as I know. Some of
> these
> machines were installed the normal way (CD etc) and we have some image
> based
> DC's that are installed on VMware.
>
> Thanks,
> Taz


Did you use Sysprep on the base image used to create the VMWare DCs?

If not, then they have duplicate operating system SIDs, which can cause
major problems.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup/forum to benefit from collaboration among
responding engineers, as well as to help others benefit from your
resolution.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
aceman@mvps.RemoveThisPart.org
http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.
Re: sysvol folders missing [message #156994 is a reply to message #156892] Mon, 29 June 2009 03:38 Go to previous messageGo to next message
Taz1972  is currently offline Taz1972
Messages: 18
Registered: October 2009
Junior Member
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


"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "Taz1972" <Taz1972@discussions.microsoft.com> wrote in message
> news:05088FB7-A085-45F9-8D87-35E5CCCEFC59@microsoft.com...
> > Hi Meinolf ,
> >
> > No, we haven't restored any DC from backup, as far as I know. Some of
> > these
> > machines were installed the normal way (CD etc) and we have some image
> > based
> > DC's that are installed on VMware.
> >
> > Thanks,
> > Taz
>
>
> Did you use Sysprep on the base image used to create the VMWare DCs?
>
> If not, then they have duplicate operating system SIDs, which can cause
> major problems.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Please reply back to the newsgroup/forum to benefit from collaboration among
> responding engineers, as well as to help others benefit from your
> resolution.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
> Microsoft Certified Trainer
> aceman@mvps.RemoveThisPart.org
> http://twitter.com/acefekay
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
>
Re: sysvol folders missing [message #157010 is a reply to message #156994] Mon, 29 June 2009 08:32 Go to previous messageGo to next message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Taz1972" <Taz1972@discussions.microsoft.com> wrote in message
news:9088532B-6E5B-44BD-AEAD-DF4561A11C28@microsoft.com...
> 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
Re: sysvol folders missing [message #157050 is a reply to message #157010] Tue, 30 June 2009 05:11 Go to previous messageGo to next message
Taz1972  is currently offline Taz1972
Messages: 18
Registered: October 2009
Junior Member
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@discussions.microsoft.com> wrote in message
> news:9088532B-6E5B-44BD-AEAD-DF4561A11C28@microsoft.com...
> > 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
>
>
>
>
>
Re: sysvol folders missing [message #157051 is a reply to message #157050] Tue, 30 June 2009 05:22 Go to previous messageGo to next message
meiweb(nospam)  is currently offline meiweb(nospam)  Germany
Messages: 1307
Registered: July 2009
Senior Member
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@discussions.microsoft.com> wrote in message
>> news:9088532B-6E5B-44BD-AEAD-DF4561A11C28@microsoft.com...
>>
>>> 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
>>
Re: sysvol folders missing [message #157055 is a reply to message #157051] Tue, 30 June 2009 07:28 Go to previous messageGo to next message
Taz1972  is currently offline Taz1972
Messages: 18
Registered: October 2009
Junior Member
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@discussions.microsoft.com> wrote in message
> >> news:9088532B-6E5B-44BD-AEAD-DF4561A11C28@microsoft.com...
> >>
> >>> 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
> >>
>
>
>
Re: sysvol folders missing [message #157057 is a reply to message #157055] Tue, 30 June 2009 07:33 Go to previous messageGo to next message
meiweb(nospam)  is currently offline meiweb(nospam)  Germany
Messages: 1307
Registered: July 2009
Senior Member
Hello Taz1972,

Check with ntdsutil if it is really a known DC 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


> 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@discussions.microsoft.com> wrote in message
>>>> news:9088532B-6E5B-44BD-AEAD-DF4561A11C28@microsoft.com...
>>>>
>>>>> 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
>>>>
Re: sysvol folders missing [message #157097 is a reply to message #157055] Tue, 30 June 2009 09:15 Go to previous message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
In news:AD6C8BC6-0437-4F8E-9287-0F7145C716E5@microsoft.com,
Taz1972 <Taz1972@discussions.microsoft.com>, posted the following, which I replied to down below...: Hello Taz1972
> 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?
>

It should belong in the Default DC OU, if it is actually believed to be a DC by AD. As Meinolf said, use ntdsutil to make sure it is listed as a DC. If you need help with ntdsutil, you can use http://support.microsoft.com/kb/216498 procedure to just check without making changes, to see if it is listed. If it is not, then we have another issue...

Ace
Previous Topic:LSASS Bleeding Over
Next Topic:Inconstant netlogon folders
Goto Forum:
  


Current Time: Fri Oct 20 02:53:04 EDT 2017

Total time taken to generate the page: 0.07182 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software