SYSVOL Doesn't Share

I installed a windows 2003 server into a domain that had a Windows 2000
server as the DC. It, in turn, had been upgraded a couple years earlier from
NT.

I did all of the stuff that had to be done to the 2000 domain to get it
ready to have a 2003 DC, and everything worked fine. No errors that I found.
I upgraded the 2003 server to a DC and noticed that the SYSVOL folder wasn't
shared correctly. There was also no "Scripts" folder within it.

I demoted the 2003 server to a member, upgraded the 2000 server to 2003 and
re-promoted the original 2003 server to a DC again. Still, SYSVOL isn't
shared correctly, and there's no "Scripts".

What's a boy to do?

make sure you have enough space on old DC. use dcdiag to check any errors. this case may help,

Upgrade 2000 DC to 2003 DC

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
"Paul Smith" <(E-Mail Removed)> wrote in message news:C7D625B5-A958-4E7B-911C-(E-Mail Removed)...
I installed a windows 2003 server into a domain that had a Windows 2000
server as the DC. It, in turn, had been upgraded a couple years earlier from
NT.

I did all of the stuff that had to be done to the 2000 domain to get it
ready to have a 2003 DC, and everything worked fine. No errors that I found.
I upgraded the 2003 server to a DC and noticed that the SYSVOL folder wasn't
shared correctly. There was also no "Scripts" folder within it.

I demoted the 2003 server to a member, upgraded the 2000 server to 2003 and
re-promoted the original 2003 server to a DC again. Still, SYSVOL isn't
shared correctly, and there's no "Scripts".

What's a boy to do?

The old server has 737MB of space on the C:\ drive. I'm unclear, however,
why that would matter since it's the new one that's having the problems. Am
I missing something?

Paul

"Robert L [MS-MVP]" wrote:

> make sure you have enough space on old DC. use dcdiag to check any errors. this case may help,
>
> Upgrade 2000 DC to 2003 DC
>
> Bob Lin, MS-MVP, MCSE & CNE
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> "Paul Smith" <(E-Mail Removed)> wrote in message news:C7D625B5-A958-4E7B-911C-(E-Mail Removed)...
> I installed a windows 2003 server into a domain that had a Windows 2000
> server as the DC. It, in turn, had been upgraded a couple years earlier from
> NT.
>
> I did all of the stuff that had to be done to the 2000 domain to get it
> ready to have a 2003 DC, and everything worked fine. No errors that I found.
> I upgraded the 2003 server to a DC and noticed that the SYSVOL folder wasn't
> shared correctly. There was also no "Scripts" folder within it.
>
> I demoted the 2003 server to a member, upgraded the 2000 server to 2003 and
> re-promoted the original 2003 server to a DC again. Still, SYSVOL isn't
> shared correctly, and there's no "Scripts".
>
> What's a boy to do?

"=?Utf-8?B?UGF1bCBTbWl0aA==?=" <(E-Mail Removed)>
wrote in news:C7D625B5-A958-4E7B-911C-(E-Mail Removed):

> I installed a windows 2003 server into a domain that had a Windows
> 2000 server as the DC. It, in turn, had been upgraded a couple years
> earlier from NT.
>
> I did all of the stuff that had to be done to the 2000 domain to get
> it ready to have a 2003 DC, and everything worked fine. No errors
> that I found.
> I upgraded the 2003 server to a DC and noticed that the SYSVOL folder
> wasn't
> shared correctly. There was also no "Scripts" folder within it.
>
> I demoted the 2003 server to a member, upgraded the 2000 server to
> 2003 and re-promoted the original 2003 server to a DC again. Still,
> SYSVOL isn't shared correctly, and there's no "Scripts".
>
> What's a boy to do?

When I encountered this problem, I ended up sharing the SYSVOL folder
manually and creating the subsequent folders, as well as the GPOs.
Fortunately, there were only four or five specialized GPOs to worry
about.

I'm sure you have viewed the following MS article, but just in case:
http://support.microsoft.com/?kbid=324392

You have also probably viewed this, but here it is anyhow:
http://www.microsoft.com/technet/pro...003/library/Op
erations/e3d471bf-658a-473c-9c4d-ad5ca71258e4.mspx

HTH

Thank you so much for this - and, on, I hadn't seen the article. I did all
of the things listed, but I hadn't seen what you sent, and it may still be
useful.

Just two more questions...first, where do I find out what GPO's have to be
modified. Second, after you did this people were able to log into the
computer, right?

Paul

"Crake" wrote:

> "=?Utf-8?B?UGF1bCBTbWl0aA==?=" <(E-Mail Removed)>
> wrote in news:C7D625B5-A958-4E7B-911C-(E-Mail Removed):
>
> > I installed a windows 2003 server into a domain that had a Windows
> > 2000 server as the DC. It, in turn, had been upgraded a couple years
> > earlier from NT.
> >
> > I did all of the stuff that had to be done to the 2000 domain to get
> > it ready to have a 2003 DC, and everything worked fine. No errors
> > that I found.
> > I upgraded the 2003 server to a DC and noticed that the SYSVOL folder
> > wasn't
> > shared correctly. There was also no "Scripts" folder within it.
> >
> > I demoted the 2003 server to a member, upgraded the 2000 server to
> > 2003 and re-promoted the original 2003 server to a DC again. Still,
> > SYSVOL isn't shared correctly, and there's no "Scripts".
> >
> > What's a boy to do?
>
> When I encountered this problem, I ended up sharing the SYSVOL folder
> manually and creating the subsequent folders, as well as the GPOs.
> Fortunately, there were only four or five specialized GPOs to worry
> about.
>
> I'm sure you have viewed the following MS article, but just in case:
> http://support.microsoft.com/?kbid=324392
>
> You have also probably viewed this, but here it is anyhow:
> http://www.microsoft.com/technet/pro...003/library/Op
> erations/e3d471bf-658a-473c-9c4d-ad5ca71258e4.mspx
>
> HTH
>
>

I just reread your reply. Do you mean that the GPO's you had to change where
ones that you configured for yourself as opposed to (as I had originally
thought) GPO's that have to be created in order for the server to function as
a point into which people can logon? If so, I'm presuming that I wouldn't
have to worry about them, right?

Paul


"Crake" wrote:

> "=?Utf-8?B?UGF1bCBTbWl0aA==?=" <(E-Mail Removed)>
> wrote in news:C7D625B5-A958-4E7B-911C-(E-Mail Removed):
>
> > I installed a windows 2003 server into a domain that had a Windows
> > 2000 server as the DC. It, in turn, had been upgraded a couple years
> > earlier from NT.
> >
> > I did all of the stuff that had to be done to the 2000 domain to get
> > it ready to have a 2003 DC, and everything worked fine. No errors
> > that I found.
> > I upgraded the 2003 server to a DC and noticed that the SYSVOL folder
> > wasn't
> > shared correctly. There was also no "Scripts" folder within it.
> >
> > I demoted the 2003 server to a member, upgraded the 2000 server to
> > 2003 and re-promoted the original 2003 server to a DC again. Still,
> > SYSVOL isn't shared correctly, and there's no "Scripts".
> >
> > What's a boy to do?
>
> When I encountered this problem, I ended up sharing the SYSVOL folder
> manually and creating the subsequent folders, as well as the GPOs.
> Fortunately, there were only four or five specialized GPOs to worry
> about.
>
> I'm sure you have viewed the following MS article, but just in case:
> http://support.microsoft.com/?kbid=324392
>
> You have also probably viewed this, but here it is anyhow:
> http://www.microsoft.com/technet/pro...003/library/Op
> erations/e3d471bf-658a-473c-9c4d-ad5ca71258e4.mspx
>
> HTH
>
>