dsccommunity / dsccommunity/SharePointDsc

Visio Graphics Service Application

Open
#1,435 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
246
Forks
106
PR merge metrics
No merged PRs in 30d

Description

Problem description

I am running SharePoint Subscription on 4 Windows Server 2022 Standard.
Setting up both Visio Graphics Service Application and Secure Store Application works fine.
But how do I set Visio Graphics Service Application with unattended account and register it in Secure Store?

Ps
Somewhat new to DSC, bare with me.
Ds

Verbose logs
From Health Analyzer:
The Unattended Service Account is a single account that all documents can use to refresh data. It is required when connecting to data sources external to SharePoint, such as SQL. Without a valid Unattended Service Account Application ID, Visio Graphics Services will not be able to refresh Web Drawings that are connected to external data sources.
The rule for the Unattended Service Account Application ID failed. The ID does not exist. Visio Graphics Service Application
DSC configuration
SPVisioServiceApp 'VisioServices' {
                    PsDscRunAsCredential = $SetupCredential
                    Name = 'Visio Graphics Service Application'
                    ApplicationPool = 'VisioServiceAppPool'
                    Ensure = 'Present'
                    DependsOn = @('[SPMinRoleCompliance]MinRoleCompliance')
                }

                SPServiceAppPool 'VisioGraphicServiceAppPool' {
                    PsDscRunAsCredential = $SetupCredential
                    Name = 'VisioServiceAppPool'
                    ServiceAccount = $SpWebAppCredential.UserName
                    Ensure = 'Present'
                    DependsOn = @('[SPMinRoleCompliance]MinRoleCompliance')
                }

                SPSecureStoreServiceApp 'SecureStoreServiceApp' {
                    PsDscRunAsCredential = $SetupCredential
                    Name = 'SecureStore Service Application'
                    ApplicationPool = 'SecureStoreServiceAppPool'
                    AuditingEnabled = $true
                    AuditlogMaxSize = 30
                    DatabaseName = '_SecureStore'
                    DatabaseServer = $DatabaseServer
                    Ensure = 'Present'
                    DependsOn = @('[SPMinRoleCompliance]MinRoleCompliance')
                }

                SPServiceAppPool 'SecureStoreServiceAppPool' {
                    PsDscRunAsCredential = $SetupCredential
                    Name = 'SecureStoreServiceAppPool'
                    ServiceAccount = $SpWebAppCredential.UserName
                    Ensure = 'Present'
                    DependsOn = @('[SPMinRoleCompliance]MinRoleCompliance')
                }
Suggested solution

Not really at this point

SharePoint version and build
SharePoint Subscription build 16.0.1436.20450
Operating system the target node is running
WS 2022 Standard
PowerShell version and build the target node is running
PwSh 5.1
SharePointDsc version
SharePointDsc 5.4.0

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the SPVisioServiceApp and SPSecureStoreServiceApp resources and the supplied DSC configuration. Trace how the Visio unattended service account and Secure Store application ID are represented, then verify the result against the Health Analyzer requirement. Done means the ID exists and Visio can refresh externally connected web drawings.

Written by the indexing model from the issue text.

Assessment

Tech stack
powershell
Domain
infrastructure
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.