Solved

OS X Server: Problem with login script.

Posted on 2009-04-06
6
1,337 Views
Last Modified: 2013-11-11
I recently deployed a Mac Os X server and am having quite a bit of trouble with user login scripts.  I've seen quite a bit of information on other users with similar issues (the scripts not running), but all are quite dated.

The issue I'm running into, is that the script isn't being run... these are the steps I've followed thus far:
Server Side:
1) I've placed my script in the Applications/Scripts folder (this folder ISN'T shared)
2) I've given it a ".hook" extension
3) I've given it the appropriate permissions
Client Side
1) set EnableMCXLoginScripts = true in the com.apple.loginwindow.plist
2) set MCXScriptTrust = FullTrust (for testing) in the com.apple.loginwindow.plist

What else could I be missing?

~Greg
0
Comment
Question by:elbarro
  • 3
6 Comments
 
LVL 6

Accepted Solution

by:
hboris earned 500 total points
ID: 24091596
Why don't you use launchd instead? Much more control, dependencies control etc.

Boris Herman, ACSA
0
 

Author Comment

by:elbarro
ID: 24092380
I'd like to use policy to determine what scripts get run on what clients from within the server.  Is this possible using launchd?

~Greg
0
 
LVL 6

Assisted Solution

by:hboris
hboris earned 500 total points
ID: 24093745
No, launchd is client side only. However, looking again at your question again I am missing a bit. The FullTrust requires that in In Directory Utility, you select Block man-in-the-middle attacks (requires Kerberos) and Digitally sign all packets (requires Kerberos). Wouldn't for testing purposes Anonymous be more appropriate, because with Trust value name Anonymous the client trusts any directory domain server? It is said that if the clients MCXScriptTrust setting is a level of trust equal to or less than the actual trust value, the client trusts the server and runs its login and logout scripts. If the clients MCXScriptTrust setting is a level of trust more than the actual trust value, the client doesnt trust the server and doesnt run its scripts. The default trust value is FullTrust.

Boris Herman, ACSA
0
 
LVL 6

Expert Comment

by:hboris
ID: 24409128
The answer has been provided. The setting MCXScriptTrust must be set to a lower value for the scripts to be run in user's configuration.

Boris Herman, ACSA
0

Featured Post

Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Finder.   The ubiquitous, built-in feature of the Mac OS X platform, that never sleeps, can help get to any destination within your Mac OS X volume, allows you to customize your desktop, files and folders and so much more. As one of the primary…
Connectivity using SMB Symptoms When connecting to Windows Server shares from a Mac you receive an error similar to "Connection failed because the original item could not be found"Authentication persistently fails to a Windows Server from a Mac wi…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …
With Secure Portal Encryption, the recipient is sent a link to their email address directing them to the email laundry delivery page. From there, the recipient will be required to enter a user name and password to enter the page. Once the recipient …

789 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question