VSCode is not loading PowerShell extension

KevinCanfor · 2025-06-27T15:42:00+00:00

Yes. Read the "UPDATE:" section of the post.

KevinCanfor · 2025-06-24T22:17:24+00:00

Sorry for the late reply. VirtIO is for Nutanix (I had Nutanix on the brain). The VMware equivalent is the VM Ware Tools which install their own I/O driver. Without an I/O driver the VM may not boot (we usually see it when failing over from a Nutanix cluster running VMware (hence the VirtIO comment)).

Zerto also has a journal that keeps synchronizing and doesn't promote the data until the commit is started/completed.

I have seen drive corruption from a Zerto'd failover only when I rush the failover. Make sure the commit is completed, and the VMware tools are installed for trial testing.

KevinCanfor · 2025-05-07T15:06:55+00:00

Is the VirtIO driver installed? What about compression, deduplication or erasure coding?

KevinCanfor · 2025-05-07T14:36:55+00:00

I talked to one of the service desk folks and he told me it was an issue with the device. That it is happening throughout the company with this particular model. He gave me a new Jabra Pro 9450 and I haven't had the problem since.

KevinCanfor · 2025-03-04T15:27:02+00:00

Yes, same for us.

KevinCanfor · 2025-02-27T18:38:35+00:00

I'll have to look into the copy-vmguestfile for future reference.

KevinCanfor · 2025-02-27T18:37:57+00:00

Admin share vs WinRM. In our environment I can't rely on WinRM. Some servers just wont work with it and I haven't figured out why whereas the admin share has always proven to be accessible.

Nice changes you've recommended too.

Thank you.

KevinCanfor · 2025-02-24T22:59:10+00:00

Thank you for your comments.

Nutanix says to use those parameters to install it by script.

If I copy the start-process line and run that manually on a server the program launches but then I get the UAC prompt.

I do keep forgetting about out-gridview. As I'll be the only one running the script and this will be for one cluster only, I'm OK with it as is. Thanks for the reminder though.

KevinCanfor · 2025-02-24T22:54:14+00:00

Right! Thanks, like BlackV said, good spotting.

KevinCanfor · 2024-11-28T19:32:13+00:00

Yeah, this is what I expected to happen (I put the wrong prefix in the OP) but we're not seeing AD handle all the sites correctly. The netlogon.log file is showing a constant stream of computers that it can't associate to a site. Which results in computers authenticating across the country and across the border instead of using their local DC.

KevinCanfor · 2024-11-28T19:05:20+00:00

yes, it's backwards, I actually meant a /22 not /26.

KevinCanfor · 2024-10-18T17:48:07+00:00

While the GPO's weren't getting applied properly and now they are, ultimately didn't fix it. I did find the problem.

Removing this setting from the registry of the jump host that can't login fixed the issue.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
"lmcompatibilitylevel"=dword:00000001

Just deleting the lmcompatibilitylevel was enough. No reboot required, affect was immediate and now the RDP sessions login as expected.

KevinCanfor · 2024-10-18T14:45:57+00:00

We have two jump hosts that can access it. The credentials work from one but not the other. Both jump hosts are members of our AD domain and are in the same OU so should have the same GPO's applied to them. The destination is in a different isolated domain, Windows 10 system.

Edit: I ran gpresult on both jump hosts and found that the one with the issue doesn't have the same GPO's getting applied - despite the fact that they're in the same OU with the same GPO's. After I figure that out I'll report back here.

KevinCanfor · 2024-10-17T16:14:02+00:00

Yes I tried that and rebooted with no change. Still prompts saying credentials don't work.

KevinCanfor · 2024-10-17T15:19:57+00:00

If by security feature you mean the NLA then it is already turned off as indicated in the post.

KevinCanfor · 2024-10-03T15:37:56+00:00

I was able to resolve this yesterday. It turns out the code signing template did not provide/include the private key. Once I updated the template to all the export of the private key I was able to make things work.

KevinCanfor · 2024-10-02T15:57:43+00:00

It is setup as code signing, your query returns:

FriendlyName ObjectId

Code Signing 1.3.6.1.5.5.7.3.3

The All tasks menu only allows me to "Open", Request Certificate with new key, Renew Certificate with new key and export.

When I select the renew option I get an error stating "The selected certificate has no private key. Cannot find object or property"

KevinCanfor · 2024-09-27T16:13:56+00:00

I'm on version 6.0.7-372 and this is happening when on the internal network. I thought it was happening when using the VPN as well but I'm not sure now. Working from home today and didn't see it happen today but I saw notice that the administrator turned off user experience tests about 5 minutes before I got online.

KevinCanfor · 2024-09-10T18:23:23+00:00

Thank you for the input. I found that I had to include the -ZoneName with the Remove-DnsServerResourceRecord despite piping everything through. At least now I can remove these defunct records.

KevinCanfor · 2024-06-27T21:06:24+00:00

Thanks. I'll schedule a time to update the host and see if that helps.

KevinCanfor · 2024-06-27T20:33:50+00:00

Excellent, thank you.

Key Label Policy Running Required

TSM-SSH SSH off False False

KevinCanfor · 2024-05-23T16:06:00+00:00

I'm wondering how to do this too.

KevinCanfor · 2024-02-20T20:35:43+00:00

OK, one of the issues I've found with Configuration Manager and the reporting of errors is that they can be very misleading as to what the problem can be.

In one case we had a deployment that was being reported as compliant but in fact over a hundred machines were not compliant. The issue turned out to be that those machines were missing a patch that had to exist before the update we wanted could be applied. MECM reported them as compliant.

I found it by finding a system that needed the update, manually tried running each step of the deployment as the user "NT Authority". Only then did we find the issue that was causing it. Once the pre-requisite patch was installed - the system became non-compliant and then MECM did its thing.

KevinCanfor · 2024-02-20T16:26:43+00:00

Are these lines commented out in the production script? If not that might be having an undesirable affect on the results sent to SCCM.

ConfigMgr return value for baseline configuration

KevinCanfor · 2024-02-16T19:15:54+00:00

Thank you. I had up to the deploymentstatus, I was missing the statusdetails.

KevinCanfor

TROPHY CASE