Forum Discussion
The error message you are encountering during the backup process indicates that there is an issue with the authentication credentials being used by the system user to access the shared folder. Here are a few steps you can take to troubleshoot and resolve the issue:
Verify the credentials: Double-check the credentials being used by the system user to ensure they are correct. Pay attention to any potential typos or changes in the password. Also, make sure the credentials have sufficient permissions to access the shared folder.
Test access to the shared folder: Manually verify if the system user has proper access to the shared folder by attempting to access it using the same credentials. This can help identify if there are any permission issues or connectivity problems between the SCCM server and the shared folder.
Validate share permissions: While you mentioned that the system users have full control on the share, it's important to also check the NTFS permissions on the shared folder. Ensure that the system user has the necessary read, write, and modify permissions on both the share level and the NTFS level.
Check for password expiration or account lockout: Verify if the system user's password has expired or if the account has been locked out due to failed login attempts. In such cases, updating the password or unlocking the account can resolve the authentication issue.
Consider using a service account: Instead of relying on the system user, you may want to consider using a dedicated service account for the backup process. This account can be granted the necessary permissions to access the shared folder and can be configured specifically for the backup operation.
Review event logs: Check the event logs on the SCCM server for any relevant error messages or warnings that could provide more details about the authentication failure. Look for events related to the backup process or the system user account.
If the issue persists after going through these steps, it's recommended to reach out to the SCCM support or your IT department for further assistance. They can provide more specific guidance based on your environment and configuration.
- charlieferreiraJul 20, 2023Copper Contributor
Thank you for your answer.
I have found the problem, which was related to the package source not having a domain. I had \\test\adr(...) and changed it to \\test.domain.pt\adr(...).
So the problem is solved.
Thank you.