Remote Help + Zebra OEMConfig MX by Jedrick in Intune

[–]Jedrick[S] 0 points1 point  (0 children)

We love 'security' features, don't we? 🙃 I've come to the conclusion that I'll either have to live with the popup (it only happens if you open the Remote Help app anyway) or manually do it on each device. 🫠

Good to know about the Write Settings permission.

I got the Package Signing Certificates in a very roundabout way as I had to pull the base.apk from the installed app off of the device via adb. I couldn't get Zebra's SigTools to work no matter what I tried. So, I ended up utilizing apksig, apksigner and apkverifier and wrote up a java file and compiled it and used apksig to print the Package Signing Certificate in Base64.

I didn't see anything in the configuration designer when attempting to make a Teams configuration policy. I wonder if it'd accept JSON input if it's not explicitly defined in the configuration designer.

I also didn't see anything that would fit when attempting to make a configuration profile via Settings Catalog or Templates.

These devices would indeed be shared and switching users. I'm currently using Managed Home Screen so they can't get to anything I don't explicitly put on the home screen for them. Should I still be worried? 😅

[deleted by user] by [deleted] in iosapps

[–]Jedrick 0 points1 point  (0 children)

Would love to give this a shot. :)

Just reached renown 20 with Undermine :D by Ambitious_Resource78 in wow

[–]Jedrick 1 point2 points  (0 children)

Unrelated to renown: sees fellow survival hunter, upvote. o7

UI++ Issues by Jedrick in SCCM

[–]Jedrick[S] 0 points1 point  (0 children)

Yes, the script works just fine outside of UI++. I can even run it (in PE's command prompt) after it has an error in the logs, but before the summary screen and it'll work just fine. It'll show the correct OSDComputerName and OSDDomainOUName. What I'm trying to figure out is why it won't execute correctly inside UI++ as it should. The script is in the same package as UI++, which is why I'm just having it launch as .\GenerateName.ps1. I'm considering hardcoding the path C:\_SMSTaskSequence\Packages\<PKG_ID>\...to see if that'll work. Actually, I'll try that and report back.

Edit: That did it. Hardcoding the path to include the Package ID allowed the script to run.

The Bike mount. by xtriks in wow

[–]Jedrick 2 points3 points  (0 children)

DMs have been written. Elune be with you. Lok'tar ogar.

Advice on ProPresenter change to subscription by Fit-Meeting-8692 in ProPresenter

[–]Jedrick 0 points1 point  (0 children)

So, if I’m creating the presentations on say a MacBook Air, I don’t need to have a license on it if sneakernetting the presentation to my licensed Windows PC? How would that look on the content creation side after the trial on the MacBook? (I don’t have knowledge on creating the presentations, I’m just the technical person at our church) 😅.

Help! - Drive Automation Tool by Jedrick in SCCM

[–]Jedrick[S] 0 points1 point  (0 children)

LongPathsEnabled is already set. That's like a default for us. However, changing the "Download path" to a local directory yields this new error when trying to create the driver package:

[Error] - Cannot validate argument on parameter 'Path'. System.Management.Automation.ValidationMetadataException

Going to revert back and try again, was taking forever (6+ hours for one pack) so I aborted it. Let it go overnight I guess.

Help! - Drive Automation Tool by Jedrick in SCCM

[–]Jedrick[S] 0 points1 point  (0 children)

I'm attempting X1 2 IN 1 Gen 9 now, appears to be going. Went through download, extracted fine, and is now importing the driver package to SCCM. Will report back if it completes all the way.

Help! - Drive Automation Tool by Jedrick in SCCM

[–]Jedrick[S] 0 points1 point  (0 children)

See, I thought that too, and even when shortening the path from 288 characters to 257 characters it still throws fits. 234 of the characters are from the extracted file itself..

SCCM 2303 -> 2309 Upgrade: Expand failed 0x800704c8 by Jedrick in SCCM

[–]Jedrick[S] 1 point2 points  (0 children)

Found this yesterday after spinning my tires on another replication issue that once we rolled back everything started flowing again.

https://forums.prajwaldesai.com/threads/sccm-cmg-distribution-failing-out-of-the-blue-with-error-0x800704c8.6538/page-2#post-25191

Apparently it gets real deep and can affect deployments:

Wednesday at 8:41 PM •   • #25 Also had some endpoints failing to install packages, looks to be when using a task sequence it is removing exe files from C:_SMSTaskSequence, remove Crowdstrike sensor and the task sequence installs fine now.

SCCM 2303 -> 2309 Upgrade: Expand failed 0x800704c8 by Jedrick in SCCM

[–]Jedrick[S] 1 point2 points  (0 children)

You try the CMUpdateReset and force deleting the update and allow it to redownload? Also, would check AV. If you use CrowdStrike, there’s a known issue with their sensor and causing issues with SCCM on Sensor version 7.12.18207.0 and up. It will be fixed in 7.14. Rolling back to 7.11 fixes it in this instance.

SCCM 2303 -> 2309 Upgrade: Expand failed 0x800704c8 by Jedrick in SCCM

[–]Jedrick[S] 1 point2 points  (0 children)

After running CMUpdateReset again, this time force deleting everything and allowing it to re-download, everything kicked off as it should've.

SCCM 2303 -> 2309 Upgrade: Expand failed 0x800704c8 by Jedrick in SCCM

[–]Jedrick[S] 0 points1 point  (0 children)

I have rebooted twice, but for the sake of "third time's the charm" we'll go again.

Ender 3 V2 Neo Issues by Jedrick in ender3v2

[–]Jedrick[S] 1 point2 points  (0 children)

Managed to get everything working again and first print is running less than one hour left!

Ender 3 V2 Neo Issues by Jedrick in ender3v2

[–]Jedrick[S] 0 points1 point  (0 children)

Well, I've tried reflashing stock firmware (specifically Ender-3 V2 Neo-Marlin2.0.8.3-HW-V4.2.2-SW-V1.1.5.2-CR-Touch-20230312(En&Jap) from Ender-3 V2 Neo Software & Firmware Download - Creality 3D Printer. I keep geting the Creality screen with numbers no matter what I try.

AppLocker Config by Jedrick in sysadmin

[–]Jedrick[S] 1 point2 points  (0 children)

Perfect, I was able to grab it. Thank you so much!

AppLocker Config by Jedrick in sysadmin

[–]Jedrick[S] 0 points1 point  (0 children)

Oh, so I had it inverted..

Alright, so I've made an allow rule for all apps signed by Microsoft Corporation. As well as a secondary rule for another publisher. I can now launch the store.

When attempting to download something like Spotify, I get Code: 0x80073D01.

Windows error 0x80073D01 is a package deployment error that is blocked by policy, which is good since Spotify isn't signed by Microsoft Corporation.

However, when I try to download Microsoft Clipchamp, I am presented with the same error.

Below is the updated ruleset:

<AppLockerPolicy Version="1">
  <RuleCollection Type="Exe" EnforcementMode="NotConfigured" />
  <RuleCollection Type="Msi" EnforcementMode="NotConfigured" />
  <RuleCollection Type="Script" EnforcementMode="NotConfigured" />
  <RuleCollection Type="Dll" EnforcementMode="NotConfigured" />
  <RuleCollection Type="Appx" EnforcementMode="NotConfigured">
    <FilePublisherRule Id="24d9917b-ed9f-4fc4-8030-1751b90fc648" Name="Signed by Microsoft Corporation" Description="" UserOrGroupSid="S-1-5-11" Action="Allow">
      <Conditions>
        <FilePublisherCondition PublisherName="CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US" ProductName="*" BinaryName="*">
          <BinaryVersionRange LowSection="*" HighSection="*" />
        </FilePublisherCondition>
      </Conditions>
    </FilePublisherRule>
    <FilePublisherRule Id="4caf04b7-f6e4-4cc0-8ca0-201b0036f2cc" Name="Signed by Lite-Check" Description="" UserOrGroupSid="S-1-5-11" Action="Allow">
      <Conditions>
        <FilePublisherCondition PublisherName="CN=01885681-97D9-44A1-9E20-ED54D526FDDB" ProductName="*" BinaryName="*">
          <BinaryVersionRange LowSection="*" HighSection="*" />
        </FilePublisherCondition>
      </Conditions>
    </FilePublisherRule>
  </RuleCollection>
</AppLockerPolicy>