Hi, Just checked now I am at work and OWA lite does seem to stick on when you enable it, again I think I have issues at home with my Passport account being different from my Office 365 account. All in all I think I will move to this at home as well, it is working out slightly cheaper than my current provider and will probably give me a better service. I will probably do the migration in August/September. Thanks. Andrew. ________________________________________ From: Blind-sysadmins [blind-sysadmins-bounces@lists.hodgsonfamily.org] on behalf of Ryan Shugart [rshugart@pcisys.net] Sent: 20 June 2013 07:30 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] MS Forefront Protection for Exchange Thanks Andrew: The Powershell stuff sounds really cool actually, I've heard you can control Office 365 through Powershell but haven't seen much on how to do it. Granted I haven't looked much since I don't have an account to play with yet. The OWA lite stuff is good info, I use OWA lite primarily as well, I'm a tad surprised Microsoft wouldn't make that easier to enable, especially since they want governments and educational institutions to switch to the service. With OWA in Exchange 2007 and 2010, there's an accessibility tab under options where OWA lite can be forced on. Is this gone in 2013? Do you need to use your work around each time you log into OWA or just the first time? Thanks. Ryan -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson Sent: Wednesday, June 19, 2013 5:03 PM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] MS Forefront Protection for Exchange Hi Ryan and all, I have recently been given the opertunity to move a charity domain to the service under the non-prophit scheme. I mainly wanted it to get a decent email service with antispam, and for that I think we will have a good service. The main parts of the service I have used include the administrative console, and the OWA service. The administrative console is usable with speech, however, when you get to more complex areas, such as the user list, or the Exchange Online views, you start running into issues. I believe that MS have tried to make it as usable as possible, for example, when using the Exchange Online consoles, you can arrow through lists of users, use first letter navigation etc. However, somehow this doesn't tally up with the keyboard navigation in Jaws. One thing I have found is you can connect to your account using PowerShell, and access the Exchange commands using that. This is pretty much how I have built up the Exchange environment currently, by getting a list of commands and using PowerShell to run these. In this regard, I believe that Office 365 gives you a much more manageable environment than any other Exchange hosting company is able to offer. The real major problem I have though which is holding me back at the moment is OWA access. I use OWA pretty much when at work and other places to access email. I use the OWA lite version, because it gives me really simple access to mail using JFW navigation keys. Currently OWA Lite in Office 365 is a real pig to get at. It officially isn't supported (according to the help), though if you access your Office 365 account, there is an option to enable OWA lite as the default when you log into OWA. The problem is, that when you log into OWA, I believe Microsoft have customised it for Office 365, and this is getting in the way of the standard OWA stuff, which is preventing the OWA lite from being accessed. I have found probably an unofficial workaround for this, by playing with a test Exchange 2013 setup, which means you need to enter in a different URL on the address bar as follows: Log into your Office 365 portal, when at the OWA full feature screen, remove everything after the /owa and enter in the following text: ?layout=lite So my OWA session URL is now: https://pod51049.outlook.com/owa/?layout=lite I haven't had much luck saving this as a favourite, something in the authentication gets screwed up somewhere. I think this may be partly down to my Office 365 email account being under a different email address than my logged in Passport account in Windows 8. I can't get a standard OWA login screen, everything seems to be tied down to Passport logins with Office 365. Any this is my experience so far. Thanks. Andrew. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Ryan Shugart Sent: 19 June 2013 22:31 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] MS Forefront Protection for Exchange Andrew: What are your thoughts on Office 365 and Forefront Protection for accessibility? I'm considering moving my Exchange hosting to Office 365. How is OWA in Exchange 2013? Thanks. Ryan ________________________________________ From: Blind-sysadmins [blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Andrew Hodgson [andrew@hodgsonfamily.org] Sent: Wednesday, June 19, 2013 11:29 AM To: Blind sysadmins list Subject: Re: [Blind-sysadmins] MS Forefront Protection for Exchange Hi, I use a cloud based AV/AS system at work, although the one we use is quite expensive: www.mimecast.com I don't like AV on the Exchange server as it creates supporting headaches when applying updates in case the AV solution breaks something, I much prefer to leave it to a dedicated email scanning solution. Some other cloud based solutions I have used are as follows: Postini: www.postini.com - This is included in my hosted Exchange account. Spamtitan: www.spamtitan.com - this is a software spam appliance solution which works very well if you have an older machine you can dedicate to this. Sophos UTM: www.sophos.com - this is a very capable firewall product which can do a range of stuff including email scanning. I use this at some remote sites at work. I should also add that I am trialing Forefront for Exchange with bcab.org.uk as part of an Office 365/Exchange online solution. Thanks. Andrew. -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of Mika Pyyhkala Sent: 19 June 2013 17:30 To: Blind sysadmins list Subject: Re: [Blind-sysadmins] MS Forefront Protection for Exchange Hi, We have used cloud based solutions to guard against spam and viruses, instead of doing it on our Exchange server. A message first hits the cloud filtering gateway provider, is inspected, and only sent on to us if it passes the spam and virus filters. The message also never hits our environment if it is sent to a user without a valid email address. We used to use Postini, which is now part of Google. They appear to be changing the Postini service, so I'm not sure how it will work going forward, it seems like its being intigrated more with Google apps. The Postini administrative interface was quite accessible. We now use IronPort appliances by Cisco. We have our IronPort appliances in a Cisco cloud, so it is completely hosted by Cisco, although you can also have an appliance as your site. The IronPort appliance is in sync with our Active Directory LDAP, so we don't need to create users in IronPort. The IronPort appliance administrative interface is useable, although to access certain menus you have to route the jaws cursor to a link and mouse click on it. Best, Mika Pyyhkala Neighborhood Health Plan -----Original Message----- From: Blind-sysadmins [mailto:blind-sysadmins-bounces@lists.hodgsonfamily.org] On Behalf Of George Bell Sent: Wednesday, June 19, 2013 11:14 AM To: Blind sysadmins list Subject: [Blind-sysadmins] MS Forefront Protection for Exchange I seem to be drawing a complete blank finding anyone who knows anything about Microsoft Forefront Protection for Exchange Server. Do any of you guys know anything at all about it? ESET is due a hefty fee for renewal soon, and at $1 per month, per user, this appears to be a decent solution. BTW, it's taken since the New Year, but we look like having resolved our SBS 2010 performance issues. It seems that the Exchange 2010 part did not like having one Outlook 2003 client for a short period early on, and messed up the RPC binding order. Just a pity that the error reports didn't point in that direction. George. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins This message contains information from Neighborhood Health Plan that may be confidential or privileged. This message is directed only to the individual or entity named above. If you are not the intended recipient, please be aware that any disclosure, copying, distribution, or use of the contents of this email is prohibited. If you have received this email in error, please notify the sender immediately and delete the message and any attachments. _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins _______________________________________________ Blind-sysadmins mailing list Blind-sysadmins@lists.hodgsonfamily.org http://lists.hodgsonfamily.org/listinfo/blind-sysadmins