VMware Workspace ONE Community
Almondli
Contributor
Contributor

Can't delete device on workspace one uem cloud portal (ver: 2011)

When I tried to delete devices, the system shows that the devices are being deleted, but stop deleting after a few minutes and return to normal (the "deleting" is gone)

This occurred after the cloud upgraded to workspace one uem version 2011

Does anyone have a similar problem/a solution?

Labels (1)
Reply
0 Kudos
10 Replies
RichB2u2
Hot Shot
Hot Shot

We are having a similar issue in our on-premise environment 2008. I have submitted tickets. There is an API process that works one by one and a SQL database command possible too but it should work in the console!

Reply
0 Kudos
Jasper2510
Contributor
Contributor

Hello Almondli,

We have the same issue. When we try to delete a device we get the message delete failed.

Did you already have a solution to this problem?

Reply
0 Kudos
J4yJ4y
Enthusiast
Enthusiast

Same issue here in SaaS (version 20.11.0.4 (2011)).
While discussing with  VMware support, this was called a known bug.

Reply
0 Kudos
rsaulitis
Enthusiast
Enthusiast

Same issue here version 2011 onprem.

Reply
0 Kudos
rsaulitis
Enthusiast
Enthusiast

Temp workaround if someone need to delete quickly device. Tested and it works in version 2011.

https://kb.vmware.com/s/article/80230?lang=en_US&queryTerm=AAPP-10567

Reply
0 Kudos
Peabadmin
Contributor
Contributor

We are on 2101 DSaaS and still got this problem...
It's begining to be a mess in the console! 😒

Reply
0 Kudos
DimitrijPrudkij
Enthusiast
Enthusiast

the same issue with 20.11.0.16 on-prem

Reply
0 Kudos
RichB2u2
Hot Shot
Hot Shot

Support says this should be fixed in version 2104. When that gets released for on-premise is unknown though. Here is their article which says deleting devices from the device list may not work but individually from the details page or using API calls will work:  https://kb.vmware.com/s/article/82359

atlauren
Contributor
Contributor

Same issue here.  It showed up after upgrading on-premises to 2011.19.  Updated to 2011.21 as a release notes item looked promising.  But the problem still exists.  

We now have a support ticket open.  Sigh.

Reply
0 Kudos
timber2
Contributor
Contributor

always the same problem wgb

Reply
0 Kudos