Exchange 2013 - systems is restarting after SP1
Hello
I notice that after installation of SP1, system restarts every day (various hours). Windows 2012 Standard, VM in Hyper-V.
BugCheck, 1001
0x000000ef (0xfffffa800828b780, 0x0000000000000000, 0x0000000000000000, 0x0000000000000000)
Before SP1 it was good. How to fix it?
--- Jacek Kochan MCSE,MCSA,MCITP
Hi Jacolex,
As others mentioned, we need more detailed information about this error, and to troubleshoot the reboot issue, you can also share your MEMORY dump file in skydrive.
Most of the time this error is caused by incompatible storage controller drivers. First please run all Windows Updates and then make sure that you have compatible drivers from your vendor.
In addition, this article may be hepful for you to troubleshoot:
Server rebooted automatically with Event ID 1001
I hope this help.
I am sick of you people.
Is this the answer or resolution of this thread? Is it?
You are so sick... What if someone else has the same issue and he/she come across with this thread!
Is your post will resolve the issue?
I am so..so frustrated with you people....
Are there any other moderator watching this thread? Can you someone take action on it....Please...
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.
Similar Messages
-
Exchange 2013 CAS incorrectly proxying after mailbox move to Exchange 2013
Hi,
I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
other clients are working.
This time I move another user this time it did not work for 3.5hrs. I had to reboot Exchange 2013 CAS server after that it worked.
There is must be something that is not refreshing on Exchange 2013 CAS server.
Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move. Currently we are in Pilot mode and only moving few
mailboxes at a time.
Thanks,
RamanHi,
I am moving Exchange 2010 mailboxes to Exchange 2013 SP1 in production. When I move 2010 mailbox Outlook, OWA works fine right after the move but ActiveSync (HTTPProxy log shows
on CAS 2013 server that it is still re-directing it to Exchange 2010 CAS servers). Exchange 2013 CAS server ActiveSync takes hours before it starts to see that mailbox is moved to Exchange 2013. I am certain it is not ActiveDirectory replication since all
other clients are working.
This time I move another user this time it did not work for 3.5hrs. I had to reboot Exchange 2013 CAS server after that it worked.
There is must be something that is not refreshing on Exchange 2013 CAS server.
Is there anything I can do right after the move to make it quick, I can not re-start server after every mailbox move. Currently we are in Pilot mode and only moving few
mailboxes at a time.
Thanks,
Raman
Does simply recycling the ActiveSync app pool speed things up?
Also, I would recommend installing CU6 instead of SP1.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied. -
Exchange 2013 Shared Mailbox Get-MailboxSentItemsConfiguration SP1 Help
Hello
My Setup
Server1: Server 2012 Standard + Exchange 2013 CU2 Standard (MBX+CAS)
Server2: Server 2012 Standard + Exchange 2013 CU2 Standard (MBX+CAS)
DAG Enable
I am having problems with Shared mailboxes, when sending E-mail from the Shared mailbox the sent E-mail will show up in the recipients Sent Items insted of the Shared mailbox sent Items.
I know that in Exchange 2010 Later SP and RU there where a PowerShell command that could send a copy to the Shared mailbox Sent Items (Get-MailboxSentItemsConfiguration)
but it doesn't seem to be there anymore, does anyone know if the cmdlet is back in CU3 or SP1? will it come back?
there is a workaround (Registry) but it doesn't help us, not for our environment.
Can I set this up by Outlook rules or maybe some kind of forwarding?
If you have any experience with this, feel free to give some advice.
Thank You very much!Hi,
*.MailboxSentItemsConfiguration has not been brought back in CU3 or CU4/SP1 and I don't know if it ever will be.
If DelegateSentItemsStyle configured in the registry is not an option for you, then using multiple Exchange accounts in the same Outlook Profile might be. The support for that was added in Outlook 2010 and personally, I like that option a lot.
Martina Miskovic -
Outlook 2013 / Outlook 365 crashes after SP1 when opening email
Hi,
I already posted this question in the Outlook forum but was referred to this one because I am connecting to Exchange servers:
I have a frustrating issue with Outlook 2013 (Work)/ Outlook 365 (Home) after the installation of Office Service Pack 1. Outlook starts fine and shows the Outlook Today screen. As soon as I go to my inbox and Outlook wants to show the preview of the first
email it crashes. The switch /NoPreview lets me go to my inbox but then Outlook crashes when I try to open an email (any email).
Outlook runs fine in Safe Mode so I tried to uninstall / disable Add Ins (set LoadBehavior to 0 in the registry). No success.
At work I could fix the issue by uninstalling SP1. But at home Office fails to roll back to a version before SP1 (integratedoffice.exe REPAIRUI RERUNMODE version xxxxxxxxxx). It says I must be online (which I am, of course). Reinstalling didn't help either.
Windows 7 Enterprise, 64 Bit (Work), Windows 7 Business, 64 Bit (Home). Office 32 Bit.
Company hosted Exchange Server 2010 (Work), 3rd party hosted Exchange account 2013 (Home), Outlook.com account (Home).
Creating a new profile with only the Outlook.com account did not fix the issue.
Outlook Product Stability Diagnostic and OfficeCAT could not find anything. So I don't know what to do anymore. Please help.
Thanks and kind regards,
iBlueDragon
PS: At home I fixed the issue by reinstalling my notebook with Windows 8.1. Now Outlook is running fine again. But still no solution for work.Is Hardware Graphics Acceleration enabled? We're seeing problems with Windows 7 when Aero is enabled - Outlook works fine with basic themes.
http://www.slipstick.com/outlook/2013/outlook-2013-hangs-due-hardware-acceleration/
Diane Poremsky [MVP - Outlook]
Outlook & Exchange Solutions Center
Outlook Tips
Subscribe to Exchange Messaging Outlook weekly newsletter -
Hi There,
I am having massive issues with my Exchange Server.
I have 2 Nodes, one has CAS and Mailbox Roles, the other just Mailbox.
I "upgraded" the CAS server to CU7 without any errors / issues.
Once I had restarted, nothing worked any more.. I couldn't access ECP, OWA, Powershell, Autodiscover or get outlook to connect.
I managed to get Powershell working, but changing the physical directory to "C:\Program Files\Microsoft\Exchange Server\V15\ClientAccess\PowerShell" from "C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\PowerShell"
But for the life of me I cannot get ECP or OWA working (haven't even tried anything else)!
I am getting a load of Events with ID 1003.
The only error I am getting is:
Server Error in '/ecp' Application.
Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.MissingMethodException: Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[MissingMethodException: Method not found: 'Boolean Microsoft.Exchange.Net.Wopi.WopiRequestPathHandler.IsWopiRequest(System.Web.HttpRequest)'.]
Microsoft.Exchange.HttpProxy.ProxyModule.AllowAnonymousRequest(HttpRequest httpRequest) +0
Microsoft.Exchange.HttpProxy.ProxyModule.OnAuthenticateInternal(HttpApplication httpApplication) +51
Microsoft.Exchange.HttpProxy.<>c__DisplayClass5.<OnAuthenticateRequest>b__4() +447
Microsoft.Exchange.Common.IL.ILUtil.DoTryFilterCatch(TryDelegate tryDelegate, FilterDelegate filterDelegate, CatchDelegate catchDelegate) +40
Microsoft.Exchange.HttpProxy.Diagnostics.SendWatsonReportOnUnhandledException(MethodDelegate methodDelegate) +408
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +165
Which is almost meaningless... but maybe someone out there has some idea?
Unfortunately this is very urgent for me a these are production servers and currently there is no email for my company.
So Please please please can someone help.
I have tried many many many things from various sites, and so far nothing has worked.
Thanks,
-TimHi Tim,
We can do the following steps to have a try:
1. Check Application settings in IIS Application under Exchange Back End web site for BinSearchFolders value.
a. Open IIS Manager. Expand Sites > Exchange Back End.
b. Click ecp. Open Application Settings in /ecp Home.
c. Please check whether the value for “BinSearchFolders” is changed to an invalid value.
2. Verify Authentication settings for OWA and ECP.
a. In IIS manager > Default Web Site, make sure Anonymous Authentication is Enabled in Authentication.
b. Confirm that "Require SSL" is checked on the root of the default website.
c. Make sure the Basic and Forms authentications are enabled in Default Web Site and Ntlm, WindowsIntegrated authentication methods are enabled in Exchange Back End for both OWA and ECP.
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]
Winnie Liang
TechNet Community Support -
Exchange 2013 OWA page blank after login
When logging into the OWA from *most* browsers (Chrome, firefox, Opera) OWA does not show up, just shows a blank page with the proper website title. OWA works fine on my mac with safari.
This is a picture of the network option in chrome development console, so there is data/files getting transferred..
http://imgur.com/yOUbAsR
This issue is leaving me dumbfounded because:
1. Everything works as expected in safari on my mac.
2. OWA worked fine a few days ago and I made no changes since then.
I have tried re-creating the SSL certificate with netsh, removing and creating a new OwaVirtualDirectory and disabling/enabling OWA on my account.Hi,
Does the issue happen to all users or only one specific user? Please check whether the issue happens in Internet Explorer in Windows.
Please make sure all browsers are using the latest version with Compatibility view. Also change a computer to have a try.
Regards,
Winnie Liang
TechNet Community Support -
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 & 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.ResponseMessageIn 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 -
Exchange 2013 - Quota notifications problem
Hello,
First of all I want to express mild disappointment with the way quota notification alerts are documented on Technet for Exchange 2013. The only reference I could find is that QuotaNotificationSchedule parameter of the Set-MailboxDatabase cmdlet no longer
does anything: "This parameter has been deprecated in Exchange 2013 and it no longer does anything.".
The only other reference I could find is this forum post:
http://social.technet.microsoft.com/Forums/exchange/en-US/f30bb2ca-91ab-4e69-a8b6-720e6a8a5b83/exchange-2013-quota-notification-message-not-sent-during-schedule?forum=exchangesvrgeneral
where it says: "Quota messages are generated once the user log in to mailbox in exchange 2013."
However, Microsoft Press published a book in 2013 "Inside Out: Microsoft Exchange Server 2013: Mailbox and High Availability" where QuotaNotificationSchedule parameter is being referenced as a working parameter which controls when Quota notification
are being sent.
My experience says that the forum post is correct.
Now onto the problem.
While our customer was still on Exchange 2010 they were the victims of this issue:
http://support.microsoft.com/kb/2480474/en-us which could easily be fixed with
CheckWarningQuota registry key.
Now we have migrated those mailboxes to Exchange 2013 and again, users are not receiving quota notification e-mails. Only a few users receive quota notifications e-mails and those are users that got their mailbox created on the new Exchange 2013 system.
Migrated users do not receive notifications. We have tried CheckWarningQuota on Exchange 2013 but it does nothing. Our theory is that mailbox flag introduced in Exchange 2010 SP1 is migrated with the mailboxes to Exchange 2013 and is the
reason why we are not receiving quota notifications again.
I appreciate thoughts and comments.
Regards,
DinkoCU8 addresses this issue, however, only for mailboxes not yet moved to 2013: https://support.microsoft.com/en-us/kb/303695
Mailboxes already moved will have to be manually fixed. The issue is they are missing their lcid (location ID). For whatever reason, the attribute does not make it across from 2010 to 2013. However, if you move the mailbox again to another 2013 database,
it fills in the lcid automatically. That is one workaround, but not necessarily a good one for people who have migrated a ton of their users already. So what do you do?
In the KB article, it shows you how to identify the users who are missing their LCID by doing the following in the exchange management shell:
#first load in the ManagedStoreDiagnosticFunctions, you will need this for the get-storequery cmdlet to work.
. .\'C:\Program Files\Microsoft\Exchange Server\V15\Scripts\ManagedStoreDiagnosticFunctions.ps1'
#then generate the list of all mailboxes with an LCID of 0.
$mbxs = get-mailbox –resultsize unlimited| ? {$_.exchangeversion.exchangebuild.major -ge 15}
$mbxsq = $mbxs | %{Get-StoreQuery -Database $_.database -query "select * from Mailbox where Mailboxguid = '$($_.ExchangeGuid)'"}
$mbxsq | ? {$_.lcid -eq 0} |fl displayname, mailboxguid, lcid
You can modify the script to dump the list to a text file if you need to.
Now, to address this, I simply populated the lcid for all my mailboxes. All of mine were en-US or lcid 1033, so it was easy to set them all at once. I just grabbed all Exchange 2013 mailboxes and applied the language (en-US) and DateFormat (MM/dd/yyyy) to
them (replace DOMAIN with your domain name) which in turn sets the lcid to 1033:
$mailboxes = get-mailbox -resultsize unlimited| ? {$_.exchangeversion.exchangebuild.major -ge 15}
($mailboxes).SamAccountName| %{set-MailboxRegionalConfiguration "DOMAIN\$_" -Language en-us -DateFormat MM/dd/yyyy} | FT -a
Incidentally, if you have already migrated all of your 2010 mailboxes, and you are on at least Exchange 2013 CU6, that script will resolve the issue whether you apply CU8 or not. CU8 fixes it for any other mailboxes that have not yet been migrated to 2013.
Hopefully this help you out.
Chris Allen
Microsoft Support Escalation Engineer -
Configuration Exchange 2013 DAG on two Server Data center 2012 with Hyper -V roles
Dears,
I try to planning and installation two hosts ( Data center 2012 servers) then install Hyper-V role on both this server, then create VM on each Data center server to be install Exchange 2013 on them.
After that I want to configure DAG between Exchanges servers, so what are the prerequisite to do that ?
Note: I use external IBM storage that will be located all VMs and DAG
Many thanksHi Moon,
In addition to Gulab's suggestion, I would like to clarify the following things:
1. Yes, we can use Standard or Datacenter version of the Windows Server 2012 operating system to configure Exchange 2013 DAG.
2. Each member of the DAG should be running the same operating system.
3. The DAG with an even number of members should have a witness server. A witness server is a server outside a DAG that's used to achieve and maintain quorum when the DAG has an even number of members.
What's more, here are some helpful articles for your reference.
Planning for High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638104(v=exchg.150).aspx#HR
High Availability and Site Resilience
http://technet.microsoft.com/en-us/library/dd638137(v=exchg.150).aspx
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support -
Cannot send email from Exchange 2007 to Exchange 2013
Hello Anyone,
Anyone can help? I've prepare MS Exchange 2013 already, for Migration MS Exchange 2007 and I got the issue.
My issue is I can't send email from Exchange 2007 to Exchagen 2013, but for Exchange 2013 can send email to Exchange 2007,
is my issue only internal email for external email both Exchange server is working fine.
Regards,
EakkasakThanks for your reply, when I send email from Exchange 2007 to Exchange 2013 I'm get the error message below.
Delivery is delayed to these recipients or distribution lists:
Eakkasak Buajan
Subject:
This message has not yet been delivered. Microsoft Exchange will continue to try delivering the message on your behalf.
Delivery of this message will be attempted until 8/29/2014 8:30:29 PM (GMT+07:00) Bangkok, Hanoi, Jakarta. Microsoft Exchange will notify you if the message can't be delivered by that time."
I'm already tick "Exchange server Authentication" in the Default Receive connector properties of Exchange 2013"
I'm restart services and restart all Exchange Server but doesn't work.
Thanks,
Eakkasak
Sent by Microsoft Exchange Server 2007 -
Is there Exchange 2013 view Exchange Management Shell command similar to Exchange 2010
Hi,
Is there anything similar in Exchange 2013 (Please refer the image). In Exchange 2010 if you make any changes via Management console you could go to "View Exchange Management Shell Command Log" and see what shell command it ran in the background.
It was very handy to copy shell command from here and then run it from shell in case you need to make bulk changes rather than try to find out the shell command from scratch.
I was wondering if there is anything similar in Exchange 2013.
Thanks,
RamanProbably in SP1...
Keep your finger cross ;)
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. -
I don't want to log into my Exchange 2013 every time when I need the Exchange Management Shell. Is that possible I can just install it on my workstation and then remote access to it? Thanks.
Lawrence FungCorrect - it is in the article Amy references, but is in the bulleted section at the top
The computer you install the management tools on must have a supported operating system (such as Windows Server 2012 or Windows 8), have enough disk space, be a member of an Active Directory domain, and satisfy other requirements. For information about system
requirements, see
Exchange 2013 System Requirements.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter: LinkedIn:
Facebook:
XING:
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. -
Exchange 2013 NLB Client Connections
Hi everyone, I'm
setting up an Exchange 2013 system,
the infrastructure that will be mounted
as follows:
-> 2 Domain Controllers
-> 2 Exchange 2013 backend servers
for DAG mailbox
-> 2 Servers frontend for
client connections on Microsoft NLB.
My question is regarding the Fronted
Microsoft NLB servers, I understand that
you have to redirect all SMTP and
IMAP traffic, POP, HTTPS, AS
... to distribute all Fronted
connections to servers (NLB shared
IP to the cluster).
This is correct?
thank you very much
Microsoft Certified IT Professional Server AdministratorHi everyone, I'm
setting up an Exchange 2013 system,
the infrastructure that will be mounted
as follows:
-> 2 Domain Controllers
-> 2 Exchange 2013 backend servers
for DAG mailbox
-> 2 Servers frontend for
client connections on Microsoft NLB.
My question is regarding the Fronted
Microsoft NLB servers, I understand that
you have to redirect all SMTP and
IMAP traffic, POP, HTTPS, AS
... to distribute all Fronted
connections to servers (NLB shared
IP to the cluster).
This is correct?
thank you very much
Microsoft Certified IT Professional Server Administrator
If you want to "Load balance" them, yes. Note that WNLB doesn't do such a great job at this and is typically not recommended as its not application aware.
Not sure what you mean by "NLB shared
IP to the cluster)" The client connections go to the CAS roles, not the DAG cluster IP
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied. -
Still restarts after instalation WIN7
Hi everyone,
I have problem, I have bought Lenovo IdeaPad G570 without OS. I tried to instal WIN7, everything going fine, but at the end of instalation, notebook wrote "logon process initialization failure" and still restarts. In instalacion I deleted partitions, and format the new one so i havent my backup file. I tried to recover it, but still the same. Could you help me pls.System get restarted after installation of windows. I would suggest you to kindly check the SATA mode controller in the BIOS mode, change it to IDE or compatible mode. To do so please restart the system and press F2 key continuously, Bios screen will appear.
Also you can check with other operating system.
Thanks & Regards,
Sameer
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution".! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter! -
Move Exchange 2013 to new Virtual Server including settings?
Since we have a failing VM Exchange 2013, we need to move the installation to a new server. We have created a new Hyper-V Server 2012 and installed a new Exchange 2013 on it. After connecting the new server to the domain we can see all settings and users
of the existing Exchange Installation.
Since the old server has a corrupt RAID, we need to move all data and settings to the new server. We have moved some user mailboxes with the ecp to the new server. They are still working, but mailtraffic takes exactly 1 hour now?! Also these users who logon
with Outlook now get the error message 'problem with the safetycertificate of the proxyserver (translated)'. The mail still works, but 1 hour delay.
Can we now move the other mailboxes too? And if we have moved them, how can we move the settings of this server? If we shutdown the old server, will Exchange (the moved one) still be up and running? Because we are afraid that when we shutdown the old server
it will not boot again.
Thanx for any tips of leads in the right direction.1. Outgoing mail from https://echange/owa is
working.
Did you try https://ip-address-of-newserver/owa and send an email outside?
2. Outlook 2010 does not start, cannot find mailboxes to open, so user won't have mail in the morning.
Get-OutlookProvider -Identity EXCH | FL
If is field CertPrincipalName empty type following:
Set-OutlookProvider EXCH -CertPrincipalName msstd:FQDN-YOUR-MAIL-SERVER
After this it should work (assuming all your mailboxes moved to the new server).
Please check this to see you the mailbox servername
http://www.zerohoursleep.com/2013/02/manual-outlook-configuration-with-exchange-2013/
3. Incoming mail cannot be delivered by the Barracuda (connection refused).
Ensure Barracuda is sending email to the new server and new server is not blocking incoming traffic.
4. OWA and ECP not working from outside (public IP).
Ensure you NAT is correct by site. Check it is listening to the port using http://www.canyouseeme.org/
Please check these and get back
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.
Maybe you are looking for
-
Word-by-word sort order in indexes
Hi again, I need to change the sort order in my indexes from letter-by-letter to word-by word. According to the help file, 1. Choose View > Reference Pages, and display the reference page that contains the special text flow for the index. 2. Add a sp
-
iPad2 did a backup when I uploaded iCloud and some of my apps like Recipe Box are missing. Where would they be now?
-
Itunes keeps skipping, still not answered!!!
i asked this question a few days ago, but no one answered and im wondering why. now all i want to do is downgrade to an earlier version of itunes because i never had these problems with itunes 6. plus i was able to organize my library from 0-9,a-z. n
-
Bought a Template for a customer Need Help
I know HTML but the coding to change things baffles me. I am out of help with the seller who is in Australia. This is what the .txt looks like that I change function with. &Home_txt8=<font color="#d0d0d0"><b>text goes here It looks straightforward b
-
Anybody know how to cut and paste text with Fascinate?