-
Notifications
You must be signed in to change notification settings - Fork 20
Works erratically (or is it me?) #61
Comments
Hmm. Odd. Does the standard users password expire? Anything in the logs? (System.log look for ADPassMon).
|
I've repeated the test again: logged on as a domain user (whose password does not expire), installed ADPassMon from scratch, verified it was working (shown in the menu bar), logged off, logged on as a domain user account (whose password does expire - 180 days) and verified ADPassMon was running (resource monitor) but now showing in the menu bar. Apr 13 08:45:47 sp-pescara.local ADPassMon[373]: Running on OS 10.9.x As you can see, there is an error, which I cannot make heads or tails about, and it seemed to have occurred upon the second logon, i.e. when I logged on as the standard user. |
By applying the suggestion in thread #59 (removing the dot from the expire date field) I've been able to make AdPassMon appear on the menu bar of the users. |
Can you folks run the below & advise what is returned?
|
Can you test the below? |
@macmule |
& the output is from the expiring account right? Sat, 10 Dec 2016 20:02:57 GMT is the epoch time converted to human readable. Can you post the ~/lLogs/ADPassMon.log from the account with the minus days? |
The output is from the account with an expiring password, yes. Thu Nov 3 13:40:11 CET 2016 Launching..... Not much there, it seems. Thanks |
Thanks. I'm just trying to figure out how to recreate the issue to fix it. Can you also post the org.pmbuko.adpassmon.plist? Should be in the users library. Regards, Ben.
|
accTest 0 expireAge 180 expireDateUnix 1,4724892 isBehaviour2Enabled 0 menu_title 137d pwdSetDate 16862.7 selectedBehaviour 1 tooltip Your password expires lunedì 29 agosto 2016 18:48:02 |
As text? Regards, Ben.
|
thanks @MaxFrames.. sorry hadn't had AM coffee.
That also gives a date of "GMT: Sat, 20 Jun 1970 10:14:52 GMT" However, that last date seems to sat 29th of August? |
It is 29th of August. That was the date when this user's password last expired. Indeed I can confirm that I last changed it on August 30th. Passwords in our domain expire every 6 months, so the current expiration date is february 26, 2017 for this account. As for the comma, I understand it shouldn't be there? Maybe it's because of regional settings? I am using the Italian version of OSX with Italian regional settings. In Italian, the comma is used as a decimal separator (so for example 1.47 becomes 1,47). |
Yep.. i've been looking at decimal marks & making it non-regionalised as AppleScript is faux-americas english, so expects no comma.. but cannot replicate yet.. i'll keep trying though! @MaxFrames can you run:
and:
Then post the results from both? |
The first command gives "No such key: msDS-UserPasswordExpiryTimeComputed" |
ok.. cool.. to the last commands result gives an Epoch of: 1472538880, which gives a date of: GMT: Tue, 30 Aug 2016 06:34:40 GMT. That's only 66 days ago, not the 137 you're seeing.. but still negative days. For the last command, you should get the result twice. Are you only getting it once?
|
@MaxFrames can you also post the output of Removing the domain info at the top
|
Yes I am only getting the output once, not twice. Active Directory Forest = mydomain.local Advanced Options - User Experience Advanced Options - Mappings Advanced Options - Administrative |
Ah! Network account. (Create mobile account at login = Disabled). Ok, gives me something else to test. |
Yep, we are not using roaming profiles. |
Cool. Something more to test, it changes the dscl calls a wee bit. I'll get back to you. On Fri, Nov 4, 2016 at 12:01 PM, MaxFrames notifications@github.com wrote:
Regards, Ben |
Can you download & run the attached, then paste the output?
The above output is from a Mac which is bound, network & non-roaming account, & os etc is in italian. |
oh.. you're on 10.12? |
The output of the py file run in a terminal: |
It sort of works! A big step forward and a small step back. |
@MaxFrames Cool. I spent ages on the expiration calls.. not the non-expiring! Can you post the log ~/Library/Logs/ADPassMon.log from the account that doesn't expire? Also, the output of |
Log: Output of command: |
Perfect! (well not, but from an issue tracking pov it is). I'll have a look at this & hopefully will have a new build out over the weekend. |
It seems to work; I see correct indications for the account with the non expiring password ("--") and for the account with the expiring password (103d). |
I wonder if I can make here a feature request. I would like to be able to change preferences globally (for all users). Specifically, I would like the password change method to default to "use adpassmon" for all users, because I want to make sure the keychain password is automatically kept in sync (a major cause of headaches); if I'm not mistaken, the only way to apply this setting to the main user of this machine is to log on with his account (I don't have the password, and I wouldn't anyway w/o permission). |
Thanks for the update @MaxFrames. :) For the settings, i'd deploy a profile to all the Macs running ADPassMon. ADPassMon would pick them up on it'a 1st launch after the profile has been installed. |
I'm trying to use the application on a domain-joined iMac running OSX 10.9.5.
Logged on as a domain user (which is also an admin on the iMac) I've downloaded the latest version, put it in the Applications directory and launched it from there. It went through a first run configuration, and it installed itself in the menu bar as supposed to.
At this point I've logged off and logged on as a different user, also a domain user but without administration rights on the machine. The application did not show in the menu bar. The task monitor showed that the process was running. I tried to kill the process and start the app, but again there was no sign of it being active at all besides it being listed in the active tasks. I've tried to promote the user to admin, uninstall the app and install it again; I've tried to delete the plist preferences and reboot, the problem was not solved.
What is the correct procedure to install the app and configure it to run automatically for all the users?
The text was updated successfully, but these errors were encountered: