Odd warning in System Event log after installing vWorkspace 7.1 on Terminal Server

Hello Caleb,

Can you let me know what Operating System this message is from, is it Windows 2003 or 2008 R1?

The file Win32k.sys helps to provide vWorkspace multi-monitor support, you will find that with an unsupported file version this will not work correctly.

Please log a support case that specifies the information from the event log entry and I will follow up with you to provide the required fix.

Regards

David

Hi David,

Sorry for the late reply...

It's from Windows 2003 Enterprise SP2 32bit

Here's something I found though... http://support.microsoft.com/kb/981957

Looks to be a part of MS10-073 released back in October.

Hi Caleb,

Thanks for the reply, can you log a support case that specifies the information from the event log entry and I will follow up with you to provide the required fix.

Regards

David

Just to update, I've logged the ticket...

I removed the MS10-073 update and I get a similar error:

Event Type:    Warning
Event Source:    pnterm
Event Category:    None
Event ID:    1
Date:        02/12/2010
Time:        11:26:22
User:        N/A
Computer:    OXNETVWSTS01
Description:
Provision Networks Termianl Services started!
    rdpdd.dll (version 5.2.3790.3959) is supported.
      File Signature: 5.2.3790.3959.73DA542A56FA4817B9E168E711D8CFB71
    win32k.sys (version 5.2.3790.4033) is not supported.
      File Signature: 5.2.3790.4033.F4367C90E67F401D945BEF66CC6040C12

Funny enough in our lab setup we have version 5.2.3790.4769 of win32k.sys and I don't have any problems!

Hi Caleb,

We hook rdpdd.dll and win32k.sys for graphics accelaration and multi-monitor support. Each version of these Dlls has a different entry point so needs a version specific registry entry under HKLM\Software\Provision Networks\Terminal Server.

If a new version of rdpdd.dll or win32k.sys is released by Microsoft in a hotfix, the vWorkspace settings have to be updated accordingly. I've just checked the latest versions and that particular version (5.2.3790.4033) isn't in the list which does include 5.2.3790.4769. Either patch your server up to the latest hotfix version or zip up, encrypt and send your copy of win32k.sys to support (log support call first ), and they should be able to provide you with an updated reg file to get rid of that error.

regards,

Rick

Ooops

wink32.sys file attached

---------------

Deleted message

Hi Caleb,

I'm not quite the right person to send this, Quest Support would have been better/easier, but I'll try and see it gets to the right place. No promises but I'l try.

It's kind of an in-between version of win32k.sys that didn't get submitted to the developers for analysis.

regards,

Rick

Hi Caleb,

I have the updated file from support overnight. I will contact you shortly to apply this and look at your other issue

Regards

David

Hi David,

Sorry to chase but do you have that fix?

Cheers

Thanks David for getting in touch!

Quest do have really good support!