--- name: visio-2016-fudan-kms description: >- Diagnose and resolve Microsoft Visio Professional 2016 installation and KMS activation on Windows with Microsoft 365 already installed, without removing Microsoft 365. Use for Visio 2016 MSI vs Click-to-Run conflicts, Office Deployment Tool (ODT) installation, Fudan University KMS activation, school activation-client incompatibility messages, ospp.vbs outputs, or legacy Office 365 Grace/NOTIFICATIONS license entries. --- # Visio 2016 + Microsoft 365 / Fudan KMS: Agent Skill ## Mission On a **Windows** PC, preserve a working **Microsoft 365** installation while diagnosing, installing (if necessary), and validating the **licensed Visio Professional 2016** volume-license Click-to-Run product, activated through Fudan University's authorized KMS at `kms.fudan.edu.cn`. Prefer **read-only checks and minimal intervention**. If Visio and Microsoft 365 are already activated, report success and stop. **Do not** modify Windows activation or clear Microsoft 365 licenses. ## Recorded known-good case (2026-10-30) - Windows 11 Home was already permanently activated independently. - Word → File → Account showed a working Microsoft 365 personal subscription; no KMS activation required. - An MSI Visio 2016 setup reported a conflict with existing Click-to-Run Microsoft 365 (`zh-cn`, `en-us`). - Microsoft ODT `setup.exe /configure configuration.xml` successfully installed Visio 2016 as `VisioProXVolume` with the public KMS GVLK. - Visio → File → Account: **Product Activated — Microsoft Visio Professional 2016**. - `ospp.vbs /act` produced `` for `Office16VisioProXC2RVL_KMS_ClientC2R`. - `ospp.vbs /dstatus` showed `VOLUME_KMSCLIENT`, `---LICENSED---`, `REMAINING GRACE: 180 days`, KMS override `kms.fudan.edu.cn:1688`. - The school's activation GUI client v5.0 said the product was unsupported; **manual KMS activation worked**. - A separate `Office16O365HomePremR_Grace` entry remained `NOTIFICATIONS` with `0xC004F009` and generated `0xC004F017` on `/act`; Word's real subscription was active. **Do not repair that legacy entry by default**. - Visio account screen showed a recent Click-to-Run build (2610), despite 2016 as the product's license edition. Do not confuse the shared application binary version with the Visio product license edition. ## Scope and safety boundaries 1. Only target machines/users authorized for a corresponding Visio 2016 volume license and school/organization KMS. Do not use third-party public KMS endpoints, crack tools, license bypasses, or non-official downloads. 2. The public Microsoft GVLK `69WXN-MBYV6-22PQG-3WGHK-RM6XC` is **not a standalone activation key**; it works only with valid authorized KMS infrastructure. 3. **No destructive repairs by default**: no `ospp.vbs /unpkey`, no license-cache purge, no registry hacks, no uninstall of Microsoft 365, no `RemoveMSI`, no Windows `slmgr` operations, no modifications to an active subscription. 4. Before initiating any installation, confirm product entitlement, check what is already installed, and explain impact. Before making changes, ask for confirmation as appropriate to the agent's execution authority. Prefer commands that show state over commands that mutate it. 5. Use administrator elevation only where necessary and with user authorization. Never claim an operation succeeded without inspecting output. 6. Existing successful activation is the stopping condition. Do not retry setup or activation just because a GUI tool shows an unsupported-product warning. ## Decision workflow ### Stage A — Identify shell, product, and current health (first) - Establish Windows edition and whether the shell is **CMD** or **PowerShell**. - Inspect **Visio → File → Account** for `Microsoft Visio Professional 2016` and `Product Activated`. - Inspect **Word → File → Account** for the Microsoft 365 subscription/activated state. - If Visio is already activated and Word is healthy: **STOP** and summarize. No repair needed. - If Visio is installed but status is uncertain: run read-only `ospp.vbs /dstatus` first (Stage D). - If Visio is not installed or the MSI installer throws a Click-to-Run conflict: proceed to Stage B if the user has an appropriate volume license. ### Stage B — Install Visio through ODT only if needed **Reason:** MSI Visio 2016 cannot coexist in this scenario with Click-to-Run Microsoft 365. Microsoft documents ODT as the alternative installation method for volume-licensed Visio 2016. 1. Download the latest **Office Deployment Tool** from Microsoft: . 2. Place the downloaded ODT self-extracting `.exe` in `C:\ODT` and extract it. Replace the example executable name with the actual file name: ```bat cd /d C:\ODT officedeploymenttool_20430-20146.exe /extract:C:\ODT /quiet dir ``` **Critical distinction:** `officedeploymenttool_*.exe` is the **extractor**, not the deployment executable. `/configure` belongs to the extracted `setup.exe`. 3. Create **`C:\ODT\configuration.xml`** with only the Visio volume-license product: ```xml ``` Do **not** substitute the sample `configuration-Office365-x64.xml`: in the recorded case that sample contained both `O365ProPlusRetail` and `VisioProRetail`, which are not the intended installation targets. Do not silently force Office bitness/channel; ensure compatibility with the installed Microsoft 365 if specifying either. 4. Verify `setup.exe` and `configuration.xml`, close Office applications, then configure: ```bat cd /d C:\ODT dir type configuration.xml setup.exe /configure configuration.xml ``` The Office download/progress UI signifies the installer has started, **not** that installation succeeded. Wait for completion; avoid duplicate concurrent installers or repeated Ctrl+C. Validate by launching Visio, then Stage C/D. ### Stage C — Activate installed Visio against authorized school KMS Prerequisites: Visio installed; lawful school license; access to campus network or school-approved VPN; correct system time/timezone; close Office apps. In **CMD**, optionally check connectivity: ```bat ping kms.fudan.edu.cn powershell -Command "Test-NetConnection kms.fudan.edu.cn -Port 1688" ``` - `Test-NetConnection` is a **PowerShell** command; it does not run unwrapped in CMD. - ICMP `ping` may be blocked even when TCP 1688 works. Run in **elevated CMD** using the actual `Office16` location: ```bat cd /d "%ProgramFiles%\Microsoft Office\root\Office16" cscript ospp.vbs /sethst:kms.fudan.edu.cn cscript ospp.vbs /act cscript ospp.vbs /dstatus ``` If no `ospp.vbs` at that path, check: ```bat cd /d "%ProgramFiles(x86)%\Microsoft Office\root\Office16" ``` Only run `cscript` after successfully finding `ospp.vbs`. Do not assume the school's legacy `%PROGRAMFILES%\Microsoft Office\Office16` path applies to Click-to-Run. ### Stage D — Interpret activation by product (read-only) Use the corresponding section of `cscript ospp.vbs /dstatus`: ```text LICENSE NAME: ...Office16VisioProXC2RVL_KMS_ClientC2R... LICENSE DESCRIPTION: ...VOLUME_KMSCLIENT... LICENSE STATUS: ---LICENSED--- REMAINING GRACE: ...days ``` **Visio `LICENSED` + Visio GUI `Product Activated` = success.** KMS periods can run up to 180 days; reconnect to authorized network for renewal. If activation fails, collect full Visio-specific error code and actual license status before advising next steps. Other installed Office keys may appear in the same output. The recorded case had: ```text LICENSE NAME: ...Office16O365HomePremR_Grace... LICENSE STATUS: ---NOTIFICATIONS--- ERROR CODE: 0xC004F009 ``` `/act` also printed `0xC004F017` for the **old Microsoft 365 Grace entry**. This is **not evidence that Visio activation failed**, and is not a definitive check of modern Microsoft 365 subscription licensing. Check Word → File → Account; if activated and working, **leave the legacy entry untouched**. Investigate Microsoft 365 separately only if its own UI reports unlicensed/disabled functionality. ### Stage E — Explain school activation GUI mismatch The Fudan activation client v5.0 displayed (recorded verbatim): > 当前产品非本平台提供的软件版本，不能提供激活服务，本平台仅提供 Windows、Office 专业版激活服务！ Do **not** state that the actual KMS host rejected Visio. The observed KMS command-line path activated it successfully. The GUI could have product edition/version/source restrictions or incomplete product recognition; its internal rule is **unverified**. Report the distinction clearly. ## Troubleshooting matrix | Symptom | Diagnostic / next step | | --- | --- | | `ls` not recognized | CMD uses `dir`; PowerShell accepts `ls`. | | ODT `.exe /configure` opens usage help | Wrong binary. Extract ODT, use `setup.exe /configure configuration.xml`. | | `setup.exe` missing | Re-run authorized ODT extraction; verify contents with `dir`. | | Visio MSI conflicts with Microsoft 365 | Use ODT Click-to-Run volume-license method; don't uninstall the working Microsoft 365. | | `Test-NetConnection` not recognized | Running in CMD; use `powershell -Command ...` or switch to PowerShell. | | `ospp.vbs` not found | Check both `Program Files` and `Program Files (x86)` `root\Office16` locations. | | Fudan activation App refuses Visio | Use documented manual activation and verify Visio-specific license; do not assume KMS host failure. | | Visio `LICENSED`, old O365 Grace `NOTIFICATIONS` | Stop Visio troubleshooting. Check Microsoft 365 via Word account UI. No blind key removal. | | Visio not `LICENSED` | Check lawful volume entitlement, campus/VPN access, KMS TCP 1688, clock, license edition, full output; request exact error. | | Visio version shows 2610/current channel | Shared C2R app binary version; use product account/volume license status to identify edition. | ## Completion criteria Only report success after evidence of **(a)** installed Visio Professional 2016, **(b)** Visio-specific `---LICENSED---` or Visio GUI `Product Activated`, **(c)** preserved functional Microsoft 365 account activation. Include the observed state, not just that commands ran. Explicitly distinguish **school KMS service** from **school GUI activation client**. ## Sources and lifecycle - Fudan Information Office, “正版软件丨如何激活微软Windows和Office” (2026-05-07): — KMS server `kms.fudan.edu.cn`, 180-day activation, campus-network renewal and manual `ospp.vbs` activation. - Microsoft Learn, *Use the Office Deployment Tool to install volume licensed versions of Project 2016 and Visio 2016*: — the MSI/C2R conflict, ODT coexistence strategy, `VisioProXVolume` and its public GVLK. - Microsoft ODT download: . - **Lifecycle:** Visio 2016 reached end of support on 2025-10-14. Activation success does not imply ongoing Microsoft security fixes. Adapt new deployments to the institution's supported, currently licensed software where feasible.