how to forcefully shut down physical server host through ILO? - vmware

I am new person of vmware environment i have shutdown a physical server through
RDP but it is not properly shutdown when i was checked in the ILO. Please suggest
how to shutdown a physical server?

To forcefully shut down a server host through iLO, you will first need to log into the blade system where the host is located. From there, click the host and in virtual power option, there should be an option to power off the blade.

Related

GCP windows VM does not work when logged off

I am running a Windows Server VM on GCP.
When logging in via Remote Desktop, I am starting certain applications which should actively run for a couple of hours.
But when closing my Remote Desktop Connection, all applications stop working.
How can I prevent this from happening?
In order to keep the session ongoing, you'll have to configure the RD Session Host time limits.
Open the group policy editor with: Windows+R, then type gpedit.msc, confirm with Enter.
Then in the management console, navigate to:
Computer Configuration
Administrative Templates
Windows Components
Remote Desktop Services
Remote Desktop Session Host
Session Time Limits
There one can adjust the settings:
Set time limit for disconnected sessions
Terminate session when time limits are reached

Can not connect Remote Desktop to windows server after restart

I have a server Google Cloud, it has been good working some years, but recently there was a problem, after restart server, I can not connect to its remote desktop, the prompt messagebox content is as follows:
Remote Desktop can’t connect to the remote computer for one of these reasons:
1.Remote access to the server is not enabled
2.The remote computer is turned off
3.The remote computer is not available on the network
But i check it is still on and has network connection, anybody help me?
update 1: I found the reason is port 3389 could not connect, but I tried the commands on command line still can't open port 3389
update 2: my team decided to destroy this server, close topic

Slow Connect via Open / OpenAsync .Net Provider Unidata

I am consistently seeing a 3+ second delay when opening a connection to a Unidata server via OpenAsync and the ADO.NET provider by Rocket.
What can I do to diagnose this delay?
I use jdbc and odbc connections all the time, and three seconds just ain't right.
You can start by breaking things down into client, network, server.
On the client, is it the same if you use an IP address vs hostname? If different, then DNS delay. Do you have any antivirus or other software that might be delaying connections? Can you turn that off, or do a test from a freshly configured machine?
For network, can you ping the unidata server in millseconds? Are there firewalls in the way? Can you install wireshark and filter packets by destination? Is there a delay when you ssh? Is the server configured with LDAP/AD, or local authentication - could be connecting to another server to authenticate?
On the server, you can turn on uniobjects logging, then restart unirpcd. Do you have something in your LOGIN/UOLOGIN that is hanging up the remote connection?
$cat $UDTHOME/serverdebug
udcs 9 /tmp/udcs.log

Check remote host state in a nework using Indy comps

I have client server application that works with Firebird server. Everytime when clients connect to the server they(client apps) don't check if there is a network connection to the server so at this time my application sometimes freezes when the server computer is switched off or service has stopped, so first of all I need to check connection if remote host is switched on or at some port anything listening....
Before establishing the connection I need to check it and make sure server and service is running using Indy components.
Any ideas? also I can use IcmpClient to ping remote host and then establish connection but which is the most optimal way ?
If you just want to check if the server computer can be reached, you could do a "ping" to check that. However, if you want to check if a specific TCP port is open, then the only way to find that out is to actually do a proper connect, which leads to the "freezing" program while the connection times out if there is no-one listening on that port.

VMware ESXi: Automatic restart of an VM

Here I have a machine with VMware ESXi 5. One of my VMs is shutting down after some time (I can't prevent this). However, I want the VM to be automatically restarted if it was shut down. But I can't find an option in my vSphere client to do this.
So is there a way to do an automatic restart?
ESXi 5 has option to start and stop VM automatically
Go to ESX host configuration and left side you can see "Virtual Machine Startup/Shutdown"
Go to properties and select "Allow virtual machine to start and stop automatically with the system"
in Startup Order move your VM machine in "Automatic Startup section"