I had quite the experience when several of my applications refused to uninstall. I spent several days troubleshooting this issue and going through logs to the point that I ended up opening a case with Microsoft.

It appears that if any of application that you’re trying to uninstall has an installation deployment job set to ‘available’ or ‘required’ – no uninstall task will work. You have to delete all your installation deployment jobs as it appears that installation jobs have a higher precedence.

Here are some notes from Microsoft.

Here are the details.

The uninstall deployment wasn’t get enforced as per the logs. Here is what we see in the logs.

Recently we started buying DELL OptiPlex 7060 desktops and I ran into a situation where WinPE wouldn’t work properly as there was no IP address assignment and no C drive showing in the environment.

Fixing the missing NIC hardware was easy enough; however, the environment was still lacking a hard drive. These 7060 models come with SATA SSD drives and an Intel Rapid Storage Technology F6 controller.

Installing Intel drivers or DELL drivers didn’t work.

After many hours of trying different things, here’s the solution I found. In the BIOS, change the storage settings from RAID ON (DELL’s default setting) to AHCI…just that simple.

There are many interesting documents comparing AHCI and Raid On, I suggest you read them, but AHCI is newer technology and we decided to stick with this setting on our desktop devices.

While attemtping to upgrade from ESXi 6.0 to 6.5, I received the following message from Upgrade Manager:

The upgrade contains the following set of conflicting VIBs: VMware_bootbank_ehci-ehci-hcd_1.0-4vmw.600.3.69.5572656 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.

After researching this message and not finding an answer that could fix it, I called Vmware support and this is what they suggested.

My server hardware: DELL PowerEdge R330

Support asked me to download 6.5 upgrade, the zip file though. ESXi 6.5 zip file for DELL PowerEdge R330 can be found here. Click on the Vmware ESXi 6.5 U2 section and then click on the ‘Other formats’ link do download the .zip file.

I was asked to share an Outlook 2013 folder for a user and I ran into a scenario…most imformation out there targets older versions of Outlook and Exchange. We run Exchange 2016 and Outlook 2013 (latest version), so most of the information out there didn’t work for me, so I decided to document how I was able to achieve sharing folders in Outlook 2013.

For this excersice we’re going to share a folder named: Test Folder

From the mailbox we want to share Outlook folders

Right-click on the user’s mailbox name and select Folder Permissions

Next, click on Permissions tab and Add the user you’re going to allow to access, or share, the folder(s)

View the screenshot for the permissions settings

Next, right click on the Inbox folder and click on Properties

Click on Permissions tab and you’re going to add the same user you added at the mailbox permissions level (step 3)

View the screenshot for the permissions settings

Next, you’re going to right click on the folder you want to share and click on Properties

Click on Permissions tab and you’re going to add the same user again

Permissions here are set based on your requirements

View the screenshot for the permissions settings

That’s all that needs to be done

The next and final step is to go to the Outlook client of the user that needs access to the folder and add the mailbox

These steps worked for me, none of the other information out there worked.

In the event that you didn’t notice the warning on top and you went ahead and renamed the domain controller and you had Dfs services running on it, here are some instructions on how to manually remove Dfs nameserver and fix the issue.