Thank you for still trying

I followed your instructions implicitly. There was no difference in my file
fxsocm.inf and the one you sent me. So I used the fxsocm_modified.inf you
sent for that contingency. Tried add/remove again and got the same copy
error. So I rebooted and tried add/remove again-again the same copy error.
So I put my original file fxsocm.inf back in the i386 folder as if nothing
had happened.

These were your instructions attendant with the zip attachment:

I'm attaching a zip file here called faxocm.zip. This zip file contains two
inf files: (a) fxsocm.inf & (b) fxsocm_modified.inf

The first thing you need to do is compare your fxsocm.inf with (a) above and
see if there are any differences, especially in the security line. If there
is any difference, you can replace your fxsocm.inf with this file and try
setting up fax.

If there is no difference, you can then use the (b) file. All they've done
there is remove the security section for the [Faxsvc.Service]. You can
rename fxsocm_modified.inf file to fxsocm.inf and copy this over your
existing fxsocm.inf and then try to setup the fax service. This will not set
the ACE specifically on the fax service object (instead it picks the Windows
default) and hence installation will most likely go through.

In the above operations, you need to ensure that "Windows Resource
Protection" is not replacing back the fxsocm.inf file with the file from the
original Windows XP CD during the installation.

I want to emphasize that this is still trying a work-around and the root
problem still exists. I expect the you to face the same setup problem with
some other services too - because most service will try "setting up ACE" for
the service object. This problem most likely lies outside fax.

Last point I want to mention is that if using fxsocm_modified.inf file
solves the problem, this is not opening any big security holes.

Russ Valentine


.

Relevant Pages

  • Re: sassar
    ... authoritative in all matters concerning Microsoft Security Alerts! ... downloaded from the microsoft.com download center or Windows Update. ... Instructions for patching and cleaning vulnerable Windows 2000 and Windows ... installation of the patch as well as removal of the worm. ...
    (microsoft.public.security.virus)
  • Sasser patching & removal instructions
    ... authoritative in all matters concerning Microsoft Security Alerts! ... downloaded from the microsoft.com download center or Windows Update. ... Instructions for patching and cleaning vulnerable Windows 2000 and Windows ... installation of the patch as well as removal of the worm. ...
    (microsoft.public.windowsxp.general)
  • Re: New IE flaw and exploit sites/migration to non-MS browser
    ... installation for workstations that has been floating around ever since ... Microsoft on their network security team at the time and followed much ... Windows 9x had no concept of admin/user. ... their computers aren't working when the power is off. ...
    (Focus-Microsoft)
  • Re: Windows Update Error on XP 64bit: update is redirected from v6
    ... Antivir *usually* does not interfere with the installation of core system updating components. ... Microsoft Windows 2000 Operating System Group Policy Result tool ... The user is a member of the following security groups: ... Open the AULOGS subfolder located in the root drive [the drive where WINDOWS is installed to, usually C:\] Extract the contents of the data.cab as you would a .zip file. ...
    (microsoft.public.windowsupdate)
  • Questions Regarding Workable SOHO Windows Installation / Configuration, Diagnostics, & Security
    ... Questions Regarding Workable SOHO Windows Installation / ... Configuration, Diagnostics, & Security Options ver. ... even an additional 5 to 8: additional antivirus and scanning software. ...
    (comp.security.misc)