chrisbrown

time.bat should read "net time" and it will still work.

I'm an IE hater since day dot. Been using Firefox for longer than I can remember, and am a recent convert to chrome (I'm a bit of a minimalist). HOWEVER. I have been using IE9 for a while now (through beta, RC and now RTM), and I must say I am extremely impressed with it. I mostly use it for sites that use client controls unsupported in Chrome/Fx such as BES. I'm one of the biggest IEbashers around. I was the guy who went to the IE9 beta launch party to pick on the IE evangelists and was piping up "chrome does that" "firefox did that 3 years ago" etc. On the record: I like it.

You need to open Exchange Management Shell. You are using vanilla PowerShell. For clarity, everyone: UNC paths and Exchange database canonical paths are completely separate ideas. It's not dissimilar to an AD canonical path. Exch01\StorageGroup1\StudentsStore is a logical path. It implies that on a server called Exch01 there is a storage group called StorageGroup1, inside which there is a store called StudentsStore. This could well be at the physical path M:\MailboxDatabases\ChickenWings\Bobsyouruncle.edb ( (which could also be shared as \\Exch01\MailDBs\Bobsyouruncle.edb). Please do not make the mistake of confusing file paths with canonical mailbox store paths, disaster will ensue. I hope this has not been too abrupt, I don't mean to be rude.\ === Edit: ergo, you should do this: 1. Open Exchange Management Shell (this icon: http://fla.im/ezfBpK ) 2. Run this command (replace $canonicalPathToStore with the path of your DB. I don't have Exchange 2007 handy, but I presume this can be done with Get-MailboxDatabase | fl) Get-Mailbox -database $canonicalPathToStore | set-mailbox -recipientlimits 1 3. You can then run this command to count how many mailboxes across the organisation received the setting: (Get-Mailbox | Where {$_.RecipientLimits -eq 1}).Count

Wouldn't have a clue, have never used it. I just remember a trainer mentioning it was the 2008/R2 successor to RMS...am I wrong? If so..sorry!

Or AD Federation Services (ADFS) if you're up to 2008/R2. Very cool stuff, but probably more effort than you want to go to. There's a lot of management overhead involved with this.

Don't forget to tick "Include inheritable permissions from this object's parent" under -> Security -> Advanced. If you don't do this, ActiveSync will not work. This is a known problem if your account is/was a domain/enterprise admin. The problem is that your account will not have inherited the ACLs for the Exchange server. Also - why on earth is your regular account a domain admin? Have you no concern for security? Never ever EVER give your logon account Domain/Enterprise/Anything Admin permissions or you're asking for trouble. You're leaving yourself open for this: Executing Code On Behalf Of Someone Else - Dreaming in PowerShell - Powershell.com As well as countless other exploits. Please, for the safety of your network, data, users and job, create yourself an administration account. I (and the rest of the sensible IT community) recommend you do this for all your IT staff. Create an account in the form of a_ or similar. I can't stress how important this is.

Cool! Let us know how you go

Can you be sure it's not a layer 8 error? Could it possibly be that your xml files don't meet the xml spec and are considered corrupt by office?

..What?

GP will let you delete the registry entry: Ned Pyle's way: Deploying Custom Registry Changes through Group Policy - Ask the Directory Services Team - Site Home - TechNet Blogs I would suggest getting rid of OLK 2003 ASAP, Exchange 2010 doesn't support it by default, and you can bet quite safely that support will only become harder and harder to find.

Out of interest, do one of these: Get-ADServerSettings | fl and see what it returns... This should at least trigger your mind as to whether something is funky with your DC config in Exchange.

No worries, let me know if there's anything else.

My two Ex2010 servers are both chewing over 20GB of their 24GB available. Hooray for cheap DIMMs!

I think you'll find they're called routers, and the reason for this segmentation is to reduce collisions on the network by creating smaller broadcast domains. Switches don't do this. The reason 100m is the limit is due to signal degradation over the distance. Same theory as USB.

Go for it. I reckon as long as your users still have full control over %userprofile% then they should be right...someone correct me if I'm wrong.

Might roll this one out in my test environment first..Has anyone else run it yet?

Since you haven't provided much detail, I'm going to assume you're talking AD. You would be best to feed your Imported CSV to a Where-Object first. Then you can query it against a boolean return, such as Get-QadUser. The below assumes your CSV username column is "username". Import-Csv $Student | ? { ! (Get-QadUser $_.Username) } | % { "Create the user } The pipeline flow goes something like this: Import a list of new students as an object: Import-Csv $student Where the user does not exist: ? {!(Get-QADUser $_.username)} ? = Where-Object ! = returns null Get-QADUser = You need to install the Quest AD cmdlets to use this, but Get-ADUser will also work if you have RSAT installed $_.Username = username field from the rows provided Let me know if this makes sense...

We had a similar problem, best thing to do was sit and monitor the event logs on the DC. This provided a realtime view of what was happening (and what wasn't)

Obtaining a SAN cert is really the way to go. It's a little more expensive but will save you lots of hassle in the long run. Put all names in that any user is likely to access your servers via. It's important that you put your external OWA URL as the primary subject name in this cert too.

Also, keep in mind that "little switches" have a tendency to lock up and stop passing traffic. Problem is, by the time this happens, you (or your successor) may have forgotten that there is even a switch in this room. I'd suggest making a note of this somewhere appropriate so that when this room falls off the network you remember to restart this switch. Chris

Interesting you say this - we've just finished setting up 802.1x backing onto 2008 R2's NAP on our WiFi. Works an absolute treat. Just have to move 2000 or so remaining computers across to the new SSIDs.

My logon script: http://farm3.static.flickr.com/2414/2398292022_d3e8a53bf3_o.jpg

We use this exact method to block phones, non-school provided laptops etc from getting addresses. There's no reason the device cannot have a manual address entered, but for the most part this works.

Check your task history. Select your task in Task Scheduler then go to the History tab. It will show you the events logged from the previous runs of the task. This should provide you a good springboard to start from.

Awesome. First thing to test - close all instances of Outlook and try with OWA