Author archives: Gert Kjerslev

“StalledDueToMailboxLock” when migrating Publicfolder to Exchange 2013

Some time ago I moved a customers public folder from Exchange 2010 to Exchange 2013 CU5. I flowed this excellent KB from Microsoft http://technet.microsoft.com/en-US/Library/jj150486. But when I got to the part of finalizing the move I got this error when I ran “Get-PublicFolderMigrationRequest | Get-PublicFolderMigrationRequestStatistics” StalledDueToMailboxLock and a message that the job will resume i 5 minutes or so. It turns out that the information store was locking the PF mailbox, after a restart of the information store service the job completed 100% at the next retry.!        

vExpert 2014 Announcement

It’s a great honour to be awarded vExpert for the second time in a row. I’m glad that I could help in the VMware community. A big thanks to VMware and the people behind vExpert.
Here’s the full list of 754 vExperts. http://blogs.vmware.com/vmtn/2014/04/vexpert-2014-announcement.html
Congratulations to all vExperts 2014, keep up the good work!


Log Insight 2.0-beta is available

VMware has just made Log Insight 2.0 beta available for downlaod. Also there is a webinar on the 1st of April. You can Register to get a quick overview of our new features:overview of our new features:
  • Scale-Out with High Availability
    • Cluster deployments up to 6 nodes
  • Proactive Analytics
    • Automated data summarization of event types
    • Smart fields to aid in extraction
  • Super-Powered Dashboards
    • Easily add new data filters on the fly
    • Interact between dashboard widgets
  • RESTful API for log ingestion
  • Improved self-monitoring tools
  • Windows collection agent
    • Forwards Windows event logs
    • Monitors & forwards flat log files
    • Centralized reporting & management
Download Log Insight 2.0-beta
VMware vCenter Log insight website


Unable to install Microsoft Windows Server 2012 on VMware ESXi host – IBM System x

This will be a “note to self” kind of post. But I guest if you work with IBM or vendor based Windows Server media like IBM’s ROC/OEM you will run in to this. When you get the Windows Server 2012 R2 Datacenter ROC media from IBM, and try to install it in a VM on a IBM VMware vSphere host, you will get to a point where the installer stops and says :
“Please check with your computer manufacturer to resoleve ant issues your are having with this computer. These tools are built to only run on IBM Computers. Since this is not an IBM computer click OK to shutdown”
IBM Windows server 2012 R2 ROC Error
IBM has been so kind to include a system check, to see if the media is used on a non IBM server. This is okay, but in my case the host is a IBM System x! The checker is not designed to run on a VM so you have to do one of two things. 1) you could go out and find a retail Windows Server 2012 R2 DC OEM media that has no hardware vendor checker. 2) you can edit the .vmx file of the VM to add the SMBIOS.reflectHost and set it to true like this : SMBIOS.reflectHost = “true”. This updates the virtual machine BIOS with the IBM Original Equipment Manufacture (OEM) information required to use IBM-provided Operating System (OS) installation media. IBM addressed this with there Windows 2008/R2 ROC media, but it is still true with Windows Server 2012 R2.
Please leave a comment below if you have similar experiences with other vendors or any comment to this post. Thank!


The vExpert 2014 applications are now open!

Applications for the 2014 vExpert program are now open. You can submit your application at : http://blogs.vmware.com/vmtn/2014/02/vexpert-2014-applications-open.html This year there is a fast track application for 2013 vExpert. Also new for 2014 there will be a nomination for 2014 for those that did not make the first cut, to get in later on in the year. You have until March 6th to get your application.


Unable to initialize the Microsoft Exchange Information Store service

Okay, so I got this error in the event log (ID 5003) on a Exchange Server 2010, after a update and a reboot of the server. The Information store service could not start up
Event ID 5003: Unable to initialize the Microsoft Exchange Information Store service because the clocks on the client and on the server machine are skewed. This may be caused by a time change either in the client or the server machine, and may require a reboot of that machine. Other than that, verify that your domain is properly configured and is currently online.
time_exchange_cannot_start_services
The time was okay on the server and the DC (PDC) was okay. Then I checked the VMware tools to see if the “Time Sync” Feature of the vmware tools was disabled, and it was. I noticed after a second reboot that the time was off by 10 minutes, and then jumped back to the correct time!?. Then I looked at the VMware vSphere host in the “Time Configuration” the time was of by… you guest it.. 10 minutes! The host was set to sync with an external time server (pool.ntp.org). But the time was off anyway. So I decided to reboot the host, to see if the time was off by 10 minutes after a reboot and it was! Then I did another reboot and jumped in the UEFI (BIOS) of the server and there it was… time in the BIOS was 10 minutes behind. I corrected it and booted the host and now the time on the host and the VM was okay even after a reboot.
I hope that you can use this information, I know where I will look next time there is a time sync issue in a VM. Please leave a comment below if found the useful. Thanks!


Using iTerm for access remote SSH to vSphere

At work I use mostly a PC, but at home I use Mac OSX. Therefor I also used Mac OSX terminal to SSH in to my home lab. But I found some shortcomings to the build-in terminal application i OSX. A friend pointed me in the direction of iTerm, and sayed I should have a go at it. So I did. Some of the problems I had with the build-in terminal application was that ESXTOP looks something terrible. But in iTerm all that just went a way. Also iTerm has some cool features like Mouseless Copy, find-on-page search and much more. It free, but I will encourage you to donate if you decide to use it. You can get iTerm from iterm2.com Try it out and let me know what you think about it in the comments below. Thank!
Mac OSX build-in terminal application running ESXTOP:
ESXTOP - MAC OSX terminal
iTerm running ESXTOP:
iTerm


Fast Active Directory object recovery tip for Veeam

The other day I had a customer who had deleted a active directory user by accident. The customer was running some Windows server 2003 DC so no AD recycle bin. So on to veeam for the restore, it took a very long time to complete all the steps, also you have to go to the enterprise manager to approve the restore lab, and then you can go back and start the restore. But I got at tip from @poulpreben over a Veeam Denmark (Thanks!). To skip the approval part in the enterprise manager, you just have to right-click the sure-backup job and choose “Active directory wizard” this will get you directly to the part where you can restore the deleted user, another tip is when you are looking for a deleted user you can just type (DELETED) in the search box, this will return all deleted users. I hope this can help you in any form or way. Please drop a comment below in the discussion box, if you have any tips for restoring AD objects with Veeam. Thanks!


Installing vCloud Usage Meter step-by-step

In this post I will go through the steps needed to setup VMware vCloud Usage Meter (v.3.2). The vCloud Usage Meter is used to collect and generate reports for VSPP’s to send back to VMware for monthly billing of usage. You will first need to download the vCloud Usage Meter virtual appliance in OVA format from VMware here you can also get the User Guide. When you have the appliance, use the vSphere client to delopy the appliance but first you will have to make a IP Pool for the appliance.
Go to the datacenter -> IP Pools tab and click add and fill in the default gateway and subnet mask on the IPv4 tab, do not set “Enable IP Pool”.pic1           
On the DNS tab fill in the DNS setting for you’re setup.

Could not connect to VCSA port 7331

When rebuilding my lab and installing VCSA 5.5, I notes that after a reboot of the VCSA I could no longer connect to my VM’s via the web clients console. I just got a webpage saying; Could not connect to VCSA_Address:7331. As I’m using the VCSA in my lab and with my clients I was a bit disappointed. VMWare has the KB2060604 that solves this problem, but I think that the “fix” should be in all my VCSA setups and therefor this post. Maybe VMware should insert the one line, “set.default.VMWARE_JAVA_HOME=/usr/java/jre-vmware” into the wrapper.conf found in the folder/usr/lib/vmware-vsphere-client/server/wrapper/conf, by default? so this issue not occurs if the VMWARE_JAVA_HOME environmental variable is not properly set after restarting the vCenter Server Appliance. Hobe this will help you as well, please leave a comment below.