Where to place Google Website Optimizer Control Script to avoid IE quirks?
If you are using Google Website Optmizer Control Script to test and improve your website, be careful about where you place the control script in your html page. IE won't like it if the script is placed before the Document Type Declaration. IE might render the content in distorted form severely impacting visitor experience.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
Just put the control script after the Document Type Declaration and you should be fine.
Administrators have role-based privileges in SureMDM
Our latest Mobile Device Management platform SureMDM supports role-based administration. Whenever a user is created, it is assigned a user type depending on the user's role. Following are the available user types:
- Super User
- Admin User
- Help-desk User
- Manager User
- End User
Super User
Super User is created during system installation and is the first and most powerful user in the system. A Super User can perform all tasks (Complete user and device management).
Admin User
Admin User is created by a Super User and can do all device management activities.
Help-desk User
Help-desk User can only perform remote support of mobile devices. They cannot perform other device management activities like installing apps on the mobile devices or adding/deleting the devices from the system etc.
Manager User
Manager User can view the list of mobile devices which are allocated to his/her team members. Besides, a manager can also track a worker's location on the map.
End User
End User is basically the user who is using the mobile device. End user can log into SureMDM and can issue remote wipe command in case a device is lost, can try to locate the device or view the call-log among other information.
SureMDM is in private beta. If you are interested in a demo, drop us a line at techsupport@42gears.com.
What’s so special about number 42?
Well take your pick...
http://en.wikipedia.org/wiki/42_%28number%29
And that's not all. There is something for the future. 
How much time to get up and running with SureLock?
Well..just did a quick test. I was able lock down a "fresh" Windows Mobile device in less than a minute, 54 seconds to be precise. Following steps were taken (Note: SureLock Studio was already installed on the desktop):
- Launched SureLock Studio
- Clicked New button on the toolbar to create a new project
- Added Internet Explorer as allowed application
- Clicked Build button to generate the CAB file
- Clicked Install button on the toolbar to transfer CAB file to the mobile device (connected with the desktop over ActiveSync) and installation was started automatically
- Once CAB installation was completed, SureLock started on the device locking it down to just Internet Explorer
Project creation and CAB building took 15 secs whereas installation took remaining 39 seconds.
Once the CAB has been built, we just have to install it on other handhelds as long as there is no change in the kiosk configuration which will require building the CAB file again.