- Hit “Winkey + R” to open the “Run” box
- write mstsc and hit Enter
- Click the “Show options” button and go to Options tab, mark the “Use all my monitors” checkbox.
Today I had a frozen ESXi server that was physically located in a different country so manually resetting it was not an option and when I tried to connect to its ILO using https with my web browser I’ve received an error and could not even get the ILO login screen.
I’ve tried to reset the ILO using SSH which usually worked for me in the past with no sucess, by the way it’s done by:
That short process resets the ILO and usually is enough to login and update the firmware from the web UI which is a lot simpler.
But in my case two things happend:
So, first of all if you have blade servers like in my case you can do many very nice things directly from SSH directly to the enclosure.
One very important thing is to reset the specific blade ILO from the enclosure using:
Reset ILO [bay number of server]
And now for updating the firmware (Finding the right bin file is at the end of this post):
There are two options that I saw, one is to use http (which didn’t work for me) and the other one is with using TFTP server (very easy once you have a guide like this one).
For the first option:
load –source http://192.168.0.1/ilo4_240.bin
The second option have two parts:
<LOGIN USER_LOGIN="username" PASSWORD="password">
Second you need to setup the TFTP server:
Now for the actual work:
hponcfg [bay number of server] tftp://TFTP_SERVER/update_firmware.xml
And that is it, basically what we did is pointed the enclosure to download from the TFTP server an update script that tells it to download a firmware bin from the TFTP server.
in case you don’t know where to download the right bin file:
you just need to know what is your ILO version and than you search google for:
“ILO4 firmware” for example, the first result should bring you to here:
Download the version for any windows server and when you run it you can select “Extract”, pick a folder and inside of the extracted content you will find the Bin file.
Hope I was able to help someone.
In exchange 2010, event id 1221 does not exist anymore, and in order for us to find the whitespace, Microsoft has provided an appropriate command shell:
Get-MailboxDatabase -Status |ft name,databasesize,availablenewmailboxspace -auto
When a new user is created, in some cases an SMTP address is generated in the format of firstname.lastname@example.org instead of email@example.com although there is no such existing address on the network
Issue is possibly due to the x400 configuration on the e-mail address policy:
When the email address is stamped, x400 finds the 2nd user as duplicated as the user’s First Name and Last Name are same.
So it adds 2 in the X400.
As the X400 found it as duplicate and added 2 , SMTP also follows the same and adds 2 to address.
Remove x400 configuration from e-mail address policy and restarted the Exchange services.
*Please note that X.400 address function is not necessarily required in pure Exchange 2007/2010 environments.
On your Exchange Server, Open the Management Console then from Server Configuration, Click on “New Exchange Certificate”
Enter A name for your Certificate, then click Next
Leave the ” Enable Wildcard Certificate ” un-checked, then click Next
Select the services that this exchange certificate will handle.
*Add or remove names -by clicking on the green Plus sign Add Or remove by selecting the name and click on the x sign
Enter Organization and Location Data.
Specify where the Certificate Request will be saved
Click Next, Then Click New
Exchange will start creating the Certificate Request
When Completed , Click Finish
Open CA web page using an Internet Browser, For Example http://caserver/CertSrv Then click on ” Request a Certificate ” Link
Then Click on Advanced Certificate Request
Then Click on ” Submit a Certificate Request ”
Open the Certificate Request file you created in Exchange With Notepad Select all Text
Paste the text into the webpage, and select ” Web Server ” from the Certificate Template list, Then Click Submit.
Select Base 64 Encoded, then click on Download Certificate Chain.
Save the certificate
On The Exchange Server:
From the Exchange Management Console –> Server Configuration,choose the the certificate you requested and Click on Complete Pending Request
Select the Certificate you downloaded from the CA, then Click Complete
Right click on the Certificate, select Assign services to certificate
Add Office 2016 Key to KMS server:
In order to add the KMS you need to install the Microsoft Office 2016 Volume License Pack
1. Download the Microsoft Office 2016 Volume License Pack fro here
Follow the steps:
Enter the Product Key
Open VMAT to see the new office 2016 product key
If you receive this error while trying to import your Windows 10 product keys to KMS VAMT server 3.1, it means that you need to upgrade your VAMT version.
It is not possible to import Windows 10 keys in VAMT 3.1 keys.
Download the adk from here
1. If you don’t have .Net framework on your KMS server the setup will install it, After the .net installation the server will reboot
2. Specify location
4. License Agreement
5. Select VAMT
9. Choose the VMAT DB And connect
10. Import your windows 10 product key
Get every new post delivered to your Inbox
Join other followers