Moving NT userprofile to another server - deleted user files come back

[Norwich]

Hi,

I'm running a network of Windows 2000 workstations on an NT server based network. I'm about to migrate user profiles from one server on the domain - PDC - to another - a BDC.

The process I used for some test accounts were as follows.

Example account:

j.blo
profile path: \\mypdc\users\j.blo\profile
home directory: P: \\mypdc\users\j.blo

Note: ownership of these profiles were already with administrator (and access was full access for admin and user) - this was to allow backups to work correctly

works fine.

Now, I transferred profile as follows:

moved directory \\mypdc\users\j.blo to \\mybdc1\users\j.blo
as permissions were changed, I took ownership as administator, added full access rights to the admin account and the specific user account.

changed profile to:

j.blo
profile path: \\mybdc1\users\j.blo\profile
home directory: P: \\mybdc1\users\j.blo

When the user now logs in, the home directory and profiles all load up OK. Files edited that are covered in the profile (My Documents etc) are saved properly and reloaded at log off / logon.

However, if a file or folder is deleted from anywhere within the profile - say, My Documents\test.doc - and it was previously saved onto the server, it will return on the user logging in again. I've tested and it is the file not being removed from \\mybdc1. Also, if a file is renamed, both the previous and new versions will exist.

Any thoughts on what I did wrong with the setup?

Thanks.

 

[wolluf]

check the access rights again - sounds like user doesn't have rights to delete (are there any shares/rights involved here?)

 

[Norwich]

Hi,

The user concerned has full control rights.

Confirmed that they can go to the profile location directly over the network and delete the concerned files. Also, the propogation rights are set up correctly too.

 

[Norwich]

I've since discovered that any accounts created from scratch against this server as the profile host will behave in the sme way - so it's something to do with the settings. But it all looks OK...?

(Users have full control rights, propogating down to all sub directories and files).

Any ideas to try more than welcome.

 

[Norwich]

Found out what it was - the server was misconfigured in a different timezone. Though the clock reported the same time, files from the workstations were timestamped incorrectly and so not allowed to be overwritten.