1 of 1 people found this helpful
Hello and welcome to the community,
The first thing I'm noticing here is that you are specifying to use a distribution server in the deployment template. You always need to make sure that all necessary patch files for deployment are downloaded and synchronized to the distribution server - otherwise it can cause issues like this.
Other than this - based on the last tracker messages you were receiving it could be an issue with the remote scheduler service we use on the target system.
For the scheduler:
-Check in the Protect console > Tools > Options > Scheduling to verify what scheduler settings you are using.
-Ensure that the scheduler port is open for communication from the console system to the target systems (default port is TCP 5120).
-You can try reinstalling the scheduler service. The easiest way to attempt this is to go into Manage > Scheduled tasks within Protect, then locate the target system in the left column. Right click and choose "Refresh selected". Once this is done, then right click on the machine again and choose Scheduler Service > Uninstall. Once this appears to be done then right click on the machine and choose Scheduler Service > Install. Try deploying again to see if this helps.
Updates are downloaded on the distribution server.
I think there is a problem with the Remote Scheduler. I tried your solution; refreshing the machines, uninstalling and reinstalling the Scheduler service. Earlier, all machines in the task list except the Protect-machine was greyed out. Now they have a coloured icon and if i select anyone of them they have pending jobs now. I'll let it be and see if the patches are deployed.
Thank you so much for your help!
Unfortunately it didn't work. Protect is set to use VMware scheduler on port 5120. The distribution server is in fact the Protect-server. How can I make sure the patch files are synchronized?
Here are some events from three diffirent servers.
I have earlier tried to re-install the agent, but that did not solve the problem. It seems that the patches are not copied to the machines. Nearly all of my customers machines are virtual.
I logged on to a server and opened up the Protect Agent and I get the following error message. I double checked the location and there was indeed no Protect.manifest.xml. I also checked the agent on a couple of other machines and the same error occured.
I also found on some servers thet had the .xml-file but the manifest was too old. I have in Protect Used Refresh Files but it seems like I get errors downloading the xml-files. I also tried to update the binaries on the server that had the old manifest without luck.
1 of 1 people found this helpful
It looks like your first issue presented is with agentless deployment, but now there is an agent involved here. Is the issue with one or the other, or both? It seems like this issue is becoming a little more complicated, and it will probably be best to open a case with us (support) directly.
Contact information for support can be found here:
It would be best if you can use the steps provided in the following KB's to obtain log files while reproducing the issue(s):
Protect console logs:
Thanks Adam! I will look into this.
Actually, I got some servers to update after finally being able to refresh the files on the Shavlik-server and then by manually updating agent binaries and patch data. I also had some luck with manually reinstalling the agents on some servers using this guide: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2031364 . Right now I am trying to figure out why not all servers got updated.