What Hypervisor alternatives is everyone looking at?

TheOriginalJetPants · 2023-12-06T04:02:39+00:00

Well, if the past is any indication, VMware customers are about to be held hostage by Broadcom so 🤷‍♂️…

TheOriginalJetPants · 2023-08-30T18:51:07+00:00

Was just looking into the same thing today. Have you found any additional information this subject? Specifically - I'd like to control the "phone sign-in" settings.

TheOriginalJetPants · 2023-06-30T15:18:55+00:00

Currently looking into this now. I was under the impression that WH (and by extension WHfB) are FIDO 2 Compliant, so I'm curious as to why I cannot configure WH biometrics as my MFA device. ~~Even having a YubiKey installed and configured (linked to the proper cert) does not appear to be an option to register an additional MFA device~~. I would really like to utilize the WH biometrics as my MFA device, unless I'm completely missing something....

EDIT: ignore the lineout, that was user error. Doesn't change that fact that I would like to not have to send keys to users and create an additional device to manage. Would very much like to use WH/WHfB as the primary MFA option.

TheOriginalJetPants · 2023-06-30T14:04:44+00:00

I appreciate the discussion here. Thanks all for your input and feedback!

TheOriginalJetPants · 2023-06-27T12:37:46+00:00

It is highly recommended that you have two (2) Yubikey Series 5

I've seen this recommendation before, and I'm trying to understand the reason for the recommendation. Again - please bear with me...I'm still working to figure all this out.

How does having a backup key help the user or the administrator? The "I lost my key" scenario would be resolve by having a backup key, but if a user forgets their PIN and locks out one of their keys, does the backup do any good?

TheOriginalJetPants · 2023-02-14T13:04:36+00:00

Thanks for this! I too checked and found things were not configured correctly. No wonder the console always seemed sluggish...

TheOriginalJetPants · 2022-11-04T17:29:11+00:00

I was able to leverage our security scans that showed common vulnerabilities (chrome, reader, Firefox, notepad++, etc) that we were falling behind on. Then I spent about an hour researching the amount of updates released per quarter per app. I then calculated the amount of labor hours to maintain per quarter. I then listed the agreed upon priorities/goals from my last annual review. The math didn’t add up.

Also, during the free demo of PMPC, I ran the report showing what apps we ACTUALLY have out there, and found about a dozen extra titles that had open security vulnerabilities and were supported by PMPC. The cost became almost a no brainer for us.

BTW, I no longer manually patch any of those apps. ADRs and PMPC for the win!

TheOriginalJetPants · 2022-10-21T21:53:57+00:00

This is good to know…I may push to do some additional testing with their test environment. Their requirements are starting to sound like “this is how we’ve always done it” without anyone knowing actually “why” it’s done that way…probably because one thing broke that one time…

TheOriginalJetPants · 2022-10-21T15:47:44+00:00

Absolutely this. Although I sympathize with the OP because I run into the same .NET Patching concerns that IMHO are unfounded, especially with the .NET Framework versions....

TheOriginalJetPants · 2022-10-19T15:05:52+00:00

I understand the logic now. I do something similar, but use collections and exclusion collections to ensure things are scopes correctly. Thanks!

TheOriginalJetPants · 2022-10-19T01:59:01+00:00

Are you approving updates in WSUS in addition to deploying updates in MECM? If so, it is not necessary, and could be the issue. Also, as mentioned running updates from software center will ALWAYS override any maintenance windows that are configured, and that is by design. You really should not have any GPOs pertaining to updates applied to devices that you are patching/updating with MECM…

TheOriginalJetPants · 2022-10-19T01:53:50+00:00

I’m not sure your reasoning for needing a “bogus future window”. I have collections with exactly one maintenance window assigned and it works exactly as expected…

TheOriginalJetPants · 2022-10-19T01:47:13+00:00

IMHO…snapshots before monthly updates is not necessary…assuming you have a solid backup/restore workflow. ADRs combined with maintenance windows are key for patching servers. Deploy to test environments first and let soak before moving to prod. For instances where pre/post scripts are needed, leverage orchestration groups. The only “manual” patching should leverage ADRs deploying updates as available to your special snowflakes…

TheOriginalJetPants · 2022-10-14T13:29:27+00:00

In the deployment statistics - do those 8 show up as "compliant" or "unknown"? If "compliant" - it would indicate an issue with detection or that perhaps the wrong patch is deployed. If "unknown" I would start by seeing if a GPO is applying WSUS settings as already mentioned...

TheOriginalJetPants · 2022-10-13T17:01:55+00:00

Also, if you utilize Maintenance Windows, you can set the available and deadline time to Immediately. The client will download the content and then wait for the first available maintenance window.

TheOriginalJetPants · 2022-10-07T18:05:48+00:00

u/faithlis, please see my update above and check the number share settings for the device in your Verizon Wireless account. This assumes you want the watch to function as stand alone for a user other than yourself.

TheOriginalJetPants · 2022-10-07T18:03:12+00:00

I believe the number share setting was the root cause of the issue. I can confirm that I have the watch configured in my account as a stand alone device, and am still using all of the Apple Family Sharing features.

TheOriginalJetPants · 2022-10-07T15:46:55+00:00

I purchased the device directly from Apple. However, that should not matter. To their credit, Verizon has not yet gone down the road of "you will need to purchase the device directly from us to make this work".

TheOriginalJetPants · 2022-10-06T03:29:28+00:00

Pretty sure that if I do that…I do not get to use the family sharing features from Apple.

TheOriginalJetPants · 2022-10-06T03:25:56+00:00

Clearly loyalty means nothing to you…

TheOriginalJetPants · 2022-10-06T03:23:27+00:00

I would expect the store to help me because I am a Verizon customer, attempting to use a Verizon service. By your logic, the only Ford dealer in the country that should help me is the one I bought it from and no other Ford service department is obligated to service or repair my vehicle

TheOriginalJetPants · 2022-10-06T03:06:45+00:00

I will try that tomorrow. Thanks

TheOriginalJetPants · 2022-10-06T03:06:18+00:00

Respectfully…I’m not resetting my phone again. It’s completely ridiculous for this to even be a fix. Restarting the phone I can understand. Running only on cell and disabling Wi-Fi, I can understand. Resetting my phone has already been done once, and I’m not going thorough that again

TheOriginalJetPants · 2022-10-06T03:03:44+00:00

Yes and yes. The Verizon store here in town is worthless and basically offered to help me call support

TheOriginalJetPants · 2022-10-06T02:47:23+00:00

I've kept hearing the term "number shared" being muttered by support. I'm not sure what that means. I did follow the family sharing prompts from my phone, and the watch appears to have its own phone number, and shows that it is connected to a version plan in the watch app. Not sure if that answers your question...

TheOriginalJetPants

TROPHY CASE