Skip to content

Script failing due to previous instances still running #6

@woodyinwoodley

Description

@woodyinwoodley

I don't have eyes on our AD Connect server, not my role, but since we set up the SyncNewAutoPilotComputersandUsersToAAD.ps1 scheduled task (every 5 mins) a couple of weeks ago, it stopped working after a few days, and now we have to wait up to 30 mins for the device syncs to happen. I'm told this is because there are multiple instances running at once, causing errors.
Thoughts:
(1) the script should log what it's doing to aid troubleshooting.
(2) the script should handle the scenario that another instance is already running.
(3) ideally, the script should create the scheduled task itself, with recommended settings for triggers etc.

Thanks for the tools, this is a fantastic idea for making Hybrid Join more viable. Really appreciate you making it available. Unfortunately without some change it doesn't really feel robust enough to use in Production. I'm going to have a go at fixing it up, but I thought this feedback might be useful. You seem to have better Powershell skills than I, so if you do have time you'd probably come up with a better solution thank I'm going to do.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions