sbs 2003 to server 2012 server migration
Hi
We are in the process of migrating an SBS2003 server hiper01 to 2 Virtualised 2012 Servers, one as a Domain Controller which we will call hiper-domain and one an Exchange 2010 Server called hiper-exchange. We are using http://demazter.wordpress.com/2010/04/29/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2/ which is an excellent document as a template.
We have come across an impasse.
We believe that file replication is not working correctly.
On the existing SBS2003 hiper01 server we had the SYSVOL and NETLOGON shares.
On the new domain controller we only had the SYSVOL share.
To rectify this we tried http://blog.ronnypot.nl/?p=738 whereby we created “Enable Journal Wrap Automatic Restore” and set it to 1 and restarted the FRS service. We waited to see if this resolved the issue but to no avail. We then tried to stopped FRS and renamed the ntfrs/jet folder and restarted the FRS service. At this point we seem to have lost the SYSVOL share although we had taken a copy of it. The folder still existed but was no longer shared. So I stopped the RFS and reverted to the old jet folder. I then restarted FRS.
The current situation is:
hiper-domain has SYSVOL share
hiper01 which is the SBS 2003 server has the SYSVOL which isn't shared and no NETLOGON folder
hiper-domain FRS event log has 13508
hiper01 has 13559 asking that we put a file name NTFRS_CMD_FILE_MOVE_ROOT under the new root path c:\windows\sysvol\domain
We haven't carried out the above yet.
Should we?
How do we get to a situation where we have the SYSVOL and the NETLOGON shares on both servers and the File Replication working again.
I realise this is a lot to ask but any help would be appreciated.
The users all can log on at the moment and access the EXCHANGE 2010 server as well as access shares on the Domain Controller. Email is all up to Exchange 2010 and remote owa works okay. At the moment. The issue was created yesterday.
We are reticent to carry on with the migration until the File Replication is working.
Look forward to your help experts
Cheers
Stuart
We are in the process of migrating an SBS2003 server hiper01 to 2 Virtualised 2012 Servers, one as a Domain Controller which we will call hiper-domain and one an Exchange 2010 Server called hiper-exchange. We are using http://demazter.wordpress.com/2010/04/29/migrate-small-business-server-2003-to-exchange-2010-and-windows-2008-r2/ which is an excellent document as a template.
We have come across an impasse.
We believe that file replication is not working correctly.
On the existing SBS2003 hiper01 server we had the SYSVOL and NETLOGON shares.
On the new domain controller we only had the SYSVOL share.
To rectify this we tried http://blog.ronnypot.nl/?p=738 whereby we created “Enable Journal Wrap Automatic Restore” and set it to 1 and restarted the FRS service. We waited to see if this resolved the issue but to no avail. We then tried to stopped FRS and renamed the ntfrs/jet folder and restarted the FRS service. At this point we seem to have lost the SYSVOL share although we had taken a copy of it. The folder still existed but was no longer shared. So I stopped the RFS and reverted to the old jet folder. I then restarted FRS.
The current situation is:
hiper-domain has SYSVOL share
hiper01 which is the SBS 2003 server has the SYSVOL which isn't shared and no NETLOGON folder
hiper-domain FRS event log has 13508
hiper01 has 13559 asking that we put a file name NTFRS_CMD_FILE_MOVE_ROOT under the new root path c:\windows\sysvol\domain
We haven't carried out the above yet.
Should we?
How do we get to a situation where we have the SYSVOL and the NETLOGON shares on both servers and the File Replication working again.
I realise this is a lot to ask but any help would be appreciated.
The users all can log on at the moment and access the EXCHANGE 2010 server as well as access shares on the Domain Controller. Email is all up to Exchange 2010 and remote owa works okay. At the moment. The issue was created yesterday.
We are reticent to carry on with the migration until the File Replication is working.
Look forward to your help experts
Cheers
Stuart
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Stuart