General ETW questions with the debugger

I’m using WinDbg version 6.2.0013.1 on Windows Server 2003 connected to a
target machine also running Windows Server 2003. Regardless of whether I
specify searchpath and guidfile parameters, I get the following error when
attempting a strdump operation.

0: kd> !wmitrace.strdump
(WmiTracing)StrDump Generic
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** ***
*************************************************************************
*************************************************************************
*** ***
*** ***
*** Your debugger is not using the correct symbols ***
*** ***
*** In order for this command to work properly, your symbol path ***
*** must point to .pdb files that have full type information. ***
*** ***
*** Certain .pdb files (such as the public OS symbols) do not ***
*** contain the required information. Contact the group that ***
*** provided you with these symbols if you need this command to ***
*** work. ***
*** ***
*** ***
*************************************************************************
LoggerContext Array @ 0x00B80003 [0 Elements]

What gives? I’ve searched Google and nothing there has helped me.

Second question: I’ve heard there is a way to get ETW messages at boot
time. Can someone please provide a link or information about this.

Last question: My customers still have alot of W2K setups. I’ve
successfully compiled the driver with ETW under W2K and would like to use
WmiTrace to troubleshoot issues on that platform. Any updates on whether
Microsoft has provided W2K support for this extension?

Thanks,
Bob