(0 comments, 96 posts)
This user hasn't shared any profile information
Home page: http://vworld.nl
Posts by Xander
I recently reinstalled my VMware servers using USB sticks. After the first reboot I noticed an yellow warning. When highlighting the different servers I noticed the “System logs are stored on non-persistent storage” warning.
This is how you can fix that :
Select a persistent (SAN?) storage that you can use and go to Browse Datastore.
Create a new folder
Give it a name..
After that go to advanced settings bij the configuration tab of your ESX server.
Go to the Syslog tab.
Give the name of the datastore between brackets and the name of the folder you just created. Hit ok and you notice that the warning is gone :
I use the community version for anti spam/virus. Mailcleaner is an Linux appliance that’s easy to set up and configure. The community version is free of charge and can be used to block spam and viruses before they enter your mailserver (for example my Exchange servers). When you have any questions or want to hear about my experience regarding Community please leave a comment.
Here is how you can update to the latest version :
cd /usr/mailcleaner cvs update -dP updates
Some days ago a friend of mine asked me how it’s possible to update the PHP version to the latest stable build. Updating using the regular (web) interface didn’t seem to work…
This is how you do that :
add-apt-repository ppa:onderj/php5 apt-get update apt-get install php5
Do you want to demonstrate or test Veeam Backup and Recovery V7?
When you are holding the vExpert/VCP/MCP/MCTS or MVP status then you’re entitled for a free 180-day NFR license for Veeam Backup & Recovery for the new 7 version.
Check it out here.
Sometimes you don’t want to wait/rely to your WSUS environment for specific updates.
But when you try to install updates manually you might notice the following message :
It’s easy to go around this, you copy/paste the following code into a reg file :
When you apply the above regfile and go to windows updates you notice that updates are possible again :
Today I ran into a problem after updating Exchange 2010. After a reboot (which took ages!) I noticed that all the services were disabled. After some troubleshooting I found out that the problem had something to do with an installed update. My resolution (and was planned) was to install the latest servicepack (SP3). There is one drawback, the services are disabled and Exchange SP3 setup is unable to stop/start them.
I used this powershell command to set the service to manual :
During the install I had to execute this command 2 times, the SP3 setup worked fine and after that the services were automatically started.
I ran into this great wiki article from Microsoft from where you can find and download (!) all the Exchange 2003/2007/2010/2013 servicepack’s and fixes. You can also check all the build versions.
You can find the link here.
Update : a co-worker attended me of the continued list of the link above here
This is how you easily can kill an running VM :
- Login to your VMware server
- Start esxtop
- Press c to show CPU resource screen
- Press Shift-V to show only virtual machines
- Press f to add a column (Leader World ID)
- Identify the machine you wish to kill (LWID)
- Press K and enter the ID
- Wait for a couple of seconds
Some time ago I ran into an error while installing Exchange. It seems this problem also occurs when upgrading/installing an Exchange Server service pack. This is how to fix this problem :
First go to the (root) domain controller and register the schema extension :
Now load the plugin by starting mmc and adding the extension
Now right-click the Active Directory Schema en select Change Active Directory Domain Controller. (Choose the domain controller you wish to transfer the schema role to)
Hit ok when you receive the read-only warning.
Now select Change Schema Master and hit Change.
A customer complained about the following error :
The problem is that the list of the Trusted Root Certificates (TRC) is too long. The solution is simple : use microsoft fixit : http://support.microsoft.com/kb/2801679 or delete the following key : HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SystemCertificates\AuthRoot\Certificates
You don’t have to restart anything afterwards.