When we deploy our code to an on-premises Windows VM using deployment groups, but the target machine appears offline in Devops after registering the deployment group.
How to establish connection between target server and Devops? Especially when the Devops server is under VPN.
Related
In Azure, want to send logs of Windows Virtual machines to 2 different Logs Analytics Workspace. I have different resource groups that want to collect logs there themselves in Logs Analytics and security logs(custom logs) to centralize(single) Logs Analytics Workspace from different resource groups.
Is it possible to send logs to multi-workspace analytics?
Since you have windows VM, you can setup to send to multiple Log Analytics Workspaces (multi-homing).
Extension is applicable for Azure Virtual Machines. Direct agent can be used for Azure and non-Azure Virtual Machines(on-premise). The agent isn't only for connecting to Azure Monitor. Other services such as Azure Security Center and Azure Sentinel rely on the agent and its connected Log Analytics workspace
If automatic provisioning is On, Security Center provisions the Log Analytics Agent on all supported Azure VMs and any new ones that are created.
Note: Windows agents can connect to up to four workspaces, even if
they are connected to a System Center Operations Manager management
group.
The Linux agent does not support multi-homing and can only connect to
a single workspace or management group.
This question is bit on the Reverse Side of Connecting via SSMS from Azure VM to on premise SQL Server.
Can Hybrid connection Manager be used to configure connectivity between Onpremise and Azure such that i can use SSMS from Azure VM to connect to OnPremise SQL Server?
I don't think you can use Hybrid connection Manager to connect between On-premise and Azure network. As far as I know, the HCM is a relay agent and included in a partition of hybrid connection feature. The hybrid connection feature consists of two outbound calls to Azure Service Bus Relay.
For example, if you want web apps in the app service to access the DB in the on-premise network. There is a connection from a library on the host where your app is running in App Service. There is also a connection from the HCM to Service Bus Relay. See how it works. Also, The new Hybrid Connections capability of Relay is a secure, open-protocol evolution based on HTTP and WebSockets. In this case, you could not create a Hybrid Connection from Azure VM to Service Bus Relay via SSMS.
So, If you want to connect the on-premise SQL server from Azure VM via SSMS, you need to set up a VPN connection between Azure and your on-premise network. Read more details about VPN gateway.
Getting below error on winrm SQL server DB deployment task in azure devops ,
Microsoft.PowerShell.Commands.WriteErrorException: Deployment on one or more machines failed.
System.Management.Automation.Remoting.PSRemotingTransportException: Connecting to remote server 1xx.xx.xx.xxx failed with the following error message : The
client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult
the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service,
run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the
about_Remote_Troubleshooting Help topic.
The hosted agent doesn't have a route to your on-premise network. You'll need to install and configure a self-hosted agent that resides within the network you're trying to connect to.
Is there a way to run Linux Docker images in a Windows Hosted Agent (Hosted Windows Container as recommended here)?
I want to run Linux Selenium Containers hosted in Docker Hub on an Azure DevOps Hosted Agent. I need to run them on a Windows Host because the next tasks in the pipeline (eg. running VS Tests) require a Windows Host.
I have setup Worklight Studio in my local Machine and developed a sample application. I need to deploy that application to a Worklight Server set up in another PC in the same network (LAN).
You already have a server in your local machine - Worklight Studio contains an internal Worklight Server. But that doesn't matter...
If you are using Worklight 5.x:
Open application-descriptor.xml
Find the worklightServerRootURL element
Change its value to that of the remote Worklight Server, for example: http://myotherserver:8080
Right-click on the application folder and choose: Run As >> Build All and Deploy
Take the *-all.wlapp and/or *.adapter files from the bin folder and deploy them via Worklight Console that resides in the other server machine.
If you are using Worklight 6.0:
Right-click on the application folder and choose: Run As >> Build for Remote Server
Enter the details of the other server machine (host, port, context root)
Take the *-all.wlapp and/or *.adapter files from the bin folder and deploy them via Worklight Console that resides in the other server machine.
The above assumes that the remote server(s) are configured to accept the applications and/or adapters you will deploy (that is, that you have deployed the .war file of the project; your scenario was not very detailed so my explanations were somewhat lexing).