I have experienced the same as wbrown and michael stump in this case. Appeasing Dr.'s in the past has been the standard response. I don't see the issue with corralling the highly edjucated uninformed users when need be. The thing is with BYOD each user has their own experience with their list of likes and dislikes creating an extensive list of devices to interact and interfere with the network. HP has a wifi mouse that shows as a Rogue network and can cause interference with your wifi connection when your neighbor is using this device. Trying to search this bad boy out was a beast; and thats just one case of a device not connected to the network. We have a guest network, but in order for Dr.'s to get the use out of their tools purchased with their own money or department funds that do not match the institutional standard they must be on our internal secure wireless network. Now the issue is their browsing habbits and a lack of security software when they come on site. This tends to keep our information security department quite busy. I am just happy the monitoring team has been removed from the remediation process(though i exect we will be handed back the process due to my teams attentiveness to detail and ability to find more specific data than some of our engineer's). A Patients connection to MS Live is crucial when tied to a bed for treatment, so we pass this traffic through. Revently we enabled on of our guests with a faster 'internal' connection for the use of a Vgo to attend classes. Our pipe for the quest is constantly at 95 to 100% due to our size so it was needed for his connectivity(A/V stream)
↧