Unsolved Mac OS X Writing to NTFS
-
So Copy-Item fails from perms, can you change perms over PowerShell to get control of the file?
-
@scottalanmiller said in MAC OS X writing to NTFS:
So Copy-Item fails from perms, can you change perms over PowerShell to get control of the file?
Not sure how to do that. Everyone already has full control and I already have ownership, and you can't give ownership. Normally the command would be get-acl, add you permissions to the ones in the array, then set-acl. You can't add yours to the list when they are already there.
-
@Mike-Davis said in MAC OS X writing to NTFS:
@scottalanmiller said in MAC OS X writing to NTFS:
So Copy-Item fails from perms, can you change perms over PowerShell to get control of the file?
Not sure how to do that. Everyone already has full control and I already have ownership, and you can't give ownership. Normally the command would be get-acl, add you permissions to the ones in the array, then set-acl. You can't add yours to the list when they are already there.
Those are NTFS ACLs. Are you sure that you have permission to read/copy in SMB? Because you are accessing through the SMB filesystem here, not talking to NTFS directly. So check those perms as well.
-
-
So how is a Mac involved here? It seems like you are trying to do a Windows to Windows copy, no Mac in the process?
-
@scottalanmiller said in Mac OS X Writing to NTFS:
So how is a Mac involved here? It seems like you are trying to do a Windows to Windows copy, no Mac in the process?
Correct. It seems that a Mac unzipped the files to the windows server. There was a bug at the time that set the file type bit to something that makes windows think it's encrypted. (thus windows shows it as green and the encrypted check box is checked)
All I'm trying to do now is copy the files from a server that is having issues to a new server.
-
I think that the Mac and the encryption are red herrings. How a file originated or that it is encrypted should not have an effect on a copy operation. I think the issue is with permissions somewhere and those factors are just causing confusion.
-
@Mike-Davis said in Mac OS X Writing to NTFS:
@scottalanmiller said in Mac OS X Writing to NTFS:
So how is a Mac involved here? It seems like you are trying to do a Windows to Windows copy, no Mac in the process?
Correct. It seems that a Mac unzipped the files to the windows server. There was a bug at the time that set the file type bit to something that makes windows think it's encrypted. (thus windows shows it as green and the encrypted check box is checked)
All I'm trying to do now is copy the files from a server that is having issues to a new server.
Where are you running the copy operation from? The new server or the server with issues?
I'd suggest trying to run the copy FROM the server with issues.
-
@dafyre said in Mac OS X Writing to NTFS:
@Mike-Davis said in Mac OS X Writing to NTFS:
@scottalanmiller said in Mac OS X Writing to NTFS:
So how is a Mac involved here? It seems like you are trying to do a Windows to Windows copy, no Mac in the process?
Correct. It seems that a Mac unzipped the files to the windows server. There was a bug at the time that set the file type bit to something that makes windows think it's encrypted. (thus windows shows it as green and the encrypted check box is checked)
All I'm trying to do now is copy the files from a server that is having issues to a new server.
Where are you running the copy operation from? The new server or the server with issues?
I'd suggest trying to run the copy FROM the server with issues.
He can't, logging in causes the system to crash.
