Skip to main content

Remote installation management agent error

Thread needs solution

Hello.

 

I'm trying to install the agent remotely from the console on a computer with windows 10. On this computer I have disabled the uac and I have the firewall disabled, but I get the error: E00450033 access ssh denied. I do not know what can happen. Can anybody help me? Thank you.

0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Hello Jose,

I'd start with checking the following:

  • Make sure you have ports 445, 9876 and 25001 open, see Using telnet to Test Open Ports;
     
  • Make sure the specified machine address and credentials are correct and the machine is available (try RDP connection under the same user for check);
     
  • Disable Simple file sharing on the remote machine: 
    Windows XP: Control panel -> Folder options -> View -> Use simple file sharing 
    Windows Vista or later: Control panel > Folder options > View > Use Sharing Wizard
     
  • Enable File and Printer Sharing on the remote machine: 
    Windows XP with Service Pack 2 or Windows 2003 Server: Control panel > Windows Firewall > Exceptions > File and Printer Sharing 
    Windows Vista, Windows Server 2008, or Windows 7: Control panel > Windows Firewall > Network and Sharing Center > Change advanced sharing settings
     
  • Make sure that the user whose credentials you use for remote installation is a member of Local administrators group on the target machine;
     
  • Make sure that the administrative share on the target machine is accessible from the source machine: 
    Go to Start -> Run and type \\Target_machine_name\admin$\ (or \\Target_machine_IP\admin$\). If the share opens correctly, check if the user under whom you are trying to install the software can copy and paste files to and from this location. If the share does not open and access cannot be granted due to a specific domain policy, install through Group Policy, see Web Help: Installing the agent through Group Policy;

    Usually something of the above leads to issues with remote installation. 

The most important part for Windows 10 remote install is to enable the built-in Administrator account.

https://kb.acronis.com/content/47403

My checklist for a successful Win 10 remote install:

  • Disable firewall, or edit it appropriately
  • Enable file/printer sharing & network discovery
  • Connect with the local admin username and password you created when you installed Windows
  • Enable the admin share (saves having to enable the built in admin and means you can leave UAC enabled)
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
    • Create a new entry by right-clicking System and then selecting DWORD (32-bit) Value.
    • Choose LocalAccountTokenFilterPolicy as name for the new entry.
    • Set the value of LocalAccountTokenFilterPolicy to 1 by right-clicking the new entry.
Iain Barlow wrote:

My checklist for a successful Win 10 remote install:

  • Disable firewall, or edit it appropriately
  • Enable file/printer sharing & network discovery
  • Connect with the local admin username and password you created when you installed Windows
  • Enable the admin share (saves having to enable the built in admin and means you can leave UAC enabled)
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System.
    • Create a new entry by right-clicking System and then selecting DWORD (32-bit) Value.
    • Choose LocalAccountTokenFilterPolicy as name for the new entry.
    • Set the value of LocalAccountTokenFilterPolicy to 1 by right-clicking the new entry.

This is awesome, I will be sure to try this out in our lab! Thanks! 

Robert Sewter wrote:
This is awesome, I will be sure to try this out in our lab! Thanks! 
 
Hope it works for you.  I've never had a problem doing it that way, although I've only used it in a local workgroup and not a domain. 
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Posts: 250
Comments: 7092

Lain, if you don't mind, I've added your checklist to Snap Deploy Tips Not Covered In User Manual 
Thank you for sharing!