Re: XPe SP2 with Domain Participation losing after 30 days

Tech-Archive recommends: Fix windows errors by optimizing your registry

Debbie,
 
I didn't know the EWF Registry filter patch was officially released. The Q871225 doesn't seem to be published on Microsoft support site.
However, I do know that EWF version in SP2 does not have the functionality of the Registry filter.
 
You have a choice:
    - Find out (with Microsoft, I guess) whether the SP2 version of the Registry Filter patch is available. Let us know if it is. Some of us here would probably interested in the patch.
 
    - Go back to SP1 version of EWF. It is possible even with SP2 version of the Configuration. You just don't have to upgrade the EWF components (and make sure that those EWF Hotfixes you mentioned are in database).
 

--
 Regards,
        KM, BSquare Corp.
Hello,
 
I had an issue awhile ago with domain joining with Xpe units.  I use the Ram-Reg EWF.  I spoke to Microsoft on this issue and they gave me a patch that included
 
EWF Registry Filter hotfix -Q871225
Enhanced Write Filter hotfix - Q871226
EWF manager console application hotfix - Q871226
Enhanced Write Filter API hotfix - Q871226
 
The issue was that every thirty-days the domain exchanges a secret password to the thin client and with EWF enabled you lose it when the unit reboots.  The patch also solved the issue with Terminal Server and licenses.  The patch looks for certain keys in the registry and when there is a change saves it.  All worked fine with this patch until I upgraded to service pack 2 and now the issue is back.  I use the SLX file that was previously used and all four components mentioned above are still there but there is a difference.  The enhanced write filter no longer shows a hotfix and neither does the manage console application but they are service pack 2 as I checked them on the description.  However, the patch that was supplied no longer works.  I tried to apply the QFE microsoft sent to me previously and the two components mentioned above do not show the hotfix.  For the time being I am disabling the check on the thin client end to bypass this issue.  Has anyone encountered this yet in SP2 or does anybody know how I can fix it or if there is an extra component that I need to add to get this working. 
 
Thanks,
 
Debbie Giuliano

--
 
---------------------------------------------------------------------
"Eliminate annoying spam!
My mailbox is protected by iHateSpam, the #1-rated spam buster."
 

GIF image

Relevant Pages

  • Re: XPe SP2 with Domain Participation losing after 30 days
    ... Debbie, ... I knew about the new Filter but I didn't know it was officially released. ... I didn't know the EWF Registry filter patch was officially released. ... I do know that EWF version in SP2 does not have the functionality of the Registry filter. ...
    (microsoft.public.windowsxp.embedded)
  • Re: [Full-disclosure] Security Alert: Unofficial IE patches appear on internet
    ... created by a vulnerability is as serious as this case and the available ... Microsoft will be inclined strongly against holding on to this patch. ... Microsoft often have patches ready but wait for the corporate known ...
    (Full-Disclosure)
  • Re: Worm in Patch
    ... a naive and trusting nature in your personality believing that you would ... "receive a patch" instead of getting it from a trusted source..? ... Essentially - Microsoft never emails you a patch. ... using Windows XP "prettifications". ...
    (microsoft.public.windowsxp.security_admin)
  • Re: Why do i keep on receiving shutdown system ?
    ... the Microsoft provided information on the matter can be ... The Symantec Repair utility and manual removal instructions can be found ... The patch that would have prevented this whole fiasco for you: ... If you have Sasser, the Microsoft provided information on the matter can be ...
    (microsoft.public.windowsxp.security_admin)
  • Re: NT Authority..
    ... You could have Blaster or you could have Sasser. ... the Microsoft provided information on the matter can be ... The patch that would have prevented this whole fiasco for you: ... After enabling the Internet Connection Firewall or creating the read-only ...
    (microsoft.public.windowsxp.help_and_support)