Minimize their interruptions, and focus on learning at first. I mean really studying, like they are in school, in college, in the library. Give them stuff to read and then simply test their comprehension assuming you already know the details of the documentation they are reading. They shouldn't be typing or talking at all in their first two weeks except perhaps to ask questions having to do with soliciting some clarification on anything vague in the learning materials.
If you have a larger organization, perhaps those first 2 weeks should be pure class time with mesmerizing PowerPoint slides, and the next 2 weeks should be pure reading.
The minute that you make them responsible for "getting things done", junior devs will go off and over-specialize in whatever you threw in front of them at first that was actually something that they could accomplish, and that whole task set will end up getting away from you. It is important for junior devs to be fully assimilated into your overall culture and understand the values and direction of your organization.
6 months is insane. It shouldn't be that long, but the only reason it is that long is because of the initial pressure to produce anything at all. I know that's why.
Managers whether technical or not will just keep throwing junior devs at the wall until they stick to tasks their given. Bad move. Instead, know that it is your responsibility to get them ramped up. If you don't have time to do that, or cannot assign someone to give them some individual attention as they get ramped up you might be hiring too fast.
Try just easing off on the gas at first, and keep it in low gear and go really slow at the beginning. The pistons will thank you once they all start firing.