{"id":332,"date":"2015-12-22T23:39:32","date_gmt":"2015-12-22T23:39:32","guid":{"rendered":"http:\/\/www.vdssystems.be\/?page_id=332"},"modified":"2018-01-18T21:15:17","modified_gmt":"2018-01-18T21:15:17","slug":"myblog","status":"publish","type":"page","link":"https:\/\/www.vdssystems.be\/en\/myblog\/","title":{"rendered":"myBlog"},"content":{"rendered":"
<\/i><\/div>
<\/div>

August 2018<\/h3>
\n
\n\n
<\/div>
<\/div>

Office 365 unlicensed product on Microsoft RDS Server 2012 or 2016<\/a><\/h2>

By vervoortjurgen<\/a><\/span><\/span>|<\/span>2018-08-23T22:36:26+01:00<\/span>August 23rd, 2018<\/span>|<\/span>Categories: Microsoft<\/a>, RDS<\/a>|<\/span>Tags: office 365 unlicensed product<\/a>, unlicensed product<\/a><\/span>|<\/span><\/p>

<\/div>

Since i ran into a couple of times getting unlicensed product on my Office 365 application running on RDS server, i tought i share my experience on how to solve it. Most articles out there tell you to check if you have an active Office 365 subscription or your internet connection is working and even do a online repair of office 365. What is this all doesn't work? So first time i came across this issue i did all this.\u00a0 [...]<\/p><\/div><\/div>

Read More<\/a><\/div>
<\/i> 0<\/a><\/div><\/div><\/div>
<\/div><\/div>\n<\/article>\n<\/div>

May 2018<\/h3>
\n
\n\n
<\/div>
<\/div>

The host returns esxupdate error code:15<\/a><\/h2>

By vervoortjurgen<\/a><\/span><\/span>|<\/span>2018-05-10T13:14:22+01:00<\/span>May 10th, 2018<\/span>|<\/span>Categories: VMware<\/a>|<\/span>Tags: 6.5<\/a>, The host returns esxupdate error code:15<\/a>, VUM update<\/a><\/span>|<\/span><\/p>

<\/div>

When trying to update a host with VUM i got the following error \"The host returns esxupdate error code:15. The package manager transaction is not successful\" After some searching i found article 2030665 on Vmware site. https:\/\/kb.vmware.com\/s\/article\/2030665 the article says that you need to recreate the version folder under \/locker\/packages. in my case the folder wasnt there. But after recreating the folder version and subfolders i resumed the remediation but it just wouldn't update. So i found another article that [...]<\/p><\/div><\/div>

Read More<\/a><\/div>
<\/i> 0<\/a><\/div><\/div><\/div>
<\/div><\/div>\n<\/article>\n<\/div>

January 2018<\/h3>
\n
\n\n
<\/div>
<\/div>

Cumulatieve update voor op Windows Server 2016 for x64 fails KB4057142<\/a><\/h2>

By vervoortjurgen<\/a><\/span><\/span>|<\/span>2018-01-31T13:20:38+01:00<\/span>January 31st, 2018<\/span>|<\/span>Categories: Microsoft<\/a>, Server 2016<\/a>|<\/span>Tags: KB4057142 failed<\/a><\/span>|<\/span><\/p>

<\/div>

Some of my windows 2016 server failed to update KB4057142 So here some steps i took to solve it Reboot the server Stop\u00a0Background Intelligent Transfer Service and Windows Update service. rename the folder\u00a0C:WindowsSoftwareDistribution Start the\u00a0Background Intelligent Transfer Service and Windows Update service Enabled \"give me updates for other Microsoft Products\" under Windows Updates -> advanced options Search for updates again. let the other products update first. KB4057142 will fail again but the server needs to reboot again. Try updates the [...]<\/p><\/div><\/div>

Read More<\/a><\/div>
<\/i> 0<\/a><\/div><\/div><\/div>
<\/div><\/div>\n<\/article>\n
\n
\n\n
<\/div>
<\/div>

Windows 2016 slow on ESXi 6.5<\/a><\/h2>

By vervoortjurgen<\/a><\/span><\/span>|<\/span>2018-01-29T23:19:11+01:00<\/span>January 29th, 2018<\/span>|<\/span>Categories: VMware<\/a>|<\/span>Tags: Windows 2016 slow on ESXi 6.5<\/a><\/span>|<\/span><\/p>

<\/div>

After some Windows 2016 server deployments on ESXi 6.5 customers started to notice slow server responses. I came across the following VMware article. https:\/\/recommender.vmware.com\/solution\/SOL-13898?src=vmw_so_vex_mrous_1194 So after checking the build numbers on the ESXi server it turned out i was on\u00a0build 5146846. I suggest you upgrade to\u00a0\u00a0ESXi 6.5 Update 1, build number should be\u00a05969303 or higher If you are unable to upgrade ESXi then use the registery settings in this VMware article. hope this helps anyone.<\/p><\/div><\/div>

Read More<\/a><\/div>
<\/i> 0<\/a><\/div><\/div><\/div>
<\/div><\/div>\n<\/article>\n<\/div>

December 2017<\/h3>
\n
\n\n
<\/div>
<\/div>

NSX Edge – Find DHCP lease<\/a><\/h2>

By vervoortjurgen<\/a><\/span><\/span>|<\/span>2017-12-15T12:10:45+01:00<\/span>December 15th, 2017<\/span>|<\/span>Categories: VMware<\/a>|<\/span>Tags: nsx<\/a>, nsx dhcp<\/a>, vmware<\/a><\/span>|<\/span><\/p>

<\/div>

NSX Edge - Find DHCP lease When you switch to NSX edge and you setup DHCP for you network, you find yourself wondering or looking for some IP address of a new device you hooked up. Since there is nog overview in the NSX interface you have to SSH into your NSX edge. So lets SSH with your favorite program into the edge (in my case I use putty) Then type the following: show service dhcp leaseinfo It shows you [...]<\/p><\/div><\/div>

Read More<\/a><\/div>
<\/i> 0<\/a><\/div><\/div><\/div>
<\/div><\/div>\n<\/article>\n<\/div>

October 2017<\/h3>
\n
\n\n
<\/div>
<\/div>

Shockwave Flash has crashed vSphere webclient<\/a><\/h2>

By vervoortjurgen<\/a><\/span><\/span>|<\/span>2017-10-21T20:52:56+01:00<\/span>October 21st, 2017<\/span>|<\/span>Categories: VMware<\/a>|<\/span><\/p>

<\/div>

Well most of you will probably run into this problem by now \"Shockwave Flash has crashed\" I use mostly chrome but i have been reading that also firefox is affected. Some update of flash makes everything crash. I found a nice fix from\u00a0virtuallyGhetto so thank you. you saved my day eventually adobe published a new beta release for Flash here here are the steps i took close all browsers uninstall Flash players from your comuter donwload en install the beta [...]<\/p><\/div><\/div>

Read More<\/a><\/div>
<\/i> 0<\/a><\/div><\/div><\/div>
<\/div><\/div>\n<\/article>\n
\n
\n\n
<\/div>
<\/div>

VMware PowerCLI 6.5 Add-PSSnapin not working<\/a><\/h2>

By vervoortjurgen<\/a><\/span><\/span>|<\/span>2017-10-08T23:33:57+01:00<\/span>October 8th, 2017<\/span>|<\/span>Categories: Uncategorized<\/a>|<\/span><\/p>

<\/div>

hello when you upgrade to POWERCLI 6.5 then you probably need to edit your scripts the Add-PSSnapin doesn't seem to work anymore replace it with Get-Module \u2013ListAvailable VM* | Import-Module say farewell to snapins article here<\/p><\/div><\/div>

Read More<\/a><\/div>
<\/i> 0<\/a><\/div><\/div><\/div>
<\/div><\/div>\n<\/article>\n<\/div>

April 2017<\/h3>
\n
\n\n
<\/div>
<\/div>

Failed to connect virtual device ‘ethernet0’<\/a><\/h2>

By vervoortjurgen<\/a><\/span><\/span>|<\/span>2017-04-19T19:03:30+01:00<\/span>April 19th, 2017<\/span>|<\/span>Categories: VMware<\/a>|<\/span>Tags: Failed to connect virtual device 'ethernet0'<\/a><\/span>|<\/span><\/p>

<\/div>

Failed to connect virtual device 'ethernet0' It seems this error is still turning up in vSphere 6.5. \u00a0I'm running vSphere 6.5.0.5400. I couldn't get the VM\u00a0connected, so after some searching i came across this blog on the VMware community here. Seems it has something to do with VMRC 9.0. now if you read the post you come to the comment of\u00a0Czernobog. at the end he had to use the fat client. \u00a0Since you cant connect with the fat client to [...]<\/p><\/div><\/div>

Read More<\/a><\/div>
<\/i> 0<\/a><\/div><\/div><\/div>
<\/div><\/div>\n<\/article>\n
\n
\n\n
<\/div>
<\/div>

ESXi 6.0 upgrade to ESXi 6.5: The upgrade contains the following set of conflicting VIBs<\/a><\/h2>

By vervoortjurgen<\/a><\/span><\/span>|<\/span>2017-04-19T12:56:52+01:00<\/span>April 19th, 2017<\/span>|<\/span>Categories: Uncategorized<\/a>, VMware<\/a>|<\/span>Tags: ESXi 6..5 upgrade<\/a>, The upgrade contains the following set of conflicting VIBs<\/a><\/span>|<\/span><\/p>

<\/div>

The upgrade contains the following set of conflicting VIBs when i tried to upgrade my ESXi host to 6.5 i ran in the error The upgrade contains the following set of conflicting VIBs: HUAWEI_bootbank_hio_2.0.0.42-1OEM.550.0.0.1331820 HUAWEI_bootbank_hio_2.0.0.42-1OEM.550.0.0.1331820 Remove the conflicting VIBs or use Image Builder to create a custom upgrade ISO image that contains the newer versions of the conflicting VIBs, and try to upgrade again. so lets remove the vib set your ESXi host in maintenance mode because you will need [...]<\/p><\/div><\/div>

Read More<\/a><\/div>
<\/i> 0<\/a><\/div><\/div><\/div>
<\/div><\/div>\n<\/article>\n
\n
\n\n\t\t\t
\n\t\t