The Tekblog

Changing the Administrator password is a pretty common and simple task. As it would seem in almost all IT oriented tasks, there are easy things to overlook. I suggest following these steps to be sure you have covered all the necessary bases.

1.) Services: Open the services management console and sort by “Logon as”. Any logging on as Administrator need to be changed to the new password. This can be accomplished by right-clicking the respective service and inputting the proper password in the correct location in the “Log on” tab.

2.) Scheduled tasks: I forget these all the time. We need not worry about the default SBS tasks and volume shadow copies as this runs under the system account. However, if there are custom scheduled tasks (like Robocopy scripts), they will need to be changed. This process is very similar to the services, you right click the task and on the main tab there is a button that says “set password”; should be self-explanatory from there.

3.) Kaseya credentials: This also needs to be changed in order for certain Kaseya tasks to complete successfully. This can be altered by selecting the respective company’s machine group, going to the agent tab and using the “Set Credential” function. Make sure to select only the PCs in the subnets covered by the server so as not to potentially change any home computers or otherwise, non-domain machines that may be managed; these machines need to retain the local administrative credentials. Once you have changed the credentials here use the test button located at the top right to ensure everything is properly input. If this isn’t done correctly-patching, backups, and certain scripts will fail to execute properly.

4.) Server Reboot Test: In cases where you are unsure of in-place configurations, it may be a good idea to reboot the server to make sure everything comes back up properly.

Following these guidelines should ensure that everything is copasetic once you have changed the password.