Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

User Rights Assignment throwing secedit.exe error #116

Open
billyhigdon opened this issue Mar 22, 2019 · 3 comments · May be fixed by #176
Open

User Rights Assignment throwing secedit.exe error #116

billyhigdon opened this issue Mar 22, 2019 · 3 comments · May be fixed by #176
Labels
discussion The issue is a discussion. needs more information The issue needs more information from the author or the community.

Comments

@billyhigdon
Copy link

Having an issue when trying to set the following with UserRightsAssignement...

    UserRightsAssignment LockPagesInMemory 
    {
            Policy = "Lock_pages_in_memory"
            Identity = "sqlservice"
    }

errors out with the following:

The term 'secedit.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
+ CategoryInfo : ObjectNotFound: (secedit.exe:) [], CimException
+ FullyQualifiedErrorId : CommandNotFoundException
+ PSComputerName : pc-new

Cannot find path 'C:\Windows\TEMP\SecurityPolicy.inf' because it does not exist.
+ CategoryInfo : ObjectNotFound: (C:\Windows\TEMP\SecurityPolicy.inf:) [], CimException
+ FullyQualifiedErrorId : PathNotFound
+ PSComputerName : pc-new

I'm on the latest build - 2.7.0.0
@gaelcolas
Copy link
Member

Can you give more information about your OS?
SecEdit should be built-in Windows.

As an Administrator account, can you try this in a shell:

C:\ PS> where.exe secedit.exe

It should return:

# C:\Windows\System32\SecEdit.exe

@gaelcolas gaelcolas added discussion The issue is a discussion. needs more information The issue needs more information from the author or the community. labels Mar 27, 2019
@SteveL-MSFT SteveL-MSFT added this to Discussion in powershell/dscresources May 14, 2019
@dtrac
Copy link

dtrac commented Jun 21, 2019

Hi Guys - I've also experienced this issue on a number (approx 1 in 3) of identical builds - Windows 2016 1607 Build 14393.2248.

I'm seeing it with the SecurityOption resource. Output:

https://gist.github.com/dtrac/5a02e0348936aab9d036e4fbc4ce71ee

Running PowerShell interactively, I can execute secedit.exe successfully, and a 'where.exe' shows it in the correct location (C:\Windows\System32).

System PATH variable has C:\Windows\system32 correctly defined.

@SteveL-MSFT SteveL-MSFT removed this from Discussion in powershell/dscresources Nov 27, 2019
@39Delta
Copy link

39Delta commented Dec 25, 2021

We are seeing this issue periodically with new Windows Server installs and the publication of DSC configurations containing the UserRightsAssignment settings. Even after joining the domain the system reports errors about the secedit.exe command not being found. Running Get-Command secedit.exe accurately locates the program but for some reason the environment paths for the system account, running the resource, fails to locate the secedit command. I am working on a possible solution for review and will be opening a PR soon.

@39Delta 39Delta linked a pull request Dec 26, 2021 that will close this issue
Open
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion The issue is a discussion. needs more information The issue needs more information from the author or the community.
Projects
None yet
Milestone
No milestone
4 participants
@gaelcolas @39Delta @billyhigdon @dtrac