Cool Solutions

Managing a virtual android device (Android x86) through ZENworks



By:

February 1, 2017 2:28 pm

Reads:943

Comments:0

Score:5

Print/PDF

ZENworks 2017 provides mobile management capabilities. You can get a first-hand experience of the features provided by trying it out on a virtual Android device if you do not have a real device handy.  The latest Android release (as of writing this article) Android-x86 6.0-r2 is available for download at http://www.android-x86.org.

The following steps may be followed to get an Android x86 virtual device deployed on a VMWare ESX Server and managed by ZENworks:

  1. Download the Android-x86 6.0-r2 iso image and copy it to the ESX datastore.
  2. Create a new virtual machine with 8GB HDD, 1GB RAM, 1/2CPU. Select CentOS as the target OS. Also, select the downloaded ISO for the CD Drive of the newly created virtual machine.
  3. Start the virtual machine and make sure the virtual machine is booting from the Android ISO.
  4. Install the Android OS (Screenshots 1 to 15 below).
  5. Restart the system in debug mode by selecting the second option from the grub menu (screen shot 16).
  6. Modify /mnt/grub/menu.lst, by adding “video=-16* nomodeset vga=833” to the parameters given to the kernel (screen shot 17). The UI will now be accessible after a reboot.
  7. Navigate to settings -> Accounts and add a google account. You may create a new account for this purpose or use your existing personal Gmail credentials.

Google PlayStore can now be accessed to install the ZENworks App (Screenshot 18 to 20).

  1. Once the ZENworks app has been installed, login to the ZENworks App and enroll the device just as you would enroll any other Android mobile device. Now, this virtual device can be managed just as any other Android mobile device.

To find out more on installing the ZENworks App and ZENworks requirements, please refer to the ZENworks Documentation available at https://www.novell.com/documentation/zenworks2017/zen_zmm/data/bookinfo.html.

Things to try:  Device Enrollment policy, Mobile Security Policy, Mobile Device Control Policy, Send Message Quick Task, Lock/Unlock Quicktask, Unenroll Quicktask etc.

 

Screen Shot 1:

Screen Shot 1

Screen Shot 2:

Screen Shot 2

Screen Shot 3:

Screen Shot 3

Screen Shot 4:

4

Screen Shot 5:

Screen Shot 5

Screen Shot 6:

Screen Shot 6

Screen Shot 7:

Screen Shot 7

Screen Shot 8:

Screen Shot 8

Screen Shot 9:

Screen Shot 9

Screen Shot 10:

Screen Shot 10

Screen Shot 11:

Screen Shot 11

Screen Shot 12:

Screen Shot 12

Screen Shot 13:

Screen Shot 13

Screen Shot 14:

Screen Shot 14

Screen Shot 15:

Screen Shot 15

Screen Shot 16:

16

Screen Shot 17:

Screen Shot 17

Screen Shot 18:

Screen Shot 18

Screen Shot 19:

Screen Shot 19

Screen Shot 20:

Screen Shot 20

 

3 votes, average: 5.00 out of 53 votes, average: 5.00 out of 53 votes, average: 5.00 out of 53 votes, average: 5.00 out of 53 votes, average: 5.00 out of 5 (3 votes, average: 5.00 out of 5)
You need to be a registered member to rate this post.
Loading...

Tags: , ,
Categories: Endpoint Management, Technical, ZENworks, ZENworks Configuration Management, ZENworks Mobile Management

0

Disclaimer: This content is not supported by Novell. It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test it thoroughly before using it in a production environment.

Comment

RSS