u/Individual_Lock7531

Just startet. Bought a set from ricardo (like e bay) for a low price. Last weekend first evening on a track. Bought another one for racing because my previously bought were more for drift. The WLToys Crap is more for fun 😂

Remote i got myself a MT12. Because i also have 2 1/10 drifter (currently under repair consteuction. One will be transfered on a Sakura D6 Chassis) and want anything on one remote with as wide as possible compatibility for RX because i bought like anything second hand haha. Also i like Radiomaster cause i also have a TX16S for my FPV drones and got to use with it 😂

Over the past few weeks, I've been working with Intune as part of an internal proof of concept. Since analyzing data on a single device can be quite tedious (gathering log files on the remote device, analyzing keys remotely via the registry, etc.), I wrote small resetters and log collection tools for my own devices. However, since I now need to perform certain analyses on other devices as well, I created a tool to simplify the work involved with Intune, specifically the analysis. I thought it might be interesting for other administrators too, so I created a Git repository.

As a disclaimer: I'm not a programmer, so I programmed the tool using Vibe coding.

Due to certain security measures, it is necessary to sign the content. This is particularly true for the "TrustedConfigs," where the allowedSource and allowedDestination addresses can also be stored. Trust is validated by comparing the executable's certificate with the catalog's certificate (which includes the path to the trustedconfig.json file). Additionally, the fingerprint of the TrustedConfig.json file is compared with the catalog's certificate. Therefore, after modifying the TrustedConfig.json file, the catalog must be recreated and re-signed. If the trust is not established, the tool can only be used in simulation mode.

i would be interested in feedback or anything else for this one, so feel free to commit

Installation/Build can be performed as follows:

1. Repository klonen

2. .\Scripts\custompacker_git.ps1 (edit paths if needed!)

3. make sure you have a valid code signing certificate imported

4. run custompacker_git.ps1

   a) it will sign all ps1 and exe

   b) it will build the project

   c) it will sign the new exe

   d) it will add a catalog for the trustedconfig.json to be valid

   e) if .\Assets\file.ico is available, it will be set as program icon

5. if you have to change trustedconfig.json after you built the project, use retrustconfig.ps1 or just build it newly. otherwise the trust cant be verificated and the program will only run in simulation mode

NSASchweiz/IntuneSupportSuite: IntuneSupportSuite

i hope this post wont be seen as advertising. Just wanted to share my work, because i thought it could be useful for others.

Hi Folks

Recently i blown my Gear Diff. So i got a new one. As it seems an official MST Replacement LSD Gear Diff. The old Pinion looked like it was Pressed on to the Ball Shaft from the Drive Shaft. Had to burn it out. The new one i cant press on idk

The Problem i have now is, that the new Pinion sits a bit different and the ball Shaft is pressed out like 2-3mm. Because of that, i cant fit the drive shaft as tight as before and i am not able to fit the holder of the drive shaft in place.

Someone experienced the same Problem? What was your solution?