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.

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

Script Problem #33

Open
rsenio opened this issue Dec 8, 2016 · 2 comments
Open

Script Problem #33

rsenio opened this issue Dec 8, 2016 · 2 comments

Comments

@rsenio
Copy link

rsenio commented Dec 8, 2016

Using the script zenoss-lpu.ps1 to assign my domain user permissions to my servers for WinRM collection must be missing a permission. When modelling my servers I am missing some items from collection, what I've seen missing is Windows services. Sometimes as little as one service missing, or 3+. Adding the domain user to the local admin group of one of these servers and remodelling fixes the handful of missing service. But that negates why I'm using this script in the first place.

@rsenio rsenio changed the title Peremissions Permissions Dec 8, 2016
@rsenio
Copy link
Author

rsenio commented Dec 8, 2016

Persuing this further, I see near the bottom of the powershell script is the query for services

get-wmiobject -query "Select * from Win32_Service"

If I run that as administrator AND my zenoss winrm user I get the same number of results.

If I run sc sdshow on a service that doesn't show up, I can see that the permissions are missing for my winRM account. Where as if I run that same command on a service that does show up, the winRM account SID is listed there.

If I reboot the server and once logged in review the event log (application) I can see the changes made by the powershell script for services. For example:

Service MSSQLServerOLAPService already contains permission for user [email protected]

The ones that are missing, for exmaple, say:

User: [email protected] was not added to service SolidWorks SolidNetWork License Manager.
Reason: The parameter is incorrect.

From what I gather here is the script isn't working when the registry key has a space in the name

HKLM\SYSTEM\CurrentControlSet\Services

Keyname in this example is "SolidWorks SolidNetwork License Manager"

@rsenio rsenio changed the title Permissions Script Problem Dec 12, 2016
@joshchi31
Copy link

I have the same issue. If there is a space in the service name, the permissions do not get applied to that service.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants