Vsphere Content Library: RuntimeFault.Summary cannot delete content library item


When trying to delete an image from content library and you receive an error of:

“RunTimeFault.Summary”

“Cannot Delete File [Datastore] /PathtoContentLibraryVMDK”

Solution I found:

  1. Log into VCenter Server
  2. Select Content Library
  3. Right click content library item
  4. Rename item
  5. Delete item

I was trying to update some images i had on my home lab and i ran into the issue and issue when trying to delete some old templates from the library. I tried multiple times to delete the template i had stored only to receive the same error.

I investigated and found that the path from the error had no VMDK in it from the content library. That being said I had two options. Delete the folder in the datastore, which could corrupt the content library or rename the library item and try to delete again.

So when I renamed the content library item and deleted the item and it worked like a charm. I could not find a KB article for this particular issue or at least one that was relevant to content library but this worked for me.

 

EMC SourceOne – Exchange 2016 “system call failed”

“System call failed.  Unknown error”

“CoExExchProvider::LogonDS: Cannot log into mailbox”

If after you migrated the SourceOne service account and journal mailbox to Exchange 2016, and your jobs keep failing you may have a similar issue to me.

During the process of migrating the last two mailboxes (Both SourceOne) to the new environment I was getting permission errors throw in the logs while attempting to run the journaling jobs. This was because SourceOne DOES NOT SUPPORT HTTPS. 

In order to get SourceOne working properly on exchange 2016 if you are forcing HTTPS you need to enable RPC over http using the KB articles below.


Each step must be done on each worker node after migration has completed:

  1. Log into worker node using SourceOne Service account
  2. Control Panel > Mail (32-Bit) > Delete old mail profile > Create new profile (Make sure to uncheck Cached exchange mode)
  3. Regedit.exe navigate to “HKEY_CURRENT_USER\Software\Microsoft\Exchange”
  4. Create new DWORD “MapiHttpDisabled”
  5. Set value to “1”
  6. Restart Outlook client

There is an KB from Microsoft that shows you how to remove this setting, so i did not add it because it may have been confusing. But the KB is 2937684.

 

EMC SourceOne 7.2 SP6- Cannot connect to journal mailbox in a mixed Microsoft Exchange scenario (2010 and 2016)

So this has bitten me for the past couple of weeks we would try to fail over our last two mailboxes from exchange 2010 to exchange 2016. One Journal and One Service account. Come to find out (No thanks to EMC SourceOne install documentation) That the service account needs to be the last mailbox to move.

Take a look at this bug report: https://community.emc.com/docs/DOC-60862

If you are going to run in a mixed environment for a long time follow the steps below in the article and always make sure you migrate your SourceOne Service account last!

With 2010/2016 co-existence, there are certain requirements for it to work.    
    
    These requirements are:-    
    
    1) Service Account mailbox needs to be always on the lower exchange version.It should be the last mailbox to move to 2016. Exchange 2010 should be configured with RPC over https.    
    2) Exchange 2016 should have RPC over https enabled. By default Exchange 2016 has MAPI over https which is not supported by SourceOne. Customer will have to enable RPC over https and configure it correctly    
    3) All ES1 servers should have only Outlook 2010 SP2 + KB2878254. No other HF or update. Updates for Outlook should be disabled.    
    4) Profile needs to be configured on Outlook to have Outlook using RPC over https with the proxy server pointing to the 2016 server. For these changes you will need to configure AutoDiscovery.    
    5) Set the correct permissions mailbox on 2016    
    
    Without these 5 criteria, they will not be able to communicate between 2 versions of exchange.       

EMC ESRSve admin password reset (VXRail Edition)

Resetting a password on a ESRS appliance is pretty straight forward. But there is a pesky error that can pop up from time to time with ESRS appliances that get deployed via the VXRail deployment.

The normal esrs admin password reset goes something like this:


ESRSapplicance:~ # cd /opt/esrs/webuimgmt-util/
ESRSapplicance:~ # ./passwordAdmin.sh

Normally this would then ask you for a new password for the admin account associated with your ESRS appliance.

But what is the error you might ask? Well it happens in lieu of asking for a new password.

“User Configuration File Missing. Please contact ESRS Support”

In order to get around this error it is a simple command you must run before starting the ./passwordadmin.sh script:


ESRSapplicance:~ # echo admin > /etc/esrsadmin.conf
ESRSapplicance:~ # cd /opt/esrs/webuimgmt-util/
ESRSapplicance:~ # ./passwordAdmin.sh

And thats it! Have fun with ESRS and let me know it this article helped you!

AppVol: Capture Machine boots to AppStack VMDK instead of OS

Been running to issues when provisioning Application stacks that the capture machine boots to the the AppStack VMDK instead of the OS VMDK . It is an annoying issue but a very easy fix!

  1. Shutdown the capture machine and take a snapshot.
  2. Edit the settings of the capture machine, change the primary hard drive to SCSI (0:0) under the Virtual Device Node option.
  3. Select the VM options tab > boot options > Force Bios Setup
  4. During the bios setup navigate to boot and ensure the harddrive is first in the boot order.
  5. Restart your capture VM and try to mount the appStack for provisioning.

 

 

RHEL/CentOS7 xrdp auto disconnects when logging on

So I ran into an issue this week with XRDP disconnecting from my RHEL/CentOS7 RDP connection the moment the logon process is finished. Searching around for different answers to this solution there seems to be no one way of doing it. So I decided to tell you what I did to fix the issue and hopefully help you avoid a major headache in the future.

 

I will start with the installation of XRDP and go through the changes.

  1. Install xrdp tigervnc-server on your RHEL/CentOS7 box
yum -y install xrdp tigervnc-server

2. Start xrdp service and enable at boot

systemctl enable xrdp
user@computer:$ systemctl start xrdp

3. Allow 3389 through the firewall and reload firewall

firewall-cmd --permanent --zone=public --add-port=3389/tcp 
user@computer:$ firewall-cmd --reload

4. Configure SELinux ( I did not need to perform this step)

chcon --type=bin_t /usr/bin/xrdp
user@computer:$ chcon --type=bin_t /usr/bin/xrdp-sesman

5. Edit the xrdp.ini file located at the /etc/xrdp/xrdp.ini

vi /etx/xrdp/xrdp.ini

6. Comment out the line that says “Channel_code=1” Here is a example of the .ini file after the change is made

[globals]
bitmap_cache=yes
bitmap_compression=yes
port=3389
crypt_level=high
#channel_code=1
max_bpp=24
#black=000000
#grey=d6d3ce
#dark_grey=808080
#blue=08246b
#dark_blue=08246b
#white=ffffff
#red=ff0000
#green=00ff00
#background=626c72

[xrdp1]
name=sesman-Xvnc
lib=libvnc.so
username=ask
password=ask
ip=127.0.0.1

Just a FYI also some of these commands I did not come up with and where figured out from other blogs. Which when I get permission from the owners I will post here.

That being said this is my first post into some real enterprise level Linux! If you have any tip or tricks as i go down the RHEL CentOS path let me know!

Resources i used:

Install xrdp on CentOS 7 / RHEL 7

Knowing Stagnation Part 1

When you start at a new company you can tell pretty quickly who is taking a deep investment in their career and future versus who is just riding the creek of stagnation waiting for that gust of wind to get them to pay-day. The signs are clear from the outside looking in, But when you are the one who is stagnant do you know?

One of the biggest mistakes an IT lady/gentleman can make is not knowing when they are stagnant. We all got into IT for the love of learning and the constant challenge,  stagnation is usually looked over and not addressed when it should be. Which can really harm your career and performance at any company. No one is immune to stagnation. The best IT people i know have had a few lulls in their career from time to time. But the question is do they notice it and re mediate?

So how do we find/treat/cure stagnation? Well it’s not easy but we can certainly give it a go.


So how do we know the signs of stagnation?

Don’t want to go to work?

Dreading work is not only caused by stagnation but also by an unhealthy work environment. If you wake up in the morning and would rather take a 2 hour shower and cry. Chances are you are in an extremely unhealthy work environment. This can be caused by a bad manager or a shitty employee maybe you been changing out printer ink for 5 years and want to move up in the world and aren’t getting that opportunity, either way this is a sign you need to leave that job and fast.

Einstein made a pretty simple equation back when he was making up science things, take heed.

UHWE x LIIJ=DICAM

In case you didn’t learn that in high school physics full read out is below.

(Unhealthy work environment x Lack of interest in job = disaster in career and mind)


Need more energy?

More coffee! Do you find yourself needing 4 or more coffee’s a day? Are you single and don’t have kids? Didn’t go out partying last night with the guy/girls? Just a normal working day? Chances are you are stagnant… or at least getting there. That doesn’t make sense Frank you must be crazy?!? Well when was the last time you needed to drink a coffee before you go to an amusement park or had a party? Not very often. It tends to be the more excited you are about a particular task the less artificial energy you need.

If you don’t get genuinely excited about changing printer ink or building a new ESXi host then you will need a little push to get up and do it. That is a sign of stagnation. Not really getting excited about the challenges that you are presented with. Regardless of how minute or honestly how uninteresting they may be shows that you are looking for a bigger more interesting challenge, and only you can find that new challenge and exploit it.


Practice makes a perfect stagnate environment

Repetition is the path to stagnation. Would you take a job for $120,000 a year sharpening pencils all day? Probably at first you would, hell I would too how hard can it be right? Well physically not very hard, But mentally I am sure it is torture. Waking up at the same time every day, making the same commute every day, doing the same task every day can get tiring really fast. Repetition is nice for learning code and such but what happens if you are not a coder? or what happens when you need to expand your mind beyond that handful of task’s? Don’t stand for a company that wants you to do one task all day. Your career is worth more than creating distribution lists all day.


More to come on this topic in the next couple of days!