Conflicting VIB: Upgrading to ESXi 6.5

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

  1. 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.
  2. Next, upload this file to the host you’re trying to upgrade.
  3. Log on to the host as root and type the following command
    1. esxcli software vib install -d “/vmfs/volumes/Datastore/DirectoryName/PatchName.zip”
  4. Reboot your host

 

The actual Vmware KB can be found here.

 

 

 

 

 

, , , , , ,

Leave a comment

Disable Instant Message History for Cisco Jabber

The following steps will allow you to disable IM history for Cisco Jabber. These steps have been confirmed on Jabber 11.x.x.

Modify Jabber Configuration File

  1. Jabber configuration file is called: jabber-config-defaults.xml
  2. File is located at: C:\Program Files (x86)\Cisco Systems\Cisco Jabber
  3. The following settings were added to the end of the file:

<!– My Customization Section –>

<userConfig name=”Disable_IM_History” value=”TRUE”/>

<userConfig name=”EnableSaveChatToFile” value=”FALSE”/>

<userConfig name=”EnableAutosave” value=”FALSE”/>

Disable_IM_History Disables instant message history. When IM window is closed all history is removed

EnableSaveChatToFile If set to FALSE, will not allowed chat to be saved to a file

EnableAutosave Specifies whether users can save instant messages automatically each time they close a conversation

4. Close Jabber and re-open it

Note: Detailed information can be found here

,

Leave a comment

How to Share a Folder in Outlook 2013

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

  1. Right-click on the user’s mailbox name and select Folder Permissions
  2. Next, click on Permissions tab and Add the user you’re going to allow to access, or share, the folder(s)
  3. View the screenshot for the permissions settings2018-05-05_1932
  4. Next, right click on the Inbox folder and click on Properties
  5. Click on Permissions tab and you’re going to add the same user you added at the mailbox permissions level (step 3)
  6. View the screenshot for the permissions settings2018-05-05_1936
  7. Next, you’re going to right click on the folder you want to share and click on Properties
  8. Click on Permissions tab and you’re going to add the same user again
  9. Permissions here are set based on your requirements
  10. View the screenshot for the permissions settings2018-05-05_1944.png
  11. That’s all that needs to be done
  12. 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.

Leave a comment

Forcibly Remove Dfs Nameserver

The following steps can be used to remove a Dfs nameserver that no longer exists in your environment.

  1. Log on to a Dfs server
  2. Open an elevated command line
  3. We’re going to use dfsutil with the following parameters: dfsutil diag unmapdomroot \<domainname><DFSname> \<DFSrootserver><DFSshare>
    1. As a sample: dfsutil diag unmapdomroot \\DfsRootName\DfsFolderName \\Server_to_remove\DfsFolderName
  4. No need to reboot just wait for replication

Leave a comment

Renaming Windows Domain Controllers

The following are the steps needed to rename a domain controller; the steps have been tested up to Windows Server 2016.

Note: If your DC is also acting as a Dfs nameroot server, make sure you remove the nameserver from Dfs first!

From an elevated command line, type the following commands:

  1. Add the new domain controller name NEW_DC; we’re replacing OLD_DC
    NETDOM COMPUTERNAME OLD_DC.companydomain.com /ADD:NEW_DC.companydomain.com
  2. Designate the new name as the primary computer name; OLD_DC gets removed and NEW_DC is new primary name
    NETDOM COMPUTERNAME OLD_DC.companydomain.com /MAKEPRIMARY:NEW_DC.companydomain.com
  3. Reboot domain controller
  4. Now, let’s remove the old domain controller name from Active Directory
    NETDOM COMPUTERNAME NEW_DC.companydomain.com /REMOVE:OLD_DC.companydomain.com
  5. Sync all DCs

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.

  1. Log on to the recently renamed domain controller
  2. Open Regedit.exe
  3. Go to HKLM\Software\Microsoft\DFS\Roots\domainV2
  4. Delete the key found under domainV2 and reboot your server
  5. Next, remove the Dfs share from the server
  6. Now you can delete the Dfs folder
  7. Done

2017-06-10_1708

Leave a comment

WinPE Nic Drivers for DELL Optiplex 7050

While running the latest version of SCCM 2012 and latest up-to-date Boot Image, network drivers for DELL OptiPlex 7050 need to be injected in order for WinPE environment to work.

Luckily, storage and network drivers for the OptiPlex 7050 model can be found on DELL’s support site.

The following screenshot will show you the file you need to download.

3-22-2017 10-34-49 AM

Once you’ve downloaded it the CAB file, then go ahead and update your Boot Image file(s).

Leave a comment

Vmware Port Mirror and MS Advanced Thread Analytics

The project was to install MS Advanced Thread Analytic Gateway in a virtual machine, in Vmware, to monitor a physical domain controller.

Hardware involved

  1. Domain controller (physical) – DCServer1
  2. DELL switch – switch1
  3. ESXi host – host1
  4. MS ATA Gateway – atagw1

Setup Port Mirroring at Physical Switch Level

DC server DCserver1 and ESXi host1 are physically connected to switch1. DCserver1 connects on port 40 and host1 connects on port 44 of the switch.

We’re going to configure port mirroring on switch1 as source being port 40 and destination port 44 and we’re going to use use both directions in our config. You can use the following link to configure port mirroring on DELL switches.

Configure Vmware for Port Mirroring

As mentioned before, host1 connects to switch1, and we’re going to use this connection (vmnic2) and create a new standard switch (that was my setup). So, at point, vmnic2 connects to port 44 on switch1.

Once your new standard switch is created (vSwitch2), then we’ll create a new port group (ATA-Capture). While creating port group ATA-Capture, make sure to enable Promiscuous Mode and set VLAN ID to All (4095) – this part crucial!

port-group

 

Configure Microsoft ATA Gateway VM

Your MS ATA Gateway will need to have two NICs. One NIC will be used for day to day work and the second NIC for capture. To make thing easier, rename the NIC to something like ‘Capture‘. Next, make sure that your Capture NIC belongs to the ATA-Capture port group.

At this point you should be able to install MS ATA Gateway software.

Leave a comment