Hi, My company have the AD migration. The moss2007 is all in one on one server in old domain: moss.aaa.com. It only used for public folder share. Now it need migrate to the new forest. no need change name: moss.bbb.com. What's the migrate step for this? the user account had already been migrate to new domain with sid quarantine:no, and enablesidhistory.

Here are the steps I would recommend for migrating a farm to a new domain. I'm providing these as reference so you can verify you haven't forgotten something. It sounds as if you've done most of these steps, in which case all that is left to do is change the domain membership of the server (steps 6, 7, and 8). Since you have only one server, you only need to rename and restart it. Full farm backupMove users to new domain. stsadm -o migrateuser will migrate the old domain accounts to the new ones in SharePointMove service accounts to new domain, or create new service accountsUpdate the farm to use the service accounts in the new domain (See KB 943838) stsadm -o updatefarmcredentials (service accounts)stsadm -o spsearch -farmserviceaccountstsadm -o spsearch -farmcontentaccessaccountstsadm -o editssp -ssplogin (for each ssp)stsadm -o osearch -farmserviceaccountSSO and any other remaining service accounts (CA -> Ops -> Service Accounts)Default content access account (SSP -> Search Settings -> Default content access account)Customizations (if there are service accounts associated with these) You'll want to do the same with the SQL Server service accounts. Not the SQL Logins -- SP will handle this (though if your SQL Server is shared with other applications you'll want to update the SQL Logins for these other applications as necessary), but rather the actual SQL Server service accounts (DB Engine, DB Agent, Reporting Services, etc.).Shut down all services on all servers in the farm (this includes SQL)Change domain membership of all farm servers, reboot or perhaps shutdown and bring back up in the following order: SQL. Verify sql server is running and accessible. Check event logs. Resolve any issues.Central Admin server. Verify CA is accessible, check event logs. Web apps and some services may not be available if they are on servers that are currently turned off. Don't worry about these (yet).Application servers, search servers, index, query, other. It's likely the WFEs will go on at this step. Verify services are accessible as expected. Check event logs. Resolve issues.Any remaining WFEs. Wash, rinse, repeat. Assuming everything is running as expected, users can access the sites, the sky did not fall, etc. take a full farm backup. Jason Warren Infrastructure Specialist Habanero Consulting Group habaneroconsulting.com/blog

Here are the steps I would recommend for migrating a farm to a new domain. I'm providing these as reference so you can verify you haven't forgotten something. It sounds as if you've done most of these steps, in which case all that is left to do is change the domain membership of the server (steps 6, 7, and 8). Since you have only one server, you only need to rename and restart it. Full farm backupMove users to new domain. stsadm -o migrateuser will migrate the old domain accounts to the new ones in SharePointMove service accounts to new domain, or create new service accountsUpdate the farm to use the service accounts in the new domain (See KB 943838) stsadm -o updatefarmcredentials (service accounts)stsadm -o spsearch -farmserviceaccountstsadm -o spsearch -farmcontentaccessaccountstsadm -o editssp -ssplogin (for each ssp)stsadm -o osearch -farmserviceaccountSSO and any other remaining service accounts (CA -> Ops -> Service Accounts)Default content access account (SSP -> Search Settings -> Default content access account)Customizations (if there are service accounts associated with these) You'll want to do the same with the SQL Server service accounts. Not the SQL Logins -- SP will handle this (though if your SQL Server is shared with other applications you'll want to update the SQL Logins for these other applications as necessary), but rather the actual SQL Server service accounts (DB Engine, DB Agent, Reporting Services, etc.).Shut down all services on all servers in the farm (this includes SQL)Change domain membership of all farm servers, reboot or perhaps shutdown and bring back up in the following order: SQL. Verify sql server is running and accessible. Check event logs. Resolve any issues.Central Admin server. Verify CA is accessible, check event logs. Web apps and some services may not be available if they are on servers that are currently turned off. Don't worry about these (yet).Application servers, search servers, index, query, other. It's likely the WFEs will go on at this step. Verify services are accessible as expected. Check event logs. Resolve issues.Any remaining WFEs. Wash, rinse, repeat. Assuming everything is running as expected, users can access the sites, the sky did not fall, etc. take a full farm backup. Jason Warren Infrastructure Specialist Habanero Consulting Group habaneroconsulting.com/blog