This message was deleted.

Yup - biggest head scratch was delay in wem service resolving AD SIDS for migrated objects - other than that, nothing to report

That's actually one area I'm worried about. We have a large number of WEM implementations, and it seems like in each of them we have an incredibly high number of assignments - both groups and users. And I'd bet that a sizeable portion of them are old and should have been cleaned up. May have to get Ops to do that before we start the migration.

Sh1t in sh1t out I guess! Always good to take the chance to clean

Apart from (obvious after the fact) limitations on storefront published apps, and the silly workarounds needed to configure custom app icons, the migration was pretty painless.

icon handling will get better soon 🙂

I requested allowing users to just put in a network path to ICO files, like you can put network paths in for application EXEs, or for that matter, like you can put in a network path for ICO files in the on prem version. Response i got back was " security risk". So i gave up asking...

There will be lots of nice new flows for troublesome items, there is a whole UX team focused on getting it right - If you want to see a snippet of something cool, go enable the external task preview feature in WEM Cloud Service - that will bring alive the external task application type and give you a feel for how things will flow moving forward with other action types etc

Yeah, I like where it's headed.

The trick with icons for me (this is cheating)… build in lab, export actions then import actions. Icon fuggery begone - but it will be better soon natively

Interesting. We're talking building in WEM Service, right?

I build loads on prem and then export to cloud - but that really is cheating and purely for icon madness

Okay, that's easy enough to do with our current on-prem WEM environments. I'll keep that in my back pocket.

I used the database migration tool. Works pretty good, after that I export and import the apps because of the icons.