@pmoncho said in ESXi 6.7 Troubleshooting:
ESXi is loaded all into memory after boot up. Other than USB disk checks, nothing is stored on the USB key after the hypervisor is loaded. It mostly writes to the USB key on reboot/shutdown.
It is on embedded installs. (not on full version installs).
@scottalanmiller said in ESXi 6.7 Troubleshooting:
The H330 is like for labs or testing. Shouldn't be found in a production environment. It's a fine card for what it is, just not a production use card
It's fine for a boot device but on Dell 14G most people use BOSS cards(Unless they are maxing out the PCI-E bays, and then getting a H330 embedded version)
@DustinB3403 said in ESXi 6.7 Troubleshooting:
ESXi recommends SD card, USB is a bit to fragile for the number of writes you'd be making to it.
M.2 SSD is the recomendation. SD cards lack any kind of ECC and the controllers are too dumb to prevent read discards. Throw in the fact that cheap SD cards are slow on boot, you can log local on a M.2, I'd say for non-lab usage M.2 is the recomendation going forward.
If you must go embedded SD card, I'd get at least 32GB as it will likely have fewer read endurance issues.
@scottalanmiller said in Veeam Company Announcement:
Waze was a blatent attempt to stop a competitor to Google Maps.
Yes, a tiny nobody competitor by the major player. Completely opposite situation in every way. Veeam wasn't purchased by a competitor, it isn't a minor player.
Also, Waze was not stopped or shut down. It was merged in. It's still going.
Ohh I agree this wasn't why Veeam was bought (you are correct) more pointing out situations where companies do buy a company and then take it apart. (Explaining the cases people are complaining about that certainly will not be happening with Veeam).
@scottalanmiller said in Veeam Company Announcement:
@StorageNinja said in Veeam Company Announcement:
Google does all the #$@% time. (Basically to destroy potential competitors). Precog antitrust actions have killed Inbox, and tons of great products.
Yeah, but Google doesn't buy companies like this. Google buys little unheard of things, not market leaders.
Waze was a blatent attempt to stop a competitor to Google Maps.
@scottalanmiller said in Veeam Company Announcement:
Yeah, no one buys a company like that and lays off sales people!
Ehhhhhhh
Google does all the #$@% time. (Basically to destroy potential competitors). Precog antitrust actions have killed Inbox, and tons of great products.
Anytime you buy a "up and coming" storage startup (epecially at fire sale prices), you generally have a lot of B/C sales tallent with hilariously low quota's. You don't necessarily fire them ALL but most of them will not survive in a more mature companies sales org that expects 3 million in sales, not $200K.
If you buy the company entirely for it's engineering tallent and have a sales org with similar capabilities (Not uncommon in my field). Again, this overlaps a bit with #1.
If you buy a company for it's IP (sightly different than the last 2). This is normally for litigation reasons and often done as part of a fire sale.
Your M&A stratagy is to milk existing customers by spiking SnS renewals and cutting sales and support and engineering to the bone. "Sunset stratagy". You do this for under performing stagnent companies to return shareholder value.
You bought the company purely for physical assets (Land, equipment etc). Normally you wouldn't buy the company in thits case...
You bought the company entirely for it's Brand (whoever buys ToysRus and rebuilds it will be doing this).
@RojoLoco said in Veeam Company Announcement:
A good friend of mine works for veeam in sales, I wonder if this will affect his job.
They'll be fine (if anything I expect them to grow their sales org).
@JaredBusch said in Veeam Company Announcement:
Private equity firms are known to fuck things up.
Public companines responding to quarter to quarter results are known to fuck up.
CEO's are known to fuck things up.
Private companies are known to mis-manage money.
Everyone fucks up.
@IRJ said in Why Right to Fire (and Hire) May Be in the Employee's Favour:
Why is most of the world against R2F? It seems like Europe, Middle East, and Asia all have laws against it? Not sure about the Americas outside of the US.
A lot of the world are still driven by lots of low paid task worker jobs that are relatively speaking easy to replace.
@scottalanmiller said in Why Right to Fire (and Hire) May Be in the Employee's Favour:
Right, so they recognize that they are crippling the economy, but don't care when it is only crippled "so much".
It's more a "have to find a middle ground with apeasing various political interests but trying to get shit done..."
@scottalanmiller said in Why Right to Fire (and Hire) May Be in the Employee's Favour:
If you don't have R2F, all feelings of or pretense of employee protection are gone. When you don't have R2F, all employee protections go to the state. Employees aren't the "children" of the employer, they are the enemies of it. Removing R2F makes an adversarial relationship between employee and employer.
What I find interesting is states where it's difficult to fire have problems with unemployeement for younger employees so they create systems where you can fire below xxx age, or offer incentives like lower minimum wage for below yyy age.
@scottalanmiller said in Why Right to Fire (and Hire) May Be in the Employee's Favour:
Even rare unskilled labour today is generally highly mobile
When I was a waiter with at least 3 months exerpiance, you could always tell the manager to go fuck thesmelfs and walk into another resturant in the same town without an issue. The bottom and the top of the job funnel always seem to have comical amounts of "another option willing to pay me what I"m being paid". Either because your value is too high, or your pay is too low.
How many of you are using any of the advanced fancy memory options SDDC, ADDDC etc? or are you just avoiding that part of the BIOS?
I did some research over memory protection over the holidays and wrote a blog about some of the stuff.
https://thenicholson.com/vmware-vsphere-reliable-memory-a-few-thoughts/
https://thenicholson.com/thinking-taking-offer-need-know/
Here is my 50+ point list of Questions and compensation related issues.
Some stuff is straight forward: but start with immortal words of Wutang Finance.
CASH
RULES
EVERYTHING
AROUND
ME
EXCEPT
WHEN
OTHER
ASSET
CLASSES
PROVIDE
HIGHER
RISK
ADJUSTED
YIELDS
What I mean by this is cash is 100% solid comp, but other benefits (RSUs, 401K match, ESPP ) should be adjusted and factored in.
Some stuff is situational:
Support for “In plan post tax 401K to Roth” conversions may not strike your fancy, but I’m going to dodge a boat load of taxes over the years using this ”One trick several senators hate!”.
@scottalanmiller said in Making a Raspberry Pi 4 or Similar SBC Desktop:
RP4 with 4GB of RAM
The problem with Pi (and frankly a lot of the low end ARM) is these things have incomplete UEFI bios etc. You currently need to really be working on one of the distro's designed for it (Which is likely fine for your use case). ARM and our engineers are working on this though..
@magicmarker said in How do you guys handle counter offers?:
It's a 19% NET raise when factoring in benefits, commute, etc. The GROSS raise is 27%. Plus a year end bonus depending on company and personal performance.
Reminder of all the things to compare: https://thenicholson.com/thinking-taking-offer-need-know/
@Pete-S said in Tool for Finding Rogue DHCP:
Capture with tcpdump, analyze with wireshark on whatever machine you want.
Turn on DHCP snooping on your switches and have it suppress DHCP servers on access ports.
@black3dynamite said in Stuck supporting out-of-date Windows Servers, what options do I have?:
That’s just putting a band-aid on something that you will to have to deal with again.
Time value money. Why not kick the can down the road and invest in an area of the company that actually produces growth instead?
@scottalanmiller said in Handling Downvotes:
Votes should be public now.
On the condition that meta bitching about who downvoted you should be a ban 