On-Premise
12 TopicsAdvantages of installing a newer build agent?
We have an on-prem Azure DevOps server (2020 update 1.2). All our builds use the "default" agent (v2.181.2) created when DevOps was installed. I'm aware that it is possible to download and install agents from here: https://github.com/microsoft/azure-pipelines-agent/releases, but what are the reasons for doing so? Are they merely to provide bug fixes and performance improvements, rather than (say) new build tasks or build task features (which I assume are part and parcel of DevOps itself, and have nothing to do with agents)? One of the reasons I ask is that last year I tried installing a new agent (v2.210.1), and builds had been working fine. However we recently started seeing our builds taking a long time, and in the agent log found that the agent was repeatedly attempting to downgrade to v2.181.2. Why was this? Is something limiting which version we can use, e.g. the version of DevOps itself, or a particular task in the build definition? (The build did continue to work when I reconfigured it to use the default agent, v2.181.2, which is coincidentally what the newer agent was trying to downgrade to). I assume I would get similar issues if I was to create an agent using the latest version (currently v3.227.2)? Like I say, curious to know why I would want to install a newer agent in the first place.874Views0likes0CommentsHow to test mail flow in Exchange 2019 in an existing Exchange 2013 environment.(Solved)
Hi experts, I'm trying to complete the upgrade process from Exchange 2013(on-premise) to Exchange 2019(on-premise). I did all the steps that are explained in Best Practice for Upgradeand the Upgrade Assistant from Microsoft experts. Also, I'd like to thank you for them. But what is my question? There are 2 Exchange 2013 servers in my domain with more than 2000 users. I installed new Exchange servers and all work fine in the organization. Regarding our business, I can not take a risk and start mailbox migration directly and would like to test all things in the new environment first, like OWA, Outlook, and all related things to the new environment. I created some databases on the new servers and some users on them to test mail flow on these servers. The problem that I have is, that I can connect directly to new servers in OWA to newserver.mydomain.com and work with test users, and mail flow there works fine. But when I try to use Outlook to test, it can not find new servers. I think my issue is autodiscover record in DNS but I can not change it at the moment, because the old environment is working. When I change this record on the new servers to itself(newserver.mydomain.com) and try to configure a profile on Outlook manually and set the mail servers on the new server directly, Outlook still can not find the servers. What is your suggestion to have a test way in my case? I searched so many articles to find a way but it seems in this way, there is no solution. I don't want to create a new zone for the test, because in the External mail flow test, I will need an SSL certificate. I appreciate any help or ideas that you can provide. Kind Regards, HassanSolved4.2KViews0likes8CommentsExchange on-prem and Global Catalog Servers
Hi everyone, We have an Exchange 2016 server on windows server 2016. And there are 3 DC and GC server that Exchange uses. I listed them withGet-ExchangeServer -Identity “ServerName” -status | fl command. One of the GC server is Server 2012 and the others are server 2016. I noticed repeated error messages on Application logs event viewer about the 2012 server. The message is below: What must we do? Get-Notification -Summary "True" contoso.com/Users/Administrator S-1-5-21-4142341382-305344678-3004717128-500 S-1-5-21-4142341382-305344678-3004717128-500 Local-ECP-Unknown 5204 w3wp#MSExchangeECPAppPool 123 00:00:00.0350004 View Entire Forest: 'True', Configuration Domain Controller: 'DC2012.contoso.com', Preferred Global Catalog: 'DC2012.contoso.com', Preferred Domain Controllers: '{ DC2012.contoso.com }' Microsoft.Exchange.Data.DataSourceOperationException: The request failed. The underlying connection was closed: An unexpected error occurred on a send. ---> Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The underlying connection was closed: An unexpected error occurred on a send. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.ConnectStream.WriteHeaders(Boolean async) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.GetResponse() at Microsoft.Exchange.Data.Storage.Management.EwsHttpWebRequestEx.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse() at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request) --- End of inner exception stack trace --- at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request) at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request) at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute() at Microsoft.Exchange.WebServices.Data.ExchangeService.FindFolders(FolderId parentFolderId, SearchFilter searchFilter, FolderView view) at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback) --- End of inner exception stack trace --- at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback) at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.GetOrCreateFolderCore(String folderName, FolderId parentFolder, Func`1 creator) at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.GetDefaultFolder() at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.get_DefaultFolder() at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<>c__DisplayClass24_0`1.<InternalFindPaged>b__0() at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback) at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.<InternalFindPaged>d__24`1.MoveNext() at Microsoft.Exchange.Data.Storage.Management.AsyncOperationNotificationDataProvider.<GetNotificationDetails>d__17.MoveNext() at Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.WriteResult[T](IEnumerable`1 dataObjects) at Microsoft.Exchange.Management.StoreTasks.GetNotification.InternalProcessRecord() at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__91_1() at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed) ServerOperation Microsoft.Exchange.WebServices.Data.ServiceRequestException: The request failed. The underlying connection was closed: An unexpected error occurred on a send. ---> System.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) --- End of inner exception stack trace --- at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest, Boolean renegotiation) at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result) at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size) at System.Net.ConnectStream.WriteHeaders(Boolean async) --- End of inner exception stack trace --- at System.Net.HttpWebRequest.GetResponse() at Microsoft.Exchange.Data.Storage.Management.EwsHttpWebRequestEx.Microsoft.Exchange.WebServices.Data.IEwsHttpWebRequest.GetResponse() at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request) --- End of inner exception stack trace --- at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.GetEwsHttpWebResponse(IEwsHttpWebRequest request) at Microsoft.Exchange.WebServices.Data.ServiceRequestBase.ValidateAndEmitRequest(IEwsHttpWebRequest& request) at Microsoft.Exchange.WebServices.Data.MultiResponseServiceRequest`1.Execute() at Microsoft.Exchange.WebServices.Data.ExchangeService.FindFolders(FolderId parentFolderId, SearchFilter searchFilter, FolderView view) at Microsoft.Exchange.Data.Storage.Management.EwsStoreDataProvider.InvokeServiceCall[T](Func`1 callback) False 0 objects execution has been proxied to remote server. 0 ActivityId: 381df104-eb5c-440b-9ec4-5441b0b6bf21 ServicePlan:;IsAdmin:True;1.1KViews0likes0CommentsOn Premise Exchange 2019- Issue sending to external addresses
This is my first on-premise Exchange setup since back in 2008SBS, so please forgive my ignorance...lots has changed. My 2019 Exchange setup is being created for around five users in a small office, so we'd like to keep things simple. No smart connectors. Simple direct connection to ISP via firewall. Not worried about receiving mail from external sources for the time being. External Domain name: example.com hosted on a standard webhost which hosts our website Internal/local Domain Name: whatever.example.com I'd like the mail to show as coming from example.com. My internal e-mail all works fine. However, when I send to external addresses, the e-mail is blocked as Junk by the external SMTP server (my ISP's server) because the outgoing mail comes from my internal server/domain (whatever.example.com) - which of course doesn't exist externally, so it is marked as SPAM by the ISP. Yet, when I run the testconnectivity (Outbound SMTP) tool, it passes with a warning about an SPF record (which, of course, doesn't exist for whatever.example.com). I'm sure I'm missing something simple, but my searches have come up empty so far. Any direction would be appreciated. In the old SBS editions, a person could simply enter the SMTP FQDN of the ISP and external SMTP worked...that's sort of what I'm hoping to emulate. Thanks!2KViews0likes3CommentsOn-prem access audit
Hi, Our customer would like to link their M365 tenancy (SharePoint) with on-prem servers (file shares) so they can have an audit / logs on the files being access and copied. We have a looked into Azure Information protection and deploying scanners but that seems to be seems mostly used for data classification. What would be the best way to achieve this?2.4KViews0likes1CommentSMTP relay - Client host rejected: AP0002
Hello everyone, We have to send emails to a Bouyges address (a french telecom company) and I got this back: Sorry, no SMTP connection got far enough; most progress: RCPT TO response; remote host said: 554 5.7.1 <...dsl.sta.abo.bbox.fr>: Client host rejected: AP0002 Please use your ISP mailserver. (#5.5.0) I searched on Google to find a way to send the emails and what I understand is that I have to configure the SMTP relay of Bouyges. What I found are only configurations for postfix and I don't know how to configure it on an Exchange On-premise server, do you have any info? The SMTP server of Bouyges issmtp.bbox.fr What I don't know if it's possible to do is to use this relay only for the bbox mails address. Thanks for any help!1.1KViews0likes0CommentsHow to connect to on-premise?
I am making a powerapp to create a better user experience with our test requests. All of the test requests, and associated data, are stored in an on-premise sharepoint. I have followed steps to setting up agatewayI don't see how this gateway allows me to do anything else. I don't set up a link to the sharepoint anywhere in this gateway, it is just associated to my account. Anyways, I connect my gateway to powerapps, and when I try connecting an existing list from the on-prem sharepoint, it gives me the following error. I know the sharepoint list exits because we use it today, but I am just not sure what else I need to do. Do I need to sign into the gateway with specific credentials (creator of the on-prem sharepoint)?2.3KViews0likes1CommentMove on-prem environment to Azure migration
Hi there, I'm working on a customer with a traditional Windows AD domain. The customer wants to have all their Windows VMs (now running on VMWare) to Azure. For the clients we recently managed to make all devices Azure AD Joined only. M365 suite is used for Teams/SharePoint/ExchangeOnline, Defender for endpoint and Endpointmanager for client management. We have no domain joined computers anymore. All the users are still in Azure AD Connect that syncs to Azure AD. Printers are on universal print and files to Teams/SharePoint. We now have a large file share that we could not migrate to sharepoint. We would like to have this on Azure Files. Right now we are in the start of creating an Azure subscription. What should be the best route to take for this? On-prem there are a couple Windows (apps) VMs that we would like to 'lift and shift' to Azure. These app servers are used for legacy/history checking... If there is any clear path or documentation that we can consult, would like to know. Thanks in advance!3.3KViews0likes3CommentsSP 2016 On-Premise Document Library New button gives error
hi all we have SP 2016 on-pemise version and we use infopath forms a lot. we had some updates applied to the server and since then when users tried to add a new form by clicking NEW button on the library opens up upload dialog instead of opening infopath server. I am very sure this is because of the windows update but the update is a permanent change and cannot reverse it, any help is greatly appriciated.!998Views0likes0CommentsDMARC reporting for Exchange on-premise
I need advise on generating human-readable DMARC reports without the use of any external reporting services provided by many companies out there. I was hoping someone has any idea of a tool that can be installed and used on-premise. It would be nice to have if the tool is also able to present recommendations or remediation tasks. Thank you.2KViews0likes3Comments