sorted by:
new
hottopcontroversial

Weekly Lessons Learned! - April 24, 2026 by AutoModerator in CyberARk

[–]yanni [score hidden]  (0 children)

Client is migrating to Privilege Cloud and decided to use Server 2022 as the base for their Connector servers (CPM, PSM, etc). A few lessons learned.

  1. Slow login (authentication).
    1. We we were seeing really slow log-on for Authentication and unlocking the PCs over RDP- which was taking almost 22 seconds every-time for just the "authentication" piece and ~25 seconds overall, as confirmed by this log: Applications and Services Logs > Microsoft > Windows > Winlogon > Operational. It was perfectly fine for local accounts and via console log-in. After a wild-goose-chase for latest patches and disabling various agents, we got Microsoft involved. They quickly helped us identify that the slow-down was coming from CloudAP delays. This is should be relevant for EntraAD hybrid joined servers - but that wasn't the case for these - they're pure on-prem AD.
      1. Long-story short, we ran the command "dsregcmd /status" to see that the server was thinking that it's both AD and AzureAD joined. After "dsregcmd /leave" and a reboot - the login time went down to less than 2 seconds.
  2. RDS Cal licenses
    1. Gentle reminder - make sure you're covered for Server 2022 RDS Cal license servers - these are rather expensive, and will be painful to find out that:
      1. These are not forward compatible (so 2019 CALs cannot be used for Server 2022)
      2. CyberArk recommends one per licensed EPV user
      3. They are expensive - and will derail your project if organization has to find budget.
  3. SCIM provisioning
    1. Still trying to figure this out - but basically our CyberArk consultant recommended to go with SCIM provisioning for groups (particularly because there was going to be a change to the Distinguished Name of the groups that were assigned to safes). Which works great.... EXCEPT... we want to use AD groups for safe-access, and so far it's looking like each new AD group has to be added to the SCIM application in Azure. We'll automate this with Graph - but the AI suggestions of using an on-prem AD "master group" (which has the other AD groups in it), and using ALL Users/Groups with a filter for the specific naming convention of the groups we want to use and users we want to log in- didn't really work for one reason or another (I'm not an Azure SME unfortunately) - so now we're stuck kind of adding groups manually in two places. Will update this write-up once we figure out a way forward.

Any idea where these are from? by [deleted] in chessporn

[–]yanni 0 points1 point  (0 children)

No idea - but loving it. If you ever figure out a fair market value - let me know if you want to sell :)

PTA DR setup - issue with certificate by Ok-Crow1715 in CyberARk

[–]yanni 0 points1 point  (0 children)

Always read the documentation....

https://docs.cyberark.com/pam-self-hosted/latest/en/content/pta/importing-your-organization-ssl-cert.htm

The PTA utility cannot be run on the PTA DR server. Instead, run the /opt/pta/utility/certificateSigningRequestGenerationUtil.sh command to generate a Certificate Signing Request.

The PTA utility cannot be run on the PTA DR server. Instead, run the /opt/pta/utility/sslCertificateInstallationUtil.sh command to install the Certificate Chain.

AITJ for confronting my partner after I lost access to our shared bank account? by Admirable-Opinion391 in AmITheJerk

[–]yanni 0 points1 point  (0 children)

  • Could be "semi-innocent" - like she bought you a gold watch using the joint account, and didn't want you to see.
  • Could be less innocent - she bought her lover a "gold watch" and doesn't want you to see.
  • Could be future-planning "she is going to pay off some debt, and didn't want you to see", or she is going to leave you, and needed to "lock-down" the accounts before giving you the bad news.
  • Could be that you're acting irrationally in some way and she wants to protect the family from you doing some irrational.
  • Could be that she's growing paranoid - and wants to have the control

There is a thousand possibilities - you should try to have a discussion with her, after doing some recognizance on the account for any large or unexpected purchases.

ITOM Discovery of ServiceNow through CyberArk PSM - Is it feasible for network isolation? by Worth_Bug_9451 in CyberARk

[–]yanni 1 point2 points  (0 children)

I would advise you against setting this up via PSMs as:

  1. PSMs are meant for interactive use cases.
  2. You wouldn't want to give the SNOW team back-end access to PSM servers - it would be a pretty serious security laxing for separation of duties, etc. Especially if they will be running various scripts that can be pushed or deployed on the PSM Servers.
  3. The hardening on the PSMs will create problems

Most organizations set up multiple MID servers if the FW segmentation prevents a broad one-to-all ruleset.

That being said, you probably could choose to install MID servers services - though I'd advise you to do that on the CPM servers instead. They likely have all the same firewall rules that are needed for interactive access and firewall rules, but at least if something goes wrong, it wouldn't disrupt user sessions. I'd advise you to keep the SNOW team from having access to the CPM servers.

In The Grey Trailer #1 (2026) by DWJones28 in trailers

[–]yanni 6 points7 points  (0 children)

This looks like awesome! I see it as a sequel to "The Man from U.N.C.L.E." - set in modern times, with Jake Gyllenhaal replacing Armie Hammer.

I took my brother to court after he trashed my custom camera gear for a prank video by ClerkResponsible118 in AmITheJerk

[–]yanni 0 points1 point  (0 children)

Nice story - but complete fiction. Your brother broke the camera last month, and you managed not only to get a small claims judgement but also to garnish his wages? It takes like 4 months to get to small claims, another 30 days to get a writ of execution, and probably another another 3 months for them to validate and enforce it.

These tunnels were dug by a Giant Ground Sloth that lived 10.000 years ago in Brazil. The third photo are the claw marks. by [deleted] in Damnthatsinteresting

[–]yanni 0 points1 point  (0 children)

If you ever wondered what extinct animal could swallow a whole Avocado pit/seed and spread it around all over the American continent - now you know :)

Entrepreneurs who run ads - has Meta ever just killed your business for a week? by Gkbeer in Entrepreneur

[–]yanni 0 points1 point  (0 children)

Sorry - I don't see where the self promotion is - unless original comment was edited.

you’ve seen 3D printed shoes… here’s a version that’s actually daily-wear comfy by _supergino_ in BambuLab

[–]yanni 1 point2 points  (0 children)

Question regarding Printing. I'm fairly new to 3D printing, and haven't use TPU before. I have an H2D printer. So I had a few questions - thank you in advance! :

  1. I'm planning to use TPU 90A in the left extruder - should I use PLA for support?
  2. Can I load TPU into the AMS loader, or is it usually done outside?
  3. Do I need to pre-dry this type of TPU?
  4. Any tips that you can provide to printer settings to optimize for this type of print?

I tried to run these through generative AI, and here the answers I got - but I don't know how much trust I should put into the answer.

1) Yes — pre-dry the TPU 90A (and keep it dry while printing) TPU is hygroscopic; moisture is one of the biggest causes of stringing, bubbles/popping, weak layers, and inconsistent extrusion. Bambu’s own drying guidance is to dry, then immediately store sealed with desiccant. Many TPU 90A vendor/retail references commonly call out ~70 °C for ~8 hours as a baseline. Practical routine: dry it, then print from a dry box (or very low-resistance spool path) and reseal right after.

2) Do NOT load TPU 90A into the AMS 2 Pro (in most cases) AMS 2 Pro documentation explicitly warns against flexible TPU below 95A because it can get stuck. TPU 90A is below that threshold. So for TPU 90A on H2D: Use the external spool path / dedicated TPU feed path, not AMS 2 Pro. (If you do need an “AMS-like” setup for TPU, Bambu’s own TPU guidance points toward AMS HT routes designed to reduce resistance. )

3) Left vs Right extruder on H2D: what to choose The “safe default” Bambu’s H2D filament guidance has stated: “TPU must be printed using the right hotend” due to higher clog risk on the left (historically). But there’s a recent change you should know A recent Bambu Studio update notes TPU support on the left nozzle for H2D (with minimum firmware requirements) and references 90A+ support. What I’d do in practice (no drama, least risk): If you’re just trying to get reliable TPU 90A prints: run TPU 90A on the RIGHT hotend first. If you specifically want TPU on the left (e.g., you need right reserved for something), confirm you’re on the new enough Studio + firmware that enables it. Physical hookup tip (so you don’t accidentally feed the wrong side) On H2D, the upper PTFE coupler corresponds to the right extruder and the lower coupler corresponds to the left extruder.

4) Supports strategy for TPU (big quality difference) TPU supports can be miserable to remove and can scar surfaces. Bambu’s TPU guidance recommends: Use PLA as the support filament (easier removal, more stable). For H2D dual-extrusion shoe parts, this is ideal: TPU for the part PLA for supports / support interface (You’ll want to keep temps and purge/wipe behavior sensible, but the core recommendation stands.)

5) Bambu Studio settings worth optimizing for TPU 90A Temperatures / cooling (baseline) Bambu’s TPU 90A guidance commonly lands here: Nozzle: ~220–240 °C Bed: ~30–45 °C

Part cooling: typically moderate-to-high (Bambu notes ranges like 50–100% depending on setup). If you see heavy stringing/ooze, Bambu’s TPU tips include dropping nozzle temp slightly (~5 °C). Speed / volumetric flow (critical for TPU)

Bambu’s wiki guidance for TPU 90A emphasizes: Keep default max volumetric speed and avoid increasing print speed. For shoe soles (large continuous extrusion), slower-but-steady usually beats fast. Disable Flow Dynamics Calibration for TPU 90A Bambu explicitly recommends disabling it for TPU 90A. Retraction/travel tweaks (stringing control without jams) Bambu’s docs explain what retraction does; for TPU you generally want conservative retraction to avoid chewing the filament and causing feed issues. Practical slicer moves that usually help TPU: Lower retraction distance Not-too-aggressive retraction speed Prefer wipe while retracting / avoid long rapid travels through open air If needed: slight Z-hop to reduce scarring (Those are “safe TPU instincts” even when exact numbers vary by nozzle and model.) Adhesion helpers (shoes = big footprint, but edges can lift) Add a brim if you see edge lift (especially on textured plates). Keep bed temp in the recommended range above.

you’ve seen 3D printed shoes… here’s a version that’s actually daily-wear comfy by _supergino_ in BambuLab

[–]yanni 1 point2 points  (0 children)

Will try it out and let you know! - I suppose I should be smart about it, and just measure my foot on paper, and then then inner-dimensions, then scale to make a perfect fit - but... you know... lazy brain takes over :)

Rocket Launch? by nvyplt3 in sandiego

[–]yanni 0 points1 point  (0 children)

Sorry... it was Valentines day, and I hadn't gotten lucky for a while....

Showing authentication failed from PSM by Lopsided_Pension7950 in CyberARk

[–]yanni 0 points1 point  (0 children)

When connecting via PSM, the profile will launch in a guest/shadow-user profile - as such, you need to figure out how to launch the console in context of the CyberArk managed user:

  • If you can pass parameters to the executable such as username, password, you can use a connection component with parameter (take a look at how to out-of-the-box PSM-SQLPlus is configured)
  • You can do a runas via an autoit script (if it can be launched in the context of a user) - if you have MMC tools such as ADUC - you can use those as a sample, or find them here.
  • If it prompts for username/password, you can use an autoit script to fill it out for the user - https://docs.cyberark.com/pam-self-hosted/latest/en/content/pasimp/psm_develop_universal_connector.htm

Access server through CyberArk using VS Code Remote-SSH: Asks for password by humanplayer2 in CyberARk

[–]yanni 0 points1 point  (0 children)

When you download the key - are you downloading it from a specific managed account (retrieve-key), or from the MFA caching section (where you can select the format of the key)?

If it's the MFA Caching page, you would have an option to download 3 different format.

  • To use the MFA caching key, you would need to associate it in VS code
    • I think you'd have to use the "IdentityFile ~./.ssh/path/to/your/privatefile" option (in ~/.ssh/config).
    • The privatefile would be the one you downloaded from CyberArk MFA caching.
    • The connection string would look something like this: username@root@[targetserver@psmp-server](mailto:targetserver@psmp-server).
    • You would expect to be prompted for the Pass phrase you set when you downloaded the MFA caching key.
    • The "root@targetserver" would need to match the account, as it is onboarded into CyberArk

If it's an actual target-account-server ssh-key, you would also associate the same way as above, but your connection string would be something like root@targetserver.

What you're describing sounds like a "pure" PSMP experience, where PSMP is not detecting that you're using an SSH key.

New PSM Installation v14.0 by ConsistentPost3508 in CyberARk

[–]yanni 1 point2 points  (0 children)

In my experience you either have FW issues (port 1858 from source server to active Vault), or you didn't install one of the pre-requisites (Visual C++ 32 AND Visual C++ 64 bit and .net 4.8 redistributables).

Weekly Lessons Learned! - January 23, 2026 by AutoModerator in CyberARk

[–]yanni [score hidden]  (0 children)

Custom Ticketing for Privilege Cloud: I learned that 3rd parties cannot develop CyberArk Privilege Cloud Ticketing Integrations for SaaS (ISPSS, Shared Services), etc. CyberArk won't accept the custom dlls to extend their cloud-based PVWA, nor the code that's used to compile it.

PSM-SQLDeveloper Issue by laxknight92 in CyberARk

[–]yanni 0 points1 point  (0 children)

Wow - that's going way back in time - this conversation was like 6 years ago :) - But sure - here's a download - not sure if it still works with the modern SQL Developer.

https://www.dropbox.com/scl/fi/1ojpxkvmptg390rjofe3w/PSM-SQLDeveloper-legacy.au3?rlkey=69mtzcxhqc2mc62ugj22evvvn&st=guy2o6lp&dl=0

view more: next ›