Automation screen is black for Lenovo X1 Yoga

I need a solution

Just received in a new Lenovo X1 Yoga 4th generation.  When booting to Automation, the screen is black.  I can’t find any WinPE 10 drivers for the display and I don’t think Deployment Solution will handle display drivers for automation anyway.  I was able to use VNC to connect, but this isn’t a solution.  You can even use the keyboard of the laptop and the characters show up on my remote VNC connection.  The touch display is also working.  The display type is an Intel UHD Graphics 620.  Anyone have a solution?



Cisco Enterprise NFV Infrastructure Software VNC Authentication Bypass Vulnerability

A vulnerability in the Virtual Network Computing (VNC) console implementation of Cisco Enterprise NFV Infrastructure Software (NFVIS) could allow an unauthenticated, remote attacker to access the VNC console session of an administrative user on an affected device.

The vulnerability is due to an insufficient authentication mechanism used to establish a VNC session. An attacker could exploit this vulnerability by intercepting an administrator VNC session request prior to login. A successful exploit could allow the attacker to watch the administrator console session or interact with it, allowing admin access to the affected device.

Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability.

This advisory is available at the following link:

Security Impact Rating: High

CVE: CVE-2019-1895


  • No Related Posts

VNC being block by SEP IPS

I need a solution

Anybody facing this? 27-28 June

Is there any new changes on the IPS signature?….seems like the rule inconsistent

The settings is allow and log only, but apparently a lot got blocked..

Only after placing under signature execption… vnc ok



7021811: Reflection X 14.x or Reflection X Advantage, Password Aging, and Secure Shell

Password Aging Management and Reflection

To change a user’s password the host typically requires an interactive shell. Although Reflection X does not provide an interactive shell, this requirement can be bypassed by configuring Reflection X for keyboard interactive authentication user authentication, and configuring the host for Password Aging Management (PAM).

Configure Reflection X 14.x or Reflection X Advantage to use Keyboard Interactive Authentication

Keyboard Interactive user authentication is automatically enabled in Reflection X 14.x or Reflection X Advantage; however, it is not the primary authentication method. Depending on how the SSH server is configured, you may need to move the keyboard Interactive user authentication option to the top of the authentication methods list.

Reflection X Advantage

Follow these steps to modify the authentication order in Reflection X Advantage.

  1. In the Reflection X Manager, configure your X client to connect with Secure Shell.
  2. Click Advanced.
  3. Click the Authentication tab.
  4. Under User Authentication Methods, select Keyboard Interactive, and click the “up” arrow to move Keyboard Interactive to the top of the list.
  1. Click Close. The changes are saved automatically.

Reflection X 14.x

Follow these steps to modify the authentication order in Reflection X 14.x.

  1. In the Reflection X Manager, select your Secure Shell client connection file.
  2. Click Advanced.
  3. Select Keyboard Interactive, and click the “up” arrow to move Keyboard Interactive to the list.
  1. Click OK.
  2. Click File > Save to save the setting.

Configure the SSH Server to use Keyboard Interactive Authentication

Follow these steps to enable the host’s Password Aging Management to interact with Reflection X 14.x or Reflection X Advantage when connecting over Secure Shell. This configuration enables users to update an expired password while connecting to the host using Reflection X 14.x or Reflection X Advantage.

Note: These steps vary based on the SSH server product and version.

Example 1

The following example is for Reflection for Secure IT UNIX Server version 7.0.

  1. Connect to your host with an account that has permissions to edit the sshd2_config file.
  2. Open the sshd2_config file in a text editor.
  3. In the sshd2_config file, ensure that keyboard interactive authentication is enabled, and that PAM is required when using keyboard interactive.
AllowedAuthentications keyboard-interactive

AuthKbdInt.Required pam
  1. Save the file.
  2. Stop and restart the sshd2_config daemon.

Example 2

This example is for OpenSSH UNIX Server v4.3p2.

  1. Connect to your host with an account that has permissions to edit the sshd_config file.
  2. Open the sshd_config file in a text editor.
  3. Ensure the following two settings are enabled:
ChallengeResponseAuthentication yes

UsePAM yes
  1. Save the file.
  2. Stop and restart the sshd_config daemon.

Once these edits have been made to the configuration file, and the daemon is restarted, users will be prompted to create a new password if their password is expired. They will be guided through creating a new password by a series of dialog boxes, similar to the ones below.



Getting TeamViewer to work with SEP 14.0 RU1 MP1

I need a solution

I have SEP 14.0 Ru1 MP1 unmanaged. I have the 64bit version installed.

I disable SEP and TeamViewer works fine.

I turn SEP back on and TeamViewer can no longer go online.

I have a rule for allow all for all TeamViewer related applications in the program files (86x) folder (no separate 64bit installer for TeamViewer)..

I have this issue on WIndows server 2008 and 2012 r2.

I have tried the blanket allow all firewall rule for everything and didn’t work.

This problem has been intermittent.




ProxySG | Unable to connect Teamviewer

I need a solution

Dear All

   I have issue about unable to connect Teamviewer via Proxy. my customer connect proxy type explicit and they have detect protocol

and i try to add CPL layer don’t detect protocol for    it can connect normal to Teamviewer.

but my customer would like to allow only some client for use teamviewer and allow only working hour monday to friday  08.00-20.00

how can i create cpl for this requirement. please recommend.

Thank you so much for your kindly to help

Best Regards,

Chakuttha R.




Re: Expiration of license in NetWorker

“DELL EMC provided him with a new license enabler which should have an expiration date somewhat in 2019. But the NMC shows that the new license expires at the end of may 2018.”

If you enter a NetWorker license, either by using the nsrcap command or using NetWorker Management Console, the license then has a certain number of days before it expires (e.g. 45 days). Before this expiration date, you are supposed to contact the licensing department, and provide them with the enabler code and the host id of the backup server. Licensing can then generate an authorization code for your customer to use to permanently authorize the license, and thereby have no expiration date.

Without knowing what license you are referring to, it is difficult to accurately predict if the backup operations will cease to function. Can you please provide the license name, and enabler code? Also the NetWorker server version?

If you have the enabler code, please use it in the following command, to be run on the NetWorker Server:

nsrcap -vnc enabler-code