Dave and I spoke yesterday. There is still something fishy but Dave's explanation somewhat made sense.
We all know *why* ReyRey is performing this bullshit: to stifle competition.
I am a dealer. I utilize the scheduler as well for internal reporting. I am not ReyRey's competition. If one of my accounts get locked I will be on the phone with my Reynolds "Advocate" before the server even closes my port.
@Jarky: No word from ReyRey regarding this change, but also no problems with any of our ERA accounts being locked.
My guess is as long as you are using all PC file output options you should be okay. I have a feeling they are somehow targeting people trying to reproduce "on screen" style output.
Jarky,
That's disturbing... Based on what I heard from Reynolds and other folks last week, I was advising the dealers who I consult for, that their process of running 7601, 7602 via the scheduler was a legit way to go, and that they didn't have to worry about their userids being locked. Seems this is not true...
I agree it is disturbing. Obviously no one outside of Reynolds knows exactly what or how they are doing it. I hope your dealers have different experiences. Just wanted to share this case as it seems the Reynolds' logic is not without issue.
Obviously no one outside of Reynolds knows exactly what or how they are doing it.
From the feedback I got from my dealers it seems to be a lot of misinformation going around, including the RR people.

Reynolds and Reynolds has implemented an automated security process that disables user IDs suspected of third-party vendor access, with locked accounts showing an "AUTOMATED ACCESS ATTEMPTS" message and no admin unlock capability in the standard interface. Dealers and IT professionals report frustration over the policy's impact on legitimate internal automation (like ERA Access scheduler scripts) and Reynolds' apparent reluctance to unlock accounts unless vendors obtain RCI certification, with some suspecting the measure is designed to stifle competition rather than genuine security threats. A Reynolds representative (Dave Bates) eventually engaged with an affected user, suggesting the policy has legitimate justification, though community skepticism remained.