This error is because you don't have WMIC in your System Path or it's been deleted from your system by someone else or by your enterprise build standard/SOP.
WMIC has been part of Windows for many years and till in Windows 10 and Windows Server 2016.
It was the other script tool many did not even know was there and thus never used it as it was intended. As a former avid WMIC user, WMIC was the predecessor to PowerShell IMHO. If you look at the WMIC docs or the stuff all over the web about it, you'll see that I mean.
WMIC - Take Command-line Control over WMI
Microsoft is creating a lot of good reasons to make the command prompt in Windows XP and the Windows Server 2003 family your home for systems management. Windows Management Instrumentation Command-line (WMIC), which uses the power of Windows Management Instrumentation (WMI) to enable systems management from the command line, is one of those reasons.
WMI has been an important part of Microsoft's systems management initiative since Microsoft Systems Management Server (SMS) 2.0 and has grown in popularity since the introduction of Windows 2000. However, until the introduction of WMIC, you couldn't easily access the WMI repository or the WMI namespace from a command prompt.
https://msdn.microsoft.com/en-us/library/bb742610.aspx
wmic vs WMI Powershell cmdlets
The WMI command-line (WMIC) utility provides a command-line interface for WMI. With Windows 7 you can do everything that you can do with wmic using Windows Powershell and much more by leveraging powerful features of Windows Powershell.
https://blogs.msdn.microsoft.com/wmi/2010/01/06/wmic-vs-wmi-powershell-cmdlets
Full disclosure, I have no idea what apache kafka is, thus no experience with using PoSH with it. Yet, that error is something I have seen more than once in customer environments.