Troubleshooting The Discovery and Push Install in Padvish Management Console

Introduction

Discovery and remote installation (Push Install) is one of the most important features of the Padvish management console which lets the network administrator remotely and from a central point with no need to the physical presence behind the systems, install antivirus or any other products of Padvish on their systems.

Discovery or remote installation demands requirements that are introduced in the Discovery and Push install requirements of the Padvish management console.

Since this process is highly dependent on network status and especially systems connection with active directory and its settings, there is a possibility of error or incomplete process due to network problems or authentication and the like.

In this topic, first, some common errors during Push Install and their solution are introduced, and then a general solution for troubleshooting other cases is provided.

If you have a problem in this section, please call the Padvish support center.

Reading logs and finding the error

In the Padvish management console, choose (Discovered computers) from the left tree.
If you adjust this part, you will view a list of systems. The Discovery Result Message column will show you the last error/message in the Discovery/Push install processes.
Also, to view the more complete log, right-click on each system, select view log and you can view the Discovery/Push install log. Pay attention that for each discovery or installation, there will be some log recorded, that normally the newest log is the error message you need to follow.
If you cannot view any system, first you need to choose settings and be sure that your Active Recovery and IP Range settings are adjusted correctly.
Also, you can choose the view log on the top of the list, and view the log of the discovery/Push install.

If you used each one of the above ways- I mean Discovery Result Message or View Log, on any clients, the appeared message may be as follows:

Message

Definition

The operation was completed successfully

This message means the operation was completed successfully with no errors.

The network path was not found. (53)

This message means no access to the mentioned client. Probable problems:

Client name does not convert to IP:

Check DNS server]
Test if the ping order with the name of the client can declare the IP or not.

Port 445 of the client is not accessible:

Check the client and network firewalls
By using telnet order from the server to the client, make sure Port 445 is open
Check (from the server) whether the Admin$ folder of the client is accessible or not.

The client-sharing file service is closed:

This problem typically occurs for non-domain clients
In client network card settings checked the File and Printing Sharing.

Also Server services from Server.MSC section must be functional

The username or password is incorrect.

In this situation, connection with the client is correctly established (have no network problem) but authentication has not been performed.

Check the settings for the adjusted username and password.
Pay attention to fill the domain for the username, if it has a domain. If there is no domain (the client is local), then you must leave it empty.
Be sure that this name is admin accessing permits to access the destination system.
Sometimes the lack of client connection to the Active Directory server may cause this problem itself. Be sure that the client visits its DC server.
Sometimes the difference between the time of the client and server causes this error. Accurately, check the date and time.

If you use a multi-username in the console, to see which username encounters with error, choose the view log option.

Access is denied.

Copy of C:\Program Files (x86)\AmnPardaz\Server\AmnPardazDiscoveryAgent.exe to remote \\IP\ADMIN$\Temp\AmnPardazDiscoveryAgent.exe failed with error Access is denied. (5).

The given username has not had the necessary admin accession:

Check that the username is completed in the admin destination system.
Pay attention that if the username has the domain, the domain part must be filled for it. And if it has no domain (it is a local client), this field must be empty.
By using this username and password open \\clientname\ADMIN$\Temp and try to create a file or folder.
To view which order faced the error, choose the view log.

Sometimes, File Copy failure will be solved with one try.

File copy failed (1000008)

About this error, you must check the previous line of the log. In most cases the reasons are:

Access is denied (5) – the username does not have admin access. Check the previous line of this guide.
The network path was not found (53) – during operation, for some reason the connection is disconnected.
The specified network name is no longer available (64) – during operation, for some reason the connection is disconnected.
There is not enough space on the disk (112) – the disk of the destination computer is full.
The network name cannot be found (67) – during operation, for some reason the connection is disconnected.
An unexpected network error occurred (59) – during operation, for some reason the connection is disconnected.

As specified above, the cause usually is a cross-sectional network outage which with one retry this problem will resolve.

Install result no found

This message is dedicated to pushing install and means that the installed file is copied and ran on the client, but the result of the install did not deliver to the server. In this situation, the antivirus is probably installed or an error occurred.

Run discovery again to discover the install status

If the problem does not fix, then follow the general process of troubleshooting.

Cannot execute the file(1000006)

Could not connect to the remote service manager with an error The RPC server is unavailable. (1722).

Could not connect to the remote service manager with error A system shutdown is in progress. (1115).

The destination system Windows does not respond to the push install command. This issue can occur for a different reasons:

Destination Windows is in the middle of the Shutdown process. During shutdown/reset, Windows will not receive new commands. Wait a few minutes and try again later.
Server or RPC service encounters trouble in destination Windows. Restart server services once. If the problem does not fix, reset the destination system.

The destination window is running low on resources (memory, etc.) and is temporarily unresponsive. Wait for a little and try again. Reset the destination computer, if necessary.

Time out (1000007)

The destination system is not responsive:

Check the network connection with the destination system. (Both ping and try to connect to sharing folder).
It is possible that a firewall blocked the connection.

Check that the destination system is turned on. (You can check the ping status, if the ping is successful, probably the problem is the type of the firewall or connection /disconnection of the network).

The general procedure for troubleshooting

The general procedure of troubleshooting has two general parts:

Follow this way only when you get no results by reading the error message and want to exactly see the issue.

Testing the access: most of the push install problems are lack of access to the destination system. So, the first step is to be sure that your server has the access to the shared folder (Admin$) on the destination client system.
- To do this test you should remotely access to Padvish management server. Because it is the management server that is connected to clients, this test must be done from the server itself until the conditions are equal and the error is observed.
- By pressing Window+R and follow phrase you can connect to the client:
\\clientname-or-ip\ADMIN$
- Pay attention that for connecting, you use the same username and password in the console.
- After connecting, try to go to the temp folder and create a sub-folder there to be sure of having full access.
- If you have any problem with creating the folder, your problem is the lack of access type problem, and must fix it for the management console to have the ability to remotely install.
- If there is complete access to the destination system, in the second stage, the Padvish installation program will run manually on the client once to view the error message
Execution test: To do this test you must remotely access one of the clients which have installation issues. Pay attention to choosing the same client which in the accession test, has tested a complete connection with the Admin$ folder.
- Deliver the Padvish installation file (or any other product that you wish to install) to the client with its relevant rgc file.
- Run the installation program (make sure that the installer is not an agent so that the user interface is visited and see if there is an error message.)
- If the installer shows an error, use the error message to fix it.
If you did not conclude anything from the error message, you need to call with Padvish support center

Introduction

Reading logs and finding the error

Leave a Reply