Skip to main content

Posts

Showing posts from January, 2020

End of Life vSphere 6.0 - My upgrade plan

vSphere 6.0 will be end of life/general support on 12 th March 2020 which is just under two months away and most people would of started or completed their journey to upgrade to vSphere 6.5 or 6.7. I have provided some of the high level steps/consideration that I have taken when I was doing my planning. As vSphere 6.5 and 6.7 both have an end of life date of 15th November 2021  I decided to look at both version for my upgrade plan with the mind of moving to 6.7 as my first choice. The reason I looked at both was in case there was issues with hardware or software that was not supported on a particular version. Throughout my planning I also put into consideration whether it is better to do fresh installs of vCenter/ESXi or an upgrade as a fresh install might be easier. For a small environment with not much integration it might be easier to just do a fresh install but that is my opinion and you would need to weight up what is better for you.  First thing first is to make sure y

Azure Preview Portal

Microsoft Azure has a preview portal at the following URL https://preview.portal.azure.com  which they use to showcase some of the possible changes that they have coming up to improve your experience of using the Azure portal. Things like improved search features, navigation, themes, change of icon for resources all popped up there before hitting the main site. I remembered some preview features/products such as the Bastion host worked only via the preview site. You was unable to see the feature in the main site. So do login to the preview site to manage your resources from time to time to have a sneak preview of what changes might be coming out. You will know you are at the preview site as the header will say Microsoft Azure (Preview)

vSphere 6.7 support backup over SMB

Since vSphere 6.7 U2 SMB protocol was introduced to allow you to backup to a file share. This was excellent news for us and I decided to test it and see how it works. Upon setting up the backup schedule I got this error  So I attempted to use the option to do a one off "Backup" and you get this message instead Both messages didn't really point me to any particular direction so I did a quick search on VMwares knowledge base and found an article KB70646  which states that it is only supported for SMB1 and currently it is still not fixed in U3 (Tested on Build number 15132721) either.  We all know SMB1 is insecure and shouldn't be using it but I still wanted to try and see how it worked so first I enabled SMB 1 on my server. For reference of the powershell cmdlets to run go to this Microsoft article  which covers SMB1/2 and 3. Once I had SMB 1 enabled I attempted to set the backup schedule and as I was filling in the "Backup server credentials" sect

DHCP Error : Delete failover relationship failed. Error 1722

I came across an issue where I was trying to delete a failover relationship between two DHCP server (Windows 2012 R2) because one of the servers had a hardware fault and we couldn’t recover the server. We knew we had to built a new one so one of the steps I tried to initially take was to mark the failed server as “partner down” in the relationship.  Upon click the button I get this message which is promising And then the final message to tell me its not going to happen Now depending on how you set you DHCP failover modes you could run in to issues if your setting was like the one I had where it was set at “Load Balance Mode” with 50/50 and I was unable to change the partner status to down. This is Microsoft explanation  of the difference of “Lost contact” vs “Partner down” “ In load balancing mode, when a DHCP server loses contact with its failover partner it will begin granting leases to all DHCP clients. If it receives a lease renewal request from a DHCP c