In my role as an engineer for XenMobile, I'm doing a lot of inserts, and there are some things that I tend to do setup XenMobile, after it is up and running. To be honest, when you finish setting it and completing the first-time use wizard, you have the feeling that you have achieved a lot.
But then you suddenly with a blank dashboard left and may not know what to take next in attack. Here are some of the recommended "next steps" to get you started.
enroll your first device
Grab an Android device (and later repeat this with an iOS device) and go to the Play Store. Search for "Worx Start" and are the "Worx Home Citrix" app to see, you should download and install. Start the app and it will ask you to enter a "UPN, e-mail or server." For now we will keep things simple and just add our server. In my case, the "acme.xm.citrix.com." It will ask whether to enroll; we say yes. Next you will be asked for your username / email and password, then asked WorxHome to activate the device administrator to the offer should be accepted. In this way WorxHome can actually adopt any policies that you will create later. It may also ask for, whether WorxHome access can have certain privileges, such as whether it can access your memory. Finally you will see a "My Apps" screen in WorxHome be shown which is initially empty.
Congratulations, you have enrolled your first device!
If you log in the XenMobile console at this point, you will see an Android device in your dashboard. Success!
creating a first policy
How to manage XenMobile, you'll be configuring many guidelines, so it is useful to familiarize yourself with this right now , A large policy Setup immediately is to remove the WorxHome Alert icon on Android devices. You may have noticed that when you enrolled your Android device, you now have a WorxHome icon in the notification area (in the top left corner).
In fact, the end user can not remove it. No matter how much they might try to fire her, the WorxHome symbol will remain persistent in their list of alerts. This symbol will remain so always lock on the screen. This could end understandably vexed, as all their other releases are traded on and released
To address this, configure the XenMobile Server console. -> Device Policies, and click "Add". In the dialog box, select the section "More" and "XenMobile options" (under the XenMobile Agent Category).
appears expand that now appears in the wizard, give your new policy a name (Ex.: "Remove Work Home Message Icon"), only Android target, they set "traybar alert - hide traybar symbol". on, and on the last screen they point back to "All Users"
Now to your device and start WorxHome. Instead of waiting, we will encourage WorxHome to draw the new policy down that we just created. Click on the menu icon in the upper left corner, and then click Settings. Go to "Device Information" and click the "Update Policy" button. You will notice that now the symbol WorxHome be gone!
press your first app
Calling this an "app" might be a stretch, since we just go an external Internet to push link. But the key concept is that it appears in the device WorxStore and you will configure able to start it
In XenMobile Server console. -> Apps, and click "Add". In the dialog box that, click "Web-Link" is displayed. You will now be in a short wizard. Give it a name like "My Storage", then a description and URL. In my case, I'll use "Helpful Links to Share File" as the description and "https://acme.sharefile.com/" as the URL. "Hosted apps on the internal network" to OFF, and click Next. Assign it to "All Users" and click "Save".
on the unit Go back and start WorxHome. You will find that familiar white screen with the text "Add apps WorxStore". It's time to click! Once the connection is established, you will be your "My Storage" app listed in WorxStore.
Click on the app, then click "Add". After a while, it will be added to your home screen. Let WorxHome and you will see, to sit there next to all of your other applications!
This is a good start. After thi, s you'll probably want your first mobile app wrapping going to attack, but that will have to be covered in a separate blog post.
0 Komentar