I can't tell if it's working or not, but the script is reporting that it is being Run As "System", not "networkservice" as my screenshot indicates it should be using.

You need to check "Local login" and "Load profile" in the Credential settings, otherwise it will just get the rights as that user and not really run as that user.

---

You need to check "Local login" and "Load profile" in the Credential settings, otherwise it will just get the rights as that user and not really run as that user.

How the heck does that work, credentials without being that user?

I think we had this discussion once before. I just checked my other servers (this is a new one) and they have both of those checked. So, has the default changed??

For example, by default, the SYSTEM account runs the VisualCron Server service. It has no network access rights by default. By using a Credential you will be able to gain the network rights of the user in that Credential. You have the option login locally and load the profile and if the whole process is loaded it will run _as_ that user.

This has changed some versions ago the following way:

1. Load profile option was moved from Execute Task to the Credential
2. since the move, other Tasks can use this feature (which wasn't available) - only network rights was possible to gain - not a full "run as"

---

But that was my question, HOW do you run as System with a user's rights and not be that user?

But that was my question, HOW do you run as System with a user's rights and not be that user?

You just uncheck Load profile. But then, as I mentioned, you will see the original username and not the one you "want".

---