LDAP Filter: (&(cn=LDAP*)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))

Let’s break down the LDAP filter and understand its components:

1. &(cn=LDAP): The filter begins with the ampersand symbol (&), indicating a logical AND operation. The cn attribute is used to filter objects based on their common name. In this case, “LDAP” denotes that the common name starts with “LDAP.”
2. !(userAccountControl:1.2.840.113556.1.4.803:=2): The exclamation mark (!) negates the condition that follows, which allows us to exclude certain user accounts. The userAccountControl attribute stores various account control flags and the value 2 represents the “ACCOUNT_DISABLED” flag. By excluding user accounts with this flag, we ensure that only active users are displayed.

By integrating this LDAP filter into your Xerox device configuration, you can experience several significant benefits:

1. Enhanced Security: By excluding disabled user accounts, you reduce the risk of unauthorized access to your Xerox devices. Only active users will have visibility and control over these devices, bolstering your overall security posture.
2. Improved User Experience: Displaying only active users simplifies the device selection process for users. It eliminates clutter and minimizes the chances of inadvertently selecting an inactive account, leading to a smoother and more efficient user experience.
3. Streamlined Device Access: With the LDAP filter in place, administrators and users can quickly locate and interact with active accounts. This streamlines device access, saving time and ensuring that users can seamlessly carry out their tasks without unnecessary disruptions.

To implement this LDAP filter on Xerox devices, follow these steps:

1. Access the device’s web-based administration interface.
2. Navigate to the LDAP settings or user authentication section.
3. Locate the field for custom LDAP filters and enter the filter:
   (&(cn=LDAP*)(!(userAccountControl:1.2.840.113556.1.4.803:=2)))
4. Save the configuration changes.
5. Test the LDAP filter by accessing the device and verifying that only active users are displayed.

Custom LDAP filters offer a powerful toolset for optimizing device management on Xerox devices. By utilizing the LDAP filter provided in this blog post, you can ensure that only active users from Active Directory are visible, enhancing security and streamlining device access. Take advantage of this filter to unleash the full potential of your Xerox devices and empower your workforce with a seamless and efficient user experience.

The post Custom LDAP Filters for Active Users on Xerox Devices first appeared on MrJordanRoth.com.

version: "3.8"

services:
  postgres:
    image: postgres:alpine
    restart: always
    ports:
      - 5432:5432
    volumes:
      - pgdata:/var/lib/postgresql/data
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -U postgres"]
      start_period: 15s
      interval: 30s
      timeout: 30s
      retries: 3
    environment:
      - POSTGRES_DB=postgres
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=postgres
      - POSTGRES_HOST=localhost

  server:
    image: amruthpillai/reactive-resume:server-latest
    # build:
    #   context: .
    #   dockerfile: ./server/Dockerfile
    restart: always
    ports:
      - 3100:3100
    depends_on:
      - postgres
    environment:
      - PUBLIC_URL=https://subdomain.yourdomain.com
      - PUBLIC_SERVER_URL=https://subdomain.yourdomain.com
      - PUBLIC_GOOGLE_CLIENT_ID=
      - POSTGRES_DB=postgres
      - POSTGRES_USER=postgres
      - POSTGRES_PASSWORD=postgres
      - SECRET_KEY=make-a-secret-key
      - POSTGRES_HOST=postgres
      - POSTGRES_PORT=5432
      - POSTGRES_SSL_CERT=
      - JWT_SECRET=make-a-secret-key
      - JWT_EXPIRY_TIME=604800
      - GOOGLE_CLIENT_SECRET=
      - GOOGLE_API_KEY=
      - MAIL_FROM_NAME=
      - MAIL_FROM_EMAIL=
      - MAIL_HOST=
      - MAIL_PORT=
      - MAIL_USERNAME=
      - MAIL_PASSWORD=
      - STORAGE_BUCKET=
      - STORAGE_REGION=
      - STORAGE_ENDPOINT=
      - STORAGE_URL_PREFIX=
      - STORAGE_ACCESS_KEY=
      - STORAGE_SECRET_KEY=
      - PDF_DELETION_TIME=

  client:
    image: amruthpillai/reactive-resume:client-latest
    # build:
    #   context: .
    #   dockerfile: ./client/Dockerfile
    restart: always
    ports:
      - 3000:3000
    depends_on:
      - server
    environment:
      - PUBLIC_URL=https://subdomain.yourdomain.com
      - PUBLIC_SERVER_URL=https://subdomain.yourdomain.com
      - PUBLIC_GOOGLE_CLIENT_ID=

volumes:
  pgdata:

*Note: You should understand the docker-compose file and edit it to your needs. This should not be copied and pasted for production use.

When you configure Nginx Proxy Manager with default settings, you may observe some broken components on the site. This is likely because the client and server are utilizing different ports, and during the initial Nginx setup, only port 3000 was specified (as mentioned in this post). To ensure smooth functioning, I identified the server-side calls and added Custom Locations. To resolve the issue, please add the following Custom Locations within the Edit Proxy Host section:

After saving this configuration, you should be able to access your locally hosted Reactive-Resume docker seamlessly from your Nginx proxy server, without encountering any issues.

The post Reactive Resume running behind Nginx Proxy Manager first appeared on MrJordanRoth.com.

We have noticed an increase in calls with customers scanning email utilizing the SMTP servers of Yahoo. The message is simple “Job failed. No messages were sent. Could not communicate with the sending mail server (SMTP). Contact your System Administrator.” At first, it seemed the messages never made it over to the Yahoo servers, but today I dug in a little further and noticed the test e-mails from the machines and the actual e-mails from the user interfaces were actually being transmitted to the servers – however, they were stuck in the Drafts folder. I examined the message and noticed each time there was a NULL e-mail address in the CC field.

Since I saw this NULL character in the CC field, I decided to test this by sending an e-mail from the machine’s user interface with a TO and a CC address, and to my astonishment, it was completed successfully. I have reached out to Xerox which said they were aware of an ongoing issue with Yahoo SMTP servers since Rogers was moving to their servers, but haven’t seen this exact issue. I have also contacted Yahoo support, or should I say I tried, but without a paid subscription to their plus service I was only able to get extremely basic information or refer to help.yahoo.com or the online chat – which was completely useless.

As of this writing, a workaround is to use the Auto Add Me to the CC field or to add an e-mail address to the TO and CC field when sending an e-mail. If I get any updates or find anything else additional, I will be sure to update this post.

SMTP Server: smtp.mail.yahoo.com
Port: 587 w/ STARTTLS
Username: full yahoo email address
Password: app password

The post SMTP services fail with app password on Yahoo servers first appeared on MrJordanRoth.com.

The good news is that this issue can be fixed rather easily, but not by re-installing or even changing the print driver on some ocasions. There are five simple steps to follow and you will be back up and running with little downtime using the currently installed driver.

1. Click on your Start menu
2. Type in command or cmd
3. Right click on Command Prompt and select Run as administrator
4. Type in “netsh winsock reset” without the quotations
5. Reboot your computer

I hope this saves you some time of frustration and gets your back to printing!

The post The print driver is not installed on this computer. first appeared on MrJordanRoth.com.

When you configure a printer, or multifunction device, on the network, it will most likely have a DHCP Address. You want to login to your router and assign a DHCP reservation or you want to STATIC the IP address outside of your DHCP range. This will make sure your printing to the correct device each and every time – a foolproof way. Now when you install a device using the Standard TCP/IP port, it almost always has SNMP enabled under the Ports Tab (click on Configure Port). This is the reason why your device may say offline or your users say when I restart the computer or printer it starts working again – disable SNMP (uncheck it).

I hope this helps someone who is consistently having issues printing and is having a difficult time figuring out what is causing such behavior.

The post My printer is Offline, when I reboot it I can print! first appeared on MrJordanRoth.com.

While it was a convenient way for many people to think outside of the box for printing, a lot of people are still wondering what they can do since Google Cloud Print will be discontinued. Personally, I have started to use PaperCut Mobility Print. It’s a free solution that isn’t very difficult to set up and it will give you the same functionality as Google Cloud Print. So if you are looking for a replacement, it’s one that I would recommend.

The post The time has come, goodbye Google Cloud Print first appeared on MrJordanRoth.com.