asked on roaming profile after remove metadata
I recently installed a new server running server 2008R2 on the network. It is a small network with a very sick server 2003 running. The FSMO all transferred as expected, and all domain users [roaming domain profiles worked fine.
I was not able to demote the old server using dcpromo. I had to use dcpromo /forceremoval.
I ran the metadata cleanup processes and all seemed to go well.
I now have an issue when logging on to the new server [old one is not on line] with the users on their workstations. The Roaming Profile cannot be found and a comment that "possible attempt to compromise" shows up in the User profile error.
The domain has always been name.url.com, but the user was NAME\User. I get the same results using name.url.com\User as using the old pre 2000 method of NAME\User.
Is there any way to connect the old profile other than remove the workstation to a workgroup and then reconnect to the new server domain. Will I need to delete the users and recreate them?
I was not able to demote the old server using dcpromo. I had to use dcpromo /forceremoval.
I ran the metadata cleanup processes and all seemed to go well.
I now have an issue when logging on to the new server [old one is not on line] with the users on their workstations. The Roaming Profile cannot be found and a comment that "possible attempt to compromise" shows up in the User profile error.
The domain has always been name.url.com, but the user was NAME\User. I get the same results using name.url.com\User as using the old pre 2000 method of NAME\User.
Is there any way to connect the old profile other than remove the workstation to a workgroup and then reconnect to the new server domain. Will I need to delete the users and recreate them?
Microsoft Server AppsMicrosoft Legacy OS
Last Comment
Wilf
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Thanks
I ended up demoting the server as the last server and reinstalling it. It works fine now, and was a small network, so I was able to do that