PTW said:
Is that not a standard Windows security login to do this? Should I only be using the BUILTIN/Administrator login to do this?
There actually is no standard Windows login for SQL Server. They are all made up individually based on the original installer's needs. Some people don't even map Windows domain accounts to the SQL admin or service accounts. Usually, you'll find that in a SOHO (small office / home office). Domain accounts for SQL Services are more common, but no means necessary, in larger environments.
As MDXer said, you'll need to remap the SQL Server and SQL Server Agent services to the new domain accounts because they will still be looking for the old ones. Be aware that any replication you have established, as well as jobs, are probably broken now that you've deleted the account. The reason for this is the unique identifier attached to every object in Active Directory called a Security Identifier (often referred to as a SID or SPid). Even though you have a domain login which has the same name, in order for AD to tell it apart from all other objects, it's assigned the new login a different SPid which means nothing is connected to it right now.
Go through SQL Server carefully, make sure to remap everything, and then check it regularly for the next couple of weeks to make sure you haven't inadvertantly forgotten anything. Also, watch your SQL Server/SQL Server Agent and Event Viewer logs which will tell you if something is broken even if you don't see it in the Enterprise Manager interface.
Last, check the Services on the OS to verify you've remapped all your SQL services and that there isn't another service dependent on the deleted NT login (there should NOT be, but it never hurts to check).
Catadmin - MCDBA, MCSA
"If a person is Microsoft Certified, does that mean that Microsoft pays the bills for the funny white jackets that tie in the back???