[Exchange 2013/Online][PS] How to retrieve existing remote PowerShell sessions

I'm trying to figure out how to retrieve all existing remote PowerShell sessions (user-managed) between a client and an Exchange 2013 server.
Running Get-PSSession only returns remote sessions created within the current PowerShell session (system-managed). I need to do this from within a
different PowerShell session, possibly even from a different computer from where those remote sessions were established.
Documentation for Get-PSSession states that this should be possible starting with PS 3.0 since user-managed sessions are now stored locally on the remote server (in my case, the Exchange 2013 server) and can later be retrieved from any system-managed session
by using Get-PSSession with either the ComputerName or ConnectionUri parameter sets.
Here's how those remote sessions are created:
PS $> $Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri https://<exchange_server>/powershell/ -Credential $credential -Authentication Basic -AllowRedirection
PS $> Import-PSSession $Session
And how I try to retrieve those session afterward:
PS $> Get-PSSession -ComputerName <exchange_server> -ApplicationName powershell -Authentication Basic -Credential $credential -UseSSL -Port 443
PS $> Get-PSSession -ConnectionUri https://<exchange_server>/powershell/ -AllowRedirection -Authentication Basic -Credential $credential
Both methods yield no results (nor errors), while running Get-PSSession (without any parameters) within the same user-managed session would successfully return the session. 
The only explanation I could think of right now is that somehow, WinRM on the Exchange server is not running PS 3.0 even though:
$PSVersionTable.PSVersion returns 3 0 -1 -1
winrm id returns ProductVersion = OS: 6.2.9200 SP: 0.0
Stack: 3.0
But when I attempt to disconnect a remote session with this Exchange server using Disconnect-PSSession, I get the
following error message: 
Disconnect-PSSession : Disconnect-PSSession operation failed for runspace Id = XXXXX
for the following reason: The disconnection operation is not supported on the remote computer. To support
disconnecting, the remote computer must be running Windows PowerShell 3.0 or a later version of Windows PowerShell.
So I guess I have a couple questions:
Are remote PSSession even supposed to be maintained on
an Exchange 2013 server? 
If so, is it possible to retrieve them from a different session using GET-PSSession?
Which version of PS 3.0 is used by WinRM on an Exchange 2013 server?
thanks

Thanks for your help. 
1. I know that remote PS sessions are supported, I have no issue connecting to the Exchange server. The issue is with
reconnecting to an existing PS session.
2. As mentioned in my original post, PS & WinRM 3.0 are installed on the client:
$PSVersionTable.PSVersion returns 3
0 -1 -1
winrm
id returns ProductVersion = OS: 6.2.9200 SP: 0.0 Stack:
3.0

Similar Messages

  • Exchange 2013 Online mode slow performance

    Hello,
    We recently moved mailboxes (180 or so) from Exchange 2007 to Exchange 2013.  We are noticing that Outlook navigation seems to be very slow compared to the last server.  Changing folder views, switching from Inbox to Calendar, Deleting items, etc. 
    Also we used to be able to send 40MB HTML emails very quickly.  This now takes about 5 min just to open a reply. (These are tripwire reports.)  Most users are using Outlook in Online mode on the new server and were using Online mode on the old server
    Environment: Exchange 2013 SP1 on Server 2012r2 Standard (6 cores 24 gigs of RAM, VMWare VM.)  Old server is Exchange 2007 8.3.348.2 on Server 2008x64 Standard SP2 (8 cores 12 gigs of RAM.
    Physical.)
    I have a ticket open with MS but didn't really get anywhere after 9 hours yesterday.
    Thanks.

    Hi everyone,
    Here we have exactly the same thing. We did the same migration from Exchange 2k7 to Exchange 2013. We run on a VMware 5.5 infrastructure. We have a lot of users running on a VM, but I can also tell you that I'm experiencing the problem even on a physical
    PC. So the problem about the client side infrastructure is maybe not that much related.
     I also found an old thread talking about a known issue with the grouping option in Outlook and online mode, but this is supposed to be only for Exchange and Outlook 2007, so i'm not able to prove this problem is exactly and only related to this issue.
    however, I tried to disable the grouping option for some folder in my Outlook and I saw an improvement immediately. Here is the thread talking about this issue and the knowledge base associated from Microsoft:
    http: //blogs.technet.com/b/mikelag/archive/2008/08/31/slow-outlook-online-mode-performance.aspx
    http: //support.microsoft.com/kb/948828
    Sorry, I cannot post the real link since my account is not verified yet... simply remove the space.
    If anyone finally found an answer please post-it, thanks.

  • Exchange 2013 Split DNS, how to get WAN clients to use public Split DNS IP when inter-office link is DOWN?!

    Hello,
    I have an Exchange 2013 deployment and a LAN/WAN setup, we have many small remote WAN linked offices that can resolve to the Exchange Server's internal IP.
    Outlook clients in remote WAN offices work fine as long as the link is UP since the Split Brain DNS for Exchange will resolve the internal clients to the internal IP of the Exchange server, Outlook connects up without issues.
    However, in the event of loosing connection to our remote sites, they will no longer be able to resolve to the internal Exchange IP, but they still have a backup public internet that they can use. So should the inter-office connectivity fail we have it setup
    so clients in remote offices can still browse the internet, etc.
    However, their Outlook fails to connect because it has a cached DNS record for our Split Brain Exchange DNS setup and tries to resolve it to its internal IP, instead of refreshing the cache and grabbing the public IP of the Exchange server since now they
    would be resolving it over the public internet.
    Is there anything I can do with my existing configuration to allow the client to pick up the public IP of the Split DNS setup when our inter-office connection is down and the client is no longer able to use the internal IP they have cached for Exchange?
    I guess I could lower the TTL on the DNS record to something like 1 minute so it does not cache the DNS record / IP for long? Is this the best approach?

    http://public.wsu.edu/~brians/errors/lose.html
    I would suggest that the best approach is to either improve the reliability of the WAN link or to configure DNS to always use the Internet path.  You might want to work with your network guy, perhaps there's a way to have your gateways automatically
    switch to an Internet VPN backup when the WAN link is down or something like that.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Cannot migrate exchange 2013 user to another database through EMC, only powershell works?

    Hi Everyone,
    I'm trying to migrate a few mailboxes from a database called "primary" to "archive". I can migrate a single user through powershell, however I cannot migrate users through the GUI. When the "syncing" starts, it reverts the total
    from "2" to "0" and makes it appear as though I never added any users to the batch job. The job then completes "successfully"
    I can see the users in the job before I hit start. Any idea why my job goes blank?
    I'm running exchange 2013 CU6

    Hi ,
    Thank you for your question.
    We could refer to the following steps to troubleshoot:
    Restart IIS to check if the issue persist.
    End up of the user job to check if the issue persist.
    Create a new account to check if the issue persist.
    We could check relevant application log, then we could check if EAC and EMS connect to same domain controller, then we could check sync between Exchange server and domain controller.
    If there are any questions regarding this issue, please be free to let me know. 
    Best Regard,
    Jim
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Jim Xu
    TechNet Community Support

  • How to retrieve string array using Session?

    Hi, I am having some problem retrieving string arrays through session.
    String personalData[] = new String[17];
    personalData = (String [])session.getValue("PersonalData");
    The coding above isn't working. Advise pls.. Thanks

    The getValue() method is deprecated - you should probably be using getAttribute.
    What about this code isn't working? Looks ok to me, as long as the "PersonalData" object in the session is a String[] it should work.
    Cheers,
    evnafets

  • Outlook 2003 and Exchange 2013

    We have just installed Exchange 2013 servers in our organization alongside existing Exchange 2007 servers. No mailboxes have been migrated yet and we are about ready to point our client access namespace to the Exchange 2013 servers and go into the co-existence
    stage.
    We still have some Outlook 2003 clients and I know these need to be updated to 2007 SP3 or 2010 Sp1 or 2013 before those mailboxes are migrated to Exchange 2013.
    However, I am curious as to whether we would hit any problems at all if we pointed our namespace to E2K13 before upgrading the Outlook 2003 clients, as long as none of the Outlook 2003 clients use Outlook Anywhere and the mailboxes those clients
    connect to remained on Exchange 2007 for the time being ?
    Clearly, Outlook 2003 is not 'supported' but the wording in the following link...
    http://social.technet.microsoft.com/wiki/contents/articles/845.outlook-versions-supported-by-exchange-200720102013online.aspx
    says " Please bear in mind there’s a difference between what is supported and what might be compatible with Exchange 2013"
    Would the situation I'm thinking of be one of those 'compatible but unsupported' scenarios. i.e I can't think of any reason why the Outlook 2003 clients would have a need to connect to an E2K13 CAS server ...
    I'd be interested to hear other people experiences/opinions on this. Thanks!

    Hi,
    Based on my knowledge, for internal users whose mailboxes exist on Exchange 2007, it is ok to still use Outlook 2003 as clients. Because
    they will still connect to the Exchange 2007 Mailbox server instance hosting the mailbox. If the user is moved to Exchange 2013, please upgrade the Outlook client to higher version. Because Exchange 2013 doesn’t support Outlook 2003 client.
    For Outlook 2003 clients connected to Exchange 2007, they doesn’t support autodiscover service to get some Exchange services such as free/busy information, OAB. Outlook 2003 would connect to Public Folder in Exchange 2007 to retrieve these
    services. For OWA and ActiveSync service, it is not related to Outlook 2003 client, the CAS2013 would redirect the service request or send to CAS2007 for necessary data.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Exchange 2013 Memory usage very low

    Hi,
    we have 4 Servers, 2 Mailbox Servers and 2 Database SErvers with DAG deployed on Exchange 2013 CU5.
    We have about 420 GB in one database.
    The Server has 40 GB Memory assigned (Windows VM), but only using about 12 GB of Memory.
    Depending on this guide, this makes sense:
    http://blogs.technet.com/b/samdrey/archive/2014/02/03/exchange-2013-memory-ram-allocation-by-the-store-with-an-example.aspx
    But, as this is only a database server with no other services on it, how can i increase the memory consumed by Exchange?
    User are reporting of slow Outlook Clients.

    Are the Outlook clients in online mode?
    This may help: ( see the solution)
    http://social.technet.microsoft.com/Forums/en-US/a07b9269-be9f-4337-a394-9faf532d38f8/exchange-2013-online-mode-slow-performance?forum=exchangesvradmin
    http://social.technet.microsoft.com/Forums/office/en-US/0d45b1b0-3047-4666-ad04-217e98ed8823/slow-online-mode-browsing?forum=exchangesvrclients
    Also, you may want to apply this hotfix to the servers:
    http://support2.microsoft.com/kb/2985459
    The W3wp.exe process has high CPU usage when you run PowerShell commands for Exchange
    Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

  • Exchange 2013 Untrusted Cross-Forest Availability Intermittently Working

    Goal:
    I’m attempting to configure cross-forest availability for Exchange 2013 using the instructions here:
    http://technet.microsoft.com/en-us/library/bb125182%28v=exchg.150%29.aspx
    At the very bottom of the page are three different methods.  I have tried the first (per-user) and the third (untrusted) methods, with identical results.  For various unfortunate reasons, I am unable to use the Microsoft Federated Gateway for availability
    information (although that is configured in the production domain and I would use it if it were possible). 
    Situation:
    When attempting to view availability information in either OWA or Outlook, the free/busy information typically isn’t visible.  If you open and close Outlook a few times, creating meetings with the users in other domains, sometimes the other user’s information
    will be visible, and sometimes it will not.  When it is not, the area is filled with diagonal lines and hovering over it says “No Information”.  The situation is the same in both Adatum trying to access Contoso, and in Contoso trying to access either
    Adatum or Fabrikam.
    I’m currently close to finishing up my third week with Microsoft Support on this issue, and am starting over with a third first level support person.  They are quickly eroding what little confidence I had in them already.  I’m posting here because
    I’m desperate, and web searches for my errors turn up zero results.  I fear this method of availability sharing doesn’t actually work correctly in Exchange 2013 as Microsoft is pushing organizations to use the Microsoft Federated Gateway, but I’d love
    to heave about anyone getting this to work, or not.
    Setup:
    There are three separate domains I am working with (names changed to protect the innocent).  Contoso.local is the production domain, containing Exchange 2007 and Exchange 2013 SP1 servers.  Adatum.local is a test domain set up fresh with Exchange
    2013 SP1.  Fabrikam.com is a remote Exchange system that I others are connecting to without issue using Exchange 2010.
    The Contoso and Adatum domain controllers are running Windows Server 2008 R2 SP1 and are running at a 2008 R2 functional levels.  The Exchange 2013 servers are all at SP1 (results were the same prior to SP1), and the OS is Windows Server 2012. 
    Contoso has two sites, connected via 10Gbps links, and ~10ms latency, with Exchange 2013 CAS and mailbox servers in both sites.  Adatum has a single site, and has two CAS and two mailbox servers.  Fabrikam has one internet facing server to connect
    to.  A handful of contacts have been created in both Contoso and Adatum for the other domains, to select to view availability.
    Contoso and Adatum domains sit on different subnets, but there is no firewall or filtering between their subnets.  Routing between them is completely unimpeded.  The Fabrikam server sits on another network across the internet, but firewalls have
    been configured and I can browse the availability website from the Contoso CAS servers.
    The CAS servers were originally set up to be load balanced, but working with Microsoft they’ve had me specify a single CAS server for autodiscover/EWS/ECP/OWA/etc in both Contoso and Adatum.  The number of actual users on Exchange 2013 in Contoso is
    ~10.  In Adatum, there are only a handful of mailboxes configured.  The Exchange 2007 servers in Contoso are using Public Folders for free/busy replication for other domains right now, and we don’t care at the moment if they can use the 2013 availability. 
    None of our testing/configurations have involved the Exchange 2007 servers.  There are no SPNs configured for the other domains in AD.
    Errors:
    There are three basic errors that are returned in Outlook diagnostics.  The first is the timeout error.  For a given mailbox server, the first time it is queried for availability information for a remote domain (after some amount of time of being
    idle) it might not respond for 70 seconds (actually somewhere between 69 and 70 seconds each time when viewing the IIS logs), and eventually fails with the timeout error.  If it doesn’t timeout, then it will respond with the Correct Response.
    Once a particular mailbox server has timed out, it will typically immediately return the first Availability Error for all subsequent calls.  Less frequently, it will return Availability Error 2.  If a mailbox server returns the first Availability
    Error, then it will continue to return that error until it times out again or starts working.  Similarly, if a mailbox server returns the second Availability Error, then it will continue to return that error until it times out again or starts working.
    If an IISRESET is performed on a mailbox server, then it will either timeout at the next cross-forest availability request, or work.  There is never an issue accessing availability information for users in the same domain as the request.
    If the remote Exchange is in an errored state, then the response includes the error.  For example, if the mailbox servers in the remote domain are turned off, and the local mailbox server that you are querying happens to be responding correctly
    for the remote domain, then it will return an error about how no mailbox servers are available in adatum.local to service the request.
    There are no Event Log errors that correspond to failed requests of any type.  IIS logs don’t show anything beyond what is shown in the Outlook diagnostics.  There are no DNS or Active Directory Replication errors in the Event Logs.
    Timeout error:
    CalendarEvents       : {}
    ViewType             : None
    MergedFreeBusyStatus : {}
    WorkingHours         :
    Result               : Error
    ErrorCode            : ErrorTimeoutExpired
    ErrorMessage         : Microsoft.Exchange.InfoWorker.Common.Availability.TimeoutExpiredException: Request could not be processed in time. Timeout occurred during 'LookupRecipientsBatchBegin'.
                           . Name of the server where exception originated: Mailbox01
    ErrorDetails         : {}
    ErrorProperties      : {}
    Availability Error:
    CalendarEvents       : {}
    ViewType             : None
    MergedFreeBusyStatus : {}
    WorkingHours         :
    Result               : Error
    ErrorCode            : ErrorProxyRequestProcessingFailed
    ErrorMessage         : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AutoDiscoverFailedException:
    AvailabilityAddressSpace 'adatum.local' couldn't be used because the Autodiscover endpoint couldn't be discovered.
                           . Name of the server where exception originated: Mailbox01
    ErrorDetails         : {}
    ErrorProperties      : {}
    Availability Error 2:
    CalendarEvents       : {}
    ViewType             : None
    MergedFreeBusyStatus : {}
    WorkingHours         :
    Result               : Error
    ErrorCode            : ErrorProxyRequestProcessingFailed
    ErrorMessage         : Unable to send cross-forest request for mailbox <Free BusyTest>SMTP:[email protected] because of invalid configuration., inner exception: Microsoft.Exchange.InfoWorker.Common.Availability.AddressSpaceNotFoundException:
    Configuration information for forest/domain swelab.wayad.corp.wayport.net could not be found in Active Directory.
                              at Microsoft.Exchange.InfoWorker.Common.Availability.TargetForestConfigurationCache.FindByDomain(OrganizationId
    organizationId, String domainName)
                              at Microsoft.Exchange.InfoWorker.Common.Availability.QueryGenerator.GetTargetForestConfiguration(EmailAddress
    emailAddress)
                           . Name of the server where exception originated: Mailbox02
    ErrorDetails         : {}
    ErrorProperties      : {}
    Working:
    CalendarEvents       : {Microsoft.Exchange.WebServices.Data.CalendarEvent}
    ViewType             : FreeBusyMerged
    MergedFreeBusyStatus : {Free, Free, Free, Free...}
    WorkingHours         : Microsoft.Exchange.WebServices.Data.WorkingHours
    Result               : Success
    ErrorCode            : NoError
    ErrorMessage         :
    ErrorDetails         : {}
    ErrorProperties      : {}
    Start : 04/09/2014 00:00:00
    End : 04/12/2014 00:00:00
    Subject :
    Location :
    Testing Methodologies:
    While it is possible to dig through Outlook diagnostics and OWA, we ended up scripting out these requests to save time.  Microsoft support refuses to use the scripts, but they produce the same output that it takes them days to find in the logs, so I’ll
    post them here to help anyone in the future.
    Through reading the documentation and experimenting, it appears that the Exchange 2013 CAS servers really do just proxy availability requests from the client to the mailbox servers.  At least by default, it seems to pick a mailbox server in the same
    site, but which mailbox server in the site appears to be random.  It will typically pick the same one repeatedly for a while.
    The first script uses the Microsoft Exchange Web Services Managed API 2.1.
    http://www.microsoft.com/en-us/download/details.aspx?id=42022
    You specify a source email address, and a target address in the remote domain, and it creates a SOAP request that it sends to a CAS server of the source email address.  The CAS proxies the request to the mailbox server which either responds with a failure
    or the free/busy data.
    The second script takes the XML SOAP request generated by the first script, and uses that to query a mailbox server directly.  That allows you to test specific mailbox servers that are working or failing, instead of randomly using whichever mailbox
    server the CAS happens to select.  I generated a SOAP request with the first script that I knew had some data, and then copy/pasted it into the second script to verify if data was being returned.
    I’ve deleted and recreated the availability address spaces in Contoso and Adatum for each other and Fabrikam multiple times.  I’ve reset the password in the OrgWideAccount in both Adatum and Contoso, and viewed the lastBadPassword attribute in both
    ADs to verify it wasn’t failing authentication.  (A failed authentication also generates a 401 error that is returned to the client.)  I can access the availability site of the other domain using the credentials of the OrgWideAccount without any
    errors ever.
    First Script:
    # Import the Exchange Web Services module
    Import-Module -Name "C:\Program Files (x86)\Microsoft\Exchange\Web Services\2.1\Microsoft.Exchange.WebServices.dll"
    # Create the services object used to connect to Exchange
    # You can specify a specific Exchange version, which I had to do to connect to 2007
    # Exchange2007_SP1
    # Exchange2010
    # Exchange2010_SP1
    # Exchange2010_SP2
    # Exchange2013
    # $ExchangeVersion = [Microsoft.Exchange.WebServices.Data.ExchangeVersion]::Exchange2007_SP1
    # $Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService($ExchangeVersion)
    $Service = New-Object Microsoft.Exchange.WebServices.Data.ExchangeService
    $Service.UseDefaultCredentials = $true
    # Specify an SMTP address. The autodiscover URL from the associated mailbox will be used to connect to Exchange
    # This is used to distinguish resolving from the 2007 server versus 2013
    #$Service.AutodiscoverUrl("[email protected]") # For Exchange 2007
    $Service.AutodiscoverUrl("[email protected]") # For Exchange 2013
    # Increase the amount output at the end to include the SOAP commands
    $Service.TraceEnabled = $true
    # Specify time frame to get free/busy for
    $StartTime = [DateTime]::Parse([DateTime]::Now.ToString("yyyy-MM-dd 0:00"))
    $EndTime = $StartTime.AddDays(7)
    # Create the various objects needed to perform the EWS request
    $drDuration = new-object Microsoft.Exchange.WebServices.Data.TimeWindow($StartTime,$EndTime)
    $AvailabilityOptions = new-object Microsoft.Exchange.WebServices.Data.AvailabilityOptions
    $AvailabilityOptions.RequestedFreeBusyView = [Microsoft.Exchange.WebServices.Data.FreeBusyViewType]::DetailedMerged
    $Attendeesbatch = New-Object "System.Collections.Generic.List[Microsoft.Exchange.WebServices.Data.AttendeeInfo]"
    $attendee = New-Object Microsoft.Exchange.WebServices.Data.AttendeeInfo($userSMTPAddress)
    # Specify SMTP addresses of accounts to request availability for
    #$Attendeesbatch.Add("[email protected]")
    $Attendeesbatch.Add("[email protected]")
    #$Attendeesbatch.Add("[email protected]")
    #$Attendeesbatch.Add("[email protected]")
    # Clear out old results so that a failed request doesn't show information still
    $availresponse = ""
    # Request the availability information from Exchange
    $availresponse = $service.GetUserAvailability($Attendeesbatch,$drDuration,[Microsoft.Exchange.WebServices.Data.AvailabilityData]::FreeBusy,$AvailabilityOptions)
    # Show summary information that would include errors
    $availresponse.AttendeesAvailability
    # Show all of the appointments in the requested time period
    foreach($avail in $availresponse.AttendeesAvailability){
    foreach($cvtEnt in $avail.CalendarEvents){
    "Start : " + $cvtEnt.StartTime
    "End : " + $cvtEnt.EndTime
    "Subject : " + $cvtEnt.Details.Subject
    "Location : " + $cvtEnt.Details.Location
    Second Script:
    # Change the server in this URL to specify which mailbox server to access
    $url = 'https://mailbox01.contoso.local:444/EWS/Exchange.asmx'
    # Uncomment the below lines if you want to query EWS using credentials other than
    # the ones used to run the script.
    #If(!(Test-Path variable:global:cred))
    # $cred = Get-Credential
    function Execute-SOAPRequest
    [Xml] $SOAPRequest,
    [String] $URL
    write-host "Sending SOAP Request To Server: $URL"
    $soapWebRequest = [System.Net.WebRequest]::Create($URL)
    # These appear to be the only things needed in the headers when making the request
    $soapWebRequest.ContentType = 'text/xml;charset="utf-8"'
    $soapWebRequest.Accept = "text/xml"
    $soapWebRequest.Method = "POST"
    If(Test-Path variable:global:cred)
    $soapWebRequest.Credentials = $cred
    Else
    $soapWebRequest.UseDefaultCredentials = $true
    write-host "Initiating Send."
    $requestStream = $soapWebRequest.GetRequestStream()
    $SOAPRequest.Save($requestStream)
    $requestStream.Close()
    write-host "Send Complete, Waiting For Response."
    $resp = $soapWebRequest.GetResponse()
    $responseStream = $resp.GetResponseStream()
    $soapReader = [System.IO.StreamReader]($responseStream)
    $ReturnXml = [Xml] $soapReader.ReadToEnd()
    $responseStream.Close()
    write-host "Response Received."
    return $ReturnXml
    # The specing and line returns in the below variable are important for some reason
    # For example, there must be a line return after the @' on the first line, or it's invalid...
    # Change the line with this:
    # <t:Address>[email protected]</t:Address>
    # to the email address in the domain you want to query
    $soap = [xml]@'
    <?xml version="1.0" encoding="utf-8"?>
    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Header>
    <t:RequestServerVersion Version="Exchange2013_SP1" />
    <t:TimeZoneContext>
    <t:TimeZoneDefinition Name="(UTC-06:00) Central Time (US &amp; Canada)" Id="Central Standard Time">
    <t:Periods>
    <t:Period Bias="P0DT6H0M0.0S" Name="Standard" Id="Std" />
    <t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/1" />
    <t:Period Bias="P0DT5H0M0.0S" Name="Daylight" Id="Dlt/2007" />
    </t:Periods>
    <t:TransitionsGroups>
    <t:TransitionsGroup Id="0">
    <t:RecurringDayTransition>
    <t:To Kind="Period">Dlt/1</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>4</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>1</t:Occurrence>
    </t:RecurringDayTransition>
    <t:RecurringDayTransition>
    <t:To Kind="Period">Std</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>10</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>-1</t:Occurrence>
    </t:RecurringDayTransition>
    </t:TransitionsGroup>
    <t:TransitionsGroup Id="1">
    <t:RecurringDayTransition>
    <t:To Kind="Period">Dlt/2007</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>3</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>2</t:Occurrence>
    </t:RecurringDayTransition>
    <t:RecurringDayTransition>
    <t:To Kind="Period">Std</t:To>
    <t:TimeOffset>P0DT2H0M0.0S</t:TimeOffset>
    <t:Month>11</t:Month>
    <t:DayOfWeek>Sunday</t:DayOfWeek>
    <t:Occurrence>1</t:Occurrence>
    </t:RecurringDayTransition>
    </t:TransitionsGroup>
    </t:TransitionsGroups>
    <t:Transitions>
    <t:Transition>
    <t:To Kind="Group">0</t:To>
    </t:Transition>
    <t:AbsoluteDateTransition>
    <t:To Kind="Group">1</t:To>
    <t:DateTime>2007-01-01T06:00:00.000Z</t:DateTime>
    </t:AbsoluteDateTransition>
    </t:Transitions>
    </t:TimeZoneDefinition>
    </t:TimeZoneContext>
    </soap:Header>
    <soap:Body>
    <m:GetUserAvailabilityRequest>
    <m:MailboxDataArray>
    <t:MailboxData>
    <t:Email>
    <t:Address>[email protected]</t:Address>
    </t:Email>
    <t:AttendeeType>Required</t:AttendeeType>
    <t:ExcludeConflicts>false</t:ExcludeConflicts>
    </t:MailboxData>
    </m:MailboxDataArray>
    <t:FreeBusyViewOptions>
    <t:TimeWindow>
    <t:StartTime>2014-04-03T00:00:00</t:StartTime>
    <t:EndTime>2014-04-10T00:00:00</t:EndTime>
    </t:TimeWindow>
    <t:MergedFreeBusyIntervalInMinutes>30</t:MergedFreeBusyIntervalInMinutes>
    <t:RequestedView>DetailedMerged</t:RequestedView>
    </t:FreeBusyViewOptions>
    </m:GetUserAvailabilityRequest>
    </soap:Body>
    </soap:Envelope>
    $ret = Execute-SOAPRequest $soap $url
    # Uncomment out one of the below two lines to get output in different alternative formats
    #$ret | Export-Clixml c:\temp\1.xml;Get-Content c:\temp\1.xml
    #$ret.InnerXml
    # If the request is successful, show the appointments, otherwise show the failure message
    If ($ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessage.ResponseClass -eq 'Success')
    $ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.FreeBusyView.CalendarEventArray.CalendarEvent
    Else
    $ret.Envelope.Body.GetUserAvailabilityResponse.FreeBusyResponseArray.FreeBusyResponse.ResponseMessage

    In this case, the SMTP domain is the same as the AD domain.  If the wrong domain were configured then the connection would never work, as opposed to sometimes work.
    RunspaceId            : abb30c12-c578-4770-987f-41fe6206a463
    ForestName            : adatum.local
    UserName              : adatum\availtest
    UseServiceAccount     : False
    AccessMethod          : OrgWideFB
    ProxyUrl              :
    TargetAutodiscoverEpr :
    ParentPathId          : CN=Availability Configuration
    AdminDisplayName      :
    ExchangeVersion       : 0.1 (8.0.535.0)
    Name                  : adatum.local
    DistinguishedName     : CN=adatum.local,CN=Availability Configuration,CN=Wayport,CN=Microsoft
                            Exchange,CN=Services,CN=Configuration,DC=contoso,DC=local
    Identity              : adatum.local
    Guid                  : 3e0ebc2c-0ebc-4be8-83d2-077746180d66
    ObjectCategory        : contoso.local/Configuration/Schema/ms-Exch-Availability-Address-Space
    ObjectClass           : {top, msExchAvailabilityAddressSpace}
    WhenChanged           : 4/15/2014 12:33:53 PM
    WhenCreated           : 4/15/2014 12:33:35 PM
    WhenChangedUTC        : 4/15/2014 5:33:53 PM
    WhenCreatedUTC        : 4/15/2014 5:33:35 PM
    OrganizationId        :
    OriginatingServer     : dc01.contoso.local
    IsValid               : True
    ObjectState           : Unchanged

  • Custom Site MailBox for Office 365 SharePoint 2013 online

    Is it possible to create programmatically create site mailbox for Office 365 SharePoint 2013 online?
    How to customize site mailbox email address like [email protected]

    Hi,
    In SharePoint 2013 Online, if you want to sync document library with local drive, you can use OneDrive to achieve it.
    http://office.microsoft.com/en-001/support/sync-onedrive-for-business-or-sharepoint-site-libraries-to-your-computer-HA102832401.aspx
    Best Regards
    Dennis Guo
    TechNet Community Support

  • Exchange 2010 mailbox prompts for authentication to Exchange 2013 mailbox

    I am in the process of a 2010 to 2013 migration. The only issue I can't seem to manage is an authentication issue with Outlook 2010. My Outlook profile consists of my Exchange 2013 mailbox and a shared mailbox on Exchange 2010. Initially, Outlook was prompting
    for authentication to the Exchange 2010 mailbox. Regardless of whether I entered the correct credentials or simply cancelled the prompt, I still had full access to both mailboxes (including Public Folders on 2010). The authentication prompt was removed with
    the following command:
    Get-OutlookAnywhere -Server my2013exchserver | Set-OutlookAnywhere -InternalClientsRequireSsl $true
    The second issue I now have is the reverse of the above: an Exchange 2010 user is prompted for authentication to an Exchange 2013 mailbox. How do I begin to troubleshoot this problem - should I run the same command (above) on 2010? I don't quite understand
    how Outlook communicates with Exchange but I am thinking there is an incorrect setting on one of the Virtual Directories(?).
    Many thanks.

    Hi Dennis,
    Please open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar –Connection Status to check the connection for your Exchange 2010 mailbox with shared 2013 mailbox. The following example in my test results:
    Please check your connection authentication. We can  run the following command to set your Outlook Anywhere for Exchange 2013:
    Set-OutlookAnywhere -Identity "E15-01\Rpc (Default Web Site)" -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl $True -InternalClientsRequireSsl $true
    In Outlook side, please ensure the following settings in Account Settings:
    In Security tab, make sure Always prompt for logon credentials is unchecked and Logon network security is set to Negotiate Authentication.
    Regards,
    Winnie Liang
    TechNet Community Support

  • Mscorsvw error message when trying to run Exchange 2013 CU 8

    I'm getting this error when trying to run CU 8 on our Exchange 2013 server.
    How to make it not happen??
    Is there any way to find out how/where this process is running so it can be closed??
    Thank you, Tom

    Hi,
    How are things going?
    Mscorsvw.exe is a component of Windows, and is otherwise known as the .NET Framework Optimization Service. It optimizes your machine to launch apps faster. Once it's done, it will go away.
    Resolution:
    By using sevices.msc, verify that no service is in “Starting pending” state.
    More information about mscorsvw.exe
    http://blogs.msdn.com/b/dotnet/archive/2013/08/06/wondering-why-mscorsvw-exe-has-high-cpu-usage-you-can-speed-it-up.aspx
    Best Regards.
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Lynn-Li
    TechNet Community Support

  • Exchange 2013 Licencing Terms and Agreements

    When you install Exchange 2013 you have to agree to the terms and conditions with the /IAcceptExchangeServerLicenceTerms
    If you dont setup.exe points you to a URL
    The the URL is http://go.microsoft.com/fwlink/p/?LinkId=150127
    However when you go to the link there is only an option for Exchange 2007 and 2010 ? Where’s the version selection for Exchange 2013?
    And How has the rest of the world been accepting these license terms for Exchange 2013?
    I need our legal department to give me (the technical guy) approval that I can accept these terms on behalf of the organization and without the terms I technically cannot go ahead..

    Hi Riccardo,
    For licensing related question, it's recommended to consult the local supplier for more accurate information,
    you may
    get effective solution timely:
    http://support.microsoft.com/gp/customer-service-phone-numbers/en-us
    Best regards,
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Niko Cheng
    TechNet Community Support

  • Exchange 2013 - Delivery Groups, Routable DAGs and Delivery Queues

    Hey Team,
    I am trying to better understand Exchange 2013 Delivery Groups and Boundaries. I think I have it almost figured out, I reviewed this article here which helped clear it up for  me:
    http://www.msexchange.org/articles-tutorials/exchange-server-2013/planning-architecture/exchange-2013-mail-flow-part2.html
    I need to understand the difference between and exchange 2013 delivery and how a delivery is group is different from the way that Exchange 2010 routed mail.
    For some reason I am just not getting the differences between 2013 and 2010 in terms of message delivery.
    Thanks,
    Robert
    Robert

    Hi,
    In Exchange 2013 there are only two roles, while five roles in Exchange 2010. There is difference between Exchange 2010 and Exchange 2013 on mail delivery.
    The following articles can help you to understand the difference of mail delivery between Exchange 2010 and Exchange 2013.
    Mail routing (For Exchange 2013)
    http://technet.microsoft.com/en-gb/library/aa998825(v=exchg.150).aspx
    Understanding Message Routing (For Exchange 2010)
    http://technet.microsoft.com/en-gb/library/aa998825(v=exchg.141).aspx
    Hope this is helpful to you.
    Best regards,
    If you have feedback for TechNet Subscriber Support, contact
    [email protected]
    Belinda Ma
    TechNet Community Support

  • Mails were deleted automatically from inbox and sent items, even in deleted items in Exchange 2013 CU2

    Dear all:
    I encountered a problem and needs to be solved.
    We runs Exchange 2013 CU2, and some users told me that their mails in sent items and inbox were automatically delivered into "deleted items", especially in last two weeks or yesterday.
    The users said they cannot delete so many mails at one time. And now I found one user's mails in "deleted items" were also deleted this morning.
    I don't know whether it was bug or not in exchange 2013 cu2, and how to solve this problem? Thanks for any help.
    koiso 
    Technet Microsoft

    Hi koiso,
    Are there any commons among problematic users or deleted emails? For example,
    they are on the same database
    they have delegate settings
    they are using mobile phone to sync emails
    At the same time, I'd recommend you enable Mailbox Audit Log for the problematic users. For your reference:
    http://technet.microsoft.com/en-us/library/ff459237(v=exchg.150).aspx
    Regards,
    Rebecca Tu
    TechNet Community Support

  • Installing / Upgrading Exchange 2013 to Exchange 2010 with a o365 Hybrid environment

    Hi
    I am trying to install a new server with Exchange  2013 on an environment with an existing Exchange 2010 Sp3. Reason for that is that I have a o365 hybrid environment and need to disconnect my on-line and on-premise e-mail connection. I want to completely
    run all my mailboxes on o365 no-longer dependent on on-premise exchange but the Exchange 2010 doesn't have a functionality to 'dismantle' the hybrid.. we need to have exchange 2013.
    When I try to install Exchange 2013 I get an error message that I need to upgrade my o365 tenant. : my o365 tenant version is : AdminDisplayVersion : 0.20 (15.1.49.12) :IsUpgradingOrganisation : False.
    Is there a better way of updating my environment.
    Regards

    Post the error from setup log for more information.
    Cheers,
    Gulab Prasad
    Technology Consultant
    Blog:
    http://www.exchangeranger.com    Twitter:
      LinkedIn:
       Check out CodeTwo’s tools for Exchange admins
    Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Maybe you are looking for

  • HCM ERP Scenario Object Manager customizing

    Hi all, I am trying to customize the PA30 Object Manager - Scenario EMPLOYEE, Node P, Position 1. There is one table T77CNODORD (path "Assign Own Column Group") which allows filling in custom text for the search help node and also, theoretically at l

  • Mysql Variable issue

    I am passing a what will soon be my search variable into php from flash. The issue is when I need to search for something that needs to find a string value in quotes it fails. Below is the like field variable declared in flash LikeField = "Model_Prof

  • How do you change the main contact in contacts/icloud?

    I've noticed in my contacts list I have one contact that is listed in blue and has a sillouete off to the right.  Also in my icloud contacts that same contacts has "me" on the contact Picture.  How do I change or delete this?

  • No Oracle MIBs in SNMP walk queries (10g)

    I configured SNMP support on my Oracle 10g database servers. However, when I attempt an SNMP walk, I get a few MIBs from SNMPv2 and HOST-RESOURCES, but nothing Oracle related, which is my goal for installing the SNMP support. Any hints or advice on w

  • Help with how to count the number of tokens from the first line

    Hi I want to count the number of tokens from the first line of text, from my incoming file and print it out. For example i have 12 tokens in the first line, so i want it to print out the number 12 my code is below thanks import java.io.*; import java