SharePoint migration-account planning

When SharePoint was deployed for the first time, there was no planning and direct installation. Some service accounts in the middle were also very temporary users, and the results were very confusing, many services use the same account. Some of the information (such as the password) of a service account may be changed frequently.

I recently read the SharePoint administrator guide, which provides a relatively basic and detailed description. It takes two chapters to explain the pre-Installation planning and deployment. Of course, the server topology is also the structure of the server. Although I looked at it, I could only look at it for resources. The more practical part is about account planning:

During configuration installation, you must specify multiple accounts: Service account, content access account, and database connection account. The lazy method is to set them to the same account, but I think SharePoint Services and web applications are relatively independent, therefore, setting different accounts for access to each service and content meets the original intention of SharePoint design. At the same time, it is easy to maintain and a certain account has changed, only a service or a Web application is affected.

User plan:

Installer: the user who installs SharePoint

Manage site configuration database connection User: this user will be considered as a system account

WSS search service account

WSS search content access user:

Office farm search service account:

Each web application: application pool account applicationProgramPool ID user,

SSP service credentials: Specify the credentials for the SSP web services to use for inter-Server Communication

And for running SSP-scoped timer jobs

Because the database is installed locally, the recommended Windows authentication is used for database connection. If separated, different users should be specified for each connection.

.....