PiqueABoo

Found out how to check this, by sneaking up to it looking for something completely different in a powershell session. Run this cmdlet: get-throttlingpolicy That displays lots of vaguely intriguing parameters, but look for RecipientRateLimit (or add stuff to the command so that's all you see). That must be the one, not least because the tenancy I'm playing with says it is 1500, plus I've got an audit log that says it was 500 back in Nov 2011.

If you're going to keep using scripts then get yourself on some scripting training. I don't do VBS but at a glance that looks like an excerpt from some bigger script and I *think* half of it is redundant (the group sid caching) and objComputer2 doesn't reference anything, so it wouldn't work.

::sits back and waits for full comparison with every mail system on the planet including any limits imposed by any given SMTP feed service you might have upstream of your own mail server::

Groups can workaround this on Live@Edu (but it's rarely practical for lots of reasons), but this isn't a Live@Edu versus Google thread ;b

Might be tied in with in progress Jan 2012 update, or not happen in Europe for ages, don't know. But if it is "upcoming weeks" you can check if yours has changed: get-mailboxplan | select displayname, recipientlimits Edit: Trusted some blog that reckoned this, but on second thoughts that's the max number of recipients on one message not the max in 24 hours, so you can't use it to check

:: I wanted that to fill some void, but it doesn't mention Live@Edu so I presume it doesn't work for that? If it won't round PSTs created via some POP3 mail service and stuff them into Live@Edu mailboxes, then I don't have any significant scenarios I think it will help with... if turned on then rounding up Outlook auto-archives perhaps, but it's not obviously worth the trouble.

Just stumbled over this on a blog I've never seen before (some Education Partner site[1]): Bit in bold is worth knowing because I've had folk legitimately hit the 500 limit e.g. Primary trying to mail parents/guardians to say the school might be closed, then is closed, then will likely be open tomorrow etc. Outlook Live accounts have historically been 500 recipients per day. Microsoft has recently updated this policy to be in line with the Exchange Online offering in Office 365. All newly provisioned tenants will see these new limits immediately. For those customers who are already on Live@EDU, you should either see these now or you will see the changes over the upcoming weeks. There is a recipient rate limit, often called a sender limit or sending limit, for cloud-based e-mail accounts. This limit defines the maximum number of recipients that can receive e-mail messages sent from a single cloud-based account in a 24-hour period. The recipient rate limit for Exchange Online is 1,500 recipients per day. [1] Not in an announcement sent to Live@Edu tenancy Contact mailbox. Not on outlookliveanswers. Not on James Marshall's blog. Etc. The biggest problem I have with cloud-Exchange versus local Exchange is being aware of changes because there is no obvious single place you can go for the info. It's the biggest "cultural" difference from local where e.g. new SP comes out so you read what's new and know you've got that when you install it, or you go change some config and know you've done it.

150-200mm here, just finished helping Sprogette make SnowLady cradling SnowBaby(!), their SnowRabbit(!!) and SnowArmchair(!!!)... managed to talk her out of the cat, coffee table, sofa, bed, TV, igloo etc... cunningly using all the snow that was on the sloping drive with Teacher t'other half's car at the top of it.

It definitely is postgreSQL. I don't know, but I'd expect the backup to have been made via pg_dump, and it can be restored via pg_restore. Whether there are things you should do before/after restoring is anyone's guess e.g. I assume you'd need RM service that talk to the DB stopped etc., and if it's an old backup then you might get discontinuity between that and user and computer objects in AD. Why do you want to do this?

+ Puzzled. How does that meet the apparent requirement "staff don't want to be bothered checking multiple accounts though.".

Uh huh.. prior to posting I'd read a thread on the RM forum where a significant part of the general drift is the difficulties deploying and running a VPC XP+VS Pro image which apparently is a 5-6GB VHD and needs a minimum 2GB RAM. Now I've spent more years professionally s/w engineering than the kids who'll start learning with that have lived, and the conversation just seems surreal. Insane. I definitely get graphical programming a la Scratch, Kodu etc. (8yo Sprogette currently loves them almost as much as Moshi Monsters) and I wouldn't want anything less than a decent syntax highlighting editor a la Notepad++, possibly more. But VS Pro? Windows SDKs? What the.. ?!? Not working for a s/w house team any more (where some of the bells & whistles do matter) if I'm writing dotNet my usual weapon of choice is VS C# *Express* because it does everything I ever need to do, and some code I'd rather write myself than have written for me. Why a beginner would need VS Pro is completely beyond me and they won't need the Windows SDK because half of that essentially relates to C++ native code which I assume definitely isn't on the curriculum(?), and web browsers make the dotNet half redundant, not that this is about learning dotNet surely? It will be interesting to see how it plays out because there's a very observable split: One side is doing the same old "must use industry standard mega tools" stuff and throwing everything but the kitchen sink at it, the others might actually have taken some clear hints from some of those ICT v. Computing reports etc. Whatever, I'll be betting on the ones with the Raspberry Pis and the like. See also my sig.

Location:Watford? If that is where your school(?) is located then I do know the LA there have done a lot of Live@Edu, so I suggest you talk and assuming they are willing, get them to suffer this because your scenario is not straight-forward: There are a couple of hard bits, several issues to consider, and possibly some kind of RBC(?) as well as the RM you're ditching to contend with. Some key points that might help explain why I think this is non-trivial: 1) Exchange 2003: You definitely can move entire mailboxes (mail, calendars, contacts, task etc.) to Live@Edu. For 20 it might be easier to dump them to PSTs and manually use Outlook to import them into Live@Edu mailboxes, but I wouldn't want to do that unless the mailboxes are small. Alternatively you configure an RPC Proxy on your Exchange box (a relatively arcane task) and get Live@Edu to do the work, and it does work but won't do contacts and distribution lists kicking around in AD so you will either need code/script magic for that, or to remake them at Live@Edu manually. If you've got shared calendars/contacts in Exchange public folders you can use PSTs and Outlook to get those across. 2) RM EasyMail: a) If the users only use the web UI or IMAP4 then the mail is all on RM servers and Live@Edu can do the work, but the process will only get mail items and folders not contacts because they are not supported by the IMAP4 protocol. Last time I touched this an Easymail *user* could export their personal address books in some prehistoric Outlook CSV export format that the Live@Edu import doesn't understand, so that CSV needs a format conversion before the users can import them into their Live@Edu mailbox. So how good are your users at doing what they're told? Easymail address books also implemented some kind of grouping which got permanently lost. b) If your users have used POP3 to download all their e-mail then you have a problem. If Outlook was used you'll have PSTs scattered around and the most efficient strategy might be to round them up, exmerge them into Exchange mailboxes and then use the RPC proxy method in 1. If Outlook Express or anything else was used to download & delete from the RM server, then you're on your own. 3) You have Easymail *and* an Exchange, so you have two different domains and there is always a risk that you want to move to using a shiny new third domain? Does "one person one address" imply any merging of two source mailboxes into one target Live@Edu mailbox? Regardless there is some potentially "interesting" complexity to work through here, and you may need two tenancies subject to whether staff are happy for students to see their mail address in the GAL and various other factors.

What's the Exchange server version?

I've seen *Primary* schools with a laminated class list - teacher does the electronic registration and simultaneously updates that list with washable (not too washable) pen at the same time. Laminated list lives on wall inside one of those cheap transparent A4 wallet thingies and goes outside with them when alarm goes off. All the logic in that works for me.

Keeping role and personal mailboxes separate is clearly a good thing, so tell 'em it's not possible and they'll have to cope which isn't hard if you connect Outlook. Failing that, I haven't done it but you could try this: 1) Make [email protected] a personal mailbox 2) Make a distribution list called [email protected] and add [email protected] as the only member. 3) Give j.bloggs Send As rights for the distribution list in 2. If you do try this uh.. brilliant theory, let use know the outcome please, especially if it works (useful for multiple folk fielding mail for a generic address)

If you want to import a PST: a) Connect full Outlook client to the target Live@Edu mailbox and use it's import PST functionality - that works fine., b) Buy some tool from somewhere (they exist)

But what about the children?!? How will they learn anything ever again unless they use the biggest, shiniest environment on the planet?

Depends on what you want to do. Whenever I've set about finding old users or computers I haven't cared about precision, so I'd be happy to use LastLogonTimestamps more than say 100 days old and not worry if that sometimes gets a few accounts that actually last logged on 84-100 days ago coz they're old too. Chasing round for the freshest LastLogon is the kind of thing I'd do if I wanted to know if someone (or a computer) logged on recently e.g. this morning, yesterday etc.,

Look again... - lastLogon gets updated every time on the DC where the logon happens but that doesn't replicate. - lastLogonTimestamp only gets updated when the a logon happens if the current value is more than 9-14 days old. If it is changed that new value does replicate. Your script uses lastLogonTimestamp and a 90 day timespan thus risks picking up some users who in the worst case, last logged on 76 days ago. They're still old and for this kind of thing it's not often an issue.. if you want to guarantee "at least 90 days old" then just use a 104 day timespan instead of 90. OTOH if you're running this daily and must get accounts as soon as they hit 90 days old you will need to look at lastLogon on all the DCs and check the age of the freshest one.

Examplars. [That get updated as the capabilities evolve] I'll use the easiest case, a complete config walk-through for typical Primary which implements all the obvious stuff: enroll domain.. make a school calendar and three groups for reviewer, author, editor... rules so mail from The Government[tm] bypasses Junkmail and optionally repeat for LA and perhaps .sch.uk and/or sch.uk (schools nonsensically abandoning that really are a complete PITA).. make 'all users', 'all staff', 'all students' groups with the obvious send to restrictions.. make a disclaimer (initially disabled, but text can simply be changed to suit then turned on).. prevent Recipient Management role from being able to touch Administrator account then you can get the school office MIS record creator simultaneously making new accounts on Live@Edu.. turn on closed campus and bypass it for 'all staff'... etc. You could of course give them less than 20 lines of powershell to do all of that in minutes, but then they wouldn't learn anything to adapt for future use. The only bit I've mentioned where there's much of a debate to be had is whether to get them using custom attributes during account creation and thus use some DDGs.. I'd prefer that and I'd like a link to AD accounts, but lack of access to custom attributes in the ECP essentially kills it and regardless it's probably mostly pointless at the smaller end of the scale. Next: Secondary without FIM.. recipe caters for more of everything, custom attributes and the extended ones for DDGs and selective access, plus an AD link (samAccountName or perhaps AD object GUID) are your friend etc. Next: Secondary with FIM. PS: Migration of content to Live@Edu mailboxes doens't go in these these, because that part obviously varies. Nor is branding, fiddling with OWA for the same reason, although turning off the MSN et al links is probably the best default.

I take it you read my pedantic comments in your related thread?? Not a huge deal but nevertheless something you should be aware of when doing anything based on when a user/computer last logged on, especially if it's a scheduled task that makes changes based on the result. -- More broadly: Perhaps it's just what turns up at the top of Google searches but I don't get why QAD keeps getting used for things like this rather than the out-of-box MS ActiveDirectory module on 2008 R2. Then again I get around a bit, so regardless of which might be easiest I will always pick tech that will be there are opposed to tech that might need installing. It's just as easy with MS in this case with their Get-ADUser or alternatively there is Search-ADAccount that can pull out inactive computer/user accounts based on a fixed date or timespan e.g. 90 days, that could then be thrown at Disable- or (don't do it!) Remove- cmdlets.

Some interesting quotes, in the sense that some folk there apparently didn't get the memos with ACADEMIC DISCIPLINE in every other sentence, and I'm pretty sure CAS sent one or two of those. Don't they have stickies in their forums in which they can write "It doesn't [bleeping] matter, provided it adequately supports teaching the following concepts:"? I wouldn't expect anyone in the real-world to care much about what language some kid learnt a little bit of at school e.g. the apparent reality according to the RS report (one they mostly side-stepped) is that most Unis don't care about Comp Sci A-Levels, they want Maths because it means you have a fighting chance of staying the course. I suspect the best answer to which programming language goes something like this: That one over there, because there are lots of ready-made lesson plans and pretty videos for the web2 generation, so you [Teacher struggling with transition from "digital literacy"] won't have to work quite so hard.

Madeira in the late 90s, didn't have the slightest clue it would be anything other than mundane, but that turned out to be a fast captivating experience in a kind of seriously turbulent imminent collision with volcanic mountain averted at the last moment by a rapid lurch to the side followed by a somewhat wobbly slam down onto the short runway for some pretty heavy braking to avoid an imminent drop into the Atlantic accompanied by many passenger screams of genuine terror.. way. [by-and-by there was lots of applause] I guess some of that might still apply but think they've added something like a km to the runway length since then, which feels like a loss.

I ever really mess up, I'm gonna blame it on pixel-deprivation during my formative years at the mercy of one of those notoriously barbaric 20th century state educations.

Fair enough, MS's "throw another box at it" enterprise approach to nearly everything is a complete PITA in Education world, especially when folk dutifully do that and by-and-by end up with enough servers to run a small planet. I'm certain that basic syncing could be done with some relatively small code running on one DC, which I assume is the story for Google? Anyone with it care to comment on how much code there is for that, it's resource requirements etc.? Hmm.. maybe I should write one and sell it for £250. I've made lots of AD enumerating/fiddling code, I've made some serious code that's long been doing powershell remoting to Live@Edu (and not relevant but yet more doing EWS to fiddle with mailbox content) it's just the bit in the middle that missing.. would be relatively easy, but rather tedious to write the delta finding/fixing stuff. -- What's really stopped me bothering is powershell. You can open a 2008 R2 AD powershell console, use it to connect to Live@Edu and then use output from the AD cmdlets as input for Live@Edu/Exchange cmdlets. Quick example one-liner: get-aduser -filter {Name -like 'test*'} | % {get-mailbox $_.SamAccountName} That gets a bunch of users[1] from AD and on the Live@Edu side lists their mailboxes[2]. Perhaps it's just me, but this kind of thing is **more fun** than some app with a GUI. Won't sync your passwords though, but there's nothing else I can imagine wanting to do that should be a problem. [1] Whose Names begin with "test" [2] Assumes we created the Live@Edu accounts with samAccountName in one of the several fields that get matched by that particular get-mailbox command.