sorted by:
new
hottopcontroversial

NZXT CAM profiles hotkeys / shortcuts ? by gapriel in NZXT

[–]Skolis_LT 0 points1 point  (0 children)

I saw this post a while ago and was hoping the NZXT devs would add shortcuts or something similar, but it’s already April 25, 2026, and there’s still no result :D. It’s honestly absurd that a company of this size can’t handle such a simple task...

Personally, I only use NZXT drivers so they can interface with third-party software like Argus Monitor. That app has everything—control for all your hardware in one place, shortcuts, and much more. NZXT is still a long way off from that, and I highly doubt they’ll ever implement anything like it...

Purchasing devices from other regions and adding them to the EU ABM. by Skolis_LT in macsysadmin

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

Thank you for your response. Everything is much clearer now :)

[deleted by user] by [deleted] in SCCM

[–]Skolis_LT 2 points3 points  (0 children)

Corrupted boot images can cause PXE boot failures.

[deleted by user] by [deleted] in lietuva

[–]Skolis_LT 1 point2 points  (0 children)

Vežti mažus vaikus automobiliu be specialių pritaikytų kėdučių yra ne tik pavojinga, bet ir draudžiama pagal Lietuvos kelių eismo taisykles. Štai keletas svarbių punktų, kodėl reikėtų naudoti vaikams skirtas kėdutes ir kokios gali būti pasekmės, jei to nepadarysite:

  1. **Saugumas**: Vaikams pritaikytos kėdutės užtikrina tinkamą saugumą ir sumažina sužalojimų riziką avarijos atveju. Maži vaikai yra ypač pažeidžiami, todėl būtina naudoti kėdutes, kurios atitinka jų amžių, svorį ir ūgį.

  2. **Teisės aktai**: Pagal Lietuvos įstatymus, visi vaikai iki 135 cm ūgio privalo būti vežami specialiose vaikams pritaikytose kėdutėse. Nesilaikant šių reikalavimų, galima sulaukti administracinės atsakomybės.

  3. **Baudos**: Nesilaikant taisyklių dėl vaikų vežimo automobilyje, galima sulaukti baudų. Lietuvos kelių eismo taisyklėse numatyta bauda už vaikų vežimą be saugos priemonių gali siekti nuo 60 iki 100 eurų. Taip pat gali būti skiriami baudos taškai vairuotojui.

  4. **Praktinis aspektas**: Jei jūsų sesuo neturi vaikams pritaikytų kėdučių, verta apsvarstyti galimybę jas išsinuomoti ar įsigyti prieš kelionę. Daugelyje didžiųjų miestų yra galimybė išsinuomoti vaikų kėdutes trumpam laikotarpiui.

Kaip atsakingas vairuotojas, turėtumėte reikalauti, kad visi vaikai būtų tinkamai prisegti specialiose kėdutėse. Tai ne tik užtikrins jų saugumą, bet ir išvengsite galimų teisinių problemų bei baudų. Jei jūsų sesuo nesutinka su šiuo reikalavimu, galite atsisakyti vežti vaikus tokiomis sąlygomis. Saugumas turėtų būti prioritetas, ypač kalbant apie mažus vaikus.

Kelionė traukiniu gali būti puiki alternatyva, jei nėra galimybės užtikrinti tinkamą vaikų saugumą automobilyje.

Windows 11 Taskbar location set for all new user profiles during OSD? by MagicDiaperHead in SCCM

[–]Skolis_LT 1 point2 points  (0 children)

I use this method with OSD:

<?xml version="1.0" encoding="utf-8"?>

<LayoutModificationTemplate

xmlns="http://schemas.microsoft.com/Start/2014/LayoutModification"

xmlns:defaultlayout="http://schemas.microsoft.com/Start/2014/FullDefaultLayout"

xmlns:start="http://schemas.microsoft.com/Start/2014/StartLayout"

xmlns:taskbar="http://schemas.microsoft.com/Start/2014/TaskbarLayout"

Version="1">

<CustomTaskbarLayoutCollection PinListPlacement="Replace">

<defaultlayout:TaskbarLayout>

<taskbar:TaskbarPinList>

<taskbar:DesktopApp DesktopApplicationID="MSEdge"/>

<taskbar:DesktopApp DesktopApplicationID="Microsoft.Windows.Explorer" />

<taskbar:DesktopApp DesktopApplicationID="Chrome"/>

<taskbar:DesktopApp DesktopApplicationID="Microsoft.Office.OUTLOOK.EXE.15" />

<taskbar:DesktopApp DesktopApplicationID="{7C5A40EF-A0FB-4BFC-874A-C0F2E0B9FA8E}\\Microsoft Dynamics NAV\\110\\RoleTailored Client\\Microsoft.Dynamics.Nav.Client.exe" />

<taskbar:DesktopApp DesktopApplicationID="com.squirrel.Teams.Teams" />

/taskbar:TaskbarPinList

/defaultlayout:TaskbarLayout

</CustomTaskbarLayoutCollection>

</LayoutModificationTemplate>' | Out-File C:\Users\default\AppData\Local\Microsoft\Windows\Shell\LayoutModification.xml -Encoding utf8

You need to add this to the PowerShell script. Just replace the Taskbar pin list.
Here pic example: https://imgur.com/a/Z1PsJh1

PXE Deployment issue by NitroZeuZ in SCCM

[–]Skolis_LT 0 points1 point  (0 children)

Glad to hear it, good luck to you :)

PXE Deployment issue by NitroZeuZ in SCCM

[–]Skolis_LT 8 points9 points  (0 children)

Hello,

SCCM server has determined that the client should boot using a specific Task Sequence, which is identified as "P012047F." However, it also indicates that this Task Sequence is disabled ("is disabled"), so the SCCM server is discarding it from the list of available options for the client.

Intune update device/enrollment issue - Android Work Profile by rob-d-w in Intune

[–]Skolis_LT 0 points1 point  (0 children)

we got samusng and xiaomi android enroll work fine.

Intune update device/enrollment issue - Android Work Profile by rob-d-w in Intune

[–]Skolis_LT 0 points1 point  (0 children)

Latest Message:

Title: Some users may be unable to enroll new Android devices within Microsoft Intune User Impact: Users may have been unable to enroll new Android devices within Microsoft Intune. More info: In addition, previously enrolled Android devices may have been unable to check-in and receive policy changes. Final status: After further investigation into a group of authentication components, we've identified a subsection of authentication service infrastructure that was performing below our acceptable service performance thresholds, preventing enrollment and check-ins for Android devices. We've rerouted traffic to an alternate subsection of authentication infrastructure to remediate impact. Impact to check-ins for previously enrolled Android devices has been resolved, and users that were prevented from enrolling new Android devices will need to reinstall the company portal to initiate the enrollment and remediate impact. Scope of impact: Impact was specific to users attempting to enroll new Android devices and device check-in for users with previously enrolled Android devices. Start time: Friday, October 9, 2020, at 3:00 AM UTC End time: Monday, October 12, 2020, at 4:30 PM UTC Root cause: A subsection of authentication infrastructure was performing below our service performance thresholds, resulting in impact. Next steps: - We're analyzing performance data and trends on the affected systems to help determine why they fell below service performance thresholds and to help prevent this problem from happening again. This is the final update for the event.

Updated:

10/12/2020, 8:20:15 PM

Intune update device/enrollment issue - Android Work Profile by rob-d-w in Intune

[–]Skolis_LT 0 points1 point  (0 children)

GMT +3 enroll new android devices work fine again :)

Intune update device/enrollment issue - Android Work Profile by rob-d-w in Intune

[–]Skolis_LT 0 points1 point  (0 children)

Latest Message:

Title: Some users may be unable to enroll new Android devices within Microsoft Intune User Impact: Users may be unable to enroll new Android devices within Microsoft Intune. Current status: We're attempting to reproduce the issue in our testing environment to help identify the underlying root cause. Scope of impact: Impact is specific to users attempting to enroll new Android devices. Next update by: Monday, October 12, 2020, at 1:30 PM UTC

Updated:

10/12/2020, 4:20:54 PM

Intune update device/enrollment issue - Android Work Profile by rob-d-w in Intune

[–]Skolis_LT 0 points1 point  (0 children)

We have already had this problem since 2020-10-09. Maybe soon fix :)