<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>vSphere 6.0 &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<atom:link href="https://magander.se/category/vsphere-6-0/feed/" rel="self" type="application/rss+xml" />
	<link>https://magander.se</link>
	<description></description>
	<lastBuildDate>Thu, 07 Jun 2018 15:52:14 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>

<image>
	<url>https://magander.se/wp-content/uploads/2021/01/cropped-Screenshot-2021-01-19-at-22.37.56-32x32.png</url>
	<title>vSphere 6.0 &#8211; Virtualization, DBaaS &amp; Whatever Crosses My Mind</title>
	<link>https://magander.se</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>VMware ESXi Upgrade 6.0 To 6.5 &#8211; Conflicting VIBs</title>
		<link>https://magander.se/vmware-esxi-upgrade-6-0-to-6-5-conflicting-vibs/</link>
					<comments>https://magander.se/vmware-esxi-upgrade-6-0-to-6-5-conflicting-vibs/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 11 Jan 2018 12:40:51 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[vSphere 6.5]]></category>
		<category><![CDATA[check scan results for details]]></category>
		<category><![CDATA[esxcli network nic list]]></category>
		<category><![CDATA[esxcli software vib list | grep -i mellanox]]></category>
		<category><![CDATA[esxcli software vib remove -n net-mst]]></category>
		<category><![CDATA[ESXi 6.5 U1]]></category>
		<category><![CDATA[ESXi 6.5 Update 1]]></category>
		<category><![CDATA[ESXi ESXi 6.5]]></category>
		<category><![CDATA[mellanox]]></category>
		<category><![CDATA[Mellanox_bootbank_net-mst_2.0.0.0-1OEM.550.0.0.600000]]></category>
		<category><![CDATA[net-mlx4-core]]></category>
		<category><![CDATA[net-mlx4-core 1.9.9.4-1OEM.550.0.0.1331820]]></category>
		<category><![CDATA[net-mlx4-en]]></category>
		<category><![CDATA[net-mlx4-en 1.9.9.4-1OEM.550.0.0.1331820]]></category>
		<category><![CDATA[net-mst]]></category>
		<category><![CDATA[net-mst 2.0.0.0-1OEM.550.0.0.600000]]></category>
		<category><![CDATA[npx005]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[Software or system configuration of host is incompatible]]></category>
		<category><![CDATA[The upgrade contains the following set of conflicting VIBs]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[VMware-ESXi-6.5.0-Update1-6765664-HPE-650.U1.10.1.5.26-Oct2017.iso]]></category>
		<guid isPermaLink="false">http://magander.se/?p=9941</guid>

					<description><![CDATA[A few days ago I was contacted by a customer I used to work with before I joined Nutanix. They were in the process of upgrading their vSphere environment from 6.0 to 6.5 and had ran into a problem with the ESXi upgrade. After creating a vSphere Update Manager (VUM) baseline with the HP ESXi &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vmware-esxi-upgrade-6-0-to-6-5-conflicting-vibs/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/vmware-esxi-upgrade-6-0-to-6-5-conflicting-vibs/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Update ESXi Fails With &#8220;DependencyError, Requirement Cannot Be Satisfied Within The ImageProfile&#8221;</title>
		<link>https://magander.se/update-esxi-fails-with-dependencyerror-requirement-cannot-be-satisfied-within-the-imageprofile/</link>
					<comments>https://magander.se/update-esxi-fails-with-dependencyerror-requirement-cannot-be-satisfied-within-the-imageprofile/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 21 Sep 2017 12:05:25 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[vSphere 6.5]]></category>
		<category><![CDATA[but the requirement cannot be satisfied within the ImageProfile]]></category>
		<category><![CDATA[Dell-ESXi-6.0]]></category>
		<category><![CDATA[Dell-ESXi-6.0U2-4192238-A04]]></category>
		<category><![CDATA[Dell-ESXi-6.5]]></category>
		<category><![CDATA[DependencyError]]></category>
		<category><![CDATA[esxcli software vib update -d]]></category>
		<category><![CDATA[npx005]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[requirement cannot be satisfied within the ImageProfile]]></category>
		<category><![CDATA[requires vsan]]></category>
		<category><![CDATA[requires vsan >= 6.0.0-2.43]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[via]]></category>
		<category><![CDATA[VIB VMware_bootbank_esx-base_6.0.0-2.43.4192238 requires vsan >= 6.0.0-2.43]]></category>
		<category><![CDATA[VMware_bootbank]]></category>
		<category><![CDATA[VSAN]]></category>
		<guid isPermaLink="false">http://magander.se/?p=9779</guid>

					<description><![CDATA[Was contacted a few days ago by customer who got the following error when trying to upgrade their ESXi hosts. [DependencyError] VIB VMware_bootbank_esx-base_6.0.0-2.43.4192238 requires vsan &#62;= 6.0.0-2.43, but the requirement cannot be satisfied within the ImageProfile. VIB VMware_bootbank_esx-base_6.0.0-2.43.4192238 requires vsan &#60;&#60; 6.0.0-2.44, but the requirement cannot be satisfied within the ImageProfile. Please refer to the &#8230; </p><p><a class="more-link block-button" href="https://magander.se/update-esxi-fails-with-dependencyerror-requirement-cannot-be-satisfied-within-the-imageprofile/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/update-esxi-fails-with-dependencyerror-requirement-cannot-be-satisfied-within-the-imageprofile/feed/</wfw:commentRss>
			<slash:comments>32</slash:comments>
		
		
			</item>
		<item>
		<title>Manage ESXi Routing Via Command Line Interface</title>
		<link>https://magander.se/manage-esxi-routing-via-command-line-interface/</link>
					<comments>https://magander.se/manage-esxi-routing-via-command-line-interface/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Wed, 12 Apr 2017 09:04:57 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[3568940]]></category>
		<category><![CDATA[build-3568940]]></category>
		<category><![CDATA[command line interface]]></category>
		<category><![CDATA[esxcli]]></category>
		<category><![CDATA[esxcli network]]></category>
		<category><![CDATA[esxcli network ip]]></category>
		<category><![CDATA[esxcli network ip interface]]></category>
		<category><![CDATA[esxcli network ip interface ipv4 get]]></category>
		<category><![CDATA[esxcli network ip interface list]]></category>
		<category><![CDATA[esxcli network ip route]]></category>
		<category><![CDATA[esxcli network ip route ipv4 add]]></category>
		<category><![CDATA[esxcli network ip route ipv4 add -n 172.16.20.0/24 -g 10.10.100.110]]></category>
		<category><![CDATA[esxcli network ip route ipv4 list]]></category>
		<category><![CDATA[esxcli network ip route ipv4 remove]]></category>
		<category><![CDATA[esxcli network ip route ipv4 remove -n 172.16.20.0/24 -g 10.10.100.110]]></category>
		<category><![CDATA[ESXi 6]]></category>
		<category><![CDATA[esxi 6.0]]></category>
		<category><![CDATA[npx005]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[route]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[VMware]]></category>
		<guid isPermaLink="false">http://magander.se/?p=9024</guid>

					<description><![CDATA[There are certain key combinations and commands I find more difficult to remember than others. I wrote about Send F Key to VMware Fusion via MacBook Keyboard and the next in line is routing for ESXi. This is not something i do very often but It happens from time to time. I will not go into &#8230; </p><p><a class="more-link block-button" href="https://magander.se/manage-esxi-routing-via-command-line-interface/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/manage-esxi-routing-via-command-line-interface/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>Heads Up! Critical Security Patch Available for VMware ESXi &#038; More</title>
		<link>https://magander.se/heads-up-critical-security-patch-available-for-vmware-esxi-more/</link>
					<comments>https://magander.se/heads-up-critical-security-patch-available-for-vmware-esxi-more/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Fri, 31 Mar 2017 05:27:17 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[vSphere 6.5]]></category>
		<category><![CDATA[2149672]]></category>
		<category><![CDATA[2149673]]></category>
		<category><![CDATA[CVE-2017-4902]]></category>
		<category><![CDATA[CVE-2017-4903]]></category>
		<category><![CDATA[CVE-2017-4904]]></category>
		<category><![CDATA[CVE-2017-4905]]></category>
		<category><![CDATA[Fusion]]></category>
		<category><![CDATA[Fusion (Fusion)]]></category>
		<category><![CDATA[KB 2149672]]></category>
		<category><![CDATA[KB 2149673]]></category>
		<category><![CDATA[npx005]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[VMSA-2017-0006]]></category>
		<category><![CDATA[VMware ESXi]]></category>
		<category><![CDATA[VMware Fusion Pro]]></category>
		<category><![CDATA[VMware Player]]></category>
		<category><![CDATA[VMware Security Advisories]]></category>
		<category><![CDATA[VMware Workstation Pro]]></category>
		<guid isPermaLink="false">http://magander.se/?p=8998</guid>

					<description><![CDATA[A few days ago, 2017-03-28, VMware released a few security patches that will prevent a guest from execute code on the ESXi host. This has been possible based on heap buffer overflow and uninitialized stack memory usage in SVGA. Available VMware KB articles for these issues are: KB 2149672 KB 2149673 Affected VMware ESXi versions &#8230; </p><p><a class="more-link block-button" href="https://magander.se/heads-up-critical-security-patch-available-for-vmware-esxi-more/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/heads-up-critical-security-patch-available-for-vmware-esxi-more/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Heads Up! No More Third Party Virtual Switches API For ESXi</title>
		<link>https://magander.se/heads-up-no-more-third-party-virtual-switches-with-esxi/</link>
					<comments>https://magander.se/heads-up-no-more-third-party-virtual-switches-with-esxi/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 30 Mar 2017 10:22:24 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[vSphere 6.5]]></category>
		<category><![CDATA[API]]></category>
		<category><![CDATA[Application Programmable Interface]]></category>
		<category><![CDATA[Cisco 1000v]]></category>
		<category><![CDATA[deprecated]]></category>
		<category><![CDATA[kb]]></category>
		<category><![CDATA[KB 2149722]]></category>
		<category><![CDATA[KB2149722]]></category>
		<category><![CDATA[Nexus 1000V]]></category>
		<category><![CDATA[Nexus 1K]]></category>
		<category><![CDATA[npx005]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[Open vSwitch]]></category>
		<category><![CDATA[OVS]]></category>
		<category><![CDATA[removed]]></category>
		<category><![CDATA[Third Party]]></category>
		<category><![CDATA[V Aware KB 2149722]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vDS]]></category>
		<category><![CDATA[virtual standard switch]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[vNetwork Distributed switch]]></category>
		<category><![CDATA[VSS]]></category>
		<guid isPermaLink="false">http://magander.se/?p=8991</guid>

					<description><![CDATA[Update 2017-04-01 No it is official, see VMware KB 2149722 for more information. —————————————————————————————– Since I know quite a few of my customers are using third party switches in their vSphere environment instead of the VMware native Virtual Standard Switch (VSS) or vNetwork Distributed Switch (VDS) i wanted to provide you with some information I have &#8230; </p><p><a class="more-link block-button" href="https://magander.se/heads-up-no-more-third-party-virtual-switches-with-esxi/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/heads-up-no-more-third-party-virtual-switches-with-esxi/feed/</wfw:commentRss>
			<slash:comments>3</slash:comments>
		
		
			</item>
		<item>
		<title>VMware vCenter Server 6.0 U3 &#038; ESXi 6.0 U3 released</title>
		<link>https://magander.se/vmware-vcenter-server-6-0-u3-esxi-6-0-u3-released/</link>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Wed, 01 Mar 2017 01:16:01 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vCenter Server]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[6.0 U3]]></category>
		<category><![CDATA[6.0 Update 3]]></category>
		<category><![CDATA[esxi 6.0]]></category>
		<category><![CDATA[ESXi 6.0 U3]]></category>
		<category><![CDATA[npx005]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[update 3]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vCenter Server 6.0]]></category>
		<category><![CDATA[vCenter Server 6.0 U3]]></category>
		<category><![CDATA[vSPhere 6.0 U3]]></category>
		<category><![CDATA[vSphere Replication]]></category>
		<category><![CDATA[vSphere Replication 6]]></category>
		<category><![CDATA[vSphere Replication 6.1.2]]></category>
		<guid isPermaLink="false">http://magander.se/?p=8912</guid>

					<description><![CDATA[A few days ago, 2017/02/24, VMware released vCenter Server 6.0 Update 3 and ESXi 6.0 Update 3. Both vCenter Server 6.0 U3 and ESXi 6.0 U3 now includes upport for TLS v 1.0, 1.1 and 1.2. For ESXi it is enabled by default and can be configurable with 6.0 U3. For vCenter Server 6.0 U3 the &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vmware-vcenter-server-6-0-u3-esxi-6-0-u3-released/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
		<item>
		<title>ESXi 6 &#8211; The VMRC Console Has Disconnected</title>
		<link>https://magander.se/esxi-6-the-vmrc-console-has-disconnected/</link>
					<comments>https://magander.se/esxi-6-the-vmrc-console-has-disconnected/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 31 Jan 2017 08:44:38 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[1012382]]></category>
		<category><![CDATA[1014508]]></category>
		<category><![CDATA[2050470]]></category>
		<category><![CDATA[2087524]]></category>
		<category><![CDATA[2143832]]></category>
		<category><![CDATA[4600944]]></category>
		<category><![CDATA[and ESX hosts]]></category>
		<category><![CDATA[attempting to reconnect]]></category>
		<category><![CDATA[C:\Program Files (x86)\VMware\Infrastructure\Virtual Infrastructure Client]]></category>
		<category><![CDATA[C:\ProgramData\VMware]]></category>
		<category><![CDATA[C:\ProgramData\VMware\VMware Remote Console\]]></category>
		<category><![CDATA[C:\Users\\AppData\Local\VMware\vpx]]></category>
		<category><![CDATA[Download vSphere Client for Windows]]></category>
		<category><![CDATA[esxi 6.0]]></category>
		<category><![CDATA[ESXi 6.0 Patch 4]]></category>
		<category><![CDATA[Network ports]]></category>
		<category><![CDATA[Network ports required to access vCenter Server]]></category>
		<category><![CDATA[npx005]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[Patch 4]]></category>
		<category><![CDATA[Remote Console]]></category>
		<category><![CDATA[The VMRC console has disconnected]]></category>
		<category><![CDATA[The VMRC console has disconnected....attempting to reconnect]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[virtual machine]]></category>
		<category><![CDATA[Virtual Machine Remote Console]]></category>
		<category><![CDATA[VM]]></category>
		<category><![CDATA[VMRC]]></category>
		<category><![CDATA[VMS]]></category>
		<category><![CDATA[vpx]]></category>
		<category><![CDATA[vSphere 6]]></category>
		<guid isPermaLink="false">http://magander.se/?p=8440</guid>

					<description><![CDATA[So a few days back i was experience an issue where i couldn’t connect to a VMware vSphere ESXi 6.0 Patch 4 (build number 4600944) based Virtual Machine Remote Console (VMRC) at a customer. I have seen this quite a few times over the years and there are a lot of VMware KB articles available on the topic. &#8230; </p><p><a class="more-link block-button" href="https://magander.se/esxi-6-the-vmrc-console-has-disconnected/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/esxi-6-the-vmrc-console-has-disconnected/feed/</wfw:commentRss>
			<slash:comments>5</slash:comments>
		
		
			</item>
		<item>
		<title>Verify vMotion functionality using PowerCLI</title>
		<link>https://magander.se/verify-vmotion-functionality-using-powercli/</link>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 11 Aug 2016 20:33:09 +0000</pubDate>
				<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[AOS]]></category>
		<category><![CDATA[ESXi]]></category>
		<category><![CDATA[ESXi 6]]></category>
		<category><![CDATA[esxi 6.0]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[nutanix]]></category>
		<category><![CDATA[Nutanix AOS]]></category>
		<category><![CDATA[PowerCLI]]></category>
		<category><![CDATA[PowerCLI 6.3 R1]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vMotion]]></category>
		<guid isPermaLink="false">http://magander.se/?p=7251</guid>

					<description><![CDATA[One very important thing during any environment deployment or environment expansion is to verify it actually works as expected. It has been a while since my last script blog post but i wanted to share one PowerCLI script i put together a while ago to verify vSphere vMotion functionality. The script has been very handy &#8230; </p><p><a class="more-link block-button" href="https://magander.se/verify-vmotion-functionality-using-powercli/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
		<item>
		<title>Register vCenter Server Lookup Service in vShield Manager</title>
		<link>https://magander.se/register-vcenter-server-lookup-service-in-vshield-manager/</link>
					<comments>https://magander.se/register-vcenter-server-lookup-service-in-vshield-manager/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Mon, 23 May 2016 07:21:17 +0000</pubDate>
				<category><![CDATA[vCenter Server]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[443]]></category>
		<category><![CDATA[5.5.4]]></category>
		<category><![CDATA[7444]]></category>
		<category><![CDATA[Initialisation of STS client failed]]></category>
		<category><![CDATA[Initialisation of STS client failed. Root Cause: The SSL certificate of STS service cannot be verified]]></category>
		<category><![CDATA[port 443]]></category>
		<category><![CDATA[port 7444]]></category>
		<category><![CDATA[Root Cause: The SSL certificate of STS service cannot be verified]]></category>
		<category><![CDATA[The SSL certificate of STS service cannot be verified]]></category>
		<category><![CDATA[vCenter Server 6.0]]></category>
		<category><![CDATA[vShield]]></category>
		<category><![CDATA[vShield Manager]]></category>
		<category><![CDATA[vShield Manager 5.5.4]]></category>
		<guid isPermaLink="false">http://magander.se/?p=7005</guid>

					<description><![CDATA[A few weeks ago i upgraded a customer environment to latest release of VMware vSphere. Customer ran 5.5 U2 and now they wanted version 6.0 U2 for both vCenter Server and ESXi. The entire process was pretty straight forward and the only little bump we had was the vShield Manager to vCenter Server Lookup Service &#8230; </p><p><a class="more-link block-button" href="https://magander.se/register-vcenter-server-lookup-service-in-vshield-manager/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/register-vcenter-server-lookup-service-in-vshield-manager/feed/</wfw:commentRss>
			<slash:comments>2</slash:comments>
		
		
			</item>
		<item>
		<title>Change ESXi password complexity policy</title>
		<link>https://magander.se/change-esxi-password-complexity-policy/</link>
					<comments>https://magander.se/change-esxi-password-complexity-policy/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 05 Apr 2016 16:15:51 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[/etc/pam.d/passwd]]></category>
		<category><![CDATA[ESXi 6]]></category>
		<category><![CDATA[esxi 6.0]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[pam.d]]></category>
		<category><![CDATA[passwd]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[vSphere 6]]></category>
		<guid isPermaLink="false">http://magander.se/?p=6779</guid>

					<description><![CDATA[The other week i was asked by a customer to change passwords for all service accounts in their environment and this includes but not limited to IPMI admin account, ESXi host root account, Nutanix Controller Virtual Machine (CVM) nutanix account vCenter Server administrator@vsphere.local account Based on existing customer password requirements for ESXi hosts, 16 characters including only &#8230; </p><p><a class="more-link block-button" href="https://magander.se/change-esxi-password-complexity-policy/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/change-esxi-password-complexity-policy/feed/</wfw:commentRss>
			<slash:comments>6</slash:comments>
		
		
			</item>
		<item>
		<title>Remove Horizon View Desktops Pools and VMs stuck in delete state</title>
		<link>https://magander.se/remove-horizon-view-desktops-pools-and-vms-stuck-in-delete-state/</link>
					<comments>https://magander.se/remove-horizon-view-desktops-pools-and-vms-stuck-in-delete-state/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Wed, 30 Mar 2016 21:19:08 +0000</pubDate>
				<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[Desktop Pools]]></category>
		<category><![CDATA[desktopName]]></category>
		<category><![CDATA[Do you want to remove the desktop machine]]></category>
		<category><![CDATA[findMachine]]></category>
		<category><![CDATA[Horizon View]]></category>
		<category><![CDATA[Horizon View 6.2]]></category>
		<category><![CDATA[hyper converged]]></category>
		<category><![CDATA[hyperconvergence]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[VDI]]></category>
		<category><![CDATA[viewdbchk]]></category>
		<category><![CDATA[viewdbchk.cmd]]></category>
		<guid isPermaLink="false">http://magander.se/?p=6742</guid>

					<description><![CDATA[A while back i had to manually clean up some Horizon View (version 6.2) Desktop pools that were stuck in the delete state. Reasons for this was failed attempts to delete Horizon View VDIs even though their corresponding vCenter Server VMs were successfully deleted. Below is a print screen from the Horizon View UI showing the state &#8230; </p><p><a class="more-link block-button" href="https://magander.se/remove-horizon-view-desktops-pools-and-vms-stuck-in-delete-state/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/remove-horizon-view-desktops-pools-and-vms-stuck-in-delete-state/feed/</wfw:commentRss>
			<slash:comments>22</slash:comments>
		
		
			</item>
		<item>
		<title>Error joining vCenter Server Appliance to Active Directory</title>
		<link>https://magander.se/error-joining-vcenter-server-appliance-to-active-directory/</link>
					<comments>https://magander.se/error-joining-vcenter-server-appliance-to-active-directory/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Tue, 01 Mar 2016 13:57:52 +0000</pubDate>
				<category><![CDATA[vCenter Server]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[/opt/likewise/bin/domainjoin-cli]]></category>
		<category><![CDATA[active directory]]></category>
		<category><![CDATA[active directory 2012]]></category>
		<category><![CDATA[AD]]></category>
		<category><![CDATA[ad 2012]]></category>
		<category><![CDATA[domainjoin-cli join]]></category>
		<category><![CDATA[error code [11]]]></category>
		<category><![CDATA[Error: ERROR_GEN_FAILURE [code 0x0000001f]]]></category>
		<category><![CDATA[Idm client exception: Error trying to join AD]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[orgUnit]]></category>
		<category><![CDATA[samss]]></category>
		<category><![CDATA[SamSS Srv]]></category>
		<category><![CDATA[SamSS Srv2]]></category>
		<category><![CDATA[SMB]]></category>
		<category><![CDATA[smb1]]></category>
		<category><![CDATA[smb2]]></category>
		<category><![CDATA[srvnet]]></category>
		<category><![CDATA[user [XXX\yyy domain [XXXX]]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vCenrter Server Appliance]]></category>
		<category><![CDATA[vCenter Server Appliance]]></category>
		<category><![CDATA[VCSA]]></category>
		<category><![CDATA[vcsa 6u1]]></category>
		<category><![CDATA[Windows 2012 R2 AD]]></category>
		<guid isPermaLink="false">http://magander.se/?p=6764</guid>

					<description><![CDATA[Time for another guest blog post and this one by my former colleague Johan Blom @ RTSAB who had problem joining a vCenter Server Appliance 6 U1 to a Windows 2012 R2 domain. When trying top join domain from vSphere Web Client the following error was seen:   Idm client exception: Error trying to join AD, error code [11], user [XXX\yyy &#8230; </p><p><a class="more-link block-button" href="https://magander.se/error-joining-vcenter-server-appliance-to-active-directory/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/error-joining-vcenter-server-appliance-to-active-directory/feed/</wfw:commentRss>
			<slash:comments>4</slash:comments>
		
		
			</item>
		<item>
		<title>vSphere 6.0 Update 1b released</title>
		<link>https://magander.se/vsphere-6-0-update-1b-released/</link>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Fri, 08 Jan 2016 13:31:15 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vCenter Server]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[ESXi 6 U1b]]></category>
		<category><![CDATA[hyper converged]]></category>
		<category><![CDATA[hyperconvergence]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[U1b]]></category>
		<category><![CDATA[Update 1]]></category>
		<category><![CDATA[Update 1b]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vCenter Server 6.0 U1]]></category>
		<category><![CDATA[vCenter Server 6.0 U1b]]></category>
		<category><![CDATA[vSphere 6]]></category>
		<category><![CDATA[vSphere 6.0 U1]]></category>
		<guid isPermaLink="false">http://magander.se/?p=6597</guid>

					<description><![CDATA[Yesterday, 2016-01-07, VMware release vSphere vCenter Server and ESXi 6.0 Update 1b. A few updates and fixes i think will be useful for at least some of my readers are listed below: VMware now supports Cisco Nexus 1000V Virtual machines protected by VMware vShield App lose network connectivity on the ESXi 6.0 hosts Windows 10 &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vsphere-6-0-update-1b-released/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
		<item>
		<title>ESXi Change Block Tracking patch released</title>
		<link>https://magander.se/esxi-change-block-tracking-patch-released/</link>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 26 Nov 2015 07:18:00 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[6]]></category>
		<category><![CDATA[6.0]]></category>
		<category><![CDATA[6.0.x]]></category>
		<category><![CDATA[CBT]]></category>
		<category><![CDATA[Change Block Tracking]]></category>
		<category><![CDATA[ESXi 6]]></category>
		<category><![CDATA[ESXi 6.0.x]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[VMware]]></category>
		<category><![CDATA[VMware ESXi 6.0.x]]></category>
		<guid isPermaLink="false">http://magander.se/?p=6470</guid>

					<description><![CDATA[Yesterday, 2015-11-25, VMware released a patch that will solve the ESXi 6.0 Change Block Tracking (CBT) problem where virtual machines backed up using CBT could experience the following problems: Inconsistent virtual machine backups The CBT API call QueryDiskChangedAreas() API call can sometimes return incorrect changed sectors, which results in inconsistent incremental virtual machine backups. The &#8230; </p><p><a class="more-link block-button" href="https://magander.se/esxi-change-block-tracking-patch-released/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
		<item>
		<title>vSphere 6.0 Update 1 released</title>
		<link>https://magander.se/vsphere-6-0-update-1-released/</link>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Fri, 11 Sep 2015 05:38:27 +0000</pubDate>
				<category><![CDATA[ESXi]]></category>
		<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vCenter Server]]></category>
		<category><![CDATA[vSphere 6 U1]]></category>
		<category><![CDATA[vSphere 6.0 Update 1]]></category>
		<guid isPermaLink="false">http://magander.se/?p=6091</guid>

					<description><![CDATA[Yesterday, 2015-09-10, VMware released vSphere 6 Update 1 (U1) and it contains quite a few enhancements and a lot of resolved issues in the following areas: ESXi API Backup CIM Installation Guest Operating System Security Storage Network Upgrade vCenter Server Upgrade Issues vCenter Single Sign-On Issues Security Issues Storage Issues vCenter Server, vSphere Web Client, &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vsphere-6-0-update-1-released/">Continue reading &#187;</a>]]></description>
		
		
		
			</item>
		<item>
		<title>vShield Manager disk 100% full</title>
		<link>https://magander.se/vshield-manager-disk-100-full/</link>
					<comments>https://magander.se/vshield-manager-disk-100-full/#comments</comments>
		
		<dc:creator><![CDATA[magander]]></dc:creator>
		<pubDate>Thu, 13 Aug 2015 03:51:51 +0000</pubDate>
				<category><![CDATA[vSphere]]></category>
		<category><![CDATA[vSphere 6.0]]></category>
		<category><![CDATA[2175697]]></category>
		<category><![CDATA[5.5.3-2175697]]></category>
		<category><![CDATA[npx5]]></category>
		<category><![CDATA[NSX]]></category>
		<category><![CDATA[NSX 6.1.4]]></category>
		<category><![CDATA[VCDX56]]></category>
		<category><![CDATA[vShield Manager]]></category>
		<category><![CDATA[vShield Manager 5.5]]></category>
		<category><![CDATA[vShield Manager 5.5.3]]></category>
		<category><![CDATA[vSM]]></category>
		<category><![CDATA[VSM 5.5]]></category>
		<category><![CDATA[VSM 5.5.3]]></category>
		<guid isPermaLink="false">http://magander.se/?p=5907</guid>

					<description><![CDATA[A few days ago my vShield Manager, VSM, virtual machine (VM) disk system was filled up to 100%. Yes i know this is due to poor monitoring but it’s in my lab and i’m using it for a specific reason from time to time. At least i had some reporting of the issue so i &#8230; </p><p><a class="more-link block-button" href="https://magander.se/vshield-manager-disk-100-full/">Continue reading &#187;</a>]]></description>
		
					<wfw:commentRss>https://magander.se/vshield-manager-disk-100-full/feed/</wfw:commentRss>
			<slash:comments>8</slash:comments>
		
		
			</item>
	</channel>
</rss>

<!--
Object Caching 22/318 objects using Disk
Page Caching using Disk: Enhanced 

Served from: magander.se @ 2026-06-21 02:05:37 by W3 Total Cache
-->