If I bind the manual group to Agent file and then bind the template in the intelligent group, the client will first upgrade Agent. After reboot, it will fail to distribute the template and prompt "client command not support".
Please make sure the Agent version running on the target client is the management system version provided. The template must be bound to the Agent version layer, or else it will fail when Agent upgrade takes place.
CCCM will check the extension of Windows image file. If the image file has no extension, please add the extension of ".dds" and then try again.
It is incurred due to the manual adding of LANG=POSIX environment variable after installing the operating system. Delete this variable and reinstall the database to solve this problem.
For Microsoft patches and XPe patches, both automatic upgrade and manual upgrade are supported by the client.
The system adopts the task scheduling mechanism. For offline clients, the installation task will be executed automatically when the client is turned on next time. Automatic upgrade is also supported for XPe patching and client upgrade.
If the printer name contains character "@" and such printer is added for the first time, the operation will fail. You can delete "@" or add another printer with name containing no "@", and then add the same type of printer with name containing "@".
- The client agent is not started when the client is shut down. Therefore, the system will indicate "Success" once the remote wakeup message is sent. The reasons why the client doesn't wake up may include:
- The client doesn't support remote wakeup (not supported in hardware, such as CT2000 network adapter).
- The management server and the client are not on the same network segment.
- The client's network has a virtual subnet.
The commands assigned by the system are executed by means of task. During configuration, you are only selecting the desired options and will not take effect on the client. By clicking "Apply" button, it means the user needs to execute the configuration task and the configurations will be applied to the client.
Probable causes include:
- The firewall or antivirus software blocks file download. Solution: Disable the firewall or antivirus software.
- The target client doesn't support such task. On the information panel or in historical task, you will see the detailed execution result of such task. If the result indicates that the task is not supported by the target client, then it is normal to see the task fails.
Probable cause:
You have changed the IP address of the server, but haven't restarted the UnitedWeb service. Solution: Restart UnitedWeb service or directly restart the server.
1. Whether the client is online?
2. Whether the client is being managed by this server?
While adding the task, make sure you have typed the full path, which shall contain not only the target directory but the filename as well.
1. Verify whether the client has been started and whether the connection between server and
client is OK.
2. Verify whether Simple File Sharing has been enabled on the client; if yes, disable this feature.
3. Verify whether the username and password are correct.
4. Verify whether firewall has been enabled on the client, including Windows firewall; if yes, disable the firewall temporarily until successful monitoring, or you may add the program to "Exceptions".
1. When using the monitoring system for the first time, the system will detect whether JRE has been installed according to user's browser environment. If not, a dialog box will pop up to prompt you to manually download and finish the installation of JRE. You can then reopen the browser and start monitoring.
2. When you use Firefox and proxy server to access Internet and if the proxy server happens to be ISA2000, the Firefox browser will freeze and cannot carry out monitoring. Please download and install JRE 1.5 or use IE browser for monitoring.
3. If the monitoring was successful and now comes the problem of white screen or black screen, please close the remote assistance window and re-click "Remote Assistance". If the problem cannot be solved, close the browser and try again.
4. When a client configured to high resolution enables Remote Desktop service and in the meantime a user connects to the client through RDP, you may encounter VNC failure if implementing remote assistance through the management tool. Restart VNC service to solve the problem.
Possible causes:
- Service port is blocked by the firewall.
- Data server is not installed.
- The default port of 9999 is occupied by another program and thus the service cannot be started.
After the database password has been changed, the database password configured in CCCM must be updated. Please refer to "Server Configuration Tool > Database" sections in User Manual to change the database password configured in CCCM.
Log in CCCM management interface and then click the icon at the top right corner to
view license information.
Log in CCCM management interface and then click the icon at the top right corner to view version information.
1. Firstly, check if the client found has been added to management by another server (check whether the "Management Server" column on the search interface is blank). Only unmanaged clients can be added to management.
2. Secondly, verify whether your management system has expired. When the licensed period has expired, you won't be able to use the system to add new clients.