Facebook and Indian telecom Reliance Communications collaborated on the launch, of Internet.org, which was announced on Tuesday.
The post Facebook Partners to Bring Free Data Access to India appeared first on Web Hosting Talk.
SocketPlane, a new Software Defined Networking startup, is working on a solution to address the performance, availability and scale requirements of networking in large, container-based cloud deployments.
The post Startup SocketPlane Plans to Bring SDN to Clouds That Use Docker Containers appeared first on Web Hosting Talk.
Have you been thinking of finding out more information about buy youtube views ? Then read this article to find out more!
Find Articles, Free Articles Directory | Web Hosting Articles
Last week we have received a support request telling that a user is being locked from the Active Directory continuously. We turned to the user (who was very annoyed) and asked her about any mobile phone or tablet that she may be using that has the corporate email account defined. She told us that she used to be using a Nokia feature phone but she has switched to iPhone and not using the Nokia anymore. We kept that and began investigating the issue by the logs and saw that she was receiving “bad password” error in every five minutes with +/- 15 seconds of difference. Digging deeper, we saw that the bad password was coming from the Exchange Server, logs directing to the hardware load balancer. When we took a network capture from the load balancer. We have narrowed to log to the second that the account received a bad password error from the Active Directory to see the IP address that made the connection. And voila! The IP address that we found belonged to an IP from a mobile carrier. Once again we turned to the user and told that a device that belonged to her, connected to that mobile carrier is trying to connect with a wrong password. She told us that she had given her Nokia phone to the repair shop and most probably the shop is testing the phone. Ticket is closed.
The whole process showed us one thing: not having a Bring-Your-Own-Device is an invitation for a disaster and not taking the necessary steps is insisting on having a disaster. This support request could easily turn to be a crisis and even downtime. As I have discussed thoroughly in the article series, these disasters can be avoided.
Before rolling out the BYOD policies, make sure that you reevaluate your existing infrastructure. This includes password change policy, existing devices that will handle the additional load which will come from the employees’ devices, firewalls etc.. Consumer-grade devices will not be able to cope with the new devices’ loads: wireless access points will serve more devices, servers will answer more queries and switches, routers and firewalls will handle more traffic. Also the network bandwidth has to be upgraded.
Supported devices and the platforms and the level of support has to be clearly defined. At one point, you will inevitably find yourself trying to cope with various Windows and Mac OS releases, Linux Distributions, iOS, Android, BlackBerry versions, ChromeOS and God knows what else. Also you are not guaranteed that the users will be using the default applications; for example what will your answer be if a user opens a ticket that says he cannot sync his Google calendar with the company’s Exchange calendar using a third-party calendaring application on a supported Android release? Limit supported devices and supported applications. Or go mad.
Next on the list is employee training, which I have spoken extensively in my previous article. The training can turn out to be a “BYOD 101” class, but it is necessary. In terms of user/device security, keeping antimalware applications updated, keeping their data secure on untrusted networks and various other security issues should be clearly communicated. The users should be reminded that failing to comply with these could expose all the enterprise network to exploits. It is easy to train the users in advance rather than dealing with the aftermaths of a breach later.
Requiring device registration is a must. A simple registration form asking the device make, model, MAC address, mobile carrier and the user is enough. Considering the case above, with this information, we could easily figure out the device itself. Considering the overall infrastructure, this information would help us track the users who are bringing their devices, who are abusing the policy, block offending users and even block the devices.
As I have told in the second article in the series, BYOD is a swift revolution and it is not possible to stand against it. It is not time for the administrators to complain about the incoming devices and the anticipated headaches. It is time for the management to sit down, understand the BYOD trend and take the necessary steps to lessen the load both on the users and the IT personnel. With these tips, I cannot say that your company’s BYOD adoption will be painless, but I can guarantee that following these tips will lessen the pain.
October 21, 2013 — Sony Online Entertainment has reached an agreement with Brazilian game publisher Gamerica to bring online first-person shooter game PlanetSide2 to Brazil as a free-to-play game with in-game purchases made possible via UOL BoaCompra.
Keep on reading: SOE, UOL BoaCompra, Gamerica Partner to Bring Online Game PlanetSide 2 to Brazil
When the company works out the policies and procedures to the BYOD initiative, the next step is to start the company-wide training. The training needs to communicate the way the company will handle the BYOD transition. There are two types of employees that will be partıcularly harder to manage: the senior management who thinks the rules don’t apply to them and the youngsters who think the rules are there just to be bypassed. The company has to communicate clearly that the breach of the policies will be “treated appropriately” during the training sessions.
The first element in the training session should be the BYOD initiative: how it started, how it happened and why it is important for the company. Then the company’s acknowledgement of the initiative and its way of managing it should be clearly communicated. This introduction to the training will help the employees understand the company’s decisions better.
The next thing is to discuss the BYOD initiative in terms of supported devices, supported mobile operating systems, supported access to the company’s network and supported applications on the employee devices. It is important to tell the employees why and how such supported platforms are decided; for example the newer version of the productivity application is not yet supported because it has incompatibilities with a certain plugin used throughout the company.
Since BYOD is about employees’ own devices, training sessions are where the company has the chance to communicate with the employees about the policies.
Reimbursements are better covered in the training sessions. Almost all employees will be questioning how the company-related expenses (call minutes, data use, SMSs) will be handled. It is better to talk about all the reimbursements in detail, including how the employees will apply for them (experience: a hands-on exercise on reimbursement application will calm everyone down and keep their focus on the training).
Corporate access, security, data ownership, and employee responsibility has to be covered in the training (experience: since the whole issue will be boring to the most of the employees, it is better to talk about the main points shortly and have a Q&A session in the remaining time). The corporate access and security part should cover how the employees access the corporate network from the corporate Wi-Fi and from the public/hotel Wi-Fi, device password and loss/theft of the device. (I also recommend to include the Virtual Private Network (VPN), access to Customer Relationship Management (CRM) and automation tools (if any, such as SalesForce) in the session. Users may already be familiar with these systems but putting them into training is what’s important.) The data ownership should cover the corporate/personal e-mail, social networks, corporate/personal contacts and the company data on the employee-owned device. The employee responsibility is the part where the technical details, such as logging in to the corporate network, receiving software, applications and updates, the responsibilities to comply with the policies and the results of breaching the policies should be clearly defined.
The employees should be aware of the Enterprise Mobility Management (EMM) application that the company uses. The main misconception with the EMM application is about having someone else – the corporate IT in this case – managing a personal device. During the training session, talking about the EMM application, why it is there, what it does, how it manages the devices and how will the BYOD user will benefit from the application will be wholesome to both the company and the employee in clearing out the misconceptions.
Finally, the training session should include how the corporate support will be provided to the BYOD users. The points that should be emphasized should be the level of support for everyday use for each device, the escalation paths and the support cases with lost/stolen devices. If a self-service portal is already available on the corporate Intranet, it is better to inform and point the users to the portal during the training.
As many things in the life, BYOD is not a destination, rather it is a gateway to many possibilities. Once the companies take solid steps to BYOD implementation, most probable next step will be the mobilization of the corporate data. By this, I do not mean mobile access to corporate resources, as I have covered through the BYOD series. Rather, I mean shaping the enterprises for the mobility – from in-house developed applications to the Big Data infrastructure. From today, it is important to have a solid understanding of the mobile future and plan for it.
References
