How to configure an operating system to troubleshoot the remote installation of the Kaspersky Security Center Network Agent
Show applications and versions that this article concerns
- Kaspersky Security Center 14.2 (version 14.2.0.26967)
- Kaspersky Security Center 14 (version 14.0.0.10902)
- Kaspersky Security Center 13.2 (version 13.2.0.1511)
- Kaspersky Security Center 13.1 (version 13.1.0.8324)
- Kaspersky Security Center 13 (version 13.0.0.11247)
These instructions do not apply directly to Kaspersky applications. Our engineers can help you configure the parameters described in the article if your operating system is not damaged and is functioning normally. In all other cases, please contact Microsoft support.
Issue
When attempting to perform the remote installation task for the Network Agent or a user package with third-party software Using operating system resources through Administration Server or Using operating system resources through distribution points, errors may occur due to incorrect OS configuration of the target device.
Cause
| Error | Cause |
|---|---|
| “Shared folder "\\192.0.2.45\admin$" is unavailable for the following accounts: <Current Administration Server service account> (Access denied)”. | Remote User Account Control (UAC) is enabled. |
| “Distribution point "˂DP_name˃” has failed to start remote installation. Installation package download from the Administration Server to the shared folder on the device returned an error: ˂Kaspersky Security Center 14.2 Network Agent service account˃ (Access denied.) No more distribution points have been found.” | |
| “Shared folder "\\192.0.2.45\admin$" is unavailable for the following accounts: Error 1181/0x43 ('System error 0x43 (The network name cannot be found.)') has occurred while obtaining access to file system object '\\192.0.2.45\admin$\Temp\KAV Remote Installations\17448b048259422d801bb86c01520348_1’”. | There are no shared administrative folders. |
| “Distribution point "˂DP_name˃” has failed to start remote installation. Installation package download from the Administration Server to the shared folder on the device returned an error: Error 1181/0x43 ('System error 0x43 (The network name cannot be found.)') has occurred while obtaining access to file system object '\\192.0.2.45\admin$\Temp\KAV Remote Installations\12ea84896a6b4b679dfdaeb663cedd00_1’. No more distribution points have been found.” | |
| “Shared folder "\\192.0.2.45\admin$" is unavailable for the following accounts: <Current Administration Server service account> (The RPC server is unavailable)”. |
|
| “Distribution point "˂DP_name˃” has failed to start remote installation. Installation package download from the Administration Server to the shared folder on the device returned an error: ˂Kaspersky Security Center 14.2 Network Agent service account˃ (The RPC server is unavailable.) No more distribution points have been found.” | |
| “The device may have been disconnected from the network.” | File and Printer Sharing is disabled. |
| “The RPC server is unavailable.” | The normal operation of the OS has been disrupted. |
Solution
Remote User Account Control is enabled
If the target devices belong to a work group and are not in the Active Directory domain, disable remote UAC on them.
- Open the command line as an administrator.
- Run the command to disable remote UAC:
- Reboot the OS on the target device.
For details about UAC, see the Microsoft website:
No shared administrative folders
To perform the remote installation task using Windows tools, it is necessary to have shared administrative folders ADMIN$, C$ and IPC$. Sometimes they can be disabled to improve the OS security.
- Open the command line as an administrator.
- Check if the ADMIN$, C$ and IPC$ folders exist using the command:
- Restore shared administrative folders, if necessary.
- Open the command line as an administrator.
- Run the commands:
REG ADD HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters /v AutoShareServer /t REG_DWORD /d 1 /fREG ADD HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters /v AutoShareWks /t REG_DWORD /d 1 /f - Reboot the OS on the target device and check once again if the administrative folders exist.
For details about problems that may occur when administrative shares are missing, see the Microsoft website.
Incorrect status of LanmanServer, RPC, DCOM services
The LanmanServer, RPC and DCOM OS services provide the remote application installation. The LanmanServer, RPC and DCOM services must be in the Running status for the remote application installation task to run.
Check the status:
- Open the command line as an administrator.
- Run the command:
If the status is different, configure the services startup settings in the domain group policies or through the local Services snap-in (services.msc).
File and Printer Sharing is disabled
File and Printer Sharing enables copying of the installation package to the target device. To enable File and Printer Sharing:
- Press
+R on the keyboard, type ncpa.cpl and click OK. - Locally on the affected device, open the context menu of the network adapter that is connected to the Administration Server or a distribution point and select Properties.
- Select the File and Printer Sharing check box and click OK.
- Switch off the network adapter and switch it on again or restart the device OS to apply the changes.
Normal operation of the OS has been disrupted
If the problem with the remote installation occurs not on all devices on the network, check the root cause of the problem on these devices and follow the recommendations below.
- No free space on the disc's system partition.
In this case, the OS services stop working correctly. Free up the disc space and restart the device. - The operating system is waiting to restart after installing updates from the Windows Update Center.
If the installation is not complete, the remote installation task may be disrupted. To resolve the issue, restart the device. - The OS has been running for a long time and has not been restarted.
Restart your OS if you haven't done so for a few months. - The WMI repository is damaged.
Check its integrity and troubleshoot using the instructions on the Microsoft website. - The OS system files are corrupted.
Check and restore the integrity of the OS system files. See the instructions on the Microsoft website to run the commands below correctly. Then restart the device.
What to do if the issue persists
- Use the additional recommendations to troubleshoot issues with network availability.
- If the installation task completes successfully and the message "Remote installation has completed successfully on this device." appears, but the Network Agent is not available or doesn’t appear on the device object, see the recommendations in the article.
- Try to exclude checking the connection of the target device to the Administration Server if Deep Packet Inspection (DPI) or decryption and traffic analysis technologies (SSL inspection) are used as part of third-party protection software.
- Use additional centralized tools to deploy the Network Agent:
- Using Active Directory group policies
- Integration into a reference OS installation image
- Third-party tools for centralized application deployment
If the issue is still relevant, submit a request to Kaspersky Technical Support via Kaspersky CompanyAccount. In your request:
- Describe the problem: attach screenshots of the installation error, specify which steps from the instructions you have performed, and provide the output of the diagnostic commands from this article.
- Collect the diagnostic information and attach the created files to your request.
Useful references
Troubleshooting the network errors related to remote installation of KSC Network Agent
Troubleshooting the errors due to incorrectly configured account rights during remote installation of Kaspersky Security Center Network Agent
Forced deployment through the remote installation task of Kaspersky Security Center
Running stand-alone packages created by Kaspersky Security Center
