KB901214 would noy install

I try to install this update through WSUS and get the Following error:


Event Type: Error
Event Source: Windows Update Agent
Event Category: Installation
Event ID: 20
Date: 8/15/2005
Time: 7:26:30 AM
User: N/A
Computer: XXXXXXXX
Description:
Installation Failure: Windows failed to install the following update
with error 0x8007f004: Security Update for Windows 2000 (KB901214).


I try downloading the update from microsoft and do a local install and I
get an error stating that I am not an administrator, eventhough I am
logged in as an administrator.

I think that I might have a permission problem and I wanted to see if
anyone knows what user account WSUS uses to install the updates on the
clients??

I have a server running Win2k SP4 and all my clients are Win2k.
any help would be greatly appreciated.

yvqkck wrote:

> I try to install this update through WSUS and get the Following error:
>
>
> Event Type: Error
> Event Source: Windows Update Agent
> Event Category: Installation
> Event ID: 20
> Date: 8/15/2005
> Time: 7:26:30 AM
> User: N/A
> Computer: XXXXXXXX
> Description:
> Installation Failure: Windows failed to install the following update
> with error 0x8007f004: Security Update for Windows 2000 (KB901214).
>
>
> I try downloading the update from microsoft and do a local install and I
> get an error stating that I am not an administrator, eventhough I am
> logged in as an administrator.
>
> I think that I might have a permission problem and I wanted to see if
> anyone knows what user account WSUS uses to install the updates on the
> clients??
>
> I have a server running Win2k SP4 and all my clients are Win2k.
> any help would be greatly appreciated.
Hi,

A)
Do you have "Client for Microsoft Networks" installed/enabled for your
network connection? If not, install it, reboot, and see if it helps.

B)
Please see if this helps:

1. Start Explorer.
2. In Explorer, right click on "My Computer"
3. Select "Manage"
4. Expand Local Users and Groups.
5. Select Users.
6. Open the account used to access Windows Update.
7. Click the Member Of tab.
8. If you find anything else than the "Administrators" group there,
remove those other entries. You need to have only the
"Administrators" group listed there.
9. If you did any changes to the Member of list, log off and on again,
and try Windows Update again.


If the above did not work, could you please post back all membership
entries for each of the local groups?



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Torgeir Bakken (MVP) wrote:
> yvqkck wrote:
>
>> I try to install this update through WSUS and get the Following error:
>>
>>
>> Event Type: Error
>> Event Source: Windows Update Agent
>> Event Category: Installation
>> Event ID: 20
>> Date: 8/15/2005
>> Time: 7:26:30 AM
>> User: N/A
>> Computer: XXXXXXXX
>> Description:
>> Installation Failure: Windows failed to install the following update
>> with error 0x8007f004: Security Update for Windows 2000 (KB901214).
>>
>>
>> I try downloading the update from microsoft and do a local install and
>> I get an error stating that I am not an administrator, eventhough I am
>> logged in as an administrator.
>>
>> I think that I might have a permission problem and I wanted to see if
>> anyone knows what user account WSUS uses to install the updates on the
>> clients??
>>
>> I have a server running Win2k SP4 and all my clients are Win2k.
>> any help would be greatly appreciated.
>
> Hi,
>
> A)
> Do you have "Client for Microsoft Networks" installed/enabled for your
> network connection? If not, install it, reboot, and see if it helps.
>
> B)
> Please see if this helps:
>
> 1. Start Explorer.
> 2. In Explorer, right click on "My Computer"
> 3. Select "Manage"
> 4. Expand Local Users and Groups.
> 5. Select Users.
> 6. Open the account used to access Windows Update.
> 7. Click the Member Of tab.
> 8. If you find anything else than the "Administrators" group there,
> remove those other entries. You need to have only the
> "Administrators" group listed there.
> 9. If you did any changes to the Member of list, log off and on again,
> and try Windows Update again.
>
>
> If the above did not work, could you please post back all membership
> entries for each of the local groups?
>
>
>
A) I have "Client for Microsoft Networks" installed and enable

B) I looked at the local users and I have an administrator and a ASPnet
account listed, no other accounts there.

What I would like to know is what account does WSUS uses for installing
the updates on the clients.

yvqkck wrote:

> A) I have "Client for Microsoft Networks" installed and enable
>
> B) I looked at the local users and I have an administrator and a ASPnet
> account listed, no other accounts there.

On a client where the update fail with the "you are not an
administrator", could you please post back *all* entries you
find in the following local groups:

1)
Administrators

2)
Backup Operators

3)
Guests

4)
Power Users

4)
Replicator

6)
Users



>
> What I would like to know is what account does WSUS uses for installing
> the updates on the clients.

The SYSTEM account I think.


--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Torgeir Bakken (MVP) wrote:

> yvqkck wrote:
>
>> A) I have "Client for Microsoft Networks" installed and enable
>>
>> B) I looked at the local users and I have an administrator and a
>> ASPnet account listed, no other accounts there.
>
>
> On a client where the update fail with the "you are not an
> administrator", could you please post back *all* entries you
> find in the following local groups:
>
> 1)
> Administrators
>
> 2)
> Backup Operators
>
> 3)
> Guests
>
> 4)
> Power Users
>
> 4)
> Replicator
>
> 6)
> Users
>
Hi,

Before doing the above, there is one thing I like you to try
first.

This issue could maybe be caused by a missing SensLogn registry
key/values.


Please put the part between the two
--------------------8<----------------------
lines below into a file that you give a .reg file extension.

NB:
The [HKEY_LOCAL_MACHINE\SOFTWARE\......\Notify\SensLogn] part needs
to be on *one* line, will wrap over to lines in this post.

If you have Windows 2000, and not Windows XP, please remove
the following 3 lines (at the bottom of the listing):

"Disconnect"="SensDisconnectEvent"
"PostShell"="SensPostShellEvent"
"Reconnect"="SensReconnectEvent"


Import the registry file by double clicking on it in Explorer,
and then reboot the computer.


When importing the registry file, you should then get this dialog box:

---------------------------
Registry Editor
---------------------------
Are you sure you want to add the information in Some.reg to the registry?
---------------------------
Yes No
---------------------------


Press the Yes button, and you should get this dialog box:

---------------------------
Registry Editor
---------------------------
Information in Some.reg has been successfully entered into the registry.
---------------------------
OK
---------------------------



Here is the content of the registry file:

--------------------8<----------------------
REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\
Winlogon\Notify\SensLogn]

"Asynchronous"=dword:00000001
"DLLName"="WlNotify.dll"
"Impersonate"=dword:00000001
"Lock"="SensLockEvent"
"Logoff"="SensLogoffEvent"
"Logon"="SensLogonEvent"
"MaxWait"=dword:00000258
"Safe"=dword:00000001
"Shutdown"="SensShutdownEvent"
"StartScreenSaver"="SensStartScreenSaverEvent"
"StartShell"="SensStartShellEvent"
"Startup"="SensStartupEvent"
"StopScreenSaver"="SensStopScreenSaverEvent"
"Unlock"="SensUnlockEvent"
"Disconnect"="SensDisconnectEvent"
"PostShell"="SensPostShellEvent"
"Reconnect"="SensReconnectEvent"


--------------------8<----------------------
(be sure to have a blank line at the end of the registry file)




--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx

Torgeir Bakken (MVP) wrote:
> Torgeir Bakken (MVP) wrote:
>
>> yvqkck wrote:
>>
>>> A) I have "Client for Microsoft Networks" installed and enable
>>>
>>> B) I looked at the local users and I have an administrator and a
>>> ASPnet account listed, no other accounts there.
>>
>>
>>
>> On a client where the update fail with the "you are not an
>> administrator", could you please post back *all* entries you
>> find in the following local groups:
>>
>> 1)
>> Administrators
>>
>> 2)
>> Backup Operators
>>
>> 3)
>> Guests
>>
>> 4)
>> Power Users
>>
>> 4)
>> Replicator
>>
>> 6)
>> Users
>>
> Hi,
>
> Before doing the above, there is one thing I like you to try
> first.
>
> This issue could maybe be caused by a missing SensLogn registry
> key/values.
>
>
> Please put the part between the two
> --------------------8<----------------------
> lines below into a file that you give a .reg file extension.
>
> NB:
> The [HKEY_LOCAL_MACHINE\SOFTWARE\......\Notify\SensLogn] part needs
> to be on *one* line, will wrap over to lines in this post.
>
> If you have Windows 2000, and not Windows XP, please remove
> the following 3 lines (at the bottom of the listing):
>
> "Disconnect"="SensDisconnectEvent"
> "PostShell"="SensPostShellEvent"
> "Reconnect"="SensReconnectEvent"
>
>
> Import the registry file by double clicking on it in Explorer,
> and then reboot the computer.
>
>
> When importing the registry file, you should then get this dialog box:
>
> ---------------------------
> Registry Editor
> ---------------------------
> Are you sure you want to add the information in Some.reg to the registry?
> ---------------------------
> Yes No
> ---------------------------
>
>
> Press the Yes button, and you should get this dialog box:
>
> ---------------------------
> Registry Editor
> ---------------------------
> Information in Some.reg has been successfully entered into the registry.
> ---------------------------
> OK
> ---------------------------
>
>
>
> Here is the content of the registry file:
>
> --------------------8<----------------------
> REGEDIT4
>
> [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\
> Winlogon\Notify\SensLogn]
>
> "Asynchronous"=dword:00000001
> "DLLName"="WlNotify.dll"
> "Impersonate"=dword:00000001
> "Lock"="SensLockEvent"
> "Logoff"="SensLogoffEvent"
> "Logon"="SensLogonEvent"
> "MaxWait"=dword:00000258
> "Safe"=dword:00000001
> "Shutdown"="SensShutdownEvent"
> "StartScreenSaver"="SensStartScreenSaverEvent"
> "StartShell"="SensStartShellEvent"
> "Startup"="SensStartupEvent"
> "StopScreenSaver"="SensStopScreenSaverEvent"
> "Unlock"="SensUnlockEvent"
> "Disconnect"="SensDisconnectEvent"
> "PostShell"="SensPostShellEvent"
> "Reconnect"="SensReconnectEvent"
>
>
> --------------------8<----------------------
> (be sure to have a blank line at the end of the registry file)
>
>
>
>

Still no luck, I followed your instructions, imported the regestry key
and still won't install.

While I was thinkering around with this issue, I noticed that if I log
in as my backup user, which is an user that I created to run Veritas, I
can install this patch with no problems. This is what is leading me to
believe that is got to be an user account issue. I tried giving system
the same priveliges as my backup user and still get the same answer.

yvqkck wrote:

> Still no luck, I followed your instructions, imported the regestry key
> and still won't install.
>
> While I was thinkering around with this issue, I noticed that if I log
> in as my backup user, which is an user that I created to run Veritas, I
> can install this patch with no problems. This is what is leading me to
> believe that is got to be an user account issue. I tried giving system
> the same priveliges as my backup user and still get the same answer.
Hi,

On a client where the update fail with the "you are not an
administrator", could you please post back *all* entries you
find in the following local groups:

1)
Administrators

2)
Backup Operators

3)
Guests

4)
Power Users

4)
Replicator

6)
Users



--
torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway
Administration scripting examples and an ONLINE version of
the 1328 page Scripting Guide:
http://www.microsoft.com/technet/scr...r/default.mspx