Answered by:
Administrator.000 after in-place upgrade

Question
-
I did a in-place upgrade from Windows 2008 Foundation to Windows 2008 Standard to Windows 2012 Standard on a one server environment that is also a DC. After the in-place upgrades completed I now have a corrupted admin profile that shows administrator.000. Since this is a DC I cannot delete the profile from users and groups.
I can log onto the server fine as domain admin and everything appears to be operating as it should. How can I fix this profile? Should I just change the registries profile?
Set is showing
C:\Users\Administrator.000>set
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\Administrator.000\AppData\Roaming
CLIENTNAME=Servername
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=Servername
ComSpec=C:\Windows\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Users\Administrator.000
LOCALAPPDATA=C:\Users\Administrator.000\AppData\Local
LOGONSERVER=\\Servername
NUMBER_OF_PROCESSORS=4
OS=Windows_NT
Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32
\WindowsPowerShell\v1.0\;C:\Program Files (x86)\PHP\v5.3;;C:\Windows\system32;C:
\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:
\Program Files (x86)\Dell\SysMgt\oma\bin;C:\Program Files (x86)\Dell\SysMgt\shar
ed\bin;C:\Program Files (x86)\Dell\SysMgt\idrac
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 42 Stepping 7, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=2a07
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
PUBLIC=C:\Users\Public
SESSIONNAME=RDP-Tcp#0
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Users\ADMINI~1.000\AppData\Local\Temp\2
TMP=C:\Users\ADMINI~1.000\AppData\Local\Temp\2
USERDNSDOMAIN=RTCH.LOCAL
USERDOMAIN=domain
USERDOMAIN_ROAMINGPROFILE=domain
USERNAME=administrator
USERPROFILE=C:\Users\Administrator.000
windir=C:\Windows
windows_tracing_flags=3
windows_tracing_logfile=C:\BVTBin\Tests\installpackage\csilogfile.log
Monday, May 27, 2013 12:48 PM
Answers
-
Hi,
It could be caused that when performing the in-place upgrade, system noticed that an old Administrator account already exists so it creating a new one with the name Administrator.000. I also found a similar issue which joined a server to 2 different domain. So it created an Administrator.000 when joined the second domain as the Administrator is already created in first one.
However I failed to find a way to rename it as it is a domain controller.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.
- Marked as answer by MedicalSMicrosoft contingent staff Wednesday, June 5, 2013 3:48 AM
Thursday, May 30, 2013 1:57 AM
All replies
-
1. Microsoft preferres migration to in-place upgrade that is long and risky. You could migrate from Foundation directly to 2012.
2. Have you checked the health of your system after first migration and administrator profile?
3. Have you checked the health of final AD?
4. The affected profile is that of Built in Administrator?
5. It seems that the SIDs do not match and that causes the appearance of another user account http://www.petri.co.il/forums/showthread.php?t=31429
Regards
Milos
- Edited by Milos Puchta Tuesday, May 28, 2013 7:23 AM
Tuesday, May 28, 2013 7:21 AM -
1 - You cannot upgrade to Foundation 2012 directly this is to supported. You can only goto Foundation 2008 to 2008 Standard then 2012 Standard. The installer wont even let you jump like that I tried.
http://technet.microsoft.com/en-us/library/dd979563(v=ws.10).aspx
As I stated above everything is operating as it should - Health is fine. Just want to change the domain admin profile back without the 000.
I have already read that link you provided in step 5 and this doesn't pertain to me as this is a domain controller.
Tuesday, May 28, 2013 11:29 AM -
Hi,
It could be caused that when performing the in-place upgrade, system noticed that an old Administrator account already exists so it creating a new one with the name Administrator.000. I also found a similar issue which joined a server to 2 different domain. So it created an Administrator.000 when joined the second domain as the Administrator is already created in first one.
However I failed to find a way to rename it as it is a domain controller.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact tnmff@microsoft.com.
- Marked as answer by MedicalSMicrosoft contingent staff Wednesday, June 5, 2013 3:48 AM
Thursday, May 30, 2013 1:57 AM