Never mind.  It's already over with.

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net]
Sent: Tuesday, October 13, 2009 5:15 PM
To: MS-Exchange Admin Issues
Subject: RE: Calendar permissions

I went back to check to be sure I'd read it right, and now there's an 
announcement that there's a series of webcasts on EWS.  The first one starts in 
45 minutes.

From: Campbell, Rob [mailto:rob_campb...@centraltechnology.net]
Sent: Tuesday, October 13, 2009 5:09 PM
To: MS-Exchange Admin Issues
Subject: RE: Calendar permissions


Hm.
I was reading the Exchange Team Blog last week, and they were talking about TE 
'09 being in November, and Exchange Connections being the same week.

(not that I could swing a trip to Berlin  either way, but I did manage to get 
LV).

From: Michael B. Smith [mailto:mich...@owa.smithcons.com]
Sent: Tuesday, October 13, 2009 4:57 PM
To: MS-Exchange Admin Issues
Subject: RE: Calendar permissions

Ilse van Criekinge did a presentation on the EWS managed api at TEC'09 in 
Berlin last month. It should be available from the conference downloads.

I look forward to seeing William's presentation as well.

P.S. Ilse joined Microsoft effective October 1. We'll miss her in the Exchange 
MVP world!

________________________________
From: Campbell, Rob [rob_campb...@centraltechnology.net]
Sent: Tuesday, October 13, 2009 5:50 PM
To: MS-Exchange Admin Issues
Subject: RE: Calendar permissions
You can use EWS  in 2007, but from what I've seen, you have to do a lot of work 
constructing the SOAP strings.

The Managed API seems to be a more direct access, and will work with 2007 mail 
stores.  It's not built into PS, but you can load that .dll into PS and use it 
from there.

This will send an email via the EWS API, and save a copy in your Sent Items 
folder.

You need to have the EWS dll installed, and edit $uri for your CAS server.
There's not much documentation out there on it yet, but it looks like it could 
be used for things like setting folder permissions, or doing a search and 
destroy on orphan delegates, among other things.

I believe William Lefkovics (sp?) is supposed to be giving a presentation on it 
at WinConnections in LV next month.



$dllpath = "C:\Program Files\Microsoft\Exchange\Web 
Services\1.0\Microsoft.Exchange.WebServices.dll"
[void][Reflection.Assembly]::LoadFile($dllpath)

$service = new-object 
Microsoft.Exchange.WebServices.Data.ExchangeService([Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1)
$uri=[system.URI] "https://006CAS-E1.cbc.cts/ews/exchange.asmx";
$service.Url = $uri

$message = New-Object Microsoft.Exchange.WebServices.Data.EmailMessage($service)
$message.Subject = "This is a test from EWS"
$message.Body = "I sent this from PowerShell via EWS."
$message.ToRecipients.Add("rob_campb...@ctsinc.biz")
$message.SendandSaveCopy.Invoke()



From: Michael B. Smith [mailto:mich...@owa.smithcons.com]
Sent: Tuesday, October 13, 2009 4:36 PM
To: MS-Exchange Admin Issues
Subject: RE: Calendar permissions

It's not present in Exchange 2010 PowerShell. You can do it with EWS in 2010 
(and thus I would assume in 2007 sp2, but I didn't check).

________________________________
From: Campbell, Rob [rob_campb...@centraltechnology.net]
Sent: Tuesday, October 13, 2009 5:31 PM
To: MS-Exchange Admin Issues
Subject: RE: Calendar permissions
That seems like another one of those things that you should be able to do with 
Powershell and that new EWS API.


From: Michael B. Smith [mailto:mich...@owa.smithcons.com]
Sent: Tuesday, October 13, 2009 4:24 PM
To: MS-Exchange Admin Issues
Subject: RE: Calendar permissions

Not to my knowledge. If you find such a thing, please let me know.

That being said, I did go take a look at pfdavadmin, and it should work on 
2003/2007.

http://www.itexperience.net/2008/10/22/set-calendar-permissions-with-pfdavadmin/

________________________________
From: Don Andrews [don.andr...@safeway.com]
Sent: Tuesday, October 13, 2009 5:19 PM
To: MS-Exchange Admin Issues
Subject: RE: Calendar permissions
I thought there is (was) a way to set the default permissions to reviewer - 
thus allowing anyone to see everyone else's calendar.

________________________________
From: Michael B. Smith [mailto:mich...@owa.smithcons.com]
Sent: Tuesday, October 13, 2009 2:03 PM
To: MS-Exchange Admin Issues
Subject: RE: Calendar permissions

You can give everyone full control to everyone else's mailbox pretty easily.

But to ONLY share the calendar, I think you'd have to write some code.

________________________________
From: James Rankin [kz2...@googlemail.com]
Sent: Friday, October 09, 2009 6:36 AM
To: MS-Exchange Admin Issues
Subject: Calendar permissions
Is there any way I can share every user's Outlook calendar with every other 
user in the company without having to request them all to manually allow it?

TIA,




JRR

--
"On two occasions...I have been asked, 'Pray, Mr Babbage, if you put into the 
machine wrong figures, will the right answers come out?' I am not able rightly 
to apprehend the kind of confusion of ideas that could provoke such a question."

http://raythestray.blogspot.com

**************************************************************************************************

Note:

The information contained in this message may be privileged and confidential and

protected from disclosure.  If the reader of this message is not the intended

recipient, or an employee or agent responsible for delivering this message to

the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by

replying to the message and deleting it from your computer.

**************************************************************************************************

**************************************************************************************************

Note:

The information contained in this message may be privileged and confidential and

protected from disclosure.  If the reader of this message is not the intended

recipient, or an employee or agent responsible for delivering this message to

the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by

replying to the message and deleting it from your computer.

**************************************************************************************************

**************************************************************************************************

Note:

The information contained in this message may be privileged and confidential and

protected from disclosure.  If the reader of this message is not the intended

recipient, or an employee or agent responsible for delivering this message to

the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by

replying to the message and deleting it from your computer.

**************************************************************************************************

**************************************************************************************************

Note:

The information contained in this message may be privileged and confidential and

protected from disclosure.  If the reader of this message is not the intended

recipient, or an employee or agent responsible for delivering this message to

the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by

replying to the message and deleting it from your computer.

**************************************************************************************************

**************************************************************************************************

Note:

The information contained in this message may be privileged and confidential and

protected from disclosure.  If the reader of this message is not the intended

recipient, or an employee or agent responsible for delivering this message to

the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by

replying to the message and deleting it from your computer.

**************************************************************************************************

**************************************************************************************************

Note:

The information contained in this message may be privileged and confidential and

protected from disclosure.  If the reader of this message is not the intended

recipient, or an employee or agent responsible for delivering this message to

the intended recipient, you are hereby notified that any dissemination,

distribution or copying of this communication is strictly prohibited. If you

have received this communication in error, please notify us immediately by

replying to the message and deleting it from your computer.

**************************************************************************************************
**************************************************************************************************
Note: 
The information contained in this message may be privileged and confidential 
and 
protected from disclosure.  If the reader of this message is not the intended  
recipient, or an employee or agent responsible for delivering this message to  
the intended recipient, you are hereby notified that any dissemination,   
distribution or copying of this communication is strictly prohibited. If you  
have received this communication in error, please notify us immediately by  
replying to the message and deleting it from your computer. 
**************************************************************************************************

Reply via email to