Delete trash folder on a remote host

Question

Hi community,
in a German forum a user is reporting an issue with odd behaviors between a Lion and a Snow Leopard client in a network. She said that if she deletes the trash folder in the Lion client, the trash folder in the Snow Leopard client become deleted too. Is there a feature in Lion that could cause this behavior? By the way, she noticed this issue as a side cross effect, primary she is searching for some mail issues. If she deletes a mail in one Client, the mail disappears in the other client also. I guess that this is a server setting problem but maybe this is associated with the trash folder issue. Any ideas?
Thx & Bye Tom

Answer 1

You're on the right track.  You can use Invoke-Command with the same credentials (or PSSession from New-PSSession, if you prefer) to execute code remotely.  The tricky thing, unfortunately, will be the credentials.  Right now you're being
prompted to enter a username and password, but in an unattended script, you'd need to have these credentials saved somehow.  That can open up a can of worms, depending on your requirements.
The simplest way to do this is to hard-code the password in your script.  No one on the planet recomments actually doing this, because well, you've just exposed an admin password to the world.
The safest way to do this is to log on as the same account that will be used to run the script, on the same computer where the script will be run, and enter the credentials once manually, and export them to an XML file.  With this approach, the credentials
in the XML file will be encrypted with the Windows Data Protection API (DPAPI), and the keys necessary to decrypt that data are only available to the current user, on the current computer.
If you need to be able to securely save the data and have it read by other users, or on other computers, things start to get more complicated.
Here's an example of the DPAPI approach:
# to create the credential file
$cred = Get-Credential
$cred | Export-Clixml -Path c:\myEncryptedCreds.xml
# to use it later (on the same computer, by the same user)
$cred = Import-Clixml -Path c:\myEncryptedCreds.xml
Invoke-Command -ComputerName SomeComputer -Credential $cred -ScriptBlock {
Do-Something