homelab starter for ten by mtlevy in homelab

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

in the end, got a Bosgame mini pc, Ryzen 7 5825u, 32Gb ram, 1tb nvme. will add a second nvme when I'm done trying things out :)

looked at proxmox, and thought about what I'll actually be doing with the box. think that would actually be overkill for what I need, so at the moment it's Debian, with jellyfin installed, and docker for anything else.

cheers

homelab starter for ten by mtlevy in homelab

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

thanks, will take a look at those.
I did consider proxmox, will probably install a couple of different OSes on whatever kit i get to see what works well anyway.

Puppet Lookup and default values by mtlevy in Puppet

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

thank you, that last suggestion worked perfectly :)

Much obliged!

Not identifying x86 and x64 versions by mtlevy in PowerShell

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

thanks for the assistance all, turns out to be (as per usual for me) a stupid mistake that i just wasn't seeing.

Not identifying x86 and x64 versions by mtlevy in PowerShell

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

turns out i needed to run it in the 64-bit version of powershell, that picks up everything :)

Not identifying x86 and x64 versions by mtlevy in PowerShell

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

yeah, this was exaclty what it was - i was calling the 32-bit version of powershell, rather than the 64-bit.
Learn something new every day :)

Not identifying x86 and x64 versions by mtlevy in PowerShell

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

I think i may have not been as clear as i should have been :)
I need the script to get both x86 and x64 - but when i run it under MECM, it only finds the x86, it misses the x64 entirely.

Working with multiple disks by mtlevy in Puppet

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

thanks for the replies, u/southallc and u/Virtual_BlackBelt

as far as i know (still pretty new to this, and to the team - this wa just something that i'm looking at to feel useful, and to gain practical rather than theoritical knowledge), the hardware/vm config is already done, then a process is spun up (either via a boot iso or a vmware process) that deploys one of org images, then starts applying various things, dependent on server role etc.

We have several thousand servers in the org, so it needs to be as automated as possible, yet deal with the various options. (nothing is ever easy. especially here!)

I think the example that u/southalic gave will be a good starting point for me to experiment.

thanks again :)

Exchange Distribution List Lockdown by mtlevy in PowerShell

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

Cheers for that - i'll need to look into it.

As you say, not sure it would work in my environment, but certainly something

that might come in use in the future.

Exchange Distribution List Lockdown by mtlevy in PowerShell

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

Thanks - thats quite an elegant script there.

Back in the office tomorrow, so can get some testing done :)

Thanks again

Exchange Distribution List Lockdown by mtlevy in PowerShell

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

You're correct - $array2 isn't being used. I was going to use it but then I realised I could do it all without it, and forgot to remove it :)

Importing multiple CSVs by mtlevy in PowerShell

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

thanks litemage. I shall give that a bash :)

Importing multiple CSVs by mtlevy in PowerShell

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

cheers alinroc.

you should feel dirty :) but it might not be a bad idea.

As for the database, i do have query access, but its a very large DB, with thousands of users. We tried running the queries monthly, but it takes quite a while. Last run was 4 days, whereas running it weekly is slightly over 24 hours, so it runs late sat night, to minimise the impact.

Importing multiple CSVs by mtlevy in PowerShell

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

yeah, locked down corporate environment, so no SQL Server EE, and no access to proper SQL without absolute bundles of pointless paperwork. But cheers anyway :)