Solved

OS X Server: Problem with login script.

Posted on 2009-04-06
6
1,324 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

Better Security Awareness With Threat Intelligence

See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.

Join & Write a Comment

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…
The error "There was an error performing the update" occurred on a Mac OS X client workstation running  Symantec AntiVirus for Mac (http://www.symantec.com/business/products/purchasing.jsp?pcid=pcat_security&pvid=825_1) - the Enterprise product vers…
Internet Business Fax to Email Made Easy - With eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, fr…
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

708 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

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now