Have a look at the logs in:
on one of the stubborn machines and see where the task fails. Could be a clue there.
Next, run the first upgrade step manually by copying the 9.3.633 package to one of the endpoints and see what happens. Chances are it'll fail, rollback, and tell you the reason.
If not try the next package in the upgrade chain till you find the problem.
Select one of the systems stuck on 9.3 in the system tree then actions>agent> show client events --- do you see any indication of the task attempting to run? Knowing whether or not the task is being sent to those still on the legacy version will tell you a lot right away.
FYI - the upgrade path you are taking is not necessary. Without looking, I can't say definitively that the 9.3.4 to 9.3.633 is unnecessary but you can certainly go straight to DLPe 10 from 9.3.633.
1 of 1 people found this helpful
Well I viewed the logs and all that that jazz, unfortunately there were no clues and no success stories. We wound up just reimaging the problem children. Thanks guys!
Sometimes that is the most time efficient way!