Hello,
If I choose shown pending updates in the context menu of a shown client in WPP and type in the username and Password of the Client machine I get the answer "Wrong username or Password" and the pending updates window does not open.
If I enter the username and Password of the local Server the window of pending updates open and I get the failure "Unauthorized Access exetption! Ensure you have admin previleges on the remote computer".
I do not have a Domain!
Best regards,
Tobias
Comments: Hi, > I do not have a Domain! And therein lies the problem ! When you choose this feature, WPP spawns a new process using the credential you have provided. These credentials need to have administrative rights on the remote computer. As you are not in a domain : - If you use local credentials, you can launch the process but don't have admin rights on the remote computer. - If you use the remote administrator account, you can't launch the process on the local computer. The workaround is to create the same account on the local computer and the remote computer. This account must have admin rights on the remote computer.
If I choose shown pending updates in the context menu of a shown client in WPP and type in the username and Password of the Client machine I get the answer "Wrong username or Password" and the pending updates window does not open.
If I enter the username and Password of the local Server the window of pending updates open and I get the failure "Unauthorized Access exetption! Ensure you have admin previleges on the remote computer".
I do not have a Domain!
Best regards,
Tobias
Comments: Hi, > I do not have a Domain! And therein lies the problem ! When you choose this feature, WPP spawns a new process using the credential you have provided. These credentials need to have administrative rights on the remote computer. As you are not in a domain : - If you use local credentials, you can launch the process but don't have admin rights on the remote computer. - If you use the remote administrator account, you can't launch the process on the local computer. The workaround is to create the same account on the local computer and the remote computer. This account must have admin rights on the remote computer.
