jamesbmarshall

So can Live@edu - with ILM or FIM!

Aside from the ability to access your Exchange server even when your Internet connection is down (something that would be a problem for every 'cloud' service) what are the features of on-prem Exchange that you feel are must-haves that aren't offered by Live@edu? Regarding the offline access point - realistically how often is your Internet connection down during work hours? Out of hours outages (i.e. on a snow day, for example, when people need access from home) are more likely to have a bigger impact, in which case a cloud service is an ideal way to ensure continuity of communications, whether that's email, IM or document storage.

I'm glad support were excellent! Not in this case. Indeed, adding those parameters is possible for the command to still work, but the error in your screen shot clearly states that it cannot find a parameter to bind the argument "Resultsize" to. This is because there's a superfluous space between "-" and "resultsize". I have since gone back, pasted the exact bit of code from my blog into PS and tested it, reproduced the error, removed the space, and found that the code works as intended. The extra parameters for DateFormat and TimeFormat shouldn't be needed if you just want to overcome the first-login regional settings screen, but you can be all means include them anyway. The bit of code I posted up is designed to be run so that your end users don't have to go through the process of selecting the correct language and country, as often they accidentally make the wrong choice, or deliberately end up picking something for a laugh and then they're unable to figure out how to change it back!

That's not technically true... Get-Mailbox –Resultsize unlimited | Set-MailboxRegionalConfiguration –Language en-gb –TimeZone "GMT Standard Time" This little bit of PS works just fine - in your original post there is an extra space, so it's reading "Get-Mailbox - Resultsize..." which is wrong. That's a typo on the blog as well, but a quick bit of debugging would've picked that up! I'll correct the typo in the post.

Using your local Exchange as a relay (or the cloud) is not a bad way to do it, it's fully supported and reliable (well, as reliable as the relay, read into that what you will when it comes to your own Exchange server). Lots of customers opt for this with no problems.

It's something you build, and host, locally. Users log into that portal and are SSO'd to Live@edu. Implement a Single Sign-On Solution for Live@edu

No. Unfortunately you cannot customise outlook.com in any way. You can build a SSO portal that users log into that could take care of this, though.

Live@edu can handle multiple domains - you could migrate your existing server (@school.county.sch.uk), and add the new domain too. Users would have a primary SMTP address of [email protected], and a second as their old [email protected]. Point your MX records in the right direction and off you go! See: Accepted Domains

Have a look here: MSDN Blogs or Outlook Web App

You do need to use PowerShell, yes. connect to another mailbox - Outlook Live Answers Live@edu is driven by Exchange 2010 SP1 at the back end, it is effectively hosted Exchange but not every function available in an on-premise environment is available in 'the cloud'.

Are you aware of the Multi-Mailbox Search feature? Multi-Mailbox Searches

Live@edu is built on Exchange Online which is a totally different platform to Hotmail. In order to give access to the Live service features like SkyDrive and Groups every user is provisioned using the Live ID mechanism which requires access to those domains. Students access their Exchange Online mailboxes by navigating to http://www.outlook.com, but filtering all of the Live properties will negatively impact the service.

Outlook 2010 will pick up the email address field from AD, so as long as it is populated and your autoconfig is setup correctly when users come to run Outlook for the first time they literally only have to click next through the wizard, pop in their password and away they go.

I think what you're talking about is the shared address space with on-premise relay option - something that is documented and supported; more info: Configure a Shared Address Space with On-Premises Relay You will need to register Live@edu on its own domain - typically "live.myschool.sch.uk" or "service.myschool.sch.uk" or something appropriate. You'll need to prove ownership and set MX records accordingly to ensure mailflow into, and out of this domain 'as normal'. Following the steps outlined in the documentation above should help you with the rest. Equally, as RabbieBurns says, you could just register a whole new subdomain - "student.myschool.sch.uk" and give them new addresses. It all depends on your requirements!

You could just create all of your staff in Live@edu as external contacts... that's one option.

As I understand it access to the remote PowerShell features is unaffected; you'll continue to access them the same way you do today.

Some of you may remember back in September Microsoft announced some changes that would need to be made to the way your users access Live@edu, and some changes you'd need to make to your SSO configuration. The deadline for that was pushed back to March 1st 2011; however, there's been a revision to that date - for more information on the revised timeline, and a reminder of the changes you'll need to make take a look at the UK Live@edu blog: Outlook Live Required URL Changes - UK Live@Edu Blog - Site Home - MSDN Blogs They're not major changes - but they will have an impact on the way you use the service.

Insider tip: rather than logging your calls by email, phone them through the first instance. If it's a high priority issue for you, it's a high priority for the support teams but you need to tell them that.

Which version of Exchange are you running?

Is the account you're attempting to connect with GALDisabled? If it is you need to manually enabled MAPI connections through PowerShell otherwise this won't work. If it's not GALDisabled... hmmm, would need to know more.

Gareth, this post is very old and considerably out of date, and also talks about corporate, rather than educational offerings. Microsoft offers Live@edu to schools, colleges and universities for free for staff, students and alumni. This includes access to an Exchange Online mailbox, and a variety of Windows Live services including SkyDrive + the Microsoft Office Web Apps. There are no on-premise requirements, and no hidden costs. You can sign up from scratch today, for free and you wouldn't need to pay a penny. I'm sorry for the sales talk there; I normally avoid it as it's a bit inappropriate of me to use it here, but would hate for you to use that article as gospel when decision making, when it is very definitely out of date.

DNS Records for Outlook Live - this page details the relevant DNS options, and there are some links at the bottom which you may find useful.

If it is for such a small number of test users why not just give them temporary passwords and have them change them? If your admin staff are savvy they won't give up their passwords, and if they do they probably need training about security. ILM is probably overkill for a small test, but once it is up and running it takes the headache away from provisioning / de-provisioning at the start and end of every academic year. Best case scenario is that you have it tied in to your MIS, so that when your admin team do the yearly enrollment your AD users and Live@edu accounts are automatically provisioned through ILM (or FIM...). Outside of Live@du there is a strong case for ID management as more and more systems require some for of ID (MIS, cloud services, databases, VLEs, etc) but have no way to bring it all together.

If you're talking about Live@edu you could set them up with random passwords and inform users that they would need to change them on first login.... however if you're using some ID management like ILM you could set up PCNS and just get the users to change their AD password which will prompt PCNS to sync that change to the cloud... There's no way trying to figure out your own users passwords sounds like a good (or easy, or possible) idea.

You can leave them if you wanted to - Live@edu is free for alumni as well, but in a school environment this might not be something you want to have to manage... By de-provisioning an account the next time that user goes to log in they are asked to nominate a new LiveID to transfer the ownership of the SkyDrive; however, they don't get to keep their mail. An advantage for keeping your leavers on for a few months, or even a year, would be that if your sixth form students track their UCAS applications through their school account they may need access beyond their last days at school - leaving them on for a while at least gives them the chance to take a backup of their mailbox before it is deleted.