Joe,
I don't remember if they told us to check if they are TS users or not to be honest as this was almost 2 years ago. I do remember that he symptoms were quite odd in that the error message dialog box would throw out an obscure error that could not be found in any online resource. They said they had to pull it out of a source code comment reference which lead them down the NWCLIENT trail. I remember writing something to identity the users in the directory that culd be affected by this issue, an someone did remediate them.
Through the years of getting support ( and giving it) I've found it best to ALWAYS question the actions you are being told, because people do make mistakes. I hate the excuse "Well I was told to do this." and they didn't think it through before doing it.
This reminds me of a tech who noticed a certain service was using alot of CPU time on our Domain Controllers. He figured it might be a problem, so he killed the exe that was eating the CPU time because the OPs guy suggested it. I guess he thought this little exe would just restart and be fine because it had an obscure name he did not recognize......LSASS.EXE :)
And then he wondered why authentication problem tickets came in at that site...
J
From: [EMAIL PROTECTED]
To: [email protected]
Subject: RE: [ActiveDir] TScmd help
Date: Fri, 5 May 2006 08:24:47 -0400
Oh sorry, yes, I completely understand that advice came from PSS from your previous post, I should have put the "Thanks PSS" on there too. :)Did PSS actually say to check of they were TS Users? I wouldn't be surprised if they hadn't. A lot of the help and direction doesn't come with much insight unless you get the "right" PSS people. Which ones are the "right" ones... the ones that are good of course, I don't believe MSFT breeds for them or even tests for them, they just sort of happen and then once you find them you don't want to let go.I once received an email from an old coworker still working for the former employeer asking if I heard this from PSS what would I have done... Keep in mind that this employee was in the USA and there was no local support where the server was other than say a janitor and a secretary nor hardware level remote control capability.... "This server you have in <insert name of some small almost third world European nation>, you want to disable NET LOGON and then reboot it and then we can check out the results..." and then 30-60 minutes later a call back from PSS "Hold on, don't do that yet, that may not be a good idea...". Then the coworker responding to PSS, "We already did, what now???"My response was that I would have openly laughed at the PSS guy as soon as he said the first thing and said go get your dad, I need to talk to a grownup. Yes that is insulting but if you are paying for best in class support, you better get it, if not, you insult them until they get you someone who will give you that support. I was once told, but if you insult them, they will remember you and won't want to work with you again. My response to that... If I am at the point that I am going to insult them, I would rather they not work with me again and better they spend their time filtering themselves out from me than spending my time while I filter them out. Plus I have learned that just asking for someone else isn't going to help you as evidenced by a problem I have been working through my current employer with PSS, the problem is approaching the one year point now, I have to be nice though, those are the rules I have to follow. If I didn't have to be nice, I can pretty much guarantee I wouldn't still be waiting for responses. I would have talked to the top person and they would either correct or have said no. Instead, I am treated like any customer who doesn't know better and sitting here not knowing anything about what PSS is doing. I have accomplished great things or at least brought great visibility to things within MSFT by being an extreme pain in the tush and making engineers feel stupid and making them want to "prove me wrong". I dislike very much that I have to do things that way but have been taught, that is how I can get results with them. Ditto for the Exchange Dev folks. The DS Dev folks on the other hand, they are great, you talk to them and they listen. They may not agree with you but they will talk to you and explain why they can't do what you are asking or what is wrong with what you want changed. They have some bad apples of course, but in that case, the barrel is mostly good apples and you aren't trying to pick and choose who you deal with, you can take a random deal and almost always be ok.joe
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jef Kazimer
Sent: Thursday, May 04, 2006 10:28 PM
To: [email protected]
Subject: RE: [ActiveDir] TScmd helpI meant that was the advice we were given from PSS on how to solve the problem. :)
Though...we did end up clearing it after finding out they were not TS users.
From: [EMAIL PROTECTED]
To: [email protected]
Subject: RE: [ActiveDir] TScmd help
Date: Thu, 4 May 2006 21:17:34 -0400
Yes some Novell stuff can be found in there as well as some other things I have heard of through the years. Just clearing that attribute is a great idea... especially if you use Novell stuff as well as TS stuff. :)
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jef Kazimer
Sent: Wednesday, May 03, 2006 10:51 PM
To: [email protected]
Subject: RE: [ActiveDir] TScmd helpMy first travesty with said blos, was when an admin could not reset a users password via the MMC. After some PSS support, it turns out it was the NWCLIENT attributes stored in the userParameters field. As it turns out these users in the NT4 days had the Netware client piece, and when they were migrated with ADMT to 2000, this nugget came with it.
The solution? Just clear the userParameters attribute for all affected users if I remember.
I think there is a KB article on it now.
From: [EMAIL PROTECTED]
To: [email protected]
Subject: RE: [ActiveDir] TScmd help
Date: Wed, 3 May 2006 19:05:10 -0400
Joe? joe? me?The TS Attributes are stored in an amazingly efficient and highly useful format called a blob. Blob as you may or may not know stands for Big Lump of ahhhh, Ok, for now on we will call what the TS attributes are stored in a Blos. So this Blos is kept in the userParameters attribute. It is a form of a name value pair setup but is entirely undocumented by MS and dorking with it is surely going to impact how PSS supports you when you encounter an issue. Instead of hearing the ubiquitous "That is By Design" or "I need you to crash the server and send us a dump" you will hear the almost as ubiquitous "That is unsupported" or "You are Unsupportable in that state". There have been some attempts in the SAMBA space to decode that information and I am not at liberty to say how they are doing on it but keep in mind, they may not have access to all different configs using that attribute because TS attributes are not the only ones that go in there.Yes, Microsoft had the opportunity to fix the issues with that and userAccountControl 6+ years ago with the release of AD and yes they did refuse that opportunity. On the positive side some thought is now going into userAccountControl nowadays with ADAM though it is still quite quite..... quite rough. TS attributes unfortunately, are still dorked. I don't see that they are attempting to clean it up either, maybe they (MSFT) are hoping they (the attributes) will just get sick and tired of being treated like second class citizens and just go away. When people ask me about setting them with admod I tend to say, go away, don't come back until you grow up and become real attributes. You can set it with admod right now, you just need to know the actual binary chunk to send into admod to do it.joe
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jef Kazimer
Sent: Wednesday, May 03, 2006 5:50 PM
To: [email protected]
Subject: RE: [ActiveDir] TScmd helpMike,
Scratch that. It is not the string I was thinking about.
I'm sure Joe will know though :)
From: [EMAIL PROTECTED]
To: [email protected]
Subject: RE: [ActiveDir] TScmd help
Date: Wed, 3 May 2006 16:38:42 -0500
Mike,
Can you use ADfind and ADmod for this?
ADfind -h <DC> -Default -f "(TSpath=Blah)" -dsq | ADMOD tspath::NewPath
Now I don't remember f TS path (I know it's not the attribute name so you will need to look at it) is a string value or if t's contained in that blob value with the other TS settings.
just an Idea
> Subject: [ActiveDir] TScmd help
> Date: Wed, 3 May 2006 15:12:42 -0600
> From: [EMAIL PROTECTED]
> To: [email protected]
>
> I need to try and find users who have a certain TS Profile path and
> change the server name.
>
> It is W2K/W2K3 mixed.
> I have googled and have tscmd, but can tell I will be needing to do some
> voodoo also. Any help is appreciated.
>
> Mike Hutchins
> Sys Admin
> [EMAIL PROTECTED]
> List info : http://www.activedir.org/List.aspx
> List FAQ : http://www.activedir.org/ListFAQ.aspx
> List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
Upgrade for free to Windows Live Mail beta and you could win an African Safari Learn more
Enter the Windows Live Mail beta sweepstakes Upgrade today
Join the next generation of Hotmail and you could win a trip to Africa Upgrade today
Upgrade for free to Windows Live Mail beta and you could win an African Safari Learn more
Join the next generation of Hotmail and you could win a trip to Africa Upgrade today
