when we try to install a new client with the policy manager (Policy Manager started with Account "Domain\Admin1") and say use different user to install ("Domain\Admin2") the Policymanager try´s to authenticate with "Admin1" at the new Server. (Windows EventLog at the new server).
Is this known?
I guess, you are talking about push installation feature. If so, browsing for needed host is executed with logged on user account (which is used to start the PMC application), while actual deployment is executed with selected in the wizard account: current user or custom one.
yes i'am talking about push installations.
In the deployment wizard i use "Admin2", but PolicyManager trys to start with "Admin1", Admin1 starts the policymanager.
Admin1 has no rights at the Remote Server, Installation failed. (WindowsEventLog at the RemoteServer)
When i start PolicyManager with Admin2 and deploy with Admin2 in the wizard the installation succced.
Toady we tried to reproduce your problem, but everything works as expected: installation at target host is processed with credentials entered in the wizard, while indeed there are number of connection attempts made with logged in user account, probably to fetch some host info while preparing the operation. Even though logon attempts of logged in user fail, installation is running smooth.
If your environment has some strict group policy rules, it might affect the push.
We are having the same problem. Push install fails, when not logged in with the user that as access rights on the client.
No strict GPOs, just default settings, UAC on default level on both systems.
We would require the diagnostic information from the affected client machine and policy manager to check the scenario. Please provide this information to support, and we will investigate further.
Visit the Community
Check our Forums or How-to & FAQs for advice or answers
View User Guides
Refer to our getting started guides and product manuals
Talk to our Support agents and get answers to your questions