The Dial-in tab does not appear when you use Active Directory Users and Computer

Microsoft states in their article: 837490

The Dial-in tab does not appear when you use Active Directory Users and Computers to view the properties for a domain user on a Windows XP-based computer
View products that this article applies to.
Article ID : 837490
Last Review : February 25, 2006
Revision : 10.0
SYMPTOMS
When you use Active Directory Users and Computers to view the properties for a domain user, the Dial-in tab does not appear. This issue occurs on your Microsoft Windows XP-based computer that has the Microsoft Windows Server 2003 Administration Tools installed. However, when you use a Terminal Services session to view the user properties on a Microsoft Windows Server 2003-based computer, the Dial-in tab appears.
RESOLUTION
To resolve this issue, install the Adminpak.msi file that was released with Windows Server 2003 Service Pack 1 (SP1). For more information on installing Adminpak.msi, visit the following Microsoft Web site:
http://technet2.microsoft.com/windowsserver/en/library/4dacb61b-7ddc-49b... (http://technet2.microsoft.com/windowsserver/en/library/4dacb61b-7ddc-49b...)
Important Before you install this file, you must uninstall the Adminpak.msi file that is currently installed.
WORKAROUND
To work around this issue, open a Terminal Services session to connect to the domain controller, and then modify the user properties. To do this, follow these steps:
1. Click Start, point to All Programs, point to Accessories, point to Communications, and then click Remote Desktop Connection.
2. In the Computer box, type the name of the domain controller, and then click Connect.
3. Type your credentials, and then click OK.
4. On the remote computer, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
5. In the left pane, expand the domain where the user account that you want to view is located, and then click Users.
6. In the right pane, right-click the user account, and then click Properties.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2.
REFERENCES
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 (http://support.microsoft.com/kb/824684/) Description of the standard terminology that is used to describe Microsoft software updates
APPLIES TO
� Microsoft Windows XP Professional
� Microsoft Windows XP Professional
Back to the top Back to the top
Keywords:
kbbug kbfix kbqfe kbserver kbactivedirectory kbprb kbhotfixserver KB837490



Primary links

Custom Search

Who's new

  • japhabept
  • Rullydery
  • eagenorce
  • rittaarier
  • swasseZex

Who's online

There are currently 0 users and 3 guests online.

KrissysCorner.com RuthSwensonLaw.com CreativeLizardProductions.com

DISCLAIMER:

None of this has anything to do with us, someone else is responsible for the entire thing, and we have no idea who or why. We do not know anything about it. It may be alien life forms for all we know: we haven't a clue. You cannot blame us for anything that may result from your visit. That was entirely your own personal choice, made by you of your own volition, and without our knowledge. We do not, after all, have any control over you and cannot by any stretch of the imagination be expected to accept or acknowledge, be it legally or morally, any accountability for decisions made by you on an independent basis, utilizing your own free will, and without our intervention. We are therefore in no way, shape, or form answerable to anyone for any consequences arising from the aforementioned or indeed any other actions, similar or otherwise, because it was not us that did, or did not do anything. It is not even remotely our fault, and we are in no way prepared or willing to accept any liability, not even slightly, ever. We are, in fact completely and utterly blameless, in that it is definitely not our concern, and no blame can possibly be laid at our doorstep, even if we had one, the possession of which we hereby reserve as being entirely our own free choice. The onus is not on us at all, and furthermore, never has been. The entire matter is wholly beyond our control, and completely out of our hands, each of which are washed scrupulously clean of the whole business. We are not accountable for anything at all, and we hereby categorically deny all responsibility for all that has ever, or will ever happen. Our innocence is therefore wholly beyond doubt and absolutely unimpeachable, and so cannot, under even the remotest or unlikeliest circumstances, be brought into question. By clicking either on a link on this site, clicking on a link that leads to this site, or by arriving at this site by natural or supernatural means, you are in effect accepting responsibility for the fact that it is all entirely your own fault, down to the most miniscule detail, and that you are wholly accountable for whatever outcome may arise as a consequence of the aforementioned action or actions insofar as they were undertaken personally by you on an entirely voluntary basis and without any persuasion, coercion or influence from any party or parties other than yourself. Don't come sniveling to us, we are only figments of your imagination. I also agree that if I am ever with a contributor to this website during mealtimes I agree to pay for any super-sizing of their meal, or at least a nice dessert or one of those foo-foo drinks with an umbrella or a monkey. By admitting to have seen the worthless spineless drivel on this website (also known as content)

I Agree Wholeheartedly and Without Reservation to the above. (Except maybe for that part about the monkey.)

All Your Base Are Belong To Us.

Soylent Green Is People!

Never make a bet with a Sicilian when Death is on the Line!

No. Really, I do agree.