This is correct. The UNIX/Linux runas account is a Windows domain account. It can be used to login to Windows and UNIX/Linux.
From: [email protected] [mailto:[email protected]] On Behalf Of Jeremy D .Pavleck Sent: Friday, April 03, 2015 5:05 PM To: [email protected] Subject: RE: [msmom] RE: SCOM 2012 R2 U4 Unix agent question Do your Unix accounts use a unified LDAP model? As in do you login to the Unix servers with a domain account that would work on the Windows servers too? Sent on a Sprint Samsung Galaxy S(r) 5 -------- Original message -------- From: Kevin Holman <[email protected]<mailto:[email protected]>> Date:04/03/2015 2:58 PM (GMT-05:00) To: [email protected]<mailto:[email protected]> Cc: Subject: [msmom] RE: SCOM 2012 R2 U4 Unix agent question A unix/linux runas account is not a Windows account, it is a credential that is LOCAL to each and every linux server.... so in what directory is this account even capable of getting locked out? From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Williams, Marlon Sent: Friday, April 3, 2015 12:53 PM To: [email protected]<mailto:[email protected]> Subject: [msmom] SCOM 2012 R2 U4 Unix agent question I recently applied the U4 update to our SCOM 2012 R2 environment and for some reason our UNIX agents are having issues after the upgrade. The UNIX agent was upgraded to v1.5.1 -138 and the UNIX RunAs service account keeps locking every hour causing the servers to go grey in the console. The servers eventually come back after the acct unlocks. We have roughly 500 UNIX/Linux servers in our environment. I've tried the following: - Checked the Windows event viewer/SCOM logs of all the UNIX Management servers for events to see which UNIX server may be causing the issue - Rechecked the UNIX RunAs account in the SCOM Console to make sure the PW was entered properly Has anyone experienced this issue in the past? Any ideas on resolving this issue? Thank you, MW
