forthphaze
asked on
SBS BPA & Migration Prep Tool Report SYSVOL Not Shared.
Trying to run the SBS08 Migration Prep Tool on an SBS03 server. I get an error when scanning for issues that the SYSVOL folder is not shared. Also get this error in the SBS03 BPA. It is shared. It shows up properly in "net share" as does the netlogon, I can browse to it on the network, the proper permissions are set.
NETLOGON C:\WINDOWS\SYSVOL\sysvol\b
SYSVOL C:\WINDOWS\SYSVOL\sysvol
I've done all the things this article suggests as actions to take.
http://technet.microsoft.com/en-us/library/cc816833(WS.10).aspx
dcdiag /test:netlogons runs clean
dcdiag /test:replications runs clean
I've re-applied the default SYSVOL security settings per the instructions here:
http://technet.microsoft.com/en-us/library/cc816750(WS.10).aspx
I've set the burflags registry setting to D4 for kicks, recreated the junction points, and restarted the ntfrs service.
There is nothing in the Logs that indicate there is a problem. The last entries in the FRS logs are event ID 13566, 13553, and 13516.
Any ideas?
NETLOGON C:\WINDOWS\SYSVOL\sysvol\b
SYSVOL C:\WINDOWS\SYSVOL\sysvol
I've done all the things this article suggests as actions to take.
http://technet.microsoft.com/en-us/library/cc816833(WS.10).aspx
dcdiag /test:netlogons runs clean
dcdiag /test:replications runs clean
I've re-applied the default SYSVOL security settings per the instructions here:
http://technet.microsoft.com/en-us/library/cc816750(WS.10).aspx
I've set the burflags registry setting to D4 for kicks, recreated the junction points, and restarted the ntfrs service.
There is nothing in the Logs that indicate there is a problem. The last entries in the FRS logs are event ID 13566, 13553, and 13516.
Any ideas?
ASKER
Yes only using itself as DNS. I am not aware of any previous servers with this client.
I had to bite the bullet and call Microsoft. They are one the system right now. The tech thought this would be a simple fix, but he's now stuck on it as well. He checked NTDS probably for the same thought as you had in your second question. I'll keep you posted. If you have any other thoughts let me know.
I had to bite the bullet and call Microsoft. They are one the system right now. The tech thought this would be a simple fix, but he's now stuck on it as well. He checked NTDS probably for the same thought as you had in your second question. I'll keep you posted. If you have any other thoughts let me know.
ASKER
The MS tech just came on the line and verified that I am not insane, everything checks out fine yet the error still is reported. He is going to do more research and get back with me.
The only other thought I had was a possible service/binding configuration problem.
Does the server still have 2 NIC's and are they both active? Disable the one that isn't in use, and even go as far as uninstalling it in Windows Device Manager.
You may need to do the same with the other "live" NIC as well. I had a similar problem to this a couple of weeks ago and it was down to a mismatch GUID on the network adapters.
When you open the network connection screen do the icons look right? Is the enabled NIC using an enabled icon?
Does the server still have 2 NIC's and are they both active? Disable the one that isn't in use, and even go as far as uninstalling it in Windows Device Manager.
You may need to do the same with the other "live" NIC as well. I had a similar problem to this a couple of weeks ago and it was down to a mismatch GUID on the network adapters.
When you open the network connection screen do the icons look right? Is the enabled NIC using an enabled icon?
If you run NETDOM QUERY DC from a command prompt what do you get back?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Excellent, good work!
ASKER
I've requested that this question be closed as follows:
Accepted answer: 0 points for forthphaze's comment http:/Q_26939255.html#35368507
for the following reason:
Called Microsoft Support who resolved issue. Turns out the source was unrelated to what the symptoms were.
Accepted answer: 0 points for forthphaze's comment http:/Q_26939255.html#35368507
for the following reason:
Called Microsoft Support who resolved issue. Turns out the source was unrelated to what the symptoms were.
ASKER
trying to close this thing so I can open a new question
Is it possible there was another domain controller on the network at one stage that wasn't demoted properly? Or failed?