Compartilhar via

Did not want to pick up Optional Updates?

  • Artigo

Some customers have indicated they want to know if there were any workarounds for the issues addressed in the October Optional updates available on the ECE site. Rebuilding the image is the most reliable way to get the fix, but some customers do not want that hassle for hundreds of deployed devices if they can just push down some files and reg keys to the runtime using the mechanism they already have for servicing the device.

There are workarounds, but each customer would have to evaluate their runtime to see if all dependencies are satisfied on their deployed runtime to facilitate the workaround.

The two issues that were fixed in the October Optional updates were:

KB942527

This issue addressed the fact that Group Policy Core- Support Files should have a dependency on Group Policy Core in order to ensure that all the registry keys and dependencies required in order to fully support Group Policy functionality are satisfied (parts of Group Policy, such as MMC, works even if Group Policy Core is not on the image, however certain aspects of functionality may not work correctly if the Core is not present). The workaround is to add Group Policy Core and it's dependencies to the runtime.

The challenge is satisfying the dependency chain. If you already have all the dependencies in your runtime then you are good to go and can use your usual servicing mechanism to apply the reg keys for Group Policy Core to your runtime (there are no file resources for this component). However, if you do not have all the dependencies in your runtime then you will also have to evaluate each of the missing ones to see how easy it would be to add those (and their dependencies) to your runtime. Remember that some components may need custom actions like registering DLLs or services to be started, so it may be easier to just apply the componentized hotfix in the long run. As always, do thorough testing to ensure all resources have been applied correctly. The deps are:

  Active Directory Service Interface (ADSI) Core
  Common Control Libraries Version 5 
  Common File Dialogs
  Local Security Authority Subsystem (LSASS)
  Microsoft Visual C++ Run Time
  Primitive: AuthZ
  Primitive: Icmp 
  Primitive: Iphlpapi 
  Primitive: Mpr 
  Primitive: Netapi32 
  Primitive: Ntdll 
  Primitive: Ole32 
  Primitive: Oleaut32
  Primitive: Profmap
  Primitive: Regapi 
  Primitive: Secur32 
  Primitive: Shell32 
  Primitive: Shlwapi
  Primitive: Userenv
  Primitive: Winmm 
  Primitive: Winsta 
  Primitive: Wintrust 
  Primitive: Wldap32
  Primitive: Wsock32 
  RPC Local Support
  Windows API - Advanced 
  Windows API - GDI 
  Windows API - Kernel
  Windows API - User 
  Windows Logon (Standard)
  Workstation Service

KB942525

This issue addressed the fact that some codecs could not be played in WMP 10 without prompting the user. The fix was to add a resource to the WMP10 component to register mp4sdmod.dll. The workaround, if you choose not to use the componentized fix) would be to use regsvr32 on runtime to register mp4sdmod.dll. Naturally this assumes that you have the Primitive: Regsvr32 component already on your runtime (or you can copy the regsvr32.exe file to your runtime).

Be sure to look out for the December Optional Updates to be posted shortly on the ECE site!

- Lynda

Technorati Tags: XPe, Componentization

Comments