Windows Server 2022 and FSLogix causing all printers to go into a Not Connected state

Question

Windows Server 2022 and FSLogix causing all printers to go into a Not Connected state

Larry Schoffstall 20

We have some 2022 servers in an RDS environment using FSLogix. Almost at random, they will go not connected on all printers.

No amount of troubleshooting brings them back. resetting spooler, clearing spooler files, uninstalling/reinstalling all printers (and this affects everything, like Microsoft Print to PDF). The only solution is to restore the server from a backup and hope whatever causes it doesn't happen again, but eventually it does happen.

It affects all users on the machine, even local users, and it seems like after it happens it also stops applying any kind of GPO settings.

Has anyone else run into this or have any idea where else to look?

1 answer

Your answer

Answer 1

Hello,
The core issue you encountered in the RDS environment where FSLogix servers randomly experience printer disconnection problems is as follows:

All printers suddenly show "Not connected" (including system-level printers such as "Microsoft Print to PDF")
Affects all users (remote users and local administrators)
Group policy settings also fail simultaneously
The only temporary solution is to restore the server backup.

Troubleshooting plan:

System integrity check


# System File Check 

sfc /scannow

# Mirror Health Check 

dism /online /cleanup-image /restorehealth

# Reset Windows Update Components 

net stop wuauserv

net stop cryptSvc

net stop bits

net stop msiserver

ren C:\Windows\SoftwareDistribution SoftwareDistribution.old

net start wuauserv

net start cryptSvc

net start bits

net start msiserver

FSLogix Configuration File Troubleshooting

Log Analysis Path: %ProgramData%\FSLogix\Logs\Profile

Pay special attention to checking the records of "Registry Configuration Unit Load Error" or "File Locked".

Temporary test plan:

1)Rename the user VHDX file to force the creation of a new configuration file.

2)Temporarily disable the FSLogix redirection function through Group Policy.

Group Policy Failure Analysis

Key Checkpoints:

Event Viewer → Application and Services Logs/Microsoft/Windows/GroupPolicy
Check for error codes 1058/1096/7016
Confirm the integrity of the C:\Windows\System32\GroupPolicy directory

Forced strategy update:


gpupdate /force

Dependency Service Detection


# Restart Critical Services 

Get-Service -Name RpcSs, DcomLaunch, Spooler | Restart-Service -Force

# Check the status of the RPC connection 

netstat -ano | findstr "135"

Conflict Resolution for Security Software

The following paths need to be excluded in the security software:
C:\Windows\System32\spool
C:\ProgramData\FSLogix

It is suggested that the real-time monitoring test be temporarily suspended.

System Update Management

Update to the latest patch

### Problem Location

Problem occurs --> Print service status --> Service stops --> Check event log --> Analyze error code --> System file/registry corruption

Problem occurs --> Print service status --> Service running --> Check port occupation --> Check RPC connection --> Network policy restriction

### Follow-up Suggestions

Immediately capture the memory dump for further analysis when the next failure occurs.

Share via

Windows Server 2022 and FSLogix causing all printers to go into a Not Connected state

1 answer

Your answer