Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 9 additions & 2 deletions AGENTS.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,13 @@
# Agent Instructions

This is the canonical documentation site for PrintMaster. Program changes live in **Printmaster-Org/printmaster**, normally checked out next to this repo at `../printmaster`. Its [AGENTS.md](../printmaster/AGENTS.md) describes how program and docs changes are paired.
This is the canonical documentation site for PrintMaster, including the application, product website, and standalone Scans utility. Their repositories are normally checked out alongside this one at `../printmaster`, `../printmaster.work`, and `../scans`. The main application's [AGENTS.md](../printmaster/AGENTS.md) describes how program and docs changes are paired.

## Keep documentation current (required)

- Review documentation impact for every feature, fix, removal, and deprecation across these repositories. Update affected guides under `content/`, API contracts under `static/openapi/` when applicable, and source-local READMEs/examples in the same task as implementation changes.
- Verify documented behavior against the implementation, preserve imported `source`/`sourceCommit` provenance, and distinguish unreleased changes from published behavior. Do not recreate removed legacy documentation trees or duplicate canonical guides in source repositories.
- Follow the [README](README.md) for editing and validation and [API_MAINTENANCE.md](API_MAINTENANCE.md) for contract changes. Link implementation and documentation commits or PRs, and report the pages changed and validation run.
- If no documentation change is needed, explicitly explain why. If a required checkout is unavailable, report the blocker and exact pages needing updates rather than silently leaving docs stale or reporting completion.

## Commit messages (required)

Expand All @@ -11,7 +18,7 @@ type(scope): imperative summary, lowercase, no trailing period

What the documentation now covers and why.

Implementation: Printmaster-Org/printmaster@<full sha> (when paired with a program change)
Implementation: Printmaster-Org/<repo>@<full sha> (when paired with an implementation change)
Co-authored-by: ... (trailers last)
```

Expand Down
16 changes: 13 additions & 3 deletions content/scanning/printmaster-scans.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,7 +32,7 @@ Windows 7, 8, 8.1, and Windows Server are not validated support targets.

3. Review the username, password, local directory, and SMB share name. The defaults are user `scans`, directory `C:\scans`, and share `scans`. Keep the generated password or use one that meets your organization's policy.
4. Use the **Settings** gear to select which steps to run, then choose **OK**.
5. Review the progress list. On successful account setup, use **Copy Password** and store the credential securely before selecting **Done**. Do not share it in screenshots or issue reports.
5. Review the progress list. If Windows rejects the password, follow the [password correction steps](#windows-rejects-the-password) before proceeding. On successful account setup, use **Copy Password** and store the credential securely before selecting **Done**. Do not share it in screenshots or issue reports.

The utility can create or update the dedicated local account, hide it from the login screen, create the folder, set folder permissions, create the SMB share, and add a desktop shortcut. It can also set non-domain network profiles to Private and enable File and Printer Sharing and Network Discovery firewall rules.

Expand Down Expand Up @@ -104,9 +104,19 @@ This still requires the online loader, manifest, and release asset. SHA-256 chec

### Windows rejects the password

`InvalidPassword` or `net user` error `2245` indicates that Windows rejected the password. Use the generated password or a longer password with uppercase and lowercase letters, numbers, and symbols, without the username. Generated passwords cannot guarantee compliance with every policy. Ask your administrator about the effective minimum length, complexity, history, and other restrictions rather than disabling policy.
`InvalidPassword` or `net user` error `2245` indicates that Windows rejected the scan-account password.

When account setup fails, hiding the account, folder-permission setup, and SMB share setup are skipped. **Copy Password** remains disabled so an unapplied password is not presented as usable. Independent steps can still run.
With the password-retry dialog, setup pauses before running any remaining steps:

1. Enter a replacement password, or choose **Generate** to create another one. **Retry** is disabled while the field is empty or contains only whitespace.
2. Choose **Retry** to attempt account setup again. Your username, folder, share name, and selected setup steps are preserved. If Windows rejects another password, edit or generate one and retry again.
3. After Windows accepts the password, setup resumes with the remaining selected steps, including account hiding, folder permissions, and SMB share configuration. **Copy Password** becomes available on completion when account creation/update is selected and succeeds; it copies the accepted replacement, not the rejected password.

Choose **Cancel setup** or close the password dialog to stop all remaining setup steps. The progress window reports **Canceled**, **Copy Password** stays disabled, and **Done** closes the window. Cancellation does not roll back changes from previous setup runs.

Use a longer password with uppercase and lowercase letters, numbers, and symbols, without the username. Generated passwords cannot guarantee compliance with every policy. Ask your administrator about the effective minimum length, complexity, history, and other restrictions rather than disabling policy.

**Release availability:** the retry dialog requires a release containing the password-retry change. Merging utility code does not update the downloaded stable release. Older versions instead show a password-error popup, skip account-dependent steps, and may continue independent steps with **Copy Password** disabled. In those versions, finish the run and rerun setup with a replacement password, or use a newer published release that includes the dialog.

### Setup finishes with errors

Expand Down
Loading