Windows 10: cant stop malicious deployment

Help!Device name Jimbo Processor Installed RAM 20.0 GB 19.8 GB usable Device ID 1BE996A9-99BD-48A2-9754-6578246216D3 Product ID 00325-81866-31452-AAOEM System type 64-bit operating system, x64-based processor Pen and touch No pen or touch input is available for this display Edition Windows 11 Home Version 22H2 Installed on ‎10/‎13/‎2023 OS build 22621.2506 Experience Windows Feature Experience Pack 1000.22677.1000.0 Ive tried to reset it but this all keeps coming back and the wifi keeps disconnecting

:)

 

MDT deployment stops after processing Custom Settings

Hello, I've recently ran into an issue where when I PXE boot a VM it will load the boot image from the deployment server but stops processing after processing the Custom Settings. It's showing only the background image. First let me say this is a home learning environment, and the issues described below only occurred after installing Cumulative Update KB5011558. I may try removing that update to see if this fixes my issue, but I'm not confident that whatever damage occurred will reverse itself. WDS Server Manager provides the following Error and Warning EVENTS: Error:

• The PXE server processed a request from a client of architecture x86. However, there were no boot images installed for this architecture. PXE clients of this architecture will not be able to complete the boot process successfully. To resolve this problem, add at least one boot image for this architecture.

Warnings:

• The default boot image Boot\x64\Images\LiteTouchPE_x64.wim was not found for the x64uefi architecture.
• … not found for the x64 architecture.
• … not found for the x86x64 architecture.

I opened the command prompt (F8) and getting Access Denied trying to access the Deployment share root. The VM was created using BIOS architecture and configured for "Windows 10 and later x64". I should note - in response to the above Error message - I have never deployed an x86 OS nor used an x86 Boot Image in my environment, nor have I ever created a VM that was not x64. The Server is using the built in Administrator account; no other accounts exist on that system. I checked the shares, and Administrators have Full access to deployment share root. I completely regenerated the Boot image and even added the x86 for shits and giggles. I can see the x64 boot image being loaded by the VM. I stopped and recreated the SMB share for the Deployment Share root. Version info:

• Windows Server 2022 Datacenter (on ESXi host)
  • MDT v8456
  • ADK/WinPE v22000
• Windows 10 Pro for Workstations v21H2 (Host for VM that's PXE booting)
  • VMware Workstation Pro 16.2.3

- - - Updated - - -

It turns out that Cumulative Update KB5011558 corrupted some of the account and NTFS permissions. See here for the resolution that helped correct my MDT Deployment Share permissions. [SOLVED] MDT deployment stops after processing Custom Settings - Software Deployment & Patching I'll be sure to create a (VM) snapshot before running future updates that size...

 

Malicious voters!

Yeah as I said, im talking about the case gallery, I am about to resend two of my cases because they were given malicious votes... given 1 without a reason... honestly whoever it is, you are a dickhead, if you are jealous, GET A JOB AND LIFE.

Now I suggest we should be allowed to see and report these malicious votes...

EDIT: Not only am I irritated it prevents my case from having fair votes as there is an "influence' thereafter.

 

Need Help in BitLocker deployment Step by Step

Dear All,

We are planning to deploy to deploy Windows 10 BitLocker in our organization. Could you please anyone help me with step by step deployment from the scratch.

1. What are the requirement?
2. How to setup BitLocker management server?
3. What are the per-cautions and best practices?

Thanks in well advance for brief guide.

Best Regards

Faisal