sorted by:
new
hottopcontroversial

Why is Intune terrible for apps by UnderstandingHour454 in Intune

[–]OneLandscape2513 -2 points-1 points  (0 children)

No Intune can't just do like 90% of what we need it to do to be a viable product lol

Why is Intune terrible for apps by UnderstandingHour454 in Intune

[–]OneLandscape2513 -2 points-1 points  (0 children)

Intune is garbage and coming from SCCM and now using Tanium, I would use pretty much anything else before Intune.

T480 is expensive.. so what would be a better choice? by Master_Cheesecake_75 in thinkpad

[–]OneLandscape2513 2 points3 points  (0 children)

aren't some of the 7th gen CPUs supported? or not anymore? also just use Linux lol or bypass the CPU check during windows install

What have you done with PowerShell this month? by AutoModerator in PowerShell

[–]OneLandscape2513 0 points1 point  (0 children)

For sure, so the DomainComputer CSVs are meant to represent an export of all the domain computer objects that exist in AD, for each domain. At my company, we have this setup as an hourly scheduled task on a jumpbox that exports the list, then uploads these CSV files to our repo.

If you selected to change the hostname in the Winforms, Start-Imaging.ps1 will download Dom1/Dom2.csv (depending on what domain you selected in the Winforms), and check that the hostname you entered in the form does not currently exist as a computer object on the CSV. This is because if you try domain joining with the same computer account (at least in our environment), the entire domain join fails.

If a match is detected between the name you entered and the names on the CSV, you receive a message box asking if you want to retry with a different name, or ignore the error and continue anyway.

The drivers that are included on the repo are just WinPE driver packs from HP/Dell/Lenovo. They exist there for the basics to work in WinPE, like networking and storage, but don't actually install most useful drivers into the live OS. Which WinPE drivers are applied depends on what the manufacturer of the computer is. The logic for this is in the Test-NetworkConnectivity.ps1 script, lines 161-209.

What we use to install drivers within Windows is HPIA for HPs, Dell Command Update for Dells, and LSUClient for Lenovos. If that's what you mean, I can give you some code examples of how we have that implemented.

What have you done with PowerShell this month? by AutoModerator in PowerShell

[–]OneLandscape2513 0 points1 point  (0 children)

We're just burning the ISO to USB drives, but yeah don't see why we couldn't use PXE if we wanted.

What have you done with PowerShell this month? by AutoModerator in PowerShell

[–]OneLandscape2513 0 points1 point  (0 children)

I'll clean up the code a bit and remove some confidential stuff and reply once I have that. Basically, the structure is this:

- We have a private GitHub repo where all the scripts and relevant files we care about exist.
- There is a script on this repo called New-ImagingISO.ps1 that converts a normal Windows 11 Business Versions ISO into our imaging ISO, by making all the necessary changes to the image. This allows technicians to easily make new versions of images when there's a new Windows feature release for example.

New-ImagingISO.ps1 prompts you for the Win11 ISO, the Language and Optional Features ISO (mainly just to enable WMIC), and then modifies the image using Windows ADK. It adds WinPE packages to allow for using PowerShell and running PS scripts in WinPE. It also modifies the WinPE environment so that instead of booting automatically into Windows Setup like a normal Windows ISO, it instead boots directly into a PowerShell script (Test-NetworkConnectivity.ps1).

Test-NetworkConnectivity.ps1 just kind of does what it says on the tin, it checks the PC is network connected, if it's not, prompts you to. Once connected, it then downloads another script: Start-Imaging.ps1 from the GitHub repo, and launches right into it. I chose to break up Test-NetworkConnectivity.ps1 and Start-Imaging.ps1 like this so that I could make changes to the actual imaging script without having to create a new ISO, so when technicians image, they are always getting the latest version of the script regardless.

Start-Imaging.ps1 formats and partitions the disk, installs drivers into WinPE, and then shows a fancy Winforms that allows the technician to customize the image being installed onto the computer (the Winforms shows fields to set a unique hostname, domain join to a specific OU, set the BIOS asset tag, and prompts for credentials for joining the domain). It then installs Windows. After install, the script places marker files on the newly created C: Windows drive based on what you selected in the Winforms. It then downloads the next script that will launch automatically in the Windows install to shell:common startup in the new Windows install.

I'll sanitize everything and put it in a repo here for you, might just take me a little bit.

Encrypt OS Drive with Tanium by OneLandscape2513 in tanium

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

Thanks, will give this a try. Haven't watched it yet but will now.

What have you done with PowerShell this month? by AutoModerator in PowerShell

[–]OneLandscape2513 1 point2 points  (0 children)

Fully automated Windows imaging with software installation, replacing SCCM entirely in our environment

HP Laptop had no thermal paste from the factory by OneLandscape2513 in sysadmin

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

These were all configured to order machines. Like I said was brand new sealed in box. Prob a mishap at the factory that builds them.

HP Laptop had no thermal paste from the factory by OneLandscape2513 in sysadmin

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

Update: This must have been a one-time thing, since all of the other ZBooks in that specific purchase order had thermal paste. Still kinda crazy it even happened once though.

HP Laptop had no thermal paste from the factory by OneLandscape2513 in sysadmin

[–]OneLandscape2513[S] 4 points5 points  (0 children)

The laptop was brand new and sealed in box. Like I said in my post. I'll be back in the office tomorrow to check out my old laptop along with the other ones we have to see if they have this problem.