Showing posts with label Snow Leopard. Show all posts
Showing posts with label Snow Leopard. Show all posts

Monday, September 5, 2011

How to configure a hidden account that has ARD access and also must request control from the user

I was asked to create a hidden account that had remote control access through ARD but that also had to request permission from the user before being allowed access to the computer

Running the following in ARD/Unix using the root account will create a hidden standard account called "hidden", set the password to "Hidden123", turn on "request permissions to observe/control" and add the account to the Remote Management "allowed users" list:

dscl . -create /Users/hidden
dscl . -create /Users/hidden UserShell /bin/bash
dscl . -create /Users/hidden RealName "hidden"
dscl . -create /Users/hidden UniqueID 499
dscl . -create /Users/hidden PrimaryGroupID 1000
dscl . -create /Users/hidden NFSHomeDirectory /Local/Users/hidden
dscl . -passwd /Users/hidden Hidden123
/System/Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Resources/kickstart -activate -configure -access -on -users hidden -privs -none -clientopts -setreqperm -reqperm yes

A "UniqueID" lower than 500 will create a hidden account.

To remove the account (run as root through ARD):

dscl . -delete /Users/hidden

This works for Leopard and Snow Leopard

Thursday, October 28, 2010

Snow Leopard Error -50 when copying to an SMB share

Symptom

Snow Leopard client copying file to SMB will get a –50 unkown error and the copying will halt. This only happens to Snow Leopard and only to SMB. Copying the same files to AFP works fine. It is also only on certain files. We can take this file to another Snow Leopard machine and reproduce it every time.

Cause

We found out that it has to do with files with resource fork. I think Snow Leopard and Leopard no longer embed resource fork into files anymore. But I am guessing these files were touched or created by older Apple OS. This explains why out of thousands of files, we only see some files with this problem. This is due to the fact that the Snow Leopard Client now defaults to using NTFS Streams rather than AppleDouble files (dot underscore files) to store the resource fork.

Solution

Turn off NTFS Streams support in Snow Leopard. You can do this on the client by running this command.

echo "[default]" | sudo tee -a /etc/nsmb.conf
echo "streams=no" | sudo tee -a /etc/nsmb.conf

Of course this would be a pain if you have to touch every clients. An easier way is to touch the share by creating a file at the root of the share called ".com.apple.smb.streams.off". As this is a hidden file, it is probably best to do this from the command line.

cd /Volumes/sharename/

touch .com.apple.smb.streams.off

No reboot is needed. Client just need to dismount and mount the share again.

Friday, May 28, 2010

Enable Screen Saver Locking From the Command Line: Snow Leopard

The settings are now stored in ~/Library/Preferences/com.apple.screensaver.plist:

$ defaults read com.apple.screensaver
{
    askForPassword = 1;
    askForPasswordDelay = 5;
}
$

To turn on the screen saver lock:

defaults write com.apple.screensaver askForPassword -int 1


To turn off the screen saver lock:

defaults write com.apple.screensaver askForPassword -int 0 

Friday, December 18, 2009

Snow Leopard: Kerberos ticket not renewing coming out of Screen Saver

We had another case opened with Apple about Kerberos ticket not renewing after typing in password coming out of screen saver in Snow Leopard. They send me this instruction on modifying a file in /etc and it looks like it is resolving the problem. If you guys have Snow Leopard machine bound to AD. Please try it out too so we can confirm it does work.

Please edit the "“system.login.screensaver” entry in the /etc/authorization file to read like this:

system.login.screensaver

class
rule
comment
(Use SecurityAgent.) The owner or any administrator can unlock the screensaver.
rule
authenticate-session-owner-or-admin


Note that the string:

The owner or any administrator can unlock the screensaver

is changed to:

(Use SecurityAgent.) The owner or any administrator can unlock the screensaver

Monday, October 19, 2009

Snow Leopard: first impressions


I did these tests using an older 1.83 GHz iMac Core Duo with 1GB of RAM

Binding

Logged in as “administrator” binding from the “Join” button in Accounts failed with an error “unable to add server eServerSendError -14740.”

When binding through Directory Utility I received a notice that the computer account already existed.  I checked the entire directory and the account was not there.

In Terminal I typed “dsconfigad- show” and found that the computer name was different than the name I had specified for the computer.  I searched the AD and found the computer account listed by the “show” command and deleted it.

I also deleted all the PRT records for my subnet and reconfigured DHCP so that our DNS service account owned the DNS records.  This is our new standard DHCP/DNS setup for all subnets.

I attempted to bind again with the [binding service account] and the bind failed with “insufficient privileges.”   Using my domain admin account, I was able to bind the computer.

The edu.mit.kerberos file generated by the binding process was incorrect (lacking realm and server information) so I replaced with a file containing the correct information.

LDAP lookups were handled properly after the bind.

dsconfigad- show displayed the correct computer name.

Restarted the computer and logged in with my AD account.  I was given a warning that my password would expire in 29 days (I had just changed my password) and it prompted me to set up a mobile account.  On subsequent logins I was not given the password expiration warning. 

Restarting the computer was very quick- it only took about 40 seconds.  Directory Services was slow to start: 30-45 seconds after the login window appeared.


File handling and transfers

It has been reported that connecting to an SMB volume produces a beach ball lockup.  I was able to connect to SMB shares (using SSO) but it took about 2 minutes.  AFP connections were virtually instantiations.

3GB transfers to/from a SMB share on a Windows 2003 server across a 100mb network took 3 minutes.

3GB transfers to/from an AFP share on a Mac Mini running 10.5.8 server across a 100mb network took 6 minutes.

If I enabled Secure Empty Trash I was unable to delete the 3GB file.  It would hang about halfway through the process and I was forced to restart the Finder.  Turning off Secure Empty Trash allowed me to empty the trash without a problem.

Deleting an item from an AFP or SMB server volume closed the window.

There is now a “put back” function in Trash just like in XP.


Mac Mail

Auto setup asked twice to trust the certificate from IPG mail server.

There was no need to configure LDAP to do a GAL lookup.

Mail cannot access Public Folders.

There is now an archive mail function.

Meeting invites from Outlook and Entourage functioned perfectly regardless of whether or not they had attachments.

Meeting invites to Outlook and Entourage functioned perfectly.

It took a long time for mail to download and display in the Inbox window.  Both my Blackberry and Entourage received mail much faster.

Notes are now synced properly with Blackberries.

Removing signatures locks up Mail.

There is no way to remove attachments!  You must delete the entire mail.

Calendar

Delegates are limited to Calendar viewing only: you cannot configure shared mailboxes from the Mail client.

Free/Busy status in Calendar worked very well and it is nice that you can search for the next available time your invitees are available.

When viewing another person’s calendar their events are merged into your calendar and displayed as a different colour.  People will either love this or hate it.

Once you’ve started to create a meeting request there is no “Cancel” button.  You have to finish the request and then delete it.

Tasks entered into Mail say they will be put into a Tasks calendar but they are not.

There doesn’t seem to be a way to change the colour of calendar events.

Invites sent from a different time zone display the correct local time in the message header.  The body text shows time for the sender, accepting the invite puts it into Calendar at the correct time.  Entourage still has the problem where meeting invites sent from different time zones display the incorrect time when you double click on the event in your calendar.

There is a handy button that changes the time zone for all events in your calendar.  Changing them back works too!


Address Book seems to be pretty much unchanged.