Can't set Terminal Services profile path for some users

[Raymond Diack]

Hi there

I need to configure a terminal services profile path for all our users. I'm
using a script, together with the TSPROF utility to do this. However, when
trying to set the profile path for SOME of our users, we get this error:-

Failed setting User Configuration, Error = 87 (0x57)

When we try and do it manually in Active Directory Users and Computers for
the same users TSPROF is failing on, we get:-

"Operation failed. The parameter is incorrect."

It must be a property of certain users that's causing this, but i can't see
anything different between users that may be causing this...?!!

Any ideas?

Thanks
Raymond

[Paul Bergson]

Are there any errors in the event log on either the DC they are authorized
from, the data store which will hold the profile or the workstation from
which this is running.

You could try running filemon from sysinternals (Freeware) and see if you
get any errors when attempting to do this.

http://www.sysinternals.com/SystemInformationUtilities.html

--
Paul Bergson
MCT, MCSE, MCSA, Security+, BS CSi
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Raymond Diack" <ray....@gmail.com.nospam> wrote in message
news:BFECB827-3785-4D4C...@microsoft.com...

[Raymond Diack]

Hi Paul

I'm actually running this on one of the DC's. I checked the event log for
errors - and couldn't see anything relevant. The DC's are otherwise
"healthy". The share holding the profiles is a Windows 2000 cluster node,
and is already storing the normal desktop profiles for our 500 users.

I noticed today that if we try and configure ANY property on the Terminal
Services tab of the properties of the User object in AD Users and Computers
it gives that "parameter is incorrect error". But it's only for about 20% of
our users. So it's not related to the actual path I'm entering, or
permissions to the profiles share etc.

Thanks
Ray

[Joe Richards [MVP]]

It is purely a guess but I expect something else wrote to that attribute
and "corrupted" it for the TS Admin interfaces. Unfortunately the TS
info was an addon and ended up getting slammed into the userParameters
attribute. That is unfortunate because you can't read the attribute
nicely to see what is in there but also because other apps may be using it.

My recommendation would be to clear the userParameters attribute of a
user you have an issue with and then see if it starts working. I expect
it will.

You can clear the attribute like this

admod -b DN_OF_OBJECT userparameters:-

Note that whatever you wrote to that as well as any current TS settings
will be wiped for that user.

joe

--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net

---O'Reilly Active Directory Third Edition now available---

http://www.joeware.net/win/ad3e.htm

[Raymond Diack]

Joe, you rock! Thanks very much - worked like a charm! Is that
userParameters attribute used for anything else apart from the TS properties?

Thanks!
Ray

[Paul Williams [MVP]]

It's a binary blob for all TS properties. In 2k you couldn't do anything
with it. In k3, there's a new ADSI interface that you can use to manipulate
it - IADsTsUserEx:
--
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/termserv/termserv/iadstsuserex.asp

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net

[Raymond Diack]

Thanks so much for your posts guys, they've been really helpful!

Regards
Raymond

[Joe Richards [MVP]]

It is or at least was used for some Novell properties. There are also
some other third party tools that mucked with it as well.