VMware Cloud Community
jocoll75
Enthusiast
Enthusiast
Jump to solution

Recent Tasks displays "Taking virtual machine screenshot " followed by "Delete File"

In the past couple of days, I've noticed some Recent Tasks in vCenter when I log on to my vCloud director web portal. After logging in and selecting My Cloud, a bunch of Recent Task appear stating "Taking virtual machine screenshot " followed by "delete file" I don't know what could be causing these tasks to start. According to "Details about the task in vCenter Server: Take virtual machine screenshot (2001467)" KB,  I've checked my vmware.log file to see if there are any corruptions to the vm's and did not see any issues. I've restarted the services on the cells and restarted the cells themselves, which did not resolve the issue. I do have a service request in with vmware, they have asked me to restart the management agents on the host. Being that I can not restart them until after business hours, I'm hoping to find some other options until I can restart the management service on the esxi hosts. I'm currently on vCloud director 5.5 and vCenter server 5.1.

Reply
0 Kudos
1 Solution

Accepted Solutions
jocoll75
Enthusiast
Enthusiast
Jump to solution

After discussing this with vmware tech support, it turns out that, the screenshots are a part of the vSphere upgrade. There is a way to filter it out, once I have the instructions on how to filter these alerts, I'll post it here.

View solution in original post

Reply
0 Kudos
3 Replies
jocoll75
Enthusiast
Enthusiast
Jump to solution

After discussing this with vmware tech support, it turns out that, the screenshots are a part of the vSphere upgrade. There is a way to filter it out, once I have the instructions on how to filter these alerts, I'll post it here.

Reply
0 Kudos
brianoc
VMware Employee
VMware Employee
Jump to solution

Hi jocoll75,

Did you get any further with filtering these out?

Thanks!

Reply
0 Kudos
Sathish_1121
Contributor
Contributor
Jump to solution

Hi,

Any new progress in this effort. This is happening in my infrastructure as well. Is this an occurrence after a specific vSphere upgrade and harmless to ignore?

Thanks.

Reply
0 Kudos