Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

update agent not work if XP_sp2_RUSSIAN !!!!

2 views
Skip to first unread message

Serg

unread,
Oct 19, 2006, 7:52:58 AM10/19/06
to
NW4.91Sp2+
491psp2_pkc.exe
491psp2_nwfs_4.exe
491psp2_login_4.exe
on the XP_SP2_RUSSIAN

UPDATE AGENT not work (if user logged as XP_USER) !!!

If XP_SP2_ENGLISH with this client and user logged as XP_USER - UPDATE AGENT
work Fine ! ! !

Any Suggestion , please..

Serg


Alan Adams

unread,
Oct 19, 2006, 1:57:35 PM10/19/06
to
"Serg" <skoltogyan...@mail.ru> wrote:

> UPDATE AGENT not work (if user logged as XP_USER) !!!
>
> If XP_SP2_ENGLISH with this client and user logged as XP_USER - UPDATE AGENT
> work Fine ! ! !

It looks like one reason that the Update Agent would not work for
Windows account that is just a "Users" group member is that on
non-English versions of Windows, the "Users" group does not have the
permissions necessary in order to start or stop the Update Agent
service.

This can be verified by logging in as an "Administrators" group member
and using SC.EXE to display the Windows security currently assigned to
the "CUSRVC" service.

(Note that SC.EXE is included with Windows XP and was part of various
resource tool kits; it can be copied from Windows XP to Windows 2000
and used successfully.)

For example, on a XP Professional SP2 Russian machine I tested here,
the security reported for the CUSRVC service was as follows:

> c:\>sc sdshow cusrvc
>
> D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

On an English machine, the security for CUSRVC includes permissions
for "WD", which is the security descriptor definition language (SDDL)
representation of the group "Everyone":

> c:\>sc sdshow cusrvc
>
> D:(A;;RPWP;;;WD)(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

So it appears as though the installation of the Novell Client is
failing to correctly add security permissions for "Everyone" on the
CUSRVC service on one or more non-English platforms. (Such as, if the
English string "Everyone" was being used, and this fails on any
platform where the translated group name is not literally "Everyone".)

You could work around this, if this is the issue you're encountering,
by manually adding the "Everyone" group to have permissions to start
and stop the CUSRVC service.

Meaning if this is what you see when running SC.EXE SDSHOW CUSRVC:

> c:\>sc sdshow cusrvc
>
> D:(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

you would add "(A;;RPWP;;;WD)" after the "D:" at the front of whatever
SDDL string was reported. Then run SC SDSET for CUSRVC along with the
complete, updated SDDL string to set same security on CUSRVC except
with the "Everyone" group added. Taking the above example, it would
look similar to the following:

> c:\>sc sdset cusrvc D:(A;;RPWP;;;WD)(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BA)(A;;CCLCSWLOCRRC;;;AU)(A;;CCLCSWRPWPDTLOCRRC;;;PU)

Note of course your newsreader is probably going to have wrapped this
line, but its all one long command line starting with "sc".

Alan Adams
alancru...@drcrumb.com
(for email, remove the crumbs)

Serg

unread,
Oct 20, 2006, 3:54:54 AM10/20/06
to
Greate !!
Your are COOL ! ! !
Yhank your for STEP BY STEP ! ! !

May be your know - this problem NW cleitn or XP ?

Serg


Alan Adams

unread,
Oct 20, 2006, 6:28:23 AM10/20/06
to
"Serg" <skoltogyan...@mail.ru> wrote:

> May be your know - this problem NW cleitn or XP ?

This would be an issue of the Novell Client, since it is responsible
for installing the CUSRVC service. The Windows default for any
service installation does not grant "Users" the ability to start or
stop the service.

So if the Novell Client requires that regular "Users" accounts be able
to start this service, the Novell Client would have to explicitly add
that security during or after the CUSRVC installation.

Serg

unread,
Oct 20, 2006, 8:26:42 AM10/20/06
to

"Alan Adams" <alancru...@drcrumb.com> ???????/???????? ? ????????
?????????: news:2s8hj2dqcsuf8798d...@4ax.com...

How forward this info to the Novell ?

Serg


Alan Adams

unread,
Oct 20, 2006, 9:19:20 AM10/20/06
to
"Serg" <skoltogyan...@mail.ru> wrote:

> How forward this info to the Novell ?

This issue has been reported to the folks managing the 4.91 SP3 beta.

For any issue where you need specific and timely follow-up on the
status and fix for the problem, opening a support incident with Novell
is the best way to report that kind of issue.

For issues you're working around and just need to inform Novell of,
you may be able to just ask one of the sysops monitoring these
newsgroups to ask or report information to Novell.

The primary avenue by which anyone can report information to Novell
directly at any time is using either the enhancement request or bug
reporting forms:

Report a Software Defect (bug)
http://support.novell.com/additional/bugreport.html

Enhancement Request
http://support.novell.com/enhancement/

0 new messages