Community
Error 17: #5
Tom Ziegler,
User (Posts: 2)
Sep 22, 2020 8:57:55 am EDT
Support level: Endpoint
Trying to remote install on a domain pc and I am getting the following error:
***** Start of log *****
Date: 22-Sep-20 08:52:02
Action: install/upgrade.
Checking files of the Host.
Login/password?
----------
Action for: LTWSPARE2607 (LTWSpare2607.algenol.local)
Connecting...
--> algenol\tzadmin
Error 17: #5
***** End of log *****
I have tried a custom MSI and the default MSI.
***** Start of log *****
Date: 22-Sep-20 08:52:02
Action: install/upgrade.
Checking files of the Host.
Login/password?
----------
Action for: LTWSPARE2607 (LTWSpare2607.algenol.local)
Connecting...
--> algenol\tzadmin
Error 17: #5
***** End of log *****
I have tried a custom MSI and the default MSI.
Pauline,
Support (Posts: 2880)
Sep 22, 2020 5:21:20 pm EDT
Hello Tom,
Thank you for your message.
The Error 17: #5 usually means that your NTLM user does not have enough privileges. Please, make sure that you have local admin rights on that machine. In addition, please double-check that admin$ (admin share) is allowed on the remote machine and you have access to it.
Hope that helps.
Thank you for your message.
The Error 17: #5 usually means that your NTLM user does not have enough privileges. Please, make sure that you have local admin rights on that machine. In addition, please double-check that admin$ (admin share) is allowed on the remote machine and you have access to it.
Hope that helps.
Tom Ziegler,
User (Posts: 2)
Sep 23, 2020 9:32:16 am EDT
Support level: Endpoint
The account I am entering for the remote push install is a domain admin account which has local admin rights and the admin share is available from the PC I am trying to push the remote install from. I decided to try it from one of the domain servers and that seems to work. Not sure why it is not working from my PC though.
Pauline,
Support (Posts: 2880)
Sep 23, 2020 2:54:30 pm EDT
Hello Tom,
I'm glad to hear you've figured out the issue and it works for you now!
Please feel free to post another message if you have other questions.
I'm glad to hear you've figured out the issue and it works for you now!
Please feel free to post another message if you have other questions.
Aaron Lorton,
User (Posts: 1)
Nov 25, 2020 3:52:37 pm EST
Support level: Pro
I was having the same issue/error with providing my administrator account credentials during the remote push dialog. My work around was to run the Remote Utilities viewer as another user, one with administrative rights. Then I was able to select the check box for "Use current security context" when pushing the client out.
* Website time zone: America/New_York (UTC -5)