> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/manage/wsus-updates-tab/wsus-options/standalone-wsus-mode.md).
# Standalone WSUS Mode section of Patch My PC Publisher
*Applies to: Patch My PC Publisher V3.x*
The **STANDALONE WSUS MODE** section on the **WSUS Options** tab of Patch My PC (PMPC) Publisher configures Standalone WSUS Mode when Publisher integrates directly with WSUS without Microsoft Configuration Manager (ConfigMgr).
This mode is intended only for environments that manage updates using WSUS standalone. It is not required and should not be enabled when ConfigMgr manages software updates.
## Make updates appear in the WSUS console. This option isn’t needed if using Configuration Manager
When you enable the **Make updates appear in the WSUS console. This option isn’t needed if using Configuration Manager** option (which isn't enabled by default) it enables Standalone WSUS Mode, which controls whether locally published third party updates are visible in the WSUS console.
When Standalone WSUS Mode is enabled, Publisher marks updates as locally published so they appear in the WSUS console and can be viewed and managed directly in WSUS.
{% hint style="danger" %}
**Important**
If ConfigMgr is present and managing software updates, you should not check this checkbox.
{% endhint %}
## Use SYSTEM account when connecting to the SQL database or define a custom account below
Enabling the **Use SYSTEM account when connecting to the SQL database or define a custom account below** option controls how Publisher connects to the WSUS SQL database when Standalone WSUS Mode.
{% hint style="success" %}
**Tip**
If your WSUS database uses the Windows Internal Database (WID), the database connection options are read-only. In this scenario, you don't need or use SQL credentials.
{% endhint %}
If enabled, Publisher connects to the WSUS database using the local SYSTEM account of the machine where Publisher is installed. This is the recommended and default option for most WSUS standalone deployments, as the SYSTEM account typically already has the required permissions to access the WSUS database.
If you don't enable this option, you can specify a custom SQL login instead by entering the credentials in the **SQL Login** and **SQL Password** fields. This may be required in environments where WSUS uses a remote SQL Server or where security policies restrict SYSTEM account access. In that case, the specified SQL account must have sufficient permissions to read and update the WSUS database.
{% hint style="info" %}
**Note**
For updates published before WSUS Standalone mode was enabled, use the [Modify Published Updates](/patch-my-pc-publisher/manage/wsus-updates-tab/wsus-options/modify-published-updates.md) wizard to make those updates appear in the WSUS console using the **Show in WSUS** option.
{% endhint %}
## SQL Permissions Required
When Publisher syncs run, if the SUSDB is remote from the Standalone WSUS server, you must grant specific permissions to the computer account where Publisher is installed so that it can update information.
Use the script below to grant the required permissions, replacing the computer account values with those appropriate to your environment.
Edit the script as needed, then run it as a SQL query in SQL Server Management Studio.
```sql
USE SUSDB
GO
-- Replace CONTOSO\ServerName$ with the appropriate value for your environment
DECLARE @UserName nvarchar(128) = 'CONTOSO\ServerName$'
DECLARE @QuotedUserToGrant nvarchar(128) = QUOTENAME(@UserName);
IF NOT EXISTS(SELECT principal_id FROM sys.server_principals WHERE name = @UserName) BEGIN
DECLARE @LoginSQL as varchar(500);
SET @LoginSQL = 'CREATE LOGIN '+ @QuotedUserToGrant + ' FROM WINDOWS';
EXEC (@LoginSQL);
END
IF NOT EXISTS(SELECT principal_id FROM sys.database_principals WHERE name = @UserName) BEGIN
DECLARE @UserSQL as varchar(500);
SET @UserSQL = 'CREATE USER ' + @QuotedUserToGrant + ' FOR LOGIN ' + @QuotedUserToGrant;
EXEC (@UserSQL);
END
DECLARE @PermissionsSQL as varchar(500);
SET @PermissionsSQL = 'GRANT UPDATE ON [dbo].[tbUpdate] ([IsLocallyPublished]) TO ' + @QuotedUserToGrant +
'GRANT SELECT ON [dbo].[tbUpdate] ([UpdateID]) TO ' + @QuotedUserToGrant;
EXEC (@PermissionsSQL);
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.patchmypc.com/patch-my-pc-publisher/manage/wsus-updates-tab/wsus-options/standalone-wsus-mode.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
