Okay, try this: Pretend you're a DB Analyst, a Project Lead, or a Network Engineer, etc., for your company and ask yourself:
"What does knowing the company's current strategic direction mean for me in terms of how I should be doing my job differently than I currently am or was under the company's prior strategic direction?"
Then identify, for each job, some specific ways of doing things that, while "right" under the old strategy, are now "wrong" under this new strategy. And vice versa -- some specific ways of doing things that, while "wrong" before and now "right."
If it's hard for you to do this, knowing the company's strategic direction as intimately as you do, it's likely impossible for those actually in the positions mentioned.
If it's easy for you to do this, it's likely still impossible for them! Why? Because it is.
So share these specific differences you identified with those actually in the positions mentioned to help jump-start their own thinking...and doing.
For example, if their job is to write code, tell them specifically how they should, and now can, write the code differently based on this new strategy. If their job is to answer calls at the service desk, tell them specifically how they should, and now are allowed to, handle complaints differently based on this new strategy. If their job is get something else done, tell them specifically how they should, and now have the authority to, do it differently based on this new strategy. Specifically how.
See what I mean?
You see the problem is likely far less about their "buy in" and far more about them just not understanding what this new strategic direction means in terms of the things they do and the choices they make on a daily, if not hourly, basis. They don't know how to connect the dots in any other way than they currently do.
If you'd like, I'd be happy to talk with you about this in more depth.