Describe the Problem: Renaming local Administrator account lead to Disk Management snap-in error like "No mapping can be be done between current username and SID". Relogon with new name give correct result. What did you expect to happen: Disk management snap-in must not use username - it must use real user info/rights regardless on username... This possibly (???) can lead to invalid privilege use if Account operator will rename Admin/non-Admin account and will try to use Disk Management. Steps to Reproduce the problem: 1. Logon as Administrator on clean PC. 2. Start -> Programs -> Administrative Tools -> Computer management -> Disk management. (works fine) 3. Local User -> Administrator : Rename "Administrator" to "XXXX" 4. Try again Disk Management (please close opened MMC first, because it will use old connection) FAULT: Lame error "No mapping can be be done between current username and SID" printed 5. Create new account with name "Administrator". 6. Try again Disk Management (please close opened MMC first, because it will use old connection) FAULT: Lame error "You do not have access rights to Logical Disk Manager on <COMPUTER NAME>" printed 7. Logoff/Login with new XXXX name 8. Disk management now works just fine Platform affected: W2K SP0, SP1 (and other "build on NT tech" up to 2296). Vendor status: NT Test team was informed and was able to repro (mail dated Thu, 9 Sep 1999 22:13:33 -0700) since W2K Beta [Bug id: 8PW0] TOD)O: Find needed combination of usernames/account right to exploit this NOTE: This information disclosed are no longer covered by NDA (MLAB) due to maximum non disclose time limit reached. Credit t(o: ============================= Andrew G. Tereschenko Software Engineer Integrated Banking Information Systems vulnat_private
This archive was generated by hypermail 2b30 : Tue Apr 17 2001 - 02:44:29 PDT