Mac OS X Writing to NTFS

DustinB3403

@Mike-Davis are you running the script from the server were the files reside, or a remote system?

Mike Davis

Owner of the file is the domain\administrators group and I can't take ownership.

I'm running the script on a remote system. This is the server where if I log in locally, it locks up. Once I have the bulk of the users files over and cut the shares over, I can probably reboot to safe mode and see if I have any more options there.

scottalanmiller

Does it lock up if you use PowerShell?

DustinB3403

Any reason you can't mount this drive into another working system to copy the files off?

DustinB3403

Doing a remote robocopy, while not "disallowed" isn't really the best approach in my experience.

I've always run robocopy from the source, not from the target (or on a intermediary server)

Mike Davis

@DustinB3403 said in MAC OS X writing to NTFS:

Any reason you can't mount this drive into another working system to copy the files off?

The old server is physical, so I would have to pull the RAID array...

Mike Davis

@DustinB3403 said in MAC OS X writing to NTFS:

Doing a remote robocopy, while not "disallowed" isn't really the best approach in my experience.

I've always run robocopy from the source, not from the target (or on a intermediary server)

When I log in locally (or with remote desktop) the server locks up.

DustinB3403

@Mike-Davis said in MAC OS X writing to NTFS:

@DustinB3403 said in MAC OS X writing to NTFS:

Any reason you can't mount this drive into another working system to copy the files off?

The old server is physical, so I would have to pull the RAID array...

OK.. yep that sucks.

DustinB3403

@Mike-Davis said in MAC OS X writing to NTFS:

@DustinB3403 said in MAC OS X writing to NTFS:

Doing a remote robocopy, while not "disallowed" isn't really the best approach in my experience.

I've always run robocopy from the source, not from the target (or on a intermediary server)

When I log in locally (or with remote desktop) the server locks up.

Any chance that the robocopy job is just too intensive? Have you tried any other solutions like powershell?

scottalanmiller

@Mike-Davis said in MAC OS X writing to NTFS:

@DustinB3403 said in MAC OS X writing to NTFS:

Doing a remote robocopy, while not "disallowed" isn't really the best approach in my experience.

I've always run robocopy from the source, not from the target (or on a intermediary server)

When I log in locally (or with remote desktop) the server locks up.

That's not exactly a direct answer. When you log in remotely from PowerShell?

Mike Davis

@scottalanmiller said in MAC OS X writing to NTFS:

@Mike-Davis said in MAC OS X writing to NTFS:

@DustinB3403 said in MAC OS X writing to NTFS:

Doing a remote robocopy, while not "disallowed" isn't really the best approach in my experience.

I've always run robocopy from the source, not from the target (or on a intermediary server)

When I log in locally (or with remote desktop) the server locks up.

That's not exactly a direct answer. When you log in remotely from PowerShell?

using the copy-item powershell command returns

Copy-Item : Access to the path '\\server1\public\Sales-Ads-Marketing2014\History2-17-14\duntonwriting\DuntonWriting
.png' is denied.
At line:1 char:10
+ Copy-Item <<<<  \\server1\public\Sales-Ads-Marketing2014\History2-17-14\duntonwriting\DuntonWriting.png c:
    + CategoryInfo          : PermissionDenied: (\\server1\publ...ntonWriting.png:FileInfo) [Copy-Item], Unauthorized
   AccessException
    + FullyQualifiedErrorId : CopyFileInfoItemUnauthorizedAccessError,Microsoft.PowerShell.Commands.CopyItemCommand

Was there another powershell command I should try?

scottalanmiller

So Copy-Item fails from perms, can you change perms over PowerShell to get control of the file?

Mike Davis

@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.

scottalanmiller

@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.

scottalanmiller

@Mike-Davis said in MAC OS X writing to NTFS:

no randsomware.

Is that related to handsomeware?

scottalanmiller

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?

Mike Davis

@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.

scottalanmiller

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.

dafyre

@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.

scottalanmiller

@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.

Unsolved Mac OS X Writing to NTFS