Skip to main content

Hi everyone...

Long time lurker, first time poster. I am running Casper 8.1 Suite, in a 72 Snowleopard Mac environment, in which I have a policy running to Update Inventory and Software Update Server is running once a day after 15 mins of activity.....and I'm starting notice that when people connect to the servers (Apple K or browsing for the server) the saved keychain of their server login and password isn't populating automatically, and instead the full computer username is instead. Which of course, the clients ignore and put their passwords in, and panic when they cannot get onto the server.

So I tell them to just type in their username (which is also the shortname on the machine) and then it saves it for the rest of the day in their keychain again. I tried to look up if the Update Inventory policy replaces a preference file or resets a system file somewhere by default, because it's the only system level change I have done in the last few weeks....but I just cant find any documentation on what the actual process of Reconning (or Updating the Inventory, which aren't they the same) is, and how it might affect server logon preferences.

Anyways you can see why I don't write these things cause I am terrible :) Anyone have any ideas?
--
tamara wiggins
it manager
tel: +1 310 382 1472 fax: +1 310 382 1401

http://www.180la.com
http://www.facebook.com/180la
http://www.twitter.com/180la
1733 ocean avenue . 4th floor . santa monica . ca 90401 tel: +1 310 382 1400 . fax: +1 310 382 1401
before you print think about the environment

This message may be legally privileged and/or confidential and is intended only for the use of casper at list.jamfsoftware.com. 180LA, LLC is neither liable for the proper transmission nor for the complete transmission of theinformation contained in this communication. If the reader of this message is not the intended recipient, you are hereby notified that any unauthorized disclosure, dissemination, distribution, copying or the taking of any action in reliance on the information herein is strictly prohibited. If you have received this communication in error, please immediately notify the sender and delete this message. 180LA, LLC, 1733 Ocean Ave., Suite 400, Santa Monica, CA 90401.

![external image link](attachments/dff46ccd7b994396a6b4e1513038b53a)
![external image link](attachments/870428cee4fd4522a3467c76b041e3a7)
![external image link](attachments/4c5acf3c87f2424cada6887b57bb670e)
![external image link](attachments/ace8ab3811c248f094e445c0feb8e4a3)

So I tell them to just type in their username (which is also the shortname on the machine) and then it saves it for the rest of the day in their keychain again. I tried to look up if the Update Inventory policy replaces a preference file or resets a system file somewhere by default, because it's the only system level change I have done in the last few weeks....but I just cant find any documentation on what the actual process of Reconning (or Updating the Inventory, which aren't they the same) is, and how it might affect server logon preferences.
On 12/8/11 5:25 PM, "Tamara Wiggins" <Tamara.Wiggins at 180LA.com<mailto:Tamara.Wiggins at 180LA.com>> wrote:

If I'm understanding you correctly I don't believe subsequent logins are necessarily working because something is getting stored in the keychain. If you connect to a server and have an active connection then any attempts to connect to other volumes or shares on the server are immediately processed without having to authenticate again. The computer name shouldn't be populating the user name field but rather the user account's display name (long name) is getting entered.

This may or may not be of use to you but in our environment, which is using AD, a user's display name is automatically populated any time he tries to authenticate to a server. This display name doesn't work with some of our Windows servers but the short name always works with any server. I have a Managed Preference (MCX) that forces the authentication window to populate the user short name instead of the display name. This saves my users from having to manually enter their short name and prevents those panic calls when they can't connect to the server with the display name.

This is one of the few managed preferences I apply to all Macs I manage. Not sure that I still need both preferences to accomplish this but I use them both for now:

Display name: All - Finder use short name
Description: This along with the "Finder use short name" setting will set the preference for the Finder to use either the display name or the user short name.
Apply Setting To: User Level Enforced
Domain: ~/Library/Preferences/com.apple.NetworkAuthorization
Key: UseShortName
Key Type: boolean
Value: True

Display name: All - Finder use default name
Description: This along with the "Finder use short name" setting will set the preference for the Finder to use either the display name or the user short name.
Apply Setting To: User Level Enforced
Domain: ~/Library/Preferences/com.apple.NetworkAuthorization
Key: UseDefaultName
Key Type: boolean
Value: True

--

William Smith
Technical Analyst
Merrill Communications LLC
(651) 632-1492

Terms & ConditionsCookie settingsAccessibility statement