Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

PeopleTools and Lifecycle Management - PSFT (MOSC)

Locking Out Users During Update. Best Practices

Sep 28, 2015 2:26PM edited Oct 8, 2015 12:29PM in PeopleTools and Lifecycle Management - PSFT (MOSC) 5 commentsAnswered ✓

Greetings All,

We are going to soon be applying HRMS Bundles in our Production environment.

We are currently on PeopleSoft 9.1

and PeopleTools 8.53

We want to lock all of our user's from Production during the update, excluding a handful of implementers and testers.

Does anyone have any best practices / suggestions as to how to go about doing a mass Lock Out?

Currently we're considering the following:

Locking accounts on the Database side using the PSOPRDEFN table: Our main concern is only unlocking the correct accounts when finished.
PeopleSoft's 'Lock Users' page: We haven't used this before and wanted to see if other have, and with what type of results

Tagged:

3

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month