• Active Directory
  • Application
  • Desktop & Mobile
  • Help Desk
  • Network
  • IT Security
  • MSP
  • On-Demand
 
 
Device Management, made easy
Manage control and secure your workstations, mobile
devices and tablets
 
 
Help Desk for Everyone
IT Help Desk Software and Customer Support Software
 
 
Protect Your IT. Save Your Business
Build a secure fortress with our security management solutions
 
 
MSP
Manage services faster, with multi-tenanted, ITIL-ready, and unified RMM solutions
 
 
On-Demand Solutions
IT Help Desk, Active Directory, and Operations Management from the Cloud
 

Software Installation - Knowledge Base

1. The status of the configurations is always in "Ready to Execute" state. Why?

Check the following:

  • Check whether the Desktop Central agent has been installed in all the computers within the defined scope. To verify this, view the Agent Installation Summary by clicking Admin --> Scope of Management link.
  • If an OU is specified as the target for a configuration, check whether that OU has users and computers within it.
  • Check for any firewall running in the machine where Desktop Central is installed. It might block the status update messages that come from client machines. Ensure that the Desktop Central Port (default 8020) is added to the exceptions list.
  • User configurations will be applied during user logon, after user logon, or every 90 minutes whichever is earlier. Till then the status will remain only in "Ready to Execute"
  • Computer configurations will be applied during system startup, after system startup, or every 90 minutes whichever is earlier. Till then the status will remain only in "Ready to Execute"
  • To apply the configurations immediately, execute the "C:\Program Files\DesktopCentral_Agent\bin\cfgupdate" command in the client computers as below:

    For applying the user configurations: cfgupdate user

    For applying computer configurations: cfgupdate computer

Questions

2. Unable to deploy the software. Why?

When Software Deployment fails, you will get to see any of the following errors in the Remarks column of the Execution Status of that configuration:

Some of the common solutions include:

  • Check whether the software being deployed can be installed in silent mode.
  • The network share from where the software has to be installed do not have necessary privileges. The network share should have read permissions for the "Authenticated Users" group for the software installation to work properly.
  • Check whether the Desktop Central agent has been installed in all the computers within the defined scope. To verify this, view the Agent Installation Summary by clicking Admin --> Scope of Management link.
  • If an OU or a Group is specified as the target for a configuration, check whether that OU/Group has users and computers within it. You should login as that user or restart the computers within that OU/Group to get the configurations deployed.
  • When the machine running Desktop Central has multiple IP Addresses, like a Virtual Adapter, two NICs, etc. Try disabling the virtual Adapters, if any.
  • When the Firewall running in the m/c running Desktop Central Server blocks the data. Ensure that the Desktop Central Port (default is 8020) is added to the exceptions list.

2.1 The Wait Option has been timed out

Cause: The installation is waiting for the user input or could not be completed within the specified time limit.

Solution: Check whether proper silent installation options have been specified correctly. Try installing the application manually in one computer using the specified options. You should not get any pop up during the installation.

If problems persists, contact support with the following details:

  1. Log files from Desktop Central Server
  2. Log files from Desktop Central Agent pertaining to the computer where installation has failed.
  3. The Software Package that you were trying to install.

2.2 The Network path not found

Cause: The network path specified while creating the package is not found

Solution: Ensure the following:

  1. The path specified is correct.
  2. The path is accessible from the client computer where the software is being installed.
  3. The path and the file is shared with necessary privileges.

2.3 The system cannot find the file specified

Cause: The executable file is not available in the specified path.

Solution: Check the following:

  1. The file name has been specified correctly
  2. The file is available in the specified path
  3. The file can be accessed from the client computer
  4. Try maually accessing the file from the client computer

2.4 Access is Denied

Cause: The file or the path do not have access privileges to all the users (everyone)

Solution:

  1. Check whether the network share has READ Access to Authenticated Users and Everyone
  2. If you have used Run As option while installing the software, ensure that the user as whom the software is installed has necessary privileges to install the software and to create folders under "Program Files"

2.5 The handle is invalid

Cause: Error while setting the given path as the working directory

Solution: Check the following:

  1. The Root Directory has been specified correctly while adding the package.
  2. The root directory is accessible from the client computer where the software is being installed.
  3. The network share has READ & EXECUTE permission to Authenticated Users and Everyone
  4. Both the network share and the client computers are in the same domain.

If problems persists, contact support with the following details:

  1. Log files from Desktop Central Server
  2. Log files from Desktop Central Agent pertaining to the computer where installation has failed.
  3. The Software Package that you were trying to install.

2.6 Incorrect Function

Cause: The installation process has quit abruptly.

Solution: Check the following:

  1. Whether shutdown / log off has been called while the installation is in progress.
  2. Whether there is enough space to install the software
  3. Whether there came a pop-up that the end user had rejected during installation.
  4. Whether there was a pop-up with an error message
  5. Try installing the application manually in one computer using the specified options.

If problems persists, contact support with the following details:

  1. Log files from Desktop Central Server
  2. Log files from Desktop Central Agent pertaining to the computer where installation has failed.
  3. The Software Package that you were trying to install.

2.7 Fatal Error during installation

Check the following:

  1. Whether the software is already installed in the client computer (for EXE based applications only)
  2. Whether the User /Computer has necessary privilege to install the software
  3. Try installing the application manually in one computer using the specified options.
  4. For MSI applications, try selecting the "Enable Logging for troubleshooting" option while adding the package and check the logs for any application specific errors.

If problems persists, contact support with the following details:

  1. Log files from Desktop Central Server
  2. Log files from Desktop Central Agent pertaining to the computer where installation has failed.
  3. The Software Package that you were trying to install.

2.8 The storage control block address is invalid

Cause: The network path specified is invalid

Solution: Check whether the network path specified while adding a package is correct.

2.9 Failed with unknown error code : <error code>

Cause: Due to some specific error related to the application being installed.

Solution:

  1. Check whether the application is already installed in the client computer
  2. Try installing the application manually in one computer using the specified options.
  3. For MSI applications, try selecting the "Enable Logging for troubleshooting" option while adding the package and check the logs for any application specific errors.

If problems persists, contact support with the following details:

  1. Log files from Desktop Central Server
  2. Log files from Desktop Central Agent pertaining to the computer where installation has failed.
  3. The Software Package that you were trying to install.

Questions