Thanks.
The full steps that got the new domain working for me were:
Change domain
Make sure you can ping the sql server in the new domain.
Run updatefarmcredentials on the account used in the app pool for Central
Admin (using stsadm). Run IISRESET
Change the other app pools as above, then run IISRESET.
Go through the local services and make sure any accounts from old domain are
changed to the current domain.
Run migrateusers through stsadm for all service accounts.
At this point all was working okay for me.
There may be a better way that will get answered by Microsoft on this post,
but I couldn't keep waiting, so the last three days (since post) was spent
figuring this out.
I am facing a similar issue. My sharepoint Box had an AD setup which got blew away, Now we have the box attached to another domain, How do i get this domain attached to the sharepoint installation. I'm sure i will have to create users again.
Thanks,
Pallavi
> On Tuesday, January 12, 2010 10:27 AM Gerhard wrote:
> I posted a question twice yesterday, but it is not showing up, so am
> reposting it. I am trying to migrate a SharePoint 2007 machine to another
> domain. The only remaining issue is on the application pools, where they
> work with the farm administrator account, but not with the accounts that were
> previously working (and have been migrated to the new domain). I have run
> MigrateUser and Update Farm credentials and also rerun the configuration
> wizard. I can get into Central Admin, SSP and the home page fine as long as
> the application pools are using the farm administrator account, but get
> access denied errors if I switch back to the individual accounts. The
> acccounts all have db_owner permission on SQL Server for the MOSS tables,
> they are also Domain Admins. What else do I need to do so I can use them in
> the application pools as identies?
>
> Thanks.
>> On Thursday, January 14, 2010 4:13 PM Gerhard wrote:
>> I figured this out, if you change the app pools via Go into Central
>> Administration -> Operations -> Service Accounts it works okay.
>>
>> The full steps that got the new domain working for me were:
>>
>> Change domain
>>
>> Make sure you can ping the sql server in the new domain.
>>
>> Run updatefarmcredentials on the account used in the app pool for Central
>> Admin (using stsadm). Run IISRESET
>>
>> Change the other app pools as above, then run IISRESET.
>>
>> Go through the local services and make sure any accounts from old domain are
>> changed to the current domain.
>>
>> Run migrateusers through stsadm for all service accounts.
>>
>> At this point all was working okay for me.
>>
>> There may be a better way that will get answered by Microsoft on this post,
>> but I could not keep waiting, so the last three days (since post) was spent
>> figuring this out.
>>
>>
>>
>>
>> "Gerhard" wrote:
>> Submitted via EggHeadCafe
>> SharePoint Tip / Thought of the Day WebPart
>> http://www.eggheadcafe.com/tutorials/aspnet/14280ff8-3c9f-46bd-8214-9267e613c8ec/sharepoint-tip--thought-of-the-day-webpart.aspx