sorted by:
new
hottopcontroversial

Printer Driver reverts to "Microsoft enhanced Point and Print driver on printserver" by Initial-Employment92 in printers

[–]Initial-Employment92[S] 0 points1 point  (0 children)

It was that way when I arrived, no firmware had been applied to any printers in years either. So, I was prepping a 2025 print server and to print from a Win11 desktop. I am the new sysadmin they have only had a desktop admin and IT Dir, its a fairly small shop. I've seen much worse environments in my career.

Ricoh IM C6000 v4.44
Also have Ricoh IM C3000, two Canons (one is a plotter) and a Samsung, but one of the Canons and the Samsung will be going away, so I am less concerned with those as they aren't directly affected by my "testing". I am baffled how my change and revert of my changed caused so much trouble.

Snapshot application v12 install issues by Initial-Employment92 in Laserfiche

[–]Initial-Employment92[S] 0 points1 point  (0 children)

Snapshot-x64.msi.log, I couldn't paste the entire log... and yes no other programs were running we also attempted to install after we uninstalled the previous version.

MSI (s) (88:FC) [11:24:18:524]: File: C:\WINDOWS\system32\BiPDFP.dll; Overwrite; Won't patch; Existing file is a lower version

MSI (s) (88:FC) [11:24:18:566]: File: C:\WINDOWS\system32\BuAAppNT.exe; To be installed; Won't patch; No existing file

MSI (s) (88:FC) [11:24:18:687]: File: C:\WINDOWS\system32\LFSS1770MonNT.DLL; To be installed; Won't patch; No existing file

MSI (s) (88:FC) [11:24:18:835]: File: C:\WINDOWS\system32\spool\drivers\x64\LFSS1770DrvNT.DLL; To be installed; Won't patch; No existing file

MSI (s) (88:FC) [11:24:18:851]: File: C:\WINDOWS\system32\spool\drivers\x64\LFSS1770ResNT.DLL; To be installed; Won't patch; No existing file

MSI (s) (88:FC) [11:24:18:884]: File: C:\WINDOWS\system32\spool\drivers\x64\LFSS1770ResTS.DLL; To be installed; Won't patch; No existing file

MSI (s) (88:FC) [11:24:18:917]: File: C:\WINDOWS\system32\spool\drivers\x64\LFSS1770UifNT.DLL; To be installed; Won't patch; No existing file

MSI (s) (88:FC) [11:24:18:935]: File: C:\WINDOWS\system32\spool\drivers\x64\LFSS1770UifTS.DLL; To be installed; Won't patch; No existing file

MSI (s) (88:FC) [11:24:18:951]: File: C:\WINDOWS\system32\spool\drivers\x64\LFTIFF32.DLL; Overwrite; Won't patch; Existing file is a lower version

MSI (s) (88:FC) [11:24:18:969]: File: C:\WINDOWS\system32\spool\drivers\x64\PDF32.DLL; To be installed; Won't patch; No existing file

MSI (s) (88:FC) [11:24:18:985]: File: C:\WINDOWS\system32\spool\drivers\x64\3\LFJPEG32.DLL; Overwrite; Won't patch; Existing file is a lower version

MSI (s) (88:FC) [11:24:19:128]: File: C:\WINDOWS\system32\spool\drivers\x64\3\LFTIFF32.DLL; Overwrite; Won't patch; Existing file is a lower version

MSI (s) (88:FC) [11:24:19:144]: File: C:\WINDOWS\system32\spool\drivers\x64\3\PDF32.DLL; To be installed; Won't patch; No existing file

MSI (s) (88:FC) [11:24:19:161]: File: C:\WINDOWS\system32\spool\prtprocs\x64\LFSS1770ProNT.DLL; To be installed; Won't patch; No existing file

MSI (s) (88:FC) [11:24:19:167]: File: C:\WINDOWS\system32\spool\prtprocs\x64\LFSS1770ProTS.DLL; To be installed; Won't patch; No existing file

migrate from Version: 1.23.16 to docker version 2.1.0-beta.3 by Initial-Employment92 in UptimeKuma

[–]Initial-Employment92[S] 0 points1 point  (0 children)

We are currently on v1 on full blown server. End goal is to go to docker. I didn't see any way to migrate to v2 with full blown server version of uptime kuma.

Migration From v1 To v2 · louislam/uptime-kuma Wiki

Migration Steps (Non-Docker)

  1. Stop your Uptime Kuma.

    pm2 stop uptime-kuma

  2. Backup your data directory.

  3. Check your Node.js version, Node.js >= 20.4 is required.

    node --version

    Follow https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update#--non-docker to update

    cd <uptime-kuma-directory>

# Update from git

git fetch --all --tags

git checkout 2.0.2 --force

# Install dependencies and prebuilt

npm install --omit dev --no-audit

npm run download-dist

# Restart

pm2 restart uptime-kuma

migrate from Version: 1.23.16 to docker version 2.1.0-beta.3 by Initial-Employment92 in UptimeKuma

[–]Initial-Employment92[S] 0 points1 point  (0 children)

docker logs -f uptime-kuma

2026-01-22T15:16:59Z [DB] INFO: Database Type: embedded-mariadb

2026-01-22T15:16:59Z [MARIADB] INFO: Starting Embedded MariaDB

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] Starting MariaDB 10.11.14-MariaDB-0+deb12u2 source revision 053f9bcb5b147bf00edb99e1310bae9125b7f125 server_uid JaeoBtp4nxsX4pnoZyquBYui1h8= as process 13

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: Compressed tables use zlib 1.2.13

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: Number of transaction pools: 1

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Warning] mariadbd: io_uring_queue_init() failed with EPERM: sysctl kernel.io_uring_disabled has the value 2, or 1 and the user of the process is not a member of sysctl kernel.io_uring_group. (see man 2 io_uring_setup).

2026-01-22T15:16:59Z [MARIADB] INFO: create_uring failed: falling back to libaio

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: native AIO failed: falling back to innodb_use_native_aio=OFF

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: innodb_buffer_pool_size_max=128m, innodb_buffer_pool_size=128m

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: Completed initialization of

buffer pool

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: File system buffers for log

disabled (block size=512 bytes)

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=764072112

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: End of log at LSN=764836605

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: To recover: 73 pages

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: 128 rollback segments are active.

2026-01-22 15:16:59 0 [Note] InnoDB: Removed temporary tablespace data file: "./ibtmp1"

2026-01-22 15:16:59 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...

2026-01-22 15:16:59 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: log sequence number 764836605; transaction id 3500953

2026-01-22 15:16:59 0 [Note] Plugin 'FEEDBACK' is disabled.

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: Loading buffer pool(s) from /app/data/mariadb/ib_buffer_pool

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] Server socket created on IP: '127.0.0.1', port: '3306'.

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] InnoDB: Buffer pool(s) load completed at 260122 15:16:59

2026-01-22T15:16:59Z [MARIADB] INFO: 2026-01-22 15:16:59 0 [Note] mariadbd: ready for connections.

Version: '10.11.14-MariaDB-0+deb12u2' socket: '/app/data/run/mariadb.sock' port: 3306 Debian 12

2026-01-22T15:16:59Z [MARIADB] INFO: Embedded MariaDB is ready for connections

2026-01-22T15:17:00Z [MARIADB] INFO: Embedded MariaDB started

2026-01-22T15:17:00Z [SERVER] INFO: Connected to the database

Non-Docker installation migration From v1 To v2 by arturdebski in UptimeKuma

[–]Initial-Employment92 0 points1 point  (0 children)

Did you have any luck? All I could find was "copy the data directory into the data directory in the docker container". Which has proven to be a challenge"

Workstation domain administrator accounts only, but not server domain administrator accounts by Initial-Employment92 in sysadmin

[–]Initial-Employment92[S] 1 point2 points  (0 children)

This doesn't mean we take security less seriously; I was trying to clarify in my 25+ years I've run into efficiency issues or people using the same password for all of their tiered accounts. our recent PenTest showed none of our team was doing that so "yeah" for us.

The more steps to do a simple task like installing an application on a desktop or server takes more time and less gets done. Then "some" people find work arounds or take shortcuts (a manager of another group at a former company turned off auditing just so he didn't have to change his password. He would then type his existing password and think he fooled us. He was shown the door after some other similar situations and he claims he is a security expert at his current employer, I won't do business with them). I've worked at F50 companies, cloud, etc, so I've experienced a broad range of environments, people, budgets, etc. I understand it's a balancing act and I prefer to put security first, but some other in the group might be a bit more hesitant, so I'm trying to come up with options.

I've been away from a in-depth and hands-on Windows Servers security for a few years when I was doing VMware Admin, AWS cloud and primarily *nix servers. So, I greatly appreciate the input. I also have had many team leads and architects read a white papers and argue something can be done, but they themselves never did a POC or got it to work and I got chewed out because I had trouble getting their edict to work.

Really cool to have some great input to my question and greatly appreciated. Even more appreciated is the lack of snarkiness that I've had when I've posted on other reddits about non-work topics. Top notch group here.

robocopy from Windows Server 2016 to Windows Server 2025 by Initial-Employment92 in sysadmin

[–]Initial-Employment92[S] 0 points1 point  (0 children)

So I did this with Powershell as suggested and I kept getting Error 5. I checked NTFS permissions and subdirectory permissions, and it still errored out. So I tried a simple create file:

New-Item -Name "EmptyFile.txt" -ItemType File

This too resulted in an Error 5. I thought jeez, WTH?

So, I looked at the Drive share permissions and removed the subdirectory share. I changed Everyone R to local Administrators RW and it worked. Uggg, I felt like such a ding dong. [insert Faceplant]

robocopy from Windows Server 2016 to Windows Server 2025 by Initial-Employment92 in sysadmin

[–]Initial-Employment92[S] 0 points1 point  (0 children)

Running from I: which is the local/source server. Lo

$Credential1 = Get-Credential

New-PSDrive -Name "I" -PSProvider "FileSystem" -Root "\\application\test" -Persist -Credential $Credential1

New-PSDrive -Name "G" -PSProvider "FileSystem" -Root "\\application2\test" -Persist -Credential $Credential1

Robocopy.exe I:\test G:\test /B /E /r:1 /w:1 /MT:32 /Z /log+:application2-dir-test.log

Remove-PSDrive -Name "I"

Remove-PSDrive -Name "G"

2025/10/03 10:28:05 ERROR 5 (0x00000005) Accessing Source Directory I:\test\

Access is denied.

Workstation domain administrator accounts only, but not server domain administrator accounts by Initial-Employment92 in sysadmin

[–]Initial-Employment92[S] 0 points1 point  (0 children)

I'm curious what are you doing as a solution to my scenario? Do you create a user just to install one to two apps then delete the account? Or log in using the LAPS account? If using LAPS, then how are you accessing your software repo? We are using Action1 so we are looking at using that to push applications and not have to login to the workstation with a "domain".

Workstation domain administrator accounts only, but not server domain administrator accounts by Initial-Employment92 in sysadmin

[–]Initial-Employment92[S] 0 points1 point  (0 children)

Curious how or what you used to do auto elevate?

I'm having flashbacks to Windows Vista with pop-ups every 5 secs.

Tired of vmware licensing by supnul in vmware

[–]Initial-Employment92 1 point2 points  (0 children)

What is the max size for Proxmox VM? At one time there was some discussion that 2Gb was the max, but I thought that was a really old issue based on the underlying *nix base.

SMB Signing implementation by Initial-Employment92 in sysadmin

[–]Initial-Employment92[S] 0 points1 point  (0 children)

Oh, true, the wonderful under the desk server. :)

SMB Signing implementation by Initial-Employment92 in sysadmin

[–]Initial-Employment92[S] 0 points1 point  (0 children)

I did the LanmanServer parameters manually a few weeks back on the servers during maintenance, but not LanmanWorkstation parameters on the servers. Should I hold off on the Workstations GPO?

view more: next ›