K223's Posts

Ok so just to recap.  And I agree with vetting new versions before deploying them.  You can easily be caught off guard with issue's.  While security is import, it should be up to you to test these new versions timely and decide if they are right for your organization. So having version say 4.9 of the secure launcher on the console and if I have checked off always use the latest version of airwatch launcher under the service apps settings.  The mdm will and can only update to this 4.9 version correct?  I realize it will update older versions for better or worse.  So to automatically have a newer version pushed out than say the 4.9 I have on the console, would be check off push service app from the play store?   Thanks

Thanks for the responses.  I was able to solve this yesterday.  My configuration on the console side was good.  I did settle on Device-Based and Work Managed Device.  Still I was having an issue after enrollment with the two test devices I had on hand.  I would still get badged apps, no launcher and a personal and work environment on the tablet.  Finally after doing a complete factory reset on the tablet, and re enrolled.  The tablet did enroll in a at work for enterprise configuration.  I have a completely managed work tablet and no badged apps, along with the launcher being pushed down.  The launcher is also acting in a shared mode allowing for different accounts to logon.

We have many public "Shared" pc's in the agency.  They are initially enrolled with a generic local user solely created within WS1 as Corporate Dedicated.  These machines are not domain joined and auto login with a local windows account.  Everything is managed via WS1.  I imagine you could enroll them as Corporate Shared as well for multi user.  

Sounds great!  We updated as well several days ago.  I just don't have any devices on hand at the moment to test in the same way as the production units.  I did however work with one device and while the enrollment wasn't the same, the Intelligent Hub loaded quickly and no problems.  So here's to hoping.  

That's generally how it will go.  It will stay in that particular mode forever in most cases.  I have been struggling to find an available device that is free and originally configured for our ABM to simulate the exact enrollment.  I guess I can try to enroll a non assigned Ipad and see how this works out anyway.  I hope support can offer quick assistance with this problem. 

My issue seems similar to yours utilizing VPP and the app coming from the MDM.  It sounds as if we are not alone.  We are applying an emergency update to take us to the latest 2011 has to offer this afternoon.  I will try to locate a device on hand to test with and see by chance, if this help's things out.  The update relates to some other connectivity issue's we are having and was just informed about.  

Yes it's a tedious work around to get all your new enrolled devices loaded and functioning.  Still it was the only way at the time I could complete my deployments.  We are at WS1 2011.0.12 (On Prem).  I never did get to try this configuration on an earlier version of WS1.  Since we both have the same issue, and if this has been corrected.  It's a fix several versions newer I gather.  Curious to what support can tell you at this point.  

My apps are purchased through our ABM and then assigned by group.  I haven't done this manually to try.  Yeah it's terrible and really throw's a wrench into the enrollment process overall.  The only work around is to power cycle or kill the hub and restart it again.  I have not taken the issue to support as of yet.  

Just had a similar issue enrolling IOS devices via DEP and utilizing the Intelligent Hub.  We were using the latest version of the Hub and running WS1 2011.  After enrolling a device, apps would begin loading and the Intelligent Hub would start.  I have a staging profile that is used when the device is checked in, which puts the device in single app mode running the Intelligent Hub for the login.  The Hub would just continue to spin and seem like it was loading.  In most cases it never did present a login.  I would have to reboot the device several times or remove the profile and manually kill the Hub on the device.  After restarting the Hub, it would normally come up fine and ask you to allow or deny sending data to VMware.  Then it would come to the login.  At this point the device would function fine.  So this is only a couple of work arounds I used to get the device loaded.  At this point, I could not resolve the problem.  It made a simple task of enrolling devices in a several day, hands on process.  

Yes this does!  I was also able to confirm this with VMware as well.  However this user's app data will still reside on the tablet and not be removed between user's checking out the tablet.  It just get's separated.  If we were to use one generic user account for checkout, we would expose various user's data.   Would anyone know of a way to clear app data on the tablet at specified time internals either through commands in a profile or through the console?  Is there any 3rd party applications out there that can accomplish this?  Utilizing multiple user accounts (for checkouts) for this project is just not feasible.

Not to hijack the thread.  But I have a similar issue.  I have unenrolled a windows machine from the console and deleted the device.  But the hub client was not uninstalled.  I did that manually from add/remove programs.  When I went to reload the hub client and re enroll the device, the device thinks it's still enrolled and after loading the hub client.  But it's not and no way to enroll it again.  Maybe there are some registry values that are not being removed after I uninstall the hub?  Any assistance would be great.