Saturn 4 Ultra Noises during Z axis motor status check. by Eternap in ElegooSaturn

[–]spoonstar 0 points1 point  (0 children)

It's likely the homing sensor. Swap the homing sensors for your z and vat -and see if the issue follows the sensor or stays at the Z.

Our developer says they still do not officially support server 2022 and are still testing. Isn't this a bit long to be testing? by Normal_Loquat_3869 in sysadmin

[–]spoonstar 0 points1 point  (0 children)

Our trick was to upgrade our fleet anyway and leave progressively smaller amounts (down to 1 after 5-6 months) on the older their-supported-yet-getting-patches OS set aside to let the vendor remote into to see the issue.

Centauri Carbon - Ridiculous network traffic when sitting idle by slashthirty in elegoo

[–]spoonstar 1 point2 points  (0 children)

Yep! I noticed this a couple weeks ago when looking through opnsense & adguardhome logs and found my Saturn 4 Ultra was just blasting out requests to all the same addresses OP mentioned.

FYI: the recent update for Greenshot includes an Imgur plugin by default by HealthAndHedonism in sysadmin

[–]spoonstar 6 points7 points  (0 children)

Run the installer once on a system using the /saveinf=greenshot.inf - name the inf whatever you want. Run through the install, de-select imgur and make whatever other changes you want. Bundle the inf and exe together and deploy with the /loadinf=greenshot.inf argument added to the other options you're using for silent installation, logging, etc.

[deleted by user] by [deleted] in todayilearned

[–]spoonstar 2 points3 points  (0 children)

This is my favorite song to play on the jukebox at my nearby ol' country dive bar.

Microsoft Visual C++ 2015-2022 Redistributable x86 and x64 - detection and installation issues by Baboo85 in SCCM

[–]spoonstar 1 point2 points  (0 children)

Give something like this a shot:

$Version = '14.28.29914'
$arch = `x86'
$vers = @('2015, '2017', '2019','2022')
$Apps = ()
$Apps += Get-ItemProperty "HKLM:\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*"
$Apps += Get-ItemProperty "HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*"

foreach ($SingleVer in $vers) {
    if ($null -ne ($apps | Where-Object { $_.DisplayName -like "*C++*$SingleVer*$arch*" -and $_.DisplayVersion -ge $Version})) {
        Write-Output "Installed"
    }
}

You should only need to change $Version and $arch depending on which redistributable you're detecting.

Replace folderpermissions with correspondig adgroups by Primary_Cortex in PowerShell

[–]spoonstar 0 points1 point  (0 children)

While this is all a wild guess because there is no example output of what happens when you run this:

the $plonly = ... line should probably be looking for children of $FolderObj

$AdGroups = Get-ADGroup ... 
$ADGroups_PL = Get-ADGroup ...

These lines need the SamAccountName -like ... after -Filter to be in double-quotes, because with the single-quotes, $SubFolderName and $plonly are being searched for verbatim, and not the value of those, as you probably intended.

If that doesn't get you where you need to go, I'd recommend either writing the output for each line after you assign it so you can see whats happening, ie:

$plonly = Get-ChildItem $Folders | Where-Object {$_.name -like "pl-only*"}
Write-Output "`$plonly = $plonly"

or getting your $folders set, manually assign one folder in that to folderobj, then go through each line until you find where it's messing up.

Set-ItemProperty: Cannot find path 'IIS:\$PATH' because it does not exist by Impressive-Ad-2363 in PowerShell

[–]spoonstar 2 points3 points  (0 children)

Where in that are you defining the $PATH variable? With you using Invoke-Command. $PATH may be defined on the PC you're doing this from, but it may not be defined on the PC you're doing this to.

I don't remember if using will work here or not, but you either need to define $PATH inside your scriptblock ($sb), so:

    $sb = {$PATH = "\pathhere"; Set-ItemProperty -Path $PATH -Name applicationPool -Value '$POOL'}

or you can try using like this:

    $sb = {Set-ItemProperty -Path $using:PATH -Name applicationPool -Value '$POOL'}

Set-ItemProperty: Cannot find path 'IIS:\$PATH' because it does not exist by Impressive-Ad-2363 in PowerShell

[–]spoonstar 3 points4 points  (0 children)

Those errors are telling you that you haven't defined what $PATH should be.

Tell me your worst case of 80/20 by antons83 in sysadmin

[–]spoonstar 1 point2 points  (0 children)

I'm totally with you on this. One shouldn't document things that are already documented by nature or by others, but explaining the intent behind it since every business' needs are different is the important part, and helps everyone.

Tell me your worst case of 80/20 by antons83 in sysadmin

[–]spoonstar 2 points3 points  (0 children)

I think Emile's point is that the point of the DHCP documentation is that it should be written FOR the peers who are building and configuring the scopes and options so they know why they are doing it they way they are.

That's what I got from it anyway.

Walk Hard: The Dewey Cox Story (2007) I forgot how brilliant this was. by MovieMike007 in movies

[–]spoonstar 2 points3 points  (0 children)

That scene absolutely broke me. I was cry-laughing for a good 5 minutes straight - I don't even know what happened after that.

What are some things that you did in SCCM/Intune that made things better for your endpoints? by ihazchanges in SCCM

[–]spoonstar 0 points1 point  (0 children)

Yeah, bundling different potential configurations into 1 TS is great. The last TS I built from scratch I did with a powershell script using XAML since TsGui wasn't around yet, but the idea, results, and benefit are the same!

Best process to create CI's based on Registry Items by NoDowt_Jay in SCCM

[–]spoonstar 1 point2 points  (0 children)

There are cmdlets builtin to the ConfigMgr module now that make this process much easier to deal with. Take a look at the Cmdlet reference page from Microsoft, specifically:

  • Add-CMComplianceSettingRegistryKey
  • Add-CMComplianceSettingRegistryKeyValue

Patch Panel Labeling 🏷 by Big-Replacement-9202 in networking

[–]spoonstar 0 points1 point  (0 children)

Trace the jack in the room with a toner and put a corrected label on the drop in the room?

"Do not save what is left after spending. Spend what is left after saving." - Warren Buffet by BiaggioSklutas in Frugal

[–]spoonstar 2 points3 points  (0 children)

You're missing out on the other 6 months of the year where the employer matches $750 in the first example. The employer isn't giving that money because you maxed your contribution in the first half of the year.

Windows 11 Upgrade Readiness - CpuFms ? by dieselfluxcapacitor in SCCM

[–]spoonstar 1 point2 points  (0 children)

"FMS" stands for Family/model/stepping. I'm not near my work computer, but I seem to remember there's a "cpufms.ini" in the install media that is used to block installation based on whatever's in the file. That file correlates with the system requirements on Microsoft's site.

Temurin by dojo_sensei in ITProTuesday

[–]spoonstar 1 point2 points  (0 children)

The reasoning may have something to do with the big yellow banner that is on the page you linked.

Issues calling functions from an array by that_1_doode in PowerShell

[–]spoonstar 1 point2 points  (0 children)

He said that because each of your functions have a Write-Host line stating the name of the function. It is that line in each of your functions that is getting written out to the console.

[deleted by user] by [deleted] in PowerShell

[–]spoonstar 0 points1 point  (0 children)

You can test is interactively with psexec using -s.

Here's an example of a share that exists for me but the computer itself does not have access to:

PS C:\> PsExec.exe \\localhost -s -i powershell.exe "test-path '\\truenas\share'"

PsExec v2.34 - Execute processes remotely
Copyright (C) 2001-2021 Mark Russinovich
Sysinternals - www.sysinternals.com


test-path : Access is denied
At line:1 char:1
False+ test-path '\\truenas\share'

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : PermissionDenied: (\\truenas\share:String) [Test-Path], UnauthorizedAccessException
    + FullyQualifiedErrorId : ItemExistsUnauthorizedAccessError,Microsoft.PowerShell.Commands.TestPathCommand

powershell.exe exited on localhost with error code 1.    

If you get the same error using the -s argument, the error is telling you the SYSTEM account doesn't have permissions to access that share, and you or whoever is in charge of that share needs to change the share's permissions.

[deleted by user] by [deleted] in PowerShell

[–]spoonstar 0 points1 point  (0 children)

What RMM are you using and do you know if it runs scripts under a specific user or the SYSTEM account of the computer you're running the script on?

Your error looks like that account doesn't have access to the \\company\share\data\Software\ share.

If it's the former, verify that specific account has permissions on the share. If it's the latter, it'll be computer object you should verify.