RE: Sysvol FRS to DFSr migration
- From: BobW <Osm3um@xxxxxxxxxxxxxx>
- Date: Wed, 30 Jul 2008 08:52:00 -0700
Another note on my other DC the sysvol key states C:\Windows\SYSVOL_DFSR\sysvol
"Miles Li [MSFT]" wrote:
Hello,.
As you have migrated the SYSVOL folder to DFRS, the FRS can be safely
disabled if no any other replication groups are using FRS.
From my search, it seems that there is a compatibility issue between
Symantec Backup Exec and DFSR. In the following Symantec knowledge base
article, it provides a workaround by stopping the DFSR service. As this
issue is related to Backup Exec, I suggest that you contact Symantec
support to see whether Backup Exec is compatible with DFSR and whether
there are any updates. Meanwhile, I suggest that you use Windows Backup to
backup System State to see whether it works. If so, the SYSVOL migration
should have been completed successfully and the problem lies in Backup Exec.
DFS backup and performance issues
http://www.backupexecfaq.com/faq/problems/dfs-backup-and-performance-issues.
html
Does Backup Exec for Windows Servers (BEWS) version 10d and above support
Microsoft Windows Server 2003 R2?
http://seer.entsupport.symantec.com/docs/281856.htm
If Windows Backup also encounters problems, please try to perform the
following steps to verify 'Eliminated' state works fine.
Step 1: Verify the DFS Replication global migration state is set to
eliminated by running the following command:
DfsrMig /GetGlobalState
Expected Output: The current DFSR global state: Eliminated. Succeeded.
Step 2: Verify that SYSVOL and NETLOGON shares are pointing to paths under
SYSVOL_DFSR Share
---------------------------------------
1. Click Start -> Run, type "regedit" in the text box, and click OK.
2. Locate the following registry value to ensure that it is pointing to the
right path. By default, it should point to "C:\Windows\SYSVOL_DFSR\sysvol"
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\Sy
sVol]
Step 3: Verify that there are no more NTFRS objects
-----------------------------------
NOTE: The ADSI Edit tool is included in Windows 2003 Support tool. If you
cannot find this tool, please install first Windows Server 2003 Support
tool.
1. Click Start -> Run, type "adsiedit.msc" in the text box, and click OK.
2. Locate the CN=Domain System Volume (SYSVOL share), CN=File Replication
Service, CN=System, DC=<Domain>, DC=<local> item, and ensure no child items.
Note that it may be necessary to force Active Directory replication and a
DFS Replication Active Directory poll on each domain controller to pick up
changes from Active Directory, if it is desired not to wait for this to
happen automatically. To force Active Directory replication, use RepAdmin
tool. To force DFS Replication Active Directory poll, use DfsrDiag PollAd
command.
Is the SYSVOL path correctly? Is the NTFRS object removed properly? If the
Windows Server Backup Tool fails to backup the system state because of the
SYSVOL corruption, could you please help to collect the Directory service
MPS report for our further investigation?
Microsoft Product Support's Reporting Tools (MPSRPT_DirSvc.EXE)
http://www.microsoft.com/downloads/details.aspx?FamilyID=CEBF3C7C-7CA5-408F-
88B7-F9C79B7306C0&displaylang=en
-----------------------
Please send the MPS report CAB file and screen shot file to
tfwst@xxxxxxxxxxxxx with the following three lines in the email body:
Sysvol FRS to DFSr migration
#42353085
Miles Li - MSFT
Thanks.
Best regards,
Miles Li
Microsoft Online Partner Support
Microsoft Global Technical Support Center
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
- References:
- RE: Sysvol FRS to DFSr migration
- From: Miles Li [MSFT]
- RE: Sysvol FRS to DFSr migration
- Prev by Date: RE: Sysvol FRS to DFSr migration
- Next by Date: Re: Invalid characters for a username.
- Previous by thread: RE: Sysvol FRS to DFSr migration
- Next by thread: Re: Windows 2003 SP2
- Index(es):
Relevant Pages
|