A.I.

Error “Group(s) not found: ui (via –with)” installing PrivateGPT 0.4 on WSL

Note: the below assumes you already have followed any other guide, but you have gotten an error up to that point. The below will pick up directly where you left off in the your original guide.

As of a few days ago, when you try to install PrivateGPT with Poetry on WSL following various guides, the commands: “cd privateGPT”, “poetry install –with ui”, “poetry install –with local”, Poetry returns the errors.

Group(s) not found: ui (via –with)
Group(s) not found: local (via –with)

When going through the commit (which can be found here: 45f0571), it turns out that ui is moved from its own group and has moved to the “extras” group. It’s unclear to me where “local” went though.

A.I.

PrivateGPT: ImportError: docx2txt is required to read Microsoft Word files

When trying to interact with Microsoft Word files, PrivateGPT throws out an error and does not want to parse it:
ImportError: docx2txt is required to read Microsoft Word files: pip install docx2txt

When actually installing docx2txt with pip, the error is still there. For some strange reason, PrivateGPT is still recommending pip, while it has moved away from pip for quite a while now. To resolve the issue, the answer is simple: Do Not Use Pip to install docx2txt (or whisper or any of the other converters you may need to upload your files.

Microsoft Generic

Active Directory: Best Practices for Internal Domain and Network Names

Introduction

When planning for a new Active Directory (AD) or upgrade AD, or merging AD one of the topics that will get on the table is planning DNS. DNS is the Domain Naming system, used to translate names into network (IP) addresses. Certainly this is the case if you need to plan for integration with an extranet, DMZ (demilitarized zone, typically between intranet and internet), or publishing website and applications

Microsoft Generic

216.146.35.35 & 216.146.36.36 added as primary to your DNS settings

With the update to their client version 5.3.1 for Windows, DynDNS sets the first to entries in your local DNS to 216.146.35.35 and 216.146.36.36. Unfortunately this causes the machine the DynDNS client is installed on to fail to contact any other server within the local network up to giving login issues over RDP if this server is domain joined and requires NLA. The reason is happens is that this update sets the option “Use Dyn Recursive DNS servers on this machine” default.
This can be disabled by opening the client, click Settings, click Preferences and uncheck “Use Dyn Recursive DNS servers on this machine”

Dyn Updater Preferences (not real IP nor account)

Once this option is unchecked, the client will stop hijacking DNS on the machine it’s installed on.

Microsoft Generic

Monitoring for WMI corruption issues and rebuilding WMI

Background

  • WMI is a Windows OS component that is present on every Windows server and PC
  • WMI corruption can cause failures that include failure to apply Group Policy
  • Some organizations rely upon Group Policy to secure servers, secure group membership to groups with elevated rights, and to provide the working environment for interactive Remote Desktop Services users
  • WMI failures could lead to service outages or security issues