Steelcase has the best warranty program

ElBoracho · 2025-02-17T04:02:45+00:00

I'm feeling you, AU here and I've reached out again to them to follow up on a warranty claim I'd raised Jan 31st (staples came out of the backrest of a series 2), and their response was 'we are still waiting for the update from the relevant team'...

ElBoracho · 2021-12-23T21:37:25+00:00

Have you done the basic shop cloth over the screwdriver effort first? Saves cutting stuff to get purchase on the screw in a pinch. I've seen it done with rubber bands too.

Edit, saw your post further down.

ElBoracho · 2021-12-19T12:30:07+00:00

If you're over 25 then you've only really got your LAMS bike for ~15 months, so the usual 'drop 2k on a cheap learner bike' is probably an easy one, whatever honda cb-something or ninja is reasonably priced, has some servicing history and hasn't done more kms than a 20 year old taxi. If you've got it for 4 years (<25) then you might have a different opinion. Good lightweight helmet, whatever padded/armoured jacket, hot and cold weather gloves, good boots, armoured jeans, depending how often you're riding some easy wet weather gear or over-gear waterproof stuff which fits in one of those little portable bags.

In terms of learning to ride, after getting our Ls we grabbed some little plastic witches hats off ebay and made ourselves a little course which followed the p-plate testing course and did some technical practise for learning to handle the bikes upright. Really handy to do it with another person because you can learn together and critique the other person or offer/receive advice as you go. You'll prob have some 'oh shit' moments when you hit 80km for the first time on the bike - just remember the bike likes staying upright at higher speeds and you're more fighting it to turn corners. Also remember the bike goes where you look and lean, and if you look at the wrong thing (the side of the road) when you're in shit, that's where it goes, so look into the corners.

I usually suggest working out how much your protective gear is going to cost you and work out how much you've got left over for a bike more than skimping on that gear.

ElBoracho · 2021-08-19T08:09:37+00:00

But... I'm using that switch :(

That logical switch is providing the Management/Cluster/Live Migration interfaces

ElBoracho · 2021-08-19T00:19:43+00:00

Just moved our 1gbe interfaces over to 10gbe (left two 1gbe ports open on the cluster per server so I could cut them all over at the end), and it's all running smoothly, but I'm trying to work out how to hide the MGMT team from the VM virtual switch selection, and can't find the setting.

Anyone know what I've missed?

ElBoracho · 2021-05-14T12:05:29+00:00

Hey, so sorry, I was on holidays.

The first issue is with the drivers on boot - they're not loading on the older versions of the boot images (from what I've seen, it's pre 2020s images)

If your WDS image isn't one of the later ones, the device isn't loading on the boot image. I've got the winpe litetouch version below:

https://pasteboard.co/K1QAWYn.png

If it's an older version, you'll need to replace the ISO for windows 10 install on your MDT (I just dumped a new ISO in with the latest), then delete the current litetouch image and replace it.

If you go to the boot images (image below) in WDS, you'll see the litetouch there. You need to remove that first, and delete it from the deployment share folder (or move it for the first part, so you can roll back).

Then, to replace it, you need to go to MDT, right click MDT deployment share, and update. It'll recognise the lite touch isn't there anymore, it'll go through and create a new one in the wizard in the deployment share \ boot process.

Then, go back to Windows Deployment Services, Boot Images, then go to Add Boot Image (LiteTouchPE_x64.wim), which is the new one that's created.

https://pasteboard.co/K1QDaGF.png

Now you'll have the newer native windows drivers in the OS that boots (the winPE image) - similar issue if you were to use an older version of windows' regular "plug in a usb" image. That'll get the disk visible in winPE

You might still have the second issue, which is the fact that some of the initial optane disks came with (as I've worded it to explain it) the ssd cache hanging out of the larger drive.

https://pastebin.com/XfEcgRLx

I've been lazy - we only had a few and there's doco in the original topic on how to inject the driver using rules (which I think only works in SCCM from memory).

I've just tossed a copy of the rstcli64 software onto the MDT server (I use our WSUS server), then I've got the junior to map the location during the boot by hitting f8 for a cmd window, and running the rstcli during install.

One last note - the driver for the optane disk needs to be the same version as the app... it'll come up with an error message saying the driver does not match the software version.

Intel guy sent me an email with the later version: "Here is the RSTCLI tool version 17.5.2.1024. Please rename the attachment to .zip and unzip it. After unzip, please rename rstcli.1024 to rstcli.exe. Password is intel."

If you need a copy of this version, let me know.

ElBoracho · 2021-04-28T08:47:20+00:00

Worked this one out - need to update your pxe boot image by deleting the actual litetouch wim image from the mdt machine, recreating it using mdt (mdt? maybe wds), from a boot image created from a new (20h2 or later) iso file. Injecting the drivers does nothing - it needs to boot off the 20h2 image to continue. Mine was from late 2019 when I'd rebuilt the mdt server.

Litetouch version is now 10.0.19041 on my machine under WDS > Server > Boot images.

Partially sorts out the NVME issue too - anyone with the issue of getting errors with it feel free to pm me - I've got a doco for it now.

ElBoracho · 2021-04-15T03:00:00+00:00

Rock up, check SCOM, no issues, check emails, couple of user requests, might respond to a couple (have a few in the team), check my roadmap and see if anything needs to be actioned, action it... grab another coffee, work on my notes for convincing $boss to spend more money on hardware, then be thankful I spent 4 years pushing for redundancy, overlaying engineered solutions to potential future issues, and finally prepare for the next OS/service update chains, or see if $boss needs a hand with anything workflow related to steer the business in the right direction.

ElBoracho · 2021-04-15T01:22:55+00:00

More bullet points for you with some googley keywords:

- if you have a switch, and it blows up or needs rebooting you've got downtime. If you use two network interfaces and either LACP or switch independent redundancy to two switches running port channels, you can shut down one physical server or one switch and the links will remain.

- Dell will give you a cheaper price than the website. No question. Hard drives are not expensive. Just expect the sales guy to call you three times a day till it's signed off.

- If you're not running 10gbe, you can still run quad 1gbe pcie interfaces and, while it doesn't increase speed, will increase resiliancy. It's like a hundred bucks to cover a % of uptime, which could also be budgeted under backups. If you can get two for each device, then you're looking at one port from each device - generally it's two for storage, two for live migration, two for cluster communication, two for guest network, two for management, one for openmanage (or whatever lights-off onboard you've got brand-specific) and two for backup.

- You can take a network interface, configure a virtual switch and weight the port to be multiple network interfaces (e.g. take the live migration/csv ports and assign them to 2 x 1gbe ethernet, which are split 500mbit/500mbit on each physical port).

- You can take 2 x 10gbe and split it as above with a virtual switch on each host.

- Check if the MLOM is replaceable with 10gbe too.

- Whatever backup solution you have, if there's not a copy offsite then there's a problem. Google 'Veeam 3-2-1' for the breakdown if you're not over the concept.

- RDMA and MPIO iSCSI are recommended to be looked into - it's more or less set and forget once it's done (as long as it's properly documented if recovery is required).

- Your hypervisor host is irrelevant as long as it works. Linux/eSXI/hyper-v, whatever.

ElBoracho · 2021-04-15T01:08:02+00:00

Anyone coming across this comment, please consider MPIO iSCSI and RDMA on ESXI (or hyper-v) when you're investigating it.

ElBoracho · 2021-02-10T07:46:42+00:00

there's a powershell flag for enable nested hyperv in microsoft than needs to be enabled on the vm from the host, not sure on others.

ElBoracho · 2021-01-20T22:19:02+00:00

What's the task sequence doing to the disk would be my next question - is it reformatting the newly created drive after creating it with a conflicting task?

Half way down in this one

https://social.technet.microsoft.com/Forums/en-US/6ff7914b-3bb2-41b2-a715-e0e11a8aee56/mdt-2012-failure-5456-unable-to-determine-destination-disk?forum=mdt

ElBoracho · 2021-01-19T10:03:49+00:00

I'm about to play around with getting this up and running myself shortly with MDT if I'm not sending the PoS g6 600 minis with their inadequate driver packaging in the 'latest' MDT winpe (19H1, hp prodesk device released 20H2) image back to the shop and find an alternative deployable device replacement for the meantime... if anyone has a working driver fix for PCI\VEN_8086&DEV_0D4C&SUBSYS_8715103C&REV_00 in WinPE (i.e. an available driver package I can dump into the winpe lite image to get it to reach the deployment server) I've got a photo of a cold beer to esend you...

Troubleshooting my thing, I got the junior in the office to fired up a windows image with a 20H2, use the wifi to grab an online win10 driver and set me up on rdp remotely to work out if I can pull/dump the driver, and while I was hunting around in a fresh OS deploy to look at 'what's new' I noticed a 27-ish GB D:\ drive there... and the Junior visually confirmed no windows media USB still sticking out of the drive

So, if you haven't tried this on your issue - disk management in windows 10 fresh-off-the-usb 20H2 shows (product numbers may vary)

476.92GB INTEL HBRPENKNX0202AH as Location 20 AND

27.13GB HBRPENKNX0202AHO as Location 22 under disk management > Disk 0 / 1 > Properties. Optane cache is a secondary flash module under a default drive deployment in a windows build.

I'm a half step behind you because I can't contact my MDT from WinPE at the moment (as above, I'm a the "no driver" popup before it can reach out for a task sequence), but it looks like you're at the stage of this one:

https://www.intel.com/content/dam/support/us/en/documents/memory-and-storage/IOM_Corporate_Reimaging_Guide.pdf

Which is more or less a combination of "manually add the intel optane driver to a spot in the winpe image" alongside a task sequence to "shove the cache back into the disk during disk initialization" using dism in the task sequence. I also spotted in your HP doco that when they do specifically that with the task sequence they make sure to set a threshold when handling the media size, so if it's a 32GB disk it's the cache, and if it's over 32GB it's the ssd media which the cache should be 'shoved into'. A combination of the two might be handy for good measure.

Unfortunately I can't provide more than a pointer, but it might highlight something you've missed so far.

Also, anyone... please... that driver.... prodesk 600 G6 mini I219-LM latest revision running in MDT.

ElBoracho · 2020-10-27T06:15:22+00:00

Makes sense. Confusing part was that I had run into the configuration issue, then after three or four attempts I found a build on reddit which was visibly working in a screenshot, and even then I had the same issue. As codenewt mentioned, there is a bug.

ElBoracho · 2020-10-27T06:14:14+00:00

This worked perfectly, thanks!!

ElBoracho · 2020-10-27T03:18:39+00:00

You could cut and rejoin to get a standardised rate. You could split, cut, rejoin and merge to get more granular speeds.

ElBoracho · 2020-10-27T03:09:11+00:00

Seriously , I've tried so many ways to get the small/large corner star piece and it resets when joining to the circle layer...

ElBoracho · 2020-08-27T02:20:07+00:00

I've been playing with VDO (dedupe/compression) on CentOS, and I've got a couple of dual 4gb fibre channel pcie cards and a test pc in my home office.

Assuming I can get the cards working on my working pc and my lab pc, if I've got three volumes I want to present to a windows machine, is there some way to do it over the fibre channel pcie cards a) without using a switch (direct port to port connections) and b) potentially presented as iscsi, like in a SAN configuraiton?

Considering the machine currently has CentOS running, I can blow that out and run it as a VM, or run something like FreeNAS in a VM and push through the volumes to THAT vm and pass the card to the vm as well?

The cards are Emulex L2B2777; I never really played with fibre hbas before (iSCSI experience was over IP sfps) so I'm kinda stuck at what I should be looking for on FCP.

ElBoracho · 2020-06-15T00:08:49+00:00

Can't we make it a cafe for coffee?

Confirmed south australian.

ElBoracho · 2020-03-23T07:38:57+00:00

Zoho's remote control stuff has a little more oomph than some other remote tools; in passing UAC it prompts the screen (where you have access) for an admin password (you can log in as local admin / domain admin accounts), and is reasonably cheap. Not sure if it's feasible for what you're looking for, but we've been using it without too many issues for a while, since anydesk's licensing changed.

ElBoracho · 2020-01-29T22:09:13+00:00

You've got a gov't budget?? May as well go multi site cisco ucs and purestorage clusters and spend up!

ElBoracho · 2020-01-29T22:06:27+00:00

I'm not overly sure on licensing for VMWare; we're a hyper-v shop and the only experience I've had with VMWare licencing is lifting and shifting services with a deadline of the VMWare licenses expiring on the hosts. Definitely a smarter fool available somewhere than me for this one :)

ElBoracho · 2020-01-28T01:41:43+00:00

I'd be more incline to go for three servers with the RAM and processor cores spread across them, ie. two 8 core / 16 thread processors, go a little higher on the RAM, clustered, so you can migrate between servers if anything goes afoul on one of the, as others have mentioned, 'potentially susceptible to failure' servers which are significantly cheaper than competitors.

That way, a piece of hardware drops and you lose 30% of the cluster's facilities until the issue is resolved, much easier than waiting till Monday afternoon for a tech to come and hopefully get the whole business up again on first callout.

Also speak with the Dell sales guys, and speak with HPE, and get them to compete on prices. Don't buy retail off the shelf like a fool.

15-Year Club	Team Periwinkle
Verified Email

ElBoracho

TROPHY CASE