Seb1780 Posted August 14, 2018 Posted August 14, 2018 (edited) Background - I'm a Data Manager, not a Network Manager so I ask in all ignorance! For $reasons we have created a new domain. When this was done we tided up AD and only current users were set up on the new domain. On the old domain I had two identities (for $other_reasons), now I only have one. We have now started to migrate all our file storage from the old domain to the new one and I have found that I cannot access any of my Office files on the new domain. So far we have established that on the old domain all the author metadata in Office files were recorded as USERNAME1, the now defunct AD account. On the new domain these files are showing as having no author metadata and cannot be opened by anyone, not even our sys admin account. We can, however, copy files one by one from the old domain backup and save them to the new domain and they are fine. Can anyone suggest a) what might have gone wrong, b) how do we stop this happening when we transfer all the other data across and c) is there a way of bulk updating metadata on the new domain to save having to do thing one file at a time? Thanks Edited August 14, 2018 by Seb1780
Steve21 Posted August 14, 2018 Posted August 14, 2018 (edited) The author won't affect any security permissions in regards to who can open it. It'll be the share/file permissions that's on said folder/share/mapped drives etc. When you're manually copying said files over one by one you're saving them as your new user so you inherit permissions on them automatically. Best way to check it would be using "effective access" right click on a file and go the properties -> security -> advanced -> effective access -> add in username etc -> view effective access and see what it returns Example below: Steve Edited August 14, 2018 by Steve21 1
Seb1780 Posted August 14, 2018 Author Posted August 14, 2018 It's all sorted now - nothing to do with permissions / AD accounts etc The files on the old domain were compressed and the copy across copied them in the compressed format, the applications could not read them in that format. Once the approriate switch was set on the new domain the files decompress on the fly and now all is good.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now