Exchange 2010 SP3 RU9 / 2013 CU8, ROLLUP and Android problems

by butsch 26. May 2015 02:16

A remote mailbox user receives the following error message when he or she tries to configure Exchange Active Sync account on an Android device:

Setup could not finish

Failed to search Exchange server automatically. Enter settings manually

https://support.microsoft.com/en-us/kb/3035227?wa=wsignin1.0

http://blogs.technet.com/b/exchange/archive/2015/03/17/announcing-update-rollup-9-for-exchange-server-2010-service-pack-3.aspx

http://www.microsoft.com/en-us/download/details.aspx?id=46372

Solution:

If the MobileSyncRedirectBypass feature is causing the problem, you can turn it off by editing the web.config file for the Autodiscover protocol:

  1. Locate the web.config file for the Autodiscover protocol:
    1. For Exchange Server 2013 MBX, the file is in the following location:

      %ExchangeInstallPath%\ClientAccess\Autodiscover

    2. For Exchange Server 2010 CAS, the file is in the following location:

      %ExchangeInstallPath%\ClientAccess\Autodiscover

  2. Open the web.config in Notepad, and then change the existing string from "true" to "false."
  3. Save the file.
  4. Run IISRESET /Norecycle.

Follow these steps on all CAS servers that will receive Autodiscover queries from devices.

Tags:

Exchange 2010 | Exchange 2013 | Microsoft Exchange | WSUS

Exchange 2007/2010/2013 with SPLIT DNS and ONE single Certificate

by butsch 3. March 2015 23:59

Problem:

You have to renew an Exchanger SAN/UC-Certificate and you can't do this anymore after 2015 because it contains a NON EXTERNAL First Level Extension like ".LOCAL".

  1. Rename the Full Windows Domain in a 1 year project and have fun
  2. Integrate a SPLIT DNS as below, Bend all Exchange URL to the same FQDN

Main Technet Link:

http://support.microsoft.com/kb/940726/en-us

 

I personally don't like this solution since you may in most complex case end up in trouble with some special cases like "RPC-over-HTTP" (Outlook anywhere) and some Autodiscover functions.

On the other side don't like Wildcard Certs for this because if you have that the other departments want to use the same Certificate and at the end everyone uses it. Worst it lays around on laptops and Servers then if you don't Controll it strict.

Currently still March 2015 this is the only solution quick and fast if you customer has a First Level Windows Domain with .LOCAL. Most it's urgent because Cert has expired.

 

Just to mention that there is another way but this needs planning and time

Enterprise way:

Internal Domain: Cover these with your own internal Certificate Authority (Ask if you have one, make a project separate for that because it's sensitive and complex) .

External Domain: Use a Cert Provider SAN/UC-Certificate as we had before for all external FQDN

This enterprise mix however leads us to splitting the CAS/OWA Directories on separates SITES within the IIS (Because of only 1 Cert per IIS-Site) or we make single separate CAS Server for internal and external (Which Microsoft does not want us).

On the other side if we have Load Balancers for the CAS mostly those separate CAS are not in the Load Balancer HA team.

 

 

Timeline for SAN/UC Certs with Local ending or non-external First level (www.technet.local)

http://www.butsch.ch/post/Exchange-Certificates-Aenderung-CAS-Outlook-mit-local-Domain.aspx

Such a SAN Certificate which includes LOCAL is not valid anymore after some date. And you can't reorder it. (Screenshot)

Powershell: Get-exchangecertificate | fl

In Green BOX there are the First Level Domains .LOCAL Domains that you can't COVERY anymore in ONE Cert in 2015.

INTERNAL DNS NAME:    customer.local (The Active Directory Domain)

EXTERNAL DNS NAME:    customer.ch (Your Webserver, FTP, MX-E-Mail Domain from external)

Third level DOMAIN: async.customer.ch

Why can't I renew?

 

Because we can't make a UC/SAN-certificate after November 2015 anymore we have to convert the DNS into SPLIT DNS setup. That means we copy the Extern DNS into Internal DNS. Even if you CAN renew it WILL only run until November 2015 with some Cert Issuer.

http://www.butsch.ch/post/Exchange-Certificates-Aenderung-CAS-Outlook-mit-local-Domain.aspx

Make the SPLIT DNS

 

See links at end for more help on the SPLIT DNS.

SPLIT DNS Copy External ZONE File to internal Active Directory DNS

  1. Get the info from External ZONE file from the Provider ISP like customer.ch. Ask them you need an extract (copy) of the ZONE file for your external Domain.
  2. Do a new Active Directory integrated Forward ZONE File with same name "customer.ch" internal
  3. Make the A-Records internal so INTERNAL users can reach www and ftp also from internal (These are shown on the right side). Make "FTP", "WWW" point to same IP as the external. (If you don't do that your INTERNAL users will not be able to reach the External Website or Cloud Service you use with your ISP)
  4. The ASYNC in OUR sample POINTS to the IP of the Exchange 2010 CAS
  5. On the External DNS the ASYNC points to our Firewall and then to the Exchange 2010 CAS

This is how this may look.

Get the NEW SINGLE FQDN Certificate

 

 

We need to change all FQDN that Exchange uses for different Service now to the SAME FQDN the SINGLE Domain Cert runs on.

FQDN Single Domain Certificate was ordered for: async.customer.ch

OLD Entry in Exchange somewhere:

https://async.cutsomer.local/OAB

 

NEW:

https://async.cutsomer.ch/OAB

 

Analyze the values you need to change by Powershell

 

 

-------------------------------------------------------------------------------------------------------------------------------------

CHANGE1

get-ClientAccessServer | fl Identity,AutodiscoverServiceInternalUri

WAS:

Identity : CAS1

AutoDiscoverServiceInternalUri : https://async.customer.local/Autodiscover/Autodiscover.xml

SET NEW:

Set-ClientAccessServer -Identity CAS1 -AutodiscoverServiceInternalUri

-------------------------------------------------------------------------------------------------------------------------------------

CHANGE2

get-WebServicesVirtualDirectory | fl Identity, InternalUrl , ExternalUrl

WAS:

InternalUrl : https://cas1.customer.local/EWS/Exchange.asmx

ExternalUrl : https://mobile.customer.local/ews/exchange.asmx

SET NEW:

Set-WebServicesVirtualDirectory -Identity "CAS1\EWS (Default Web Site)" -InternalUrl https://async.customer.ch/EWS/Exchange.asmx

Set-WebServicesVirtualDirectory -Identity "CAS1\EWS (Default Web Site)" -ExternalUrl https://async.customer.ch/EWS/Exchange.asmx

-------------------------------------------------------------------------------------------------------------------------------------

CHANGE3

get-OABVirtualDirectory | fl Identity, InternalUrl, ExternalUrl

WAS:

InternalUrl : http://cas1.customer.local/OAB

ExternalUrl : https://mobile.customer.local/OAB

SET NEW:

Set-OABVirtualDirectory -Identity "CAS1\OAB (Default Web Site)" -InternalUrl http://async.customer.ch/OAB

Set-OABVirtualDirectory -Identity "CAS1\OAB (Default Web Site)" -ExternalUrl http://async.customer.ch/OAB

-------------------------------------------------------------------------------------------------------------------------------------

If you don't have UTM Service (Unified Messaging leave that)

Change Values in Exchange 2010 GUI

 

Change all other things in Exchange 2010 GUI on the tabs below to corresponding values.

Some you may have changed above already. Check them twice.

 

 

 

  • Do this for all possible location Web app/Activesync/Offline etc.
  • DO this for INTERNAL and EXTERNAL (Set the SAME value)
  • Do not change AYNTHING behind the FQDN name as example
  • AT the end Restart Exchange or do a CMD.exe then IISRESET

 

OLD:

https://async.cutsomer.local/OAB

NEW:

https://async.cutsomer.ch/OAB

 

Activate the Certificate in Exchange 2010 GUI or Powershell and RESET IIS

 

Activate the new SINGLE Certificate in Exchange for IIS.

 

Get-exchangecertificate | fl

Get the GUID sample: 020564B683E9D540DA0DF20A

enable-exchangecertificate -identity 020562B683E5D540DA0DF20A -Services "IIS"

 

AT the end Restart Exchange:

CMD.exe then IISRESET

 

References:

 

SPLIT DNS, Windows Server 2008: The Definitive Guide

https://books.google.de/books?id=H7RgtZEgUvsC&pg=PA137&dq=split+dns&hl=de&sa=X&ei=a9H2VMrNJ4TXyQPBkoFg&ved=0CCcQ6AEwAQ#v=onepage&q=split%20dns&f=false

SPLIT DNS with ISA

http://www.isaserver.org/img/upl/isabokit/9dnssupport/9dnssupport.htm#_Toc63649957

Exchange PRO

http://exchangeserverpro.com/ssl-requirements-for-exchange-when-certificate-authorities-wont-issue-certificate/

Main Technet Link

http://support.microsoft.com/kb/940726/en-us

 

Tags:

Exchange 2007 | Exchange 2010 | Microsoft Exchange | Server 2012 R2

Exchange Server Release und Build numbers SEP 2012

by butsch 24. September 2012 03:40

 

Follow MS person on Social posting Release on SP 2007/2010/2013

https://social.technet.microsoft.com/Profile/MSFTJoaoRibeiro/activity

 

Exchange Server Release dates

Product name

Build number

Date

 Microsoft Exchange Server 2003

 6.5.6944

 6/30/2003

 Microsoft Exchange Server 2003 SP1

 6.5.7226

 5/25/2004

 Microsoft Exchange Server 2003 SP2

 6.5.7638

 10/19/2005

 Microsoft Exchange Server 2007

 8.0.685.24

 12/9/2006

 Microsoft Exchange Server 2007

 8.0.685.25

 12/9/2006

 Microsoft Exchange Server 2007 SP1

 8.1.240.6

 11/29/2007

 Microsoft Exchange Server 2007 SP2

 8.2.176.2

 8/24/2009

 Microsoft Exchange Server 2007 SP3

 8.3.083.6

 6/20/2010

 Microsoft Exchange Server 2010

 14.0.639.21

 11/9/2009

 Microsoft Exchange Server 2010 SP1

 14.1.218.15

 8/24/2010

 Microsoft Exchange Server 2010 SP2

 14.2.247.5

 12/4/2011


 
Exchange Server 2007 Service Pack 1

Product name

Build number

Date

KB

 Microsoft Exchange Server Exchange 2007 SP1

 8.1.240.6

 11/29/2007

  

 Update Rollup 1 for Exchange Server 2007 Service Pack 1

 8.1.263.1

 2/28/2008

 KB945684

 Update Rollup 2 for Exchange Server 2007 Service Pack 1

 8.1.278.2

 5/8/2008

 KB948016

 Update Rollup 3 for Exchange Server 2007 Service Pack 1

 8.1.291.2

 7/8/2008

 KB949870

 Update Rollup 4 for Exchange Server 2007 Service Pack 1

 8.1.311.3

 10/7/2008

 KB952580

 Update Rollup 5 for Exchange Server 2007 Service Pack 1

 8.1.336.1

 11/20/2008

 KB953467

 Update Rollup 6 for Exchange Server 2007 Service Pack 1

 8.1.340.1

 2/10/2009

 KB959241

 Update Rollup 7 for Exchange Server 2007 Service Pack 1

 8.1.359.2

 3/18/2009

 KB960384

 Update Rollup 8 for Exchange Server 2007 Service Pack 1

 8.1.375.2

 5/19/2009

 KB968012

 Update Rollup 9 for Exchange Server 2007 Service Pack 1

 8.1.393.1

 7/17/2009

 KB970162

 Update Rollup 10 for Exchange Server 2007 Service Pack 1

 8.1.436.0

 4/9/2010

 KB981407


Exchange Server 2007 Service Pack 2

Product name

Build number

Date

KB

 Microsoft Exchange Server 2007 SP2

 8.2.176.2

 8/24/2009

  

 Update Rollup 1 for Exchange Server 2007 Service Pack 2

 8.2.217.3

 11/19/2009

 KB971534

 Update Rollup 2 for Exchange Server 2007 Service Pack 2

 8.2.234.1

 1/22/2010

 KB972076

 Update Rollup 3 for Exchange Server 2007 Service Pack 2

 8.2.247.2

 3/17/2010

 KB979784

 Update Rollup 4 for Exchange Server 2007 Service Pack 2

 8.2.254.0

 4/9/2010

 KB981383

 Update Rollup 5 for Exchange Server 2007 Service Pack 2

 8.2.305.3

 12/7/2010 

 KB2407132

   

Exchange Server 2007 Service Pack 3

Product name

Build number

Date

KB

 Microsoft Exchange Server 2007 SP3

 8.3.083.6

 6/20/2010

  

 Update Rollup 1 for Exchange Server 2007 Service Pack 3

 8.3.106.2

 9/9/2010

 KB2279665

 Update Rollup 2 for Exchange Server 2007 Service Pack 3

 8.3.137.3

 12/10/2010

 KB2407025

 Update Rollup 3 for Exchange Server 2007 Service Pack 3

 8.3.159.0

 3/2/2011

 KB2492691

 Update Rollup 3-v2 for Exchange Server 2007 Service Pack 3

 8.3.159.2

 3/30/2011

 KB2530488

 Update Rollup 4 for Exchange Server 2007 Service Pack 3

 8.3.192.1

 7/7/2011

 KB2509911

 Update Rollup 5 for Exchange Server 2007 Service Pack 3

 8.3.213.1

 9/21/2011

 KB2602324

 Update Rollup 6 for Exchange Server 2007 Service Pack 3

 8.3.245.2

 1/25/2012

 KB2608656

 Update Rollup 7 for Exchange Server 2007 Service Pack 3

 8.3.264.0

 4/16/2012

 KB2655203

 Update Rollup 8 for Exchange Server 2007 Service Pack 3

 8.3.279.3

 8/13/2012

 KB2734232


Exchange Server 2010

Product name

Build number

Date

KB

 Microsoft Exchange Server 2010 RTM

 14.0.639.21

 11/9/2009

  

 Update Rollup 1 for Exchange Server 2010

 14.0.682.1

 12/9/2009

 KB976573

 Update Rollup 2 for Exchange Server 2010

 14.0.689.0

 3/4/2010

 KB979611

 Update Rollup 3 for Exchange Server 2010

 14.0.694.0

 4/9/2010

 KB981401

 Update Rollup 4 for Exchange Server 2010

 14.0.702.1

 6/17/2010

 KB982639

 Update Rollup 5 for Exchange Server 2010

 14.0.726.0

 12/13/2010

 KB2407113


Exchange Server 2010 Service Pack 1

Product name

Build number

Date

KB

 Microsoft Exchange Server 2010 SP1

 14.1.218.15

 8/24/2010

  

 Update Rollup 1 for Exchange Server 2010 SP1

 14.1.255.2

 10/4/2010

 KB2407028

 Update Rollup 2 for Exchange Server 2010 SP1

 14.1.270.1

 12/9/2010

 KB2425179

 

 Update Rollup 3 for Exchange Server 2010 SP1

 14.1.289.3

 3/7/2011

 KB2492690

 Update Rollup 3-v3 for Exchange Server 2010 SP1

 14.1.289.7

 4/1/2011

 KB2529939

 Update Rollup 4 for Exchange Server 2010 SP1

 14.1.323.1

 6/22/2011

 KB2509910

 Update Rollup 4-v2 for Exchange Server 2010 SP1

 14.1.323.6

 7/27/2011

 KB2579150

 Update Rollup 5 for Exchange Server 2010 SP1

 14.1.339.1

 8/23/2011

 KB2582113

 Update Rollup 6 for Exchange Server 2010 SP1

 14.1.355.2

 10/27/2011

 KB2608646

 Update Rollup 7 for Exchange Server 2010 SP1

 14.1.421.0

  8/13/2012

 KB2743248

 
Exchange Server 2010 Service Pack 2

Product name

Build number

Date

KB

 Microsoft Exchange Server 2010 SP2

 14.2.247.5

 12/4/2011

 

 Update Rollup 1 for Exchange Server 2010 SP2

 14.2.283.3

 2/13/2012

 KB2645995

 Update Rollup 2 for Exchange Server 2010 SP2

 14.2.298.4

 4/16/2012

 KB2661854

 Update Rollup 3 for Exchange Server 2010 SP2

 14.2.309.2

 5/29/2012

 KB2685289

 Update Rollup 4 for Exchange Server 2010 SP2

 14.2.318.2

 8/13/2012

 KB2706690

 
Exchange Server 2013 Preview

Product name

Build number

Date

KB

 Microsoft Exchange Server 2013 Preview

 15.0.466.13

 7/16/2012

  

Tags:

Exchange 2007 | Exchange 2010 | Microsoft Exchange

Exchange: Setting max mail sizes in mail flow

by butsch 24. July 2012 05:25

Default size is 10MB and that is just how it should be. Even if freeware mail provider has 50MB Limits. It's not a law but it's historical SMTP/RFC value from and people have lived with it for 15 years. Then some nerd put it up 5MB and others had to follow.

Everyone who lets a e-mail attachment larger than 20MB in the www should be blocked and blacklisted.

Use FTP, SharePoint or a commercial Data room solution (Not free stuff) if you are too stupid for ZIP or Splitting ZIPS.

 

Find all users in Exchange who have special Sizes:

Get-Mailbox -FIlter {MaxSendSize -ne $null -OR MaxReceiveSize -ne $null} | ft Name,MaxSendSize,MaxReceiveSize

Per User in GUI:

Per Exchange Organisation with Powershell:

Set-TransportConfig -MaxReceiveSize 50MB -MaxSendSize 50MB

These are per attachment size settings:

set-transportconfig -ExternalDsnMaxMessageAttachSize 40mb -InternalDsnMaxMessageAttachSize 40mb
get-TransportConfig | fl

 

 

 

On the separate Receive Connectors:

 

Here is a logfile:

Here is how to check the Sizes with telnet. Make sure your Mcafee or other virus Software does not block SMTP/Ports25 from test client.

 

 

Do Not forget to check the SIZE on your in-house SPAM Filter

 

Exchange will DROP the e-mail IF you have a mismatch in the size in your internal networtk. As example if you have a Fortimail 100 and an Exchange 2010 and the sizes are different. Fortimail will not re-try internal per default.

You will loose that e-mail!

 

Some links:

http://exchangepedia.com/2007/09/exchange-server-2007-setting-message-size-limits.html

 Text from RFC and why it's OK some device just drops the email which is too big.

http://tools.ietf.org/html/rfc1870

 

6.2  Client action on receiving response to extended MAIL command

 


   The client, upon receiving the server's response to the extended MAIL
   command, acts as follows:

   (1) If the code "452 insufficient system storage" is returned, the
       client should next send either a RSET command (if it wishes to
       attempt to send other messages) or a QUIT command. The client
       should then repeat the attempt to send the message to the server
       at a later time.

   (2) If the code "552 message exceeds fixed maximum message size" is
       received, the client should immediately send either a RSET command
       (if it wishes to attempt to send additional messages), or a QUIT
       command.  The client should then declare the message undeliverable
       and return appropriate notification to the sender (if a sender
       address was present in the MAIL command).

   A successful (250) reply code in response to the extended MAIL
   command does not constitute an absolute guarantee that the message
   transfer will succeed.  SMTP clients using the extended MAIL command
   must still be prepared to handle both temporary and permanent error
   reply codes (including codes 452 and 552), either immediately after
   issuing the DATA command, or after transfer of the message.

 

 

 

 

 

 

 

Tags:

Exchange 2007 | Exchange 2010 | Microsoft Exchange

Exchange 2007/2010 Meeting Resource Rooms, Booking, Delegate to Assitant

by butsch 23. January 2012 04:36

Exchange 2007/2010 Meeting Resource Rooms, Booking, Delegate to Assitant

What we want:

Because users can book meeting rooms and sometimes do that wrong IT or assitants want a solution so they can "Approve" each meeting before it get's finally booked.

This is called Resource Delegates in Exchange World ;-) Microsoft has made a great effort to make things complicated so only someone understands this who has written a post-doc report on Groupware.

 Here is an example of a room resource "car1" and two people who have to aprove each meeting BEFORE it finally get fixed.

1) A users books a meeting the right WAY (He invites other people AND additional the ROOM itself to the meeting) (Do not use Direct booking > Right click!)

2) The meeting temporary get's booked BUT the two Delegates will get an E-Mail and they have to approve the meeting before it get's booked finally.

Here is our sample Room Resource / Raum Postfach

Room Resource: car1

Deleagte 1 we want user: assitant

Delagte 2 we want user: m.butsch

Exchange Administrator account: yourexchangeadminaccount (This may be a account your work with and has temporary permission on most room resources)

a) In Exchange 2007 GUI > New Mailbox > Room Resource > New User (This will generate a pseudo user for the room resource)

b) Use following Powershell command to set everything you can do in Exchange Powershell

set-MailboxCalendarSettings "car1" -AutomateProcessing Autoaccept

set-MailboxCalendarSettings "car1" -MaximumDurationInMinutes 10080
set-MailboxCalendarSettings "car1" -BookingWindowInDays 730

set-MailboxCalendarSettings "car1" -DeleteSubject $False
set-MailboxCalendarSettings "car1" -DeleteComments $False
set-MailboxCalendarSettings "car1" -DeleteAttachments $False

set-MailboxCalendarSettings "car1" -AllRequestOutOfPolicy $False
set-MailboxCalendarSettings "car1" -AllBookinpolicy $False
set-MailboxCalendarSettings "car1" -AllRequestinPolicy $True

Also add oin Exchange2010:

----------------------------------------------------------------------------------------------------

Add-MailboxPermission "car1"-AccessRights:fullaccess -User ( 'assistant','m.butsch','yourexchangeadminaccount')

Also add on Exchange 2007:

$raumname ="car1"
Add-MailboxPermission $raumname -User "assistant" -AccessRights FullAccess
Add-MailboxPermission $raumname -User "m.butsch" -AccessRights FullAccess

Add-MailboxPermission $raumname -User "yourexchangeadminaccount" -AccessRights FullAccess

 

c LOGON to OWA https://exchangeserver/owa with your yourexchangeadminaccount and open the Resource Mailbox (Right upper corner) and check OPTIONS.

Add the ALIAS/LOGONNAMES of the two Deleagates ; (Semilkon) seperated to the shown fields.

> the tricky part > These settings sometimes FAIL to SAVE or IF you and then re-OPEN they change. At the End you best control everything in Powershell with command:

get-MailboxCalendarSettings "car1" | fl

 

 

 

 

 

----------------------------------------------------------------------------------------------------

Some settings explained: 

 

MaximumDurationInMinutes=10080 (Default 1440 and set the maximum a meeting can run = new 1 week)

BookingWindowInDays=730 (Default 180 and sets the time in advance [In the future] you can schedule a meeting

DeleteSubject=False (Per default any attachment or subject a person adds is removed. This is a privacy options. As example HR books a meeting called replacement wotrkforce Switzerland and other people should not know about it.

DeleteComments=False (Privacy same as above)

DeleteAttachments=False (Privacy same as above)

----------------------------------------------------------------------------------------------------

More settings explained: 

Send all request FIRST to the listed delegates:

ForwardRequestsToDelegates          : True

Accept the meeting first temporary UNTIL one of the delegates DOES accept it:

TentativePendingApproval            : True

These people have to aprobe (One of them):

ResourceDelegates                   : {m.butsch, assistant}

These people can book the meeting room as admin and need no aproval:

RequestOutOfPolicy                  : {m.butsch, assistant}

AllRequestOutOfPolicy               : False

These people can book the meeting room as admin and need no aproval:

BookInPolicy                        : {m.butsch, assistant}

AllBookInPolicy                     : False

RequestInPolicy                     : {m.butsch, assistant}

AllRequestInPolicy                  : True

AddAdditionalResponse               : True

----------------------------------------------------------------------------------------------------

Here is how to get a list of all rooms or mailboxes wich are called "RAUM******":

get-Mailbox | Where-Object {$_.Name -like 'raum*' }

get-Mailbox | Where-Object {$_.Name -like 'raum*' } | select name,Alias | Format-Table -AutoSize | out-File ('c:\edv\alle_raueme.txt')

----------------------------------------------------------------------------------------------------

Some nice Links:

Managing Resource Mailbox Calendars

http://knicksmith.blogspot.com/2007/05/managing-resource-mailbox-calendars.html

Resource scheduling in Exchange Server 2007

http://blogs.technet.com/b/exchange/archive/2007/05/14/resource-scheduling-in-exchange-server-2007.aspx

 http://www.msexchange.org/articles_tutorials/exchange-server-2007/management-administration/managing-resource-mailboxes-exchange-server-2007-part2-.html

 ----------------------------------------------------------------------------------------------------

Exchange 2010 change certain values:

get-CalendarProcessing -identity "Sitzungszimmer_1_OG" | fl


[PS] C:\>set-CalendarProcessing -identity "Sitzungszimmer_1_OG" -DeleteSubject $false
[PS] C:\>set-CalendarProcessing -identity "Sitzungszimmer_2_OG" -DeleteSubject $false


[PS] C:\>get-CalendarProcessing -identity "Sitzungszimmer_1_OG" | fl


RunspaceId                          : 6b6a4e3f-72b7-4000-ab30-87a93f3e
AutomateProcessing                  : AutoAccept
AllowConflicts                      : True
BookingWindowInDays                 : 720
MaximumDurationInMinutes            : 1440
AllowRecurringMeetings              : True
EnforceSchedulingHorizon            : True
ScheduleOnlyDuringWorkHours         : False
ConflictPercentageAllowed           : 2
MaximumConflictInstances            : 2
ForwardRequestsToDelegates          : True
DeleteAttachments                   : True
DeleteComments                      : True
RemovePrivateProperty               : True
DeleteSubject                       : True
AddOrganizerToSubject               : True
DeleteNonCalendarItems              : True
TentativePendingApproval            : True
EnableResponseDetails               : True
OrganizerInfo                       : True
ResourceDelegates                   : {}
RequestOutOfPolicy                  : {}
AllRequestOutOfPolicy               : False
BookInPolicy                        : {}
AllBookInPolicy                     : True

 

 

 

 

Tags:

Exchange 2007 | Exchange 2010 | Microsoft Exchange