Sync Center and Domain problem

[beidog]

All our users' profiles (desktop and Documents) are stored in the server (AD server). When they log on or log off, their offline files will auto sync. (I believed it’s a domain policy; when a user is created on AD, the profile folder will auto create for sync as well).

Here is the case:
We have a local branch office; they connect to head quarter via VPN. Branch has their own local AD server and users’ profiles are store there locally (but all AD servers link together).
We brought a Win7 PC back from branch to head quarter.
I change this PC’s IP and computer name (take off and re-add to the domain).
I also deleted all other user’s profile on the local computer.
However, while a Head quarter user(including admin) log on to this PC, it will auto link to the AD server on branch office, then the sync will fail, since the user’s profile is not there.
I tried to relocate the sync folder, but the user got access denied whiling he tried to view his own profile.
I don’t know how to change its default sync folder and delete it. When I tried to add a new folder, it said that there are no new sync partnerships I can set up.
I am pretty new to feather of Sync Center.
Any suggestion?

 

[WindowsStar]

How long was the Windows 7 Machine Removed from the domain?? Did the DCs have time to replicate? If not you need to remove the machine from the domain and force a replication, then wait about 15 minutes and add the machine back to the domain. -WS

 

[beidog]

How long was the Windows 7 Machine Removed from the domain?? Did the DCs have time to replicate? If not you need to remove the machine from the domain and force a replication, then wait about 15 minutes and add the machine back to the domain. -WS

I tried it, but no luck!

 

[WindowsStar]

Background:
When a workstation contacts a DC it will go to the closest one. It is not magic it looks in AD and looks up the segment of the network it is on.

So if your HQ is on: 172.16.1.1 and your remote office is on 172.17.1.1 AD will look at the workstations address and then use the DC on its segment if there is one.

Possibly what is happening:
If you do not have your segments setup in AD, it may be that the remote DC has the GUID for that computer and has not released it and will always answer for that workstation.

Look at AD and make sure it is setup correctly for each segment (typos, et cetera)

If the workstation is going back to the remote site, you can repair it and send it back, since it is answering to the correct DC. -WS