How to add Target Servers to vMA

I have had this one post sitting around for a while and I figured I should get it written before it gets lost.

Earlier I was working on getting vMA stood up in my lab environment and I figured that I should do a post about how to configure vMA to connect to a target. Adding a Target Server in vMA is a faster way for you to be able to issue commands. Rather than having to specify which server you want to run commands against (especially if you are running several commands on the same box) you should set the server as a target. In this instance I will run through the steps of setting a target for an AD Authenticated host or vCenter. 

From the vMA console you will type the following command out:

vifp addserver <vcenter server name.domain.local> --authpolicy adauth --username <AD DOMAIN\UserName>

and press Enter and you will be prompted for the Password of the AD account that you referenced.

To verify that the server is connected you can use the following command:
vifp listservers --long

This will tell you the server name as well as the method of authentication. Now anytime you want to run a command against that host you will be able to do so without having to re-authenticate every time.

To set your Target server you can use the following command prior to running your actual command or script.

vifptarget -s <servername>

Clients are not receiving emails from Exchange

So I had a client call in today and say that they are not receiving emails. That is as descriptive as it gets sometimes, so the first thing I did was check their Mail Gateway which caches email if their Exchange server is not running. So I looked and there is nothing in the queues, so that tells me that things are making it's way to Exchange.

I then go and open the Exchange Management Shell which will tell me really quickly if the problem is what I think it is. So I fire it up and here is what I get

Note: If you try to open the web console you may have similar issues.

Having seen this message before with this particular client I know now that I have a time sync issue on my hands.

The First thing I look at is the time on the Exchange server.

Then I check the time on one of the Domain Controllers which is the PDC Emulator.

Then I check one of the other Domain Controllers and I find this.

As you can see the time difference is greater than 5 minutes which will cause your Exchange Server to be very unhappy.

Once you fix the time issue you can then try to reopen the Exchange Management Shell and you will see that you can connect without an issue.

Let me know if this was helpful by leaving a comment below.

thank you

VMWare Virtual Machine will not Start in vCenter

So I was asked by a client to do up "hardware upgrades" on one of their virtual machines. This VM is not production and is not running anything at the moment, but will soon become an SQL Server running an application. So I went and powered off the VM, logged into the C# vSphere client (they are running vSphere 6.0), and doubled the memory as requested by the client.

After making the change I went to power on the VM and I get presented with this pop up error message from VMWare

The message itself seems pretty generic but I have actually seen this one before. This error has to do with  an issue with the management agents on  your ESXi host.

I followed the instructions found on this KB article but it did not resolve my issue. I also found this KB article which might yield better results but as this whole environment is production, I will need to wait to test that.

WORK AROUND:

In order to get this VM powered back online, I needed to log directly into the virtual host and power on the machine.

The VM powered on with no issues.

I hope you find this helpful and I will update this when I have a solution.

Windows Update cannot currently check for updates because the service is not running

I recently ran into an issue where a client of mine had a issue with Windows Update failing to run. It gave the end user a pop up error message that looks like this:

Once you click okay you will then see this on the Window's Update screen. Clicking Check for updates will result in the same message. 

I did some googling and found that if I Stop the Windows Update service and then delete or rename C:\Windows\SoftwareDistribution and then restart the service you would then be able to run Windows update. However this did not work. 

I then found a Microsoft Support KB article KB3102810 which will allow you to download an update which will resolve the issue. After the update is installed you will need to stop the Windows Update Service again, delete or rename the Software Distribution folder and restart the machine. Once it comes back up you can then click Check for Update and after about an hour (because it now has to rebuild it's update catalog)  you will get a similar screen to what you will see below. 

Hope you find this helpful with your Windows update issues.