Possessing a pawn on a second client while using a dedicated server prevents the pawn from moving until net.shareshadowstate is set to false.
This appears to be a regression. I was not able to reproduce the behavior in 4.13.2
Result: This pawn is unable to move. Setting net.shareshadowstate to false allows the pawn to move.
Expected: The pawn would be able to move as the first client is.
Head over to the existing AnswerHub thread and let us know what's up.