If you have any managed resources that requires user authentication, then the account must be updated if it was using a domain user account. The typical managed resources that may require user authentication are a module instance, utility process, process, and Node Alias. If the account is not updated the managed resource will fail after the domain is changed.
I would make sure these accounts are added to the valid user list prior to the AD changes:
- The Local Administrator account for both nodes
- The future Active Directory Domain account
As a preventative measure, I would suggest taking an AutoStart database backup prior to the change and ensure the resources are offline during the change.
Adding to the responses from Mr. Ito and Emiliano.
It would also be advisable to have a backup.def file from AutoStart saved to another location. In the case of something going amiss and an uninstall/reinstall, this will allow you to more quickly reload the configuration.
Since often AutoStart is installed via a Domain Administrator, it would be higly recommended (as Emiliano already advised) to be sure that the Local Administrators from both nodes are added in to AutoStart's user list, with full Admin priveledges. This should help prevent problems accessing AutoStart after the rebuilding of AD.
yito1
262 Posts
0
October 29th, 2010 15:00
Hi,
Perhaps there will not be the influence.
If Active Directory Domain name changes, please edit Valid User List in a license/security tab.
You should perform enough tests before working.
ecervant
63 Posts
0
November 3rd, 2010 09:00
If you have any managed resources that requires user authentication, then the account must be updated if it was using a domain user account. The typical managed resources that may require user authentication are a module instance, utility process, process, and Node Alias. If the account is not updated the managed resource will fail after the domain is changed.
I would make sure these accounts are added to the valid user list prior to the AD changes:
- The Local Administrator account for both nodes
- The future Active Directory Domain account
As a preventative measure, I would suggest taking an AutoStart database backup prior to the change and ensure the resources are offline during the change.
daniel_vongehr
34 Posts
0
November 3rd, 2010 15:00
Adding to the responses from Mr. Ito and Emiliano.
It would also be advisable to have a backup.def file from AutoStart saved to another location. In the case of something going amiss and an uninstall/reinstall, this will allow you to more quickly reload the configuration.
Since often AutoStart is installed via a Domain Administrator, it would be higly recommended (as Emiliano already advised) to be sure that the Local Administrators from both nodes are added in to AutoStart's user list, with full Admin priveledges. This should help prevent problems accessing AutoStart after the rebuilding of AD.
Best Regards,
Daniel Vongehr
Technical Support Engineer
Worldwide Technical Support
EMC2 Corporation