Active Directory W2K Servers and WinXP w/ SP2

J

James

Just noticed this and was wondering if anyone else has
experienced this. We are testing SP2 on a couple on
machines, mine being one of them. I have rights to our AD
and work w/ our G.P.s I noticed now when ever I open a
policy on our win2k servers (only affects the policies I
have previously opened on my XP machine), that we receive
approx 140 error messages complaining that "The following
entry in the [strings] section is too long and has been
truncated. If you enable any policies for the security
page, it is strongly recommended that you also configure
policy to disable the security page from being presented
in the UI to prevent users from believing that they can
change their security settings" and etc.

I've created a test policy from our server and was able
to open it up with no error messages. I then opened the
policy from my desktop and made no changes, and went back
to the server and opened the policy. The error messages
began appearing as soon as I opened the policy.

Any help would be greatly appreciated.
 
J

James

Thanks for the quick reply. Just to be certain, this
update is ok to apply to win2k server? I see that it's
listed as product affected, but I only see download for
win2k. Is that download also for win2k server?
-----Original Message-----
This is the first hit in google for your error message

http://support.microsoft.com/default.aspx?kbid=842933



--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net


Just noticed this and was wondering if anyone else has
experienced this. We are testing SP2 on a couple on
machines, mine being one of them. I have rights to our AD
and work w/ our G.P.s I noticed now when ever I open a
policy on our win2k servers (only affects the policies I
have previously opened on my XP machine), that we receive
approx 140 error messages complaining that "The following
entry in the [strings] section is too long and has been
truncated. If you enable any policies for the security
page, it is strongly recommended that you also configure
policy to disable the security page from being presented
in the UI to prevent users from believing that they can
change their security settings" and etc.

I've created a test policy from our server and was able
to open it up with no error messages. I then opened the
policy from my desktop and made no changes, and went back
to the server and opened the policy. The error messages
began appearing as soon as I opened the policy.

Any help would be greatly appreciated.
.
 
J

Joe Richards [MVP]

I haven't looked that closely at it, all I did was search google for your issue
description and that is what popped up.

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net


Thanks for the quick reply. Just to be certain, this
update is ok to apply to win2k server? I see that it's
listed as product affected, but I only see download for
win2k. Is that download also for win2k server?
-----Original Message-----
This is the first hit in google for your error message

http://support.microsoft.com/default.aspx?kbid=842933



--
Joe Richards Microsoft MVP Windows Server Directory
Services

www.joeware.net


Just noticed this and was wondering if anyone else has
experienced this. We are testing SP2 on a couple on
machines, mine being one of them. I have rights to our
AD
and work w/ our G.P.s I noticed now when ever I open a
policy on our win2k servers (only affects the policies
I
have previously opened on my XP machine), that we
receive
approx 140 error messages complaining that "The
following
entry in the [strings] section is too long and has
been
truncated. If you enable any policies for the security
page, it is strongly recommended that you also
configure
policy to disable the security page from being
presented
in the UI to prevent users from believing that they
can
change their security settings" and etc.

I've created a test policy from our server and was
able
to open it up with no error messages. I then opened
the
policy from my desktop and made no changes, and went
back
to the server and opened the policy. The error
messages
began appearing as soon as I opened the policy.

Any help would be greatly appreciated.

.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top