Rotate Local Workstation Passwords Crate
What does the Rotate Local Workstation Passwords Crate do?
This Crate provisions a dedicated local administrator account on each workstation and rotates that account’s password on a weekly schedule by default.
How the Crate works
The Crate's workflow retrieves the workstation list from your RMM.
It then uses PowerShell to manage the local administrator account by:
Creating the configured admin account on each workstation with the account name defined in the trigger.
Rotating the password on a weekly schedule, defaulting to every Friday but modifiable in the trigger
Each generated password in your configured documentation tool is then documented.
On the first run, a Flexible Asset in IT Glue or Asset Layout Type in Hudu is automatically created. The type name is Local Administrator Password Rotation.
For each workstation, an asset is created or updated based on MAC address, to include workstation name, MAC address, and corresponding password.
Workflow breakdown
The workflow begins with the START task using the noop action, which validates that both documentation and RMM integrations are properly configured by checking for required organization variables and determines the documentation platform to use.
The rmm_list_workstations task using the [REWST - OPT GEN] RMM: List Workstations action retrieves a list of all workstations from the configured RMM system for the organization.
The check_variables task using the noop action validates that workstations were successfully retrieved and that an admin username is available, routing to failure if either condition is not met.
The rotate_passwords task using the [REWST - TASK] Run Powershell via RMM action executes a PowerShell script on each workstation through the RMM to rotate the local administrator password, running with concurrency of 5 devices at a time.
The check_for_changed_passwords task using the noop action evaluates the results from the password rotation task to determine if any passwords were successfully changed.
The get_documentation_asset task using the [REWST - CRATE] Rotate Local Password: Upsert Asset action retrieves or creates the appropriate documentation asset structure in either IT Glue or Hudu based on the configured documentation platform.
The update_documentation task using the [REWST - PROC] Rotate Local Password: Update Documentation action updates the documentation platform with the new password information for each device that had its password successfully rotated, running with concurrency of 5 devices at a time.
Any failures throughout the process are handled by the failure_catch task using the noop action, which sets the success flag to false and routes to the end of the workflow.
Crate prerequisites
Your RMM must be successfully integrated with Rewst.
IT Glue or Hudu integration must successfully be set up with Rewst.
Unpack the Rotate Local Workstation Passwords Crate
Navigate to Crates > Crate Marketplace in the left side menu Rewst platform.
Search for
Rotate Local Workstation Passwords.
Click on the Crate tile to begin unpacking.
Click Unpack Crate.
Click Continue.
Ensure that Enabled is toggled on for Cron Job under Configure Triggers. Note that you have the option under the accordion menu of the trigger to activate the Crate for all future organizations in addition to the current one. You may also set the trigger criteria or integration overrides.
Click Unpack.
Use the Crate
To test this Crate, you'll need to adjust the cron trigger's schedule to a few minutes in the future, then adjust it back to your regular schedule after the test. Alternatively, you could wait until the regularly scheduled run occurs and check your result, which would not require you to update the cron trigger schedule. To edit a cron trigger in the workflow to either test it once or change the time it will routinely run:
Navigate to Automations > Workflows in the left side menu of your Rewst platform.
Search for
[REWST - CRATE] Rotate Local Workstation Passwords.Click on the workflow to view it in the Workflow Builder.
Click
to open the Edit Trigger menu.The default Cron Schedule under Trigger Parameters is currently set to Friday at 3:20 PM UTC. This may be kept as is or if desired, be modified. To modify, update the timing of the cron trigger in the fields under Trigger Parameters. Note that when entering the time into the Cron Schedule field, the correct format is minutes followed by hour. For example, 18 3, not 3 18.
Click Submit.
Click Save.
You'll see a green message at the top of your screen indicating the trigger is saved.
Check your documentation tool to ensure that the asset is created.
Last updated
Was this helpful?

