WMI Reset 배치 파일

스크립트를 bat 파일로 만들어서 실행시키면 초기화된다. 

조건에 따른 쿼리문 종류는 다음과 같습니다.
Collection으로 지정은 PC 혹은 사용자를 대상으로 다양한 조건으로 생성이 가능합니다.
그 중에서 PC이름, IP주소, 사용자ID, OU(Organization Unit) 단위로 생성하는 쿼리는 알아보겠습니다.


PC이름

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where name in ("PC이름")

IP주소

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where IPSubnets in ("10.177.210.0")

사용자ID

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where lastlogonusername in ("userid")

OU(Organization Unit)

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.SystemOUName = "OU Path"

상기 Query 외에 전체 Collection 중에서 SC agent가 미설치된 PC만을 선별할 수 있다.

 미설치된 PC 수집

select SMS_R_SYSTEM.ResourceID,SMS_R_SYSTEM.ResourceType,SMS_R_SYSTEM.Name,SMS_R_SYSTEM.SMSUniqueIdentifier,SMS_R_SYSTEM.ResourceDomainORWorkgroup,SMS_R_SYSTEM.Client from SMS_R_System where SMS_R_System.Client is null

SCCM와 WSUS 관련 로그 설명

Client Log Files

• CAS - Content Access Service. Maintains the local package cache.

• Ccmexec.log - Records activities of the client and the SMS Agent Host service.

• CertificateMaintenance.log - Maintains certificates for Active Directory directory service and management points.

• ClientIDManagerStartup.log - Creates and maintains the client GUID.

• ClientLocation.log - Site assignment tasks.

• ContentTransferManager.log - Schedules the Background Intelligent Transfer Service (BITS) or the Server Message Block (SMB) to download or to access SMS packages.

• DataTransferService.log - Records all BITS communication for policy or package access.

• Execmgr.log - Records advertisements that run.

• FileBITS.log - Records all SMB package access tasks.

• Fsinvprovider.log (renamed to FileSystemFile.log in all SMS 2003 Service Packs) - Windows Management Instrumentation (WMI) provider for software inventory and file collection.

• InventoryAgent.log - Creates discovery data records (DDRs) and hardware and software inventory records.

• LocationServices.log - Finds management points and distribution points.

• Mifprovider.log - The WMI provider for .MIF files.

• Mtrmgr.log - Monitors all software metering processes.

• PolicyAgent.log - Requests policies by using the Data Transfer service.

• PolicyAgentProvider.log - Records policy changes.

• PolicyEvaluator.log - Records new policy settings.

• Remctrl.log - Logs when the remote control component (WUSER32) starts.

• Scheduler.log - Records schedule tasks for all client operations.

• Smscliui.log - Records usage of the Systems Management tool in Control Panel.

• StatusAgent.log - Logs status messages that are created by the client components.

• SWMTRReportGen.log - Generates a usage data report that is collected by the metering agent. (This data is logged in Mtrmgr.log.)

Server Log Files

• Ccm.log - Client Configuration Manager tasks.

• Cidm.log - Records changes to the client settings by the Client Install Data Manager (CIDM).

• Colleval.log - Logs when collections are created, changed, and deleted by the Collection Evaluator.

• Compsumm.log - Records Component Status Summarizer tasks.

• Cscnfsvc.log - Records Courier Sender confirmation service tasks.

• Dataldr.log - Processes Management Information Format (MIF) files and hardware inventory in the Configuration Manager 2007 database.

• Ddm.log - Saves DDR information to the Configuration Manager 2007 database by the Discovery Data Manager.

• Despool.log - Records incoming site-to-site communication transfers.

• Distmgr.log - Records package creation, compression, delta replication, and information updates.

• Hman.log - Records site configuration changes, and publishes site information in Active Directory Domain Services.

• Inboxast.log - Records files that are moved from the management point to the corresponding SMS\INBOXES folder.

• Inboxmgr.log - Records file maintenance.

• Invproc.log - Records the processing of delta MIF files for the Dataloader component from client inventory files.

• Mpcontrol.log - Records the registration of the management point with WINS. Records the availability of the management point every 10 minutes.

• Mpfdm.log - Management point component that moves client files to the corresponding SMS\INBOXES folder.

• MPMSI.log - Management point .msi installation log.

• MPSetup.log - Records the management point installation wrapper process.

• Ntsvrdis.log - Configuration Manager 2007 server discovery.

• Offermgr.log - Records advertisement updates.

• Offersum.log - Records summarization of advertisement status messages.

• Policypv.log - Records updates to the client policies to reflect changes to client settings or advertisements.

• Replmgr.log - Records the replication of files between the site server components and the Scheduler component.

• Rsetup.log - Reporting point setup log.

• Sched.log - Records site-to-site job and package replication.

• Sender.log - Records files that are sent to other child and parent sites.

• Sinvproc.log - Records client software inventory data processing to the site database in Microsoft SQL Server.

• Sitecomp.log - Records maintenance of the installed site components.

• Sitectrl.log - Records site setting changes to the Sitectrl.ct0 file.

• Sitestat.log - Records the monitoring process of all site systems.

• Smsdbmon.log - Records database changes.

• Smsexec.log - Records processing of all site server component threads.

• Smsprov.log - Records WMI provider access to the site database.

• SMSReportingInstall.log - Records the Reporting Point installation. This component starts the installation tasks and processes configuration changes.

• SMSSHVSetup.log - Records the success or failure (with failure reason) of installing the System Health Validator point.

• Srvacct.log - Records the maintenance of accounts when the site uses standard security.

• Statmgr.log - Writes all status messages to the database.

• Swmproc.log - Processes metering files and maintains settings.

Admin Console Log Files

• RepairWizard.log - Records errors, warnings, and information about the process of running the Repair Wizard.

• ResourceExplorer.log - Records errors, warnings, and information about running the Resource Explorer.

• SMSAdminUI.log - Records the local Configuration Manager 2007 console tasks when you connect to Configuration Manager 2007 sites.

Management Point Log Files

• MP_Ddr.log - Records the conversion of XML.ddr records from clients, and copies them to the site server.

• MP_GetAuth.log - Records the status of the site management points.

• MP_GetPolicy.log - Records policy information.

• MP_Hinv.log - Converts XML hardware inventory records from clients and copies the files to the site server.

• MP_Location.log - Records location manager tasks.

• MP_Policy.log - Records policy communication.

• MP_Relay.log - Copies files that are collected from the client.

• MP_Retry.log - Records the hardware inventory retry processes.

• MP_Sinv.log - Converts XML hardware inventory records from clients and copies them to the site server.

• MP_Status.log - Converts XML.svf status message files from clients and copies them to the site server.

Mobile Device Management Log Files

• DmClientHealth.log - Records the GUIDs of all the mobile device clients that are communicating with the Device Management Point.

• DmClientRegistration.log - Records registration requests from and responses to the mobile device client in Native mode.

• DmpDatastore.log - Records all the site database connections and queries made by the Device Management Point.

• DmpDiscovery.log - Records all the discovery data from the mobile device clients on the Device Management Point.

• DmpFileCollection.log - Records mobile device file collection data from mobile device clients on the Device Management Point.

• DmpHardware.log - Records hardware inventory data from mobile device clients on the Device Management Point.

• DmpIsapi.log - Records mobile device communication data from device clients on the Device Management Point.

• dmpMSI.log - Records the MSI data for Device Management Point setup.

• DMPSetup.log - Records the mobile device management setup process.

• DmpSoftware.log - Records mobile device software distribution data from mobile device clients on the Device Management Point.

• DmpStatus.log - Records mobile device status messages data from mobile device clients on the Device Management Point.

• FspIsapi.log - Records Fallback Status Point communication data from mobile device clients and client computers on the Fallback Status Point.

Mobile Device Client Log Files

• DmCertEnroll.log - Records certificate enrollment data on mobile device clients.

• DMCertResp.htm (in \temp) - Records HTML response from the certificate server when the mobile device Enroller program requests a client authentication certificate on mobile device clients.

• DmClientSetup.log - Records client setup data on mobile device clients.

• DmClientXfer.log - Records client transfer data for Windows Mobile Device Center and ActiveSync deployments.

• DmCommonInstaller.log - Records client transfer file installation for setting up mobile device client transfer files on client computers.

• DmInstaller.log - Records whether DMInstaller correctly calls DmClientSetup and whether DmClientSetup exits with success or failure on mobile device clients.

• DmInvExtension.log - Records Inventory Extension file installation for setting up Inventory Extension files on client computers.

• DmSvc.log - Records mobile device management service data on mobile device clients.

Operating System Deployment Log Files

• CCMSetup.log - Provides information about client-based operating system actions.

• CreateTSMedia.log - Provides information about task sequence media when it is created. This log is generated on the computer running the Configuration Manager 2007 administrator console.

• DriverCatalog.log - Provides information about device drivers that have been imported into the driver catalog.

• MP_ClientIDManager.log - Provides information about the Configuration Manager 2007 management point when it responds to Configuration Manager 2007 client ID requests from boot media or PXE. This log is generated on the Configuration Manager 2007 management point.

• MP_DriverManager.log - Provides information about the Configuration Manager 2007 management point when it responds to a request from the Auto Apply Driver task sequence action. This log is generated on the Configuration Manager 2007 management point.

• MP_Location.log - Provides information about the Configuration Manager 2007 management point when it responds to request state store or release state store requests from the state migration point. This log is generated on the Configuration Manager 2007 management point.

• Pxecontrol.log - Provides information about the PXE Control Manager.

• PXEMsi.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.

• PXESetup.log - Provides information about the PXE service point and is generated when the PXE service point site server has been created.

• Setupact.log Setupapi.log Setuperr.log Provide information about Windows Sysprep and setup logs.

• SmpIsapi.log - Provides information about the state migration point Configuration Manager 2007 client request responses.

• Smpmgr.log - Provides information about the results of state migration point health checks and configuration changes.

• SmpMSI.log - Provides information about the state migration point and is generated when the state migration point site server has been created.

• Smsprov.log - Provides information about the SMS provider.

• Smspxe.log - Provides information about the Configuration Manager 2007 PXE service point.

• SMSSMPSetup.log - Provides information about the state migration point and is generated when the state migration point site server has been created.

• Smsts.log - General location for all operating system deployment and task sequence log events.

• TaskSequenceProvider.log - Provides information about task sequences when they are imported, exported, or edited.

• USMT Log loadstate.log - Provides information about the User State Migration Tool (USMT) regarding the restore of user state data.

• USMT Log scanstate.log - Provides information about the USMT regarding the capture of user state data.

Network Access Protection Log Files

• Ccmcca.log - Logs the processing of compliance evaluation based on Configuration Manager NAP policy processing and contains the processing of remediation for each software update required for compliance.

• CIAgent.log - Tracks the process of remediation and compliance. However, the software updates log file, *Updateshandler.log - provides more informative details on installing the software updates required for compliance.

• locationservices.log - Used by other Configuration Manager features (for example, information about the client’s assigned site) but also contains information specific to Network Access Protection when the client is in remediation. It records the names of the required remediation servers (management point, software update point, and distribution points that host content required for compliance), which are also sent in the client statement of health.

• SDMAgent.log - Shared with the Configuration Manager feature desired configuration management and contains the tracking process of remediation and compliance. However, the software updates log file, Updateshandler.log, provides more informative details about installing the software updates required for compliance.

• SMSSha.log - The main log file for the Configuration Manager Network Access Protection client and contains a merged statement of health information from the two Configuration Manager components: location services (LS) and the configuration compliance agent (CCA). This log file also contains information about the interactions between the Configuration Manager System Health Agent and the operating system NAP agent, and also between the Configuration Manager System Health Agent and both the configuration compliance agent and the location services. It provides information about whether the NAP agent successfully initialized, the statement of health data, and the statement of health response.

System Health Validator Point Log Files

• Ccmperf.log -Contains information about the initialization of the System Health Validator point performance counters.

• SmsSHV.log - The main log file for the System Health Validator point; logs the basic operations of the System Health Validator service, such as the initialization progress.

• SmsSHVADCacheClient.log - Contains information about retrieving Configuration Manager health state references from Active Directory Domain Services.

• SmsSHVCacheStore.log - Contains information about the cache store used to hold the Configuration Manager NAP health state references retrieved from Active Directory Domain Services, such as reading from the store and purging entries from the local cache store file. The cache store is not configurable.

• SmsSHVRegistrySettings.log - Records any dynamic changes to the System Health Validator component configuration while the service is running.

• SmsSHVQuarValidator.log - Records client statement of health information and processing operations. To obtain full information, change the registry key LogLevel from 1 to 0 in the following location:HKLM\SOFTWARE\Microsoft\SMSSHV\Logging\@GLOBAL

Desired Configuration Management Log Files

• ciagent.log - Provides information about downloading, storing, and accessing assigned configuration baselines.

• dcmagent.log - Provides high-level information about the evaluation of assigned configuration baselines and desired configuration management processes.

• discovery.log - Provides detailed information about the Service Modeling Language (SML) processes.

• sdmagent.log - Provides information about downloading, storing, and accessing configuration item content.

• sdmdiscagent.log - Provides high-level information about the evaluation process for the objects and settings configured in the referenced configuration items.

Wake On LAN Log Files

• Wolmgr.log - Contains information about wake-up procedures such as when to wake up advertisements or deployments that are configured for Wake On LAN.

• WolCmgr.log - Contains information about which clients need to be sent wake-up packets, the number of wake-up packets sent, and the number of wake-up packets retried.

Software Updates Site Server Log Files

• ciamgr.log - Provides information about the addition, deletion, and modification of software update configuration items.

• distmgr.log - Provides information about the replication of software update deployment packages.

• objreplmgr.log - Provides information about the replication of software updates notification files from a parent to child sites.

• PatchDownloader.log - Provides information about the process for downloading software updates from the update source specified in the software updates metadata to the download destination on the site server.

• replmgr.log - Provides information about the process for replicating files between sites.

• smsdbmon.log - Provides information about when software update configuration items are inserted, updated, or deleted from the site server database and creates notification files for software updates components.

• SUPSetup - Provides information about the software update point installation. When the software update point installation completes, Installation was successful is written to this log file.

• WCM.log - Provides information about the software update point configuration and connecting to the Windows Server Update Services (WSUS) server for subscribed update categories, classifications, and languages.

• WSUSCtrl.log - Provides information about the configuration, database connectivity, and health of the WSUS server for the site.

• wsyncmgr.log -Provides information about the software updates synchronization process.

WSUS Server Log Files

• Change.log - Provides information about the WSUS server database information that has changed.

• SoftwareDistribution.log - Provides information about the software updates that are synchronized from the configured update source to the WSUS server database.

Software Updates Client Computer Log Files

• CAS.log - Provides information about the process of downloading software updates to the local cache and cache management.

• CIAgent.log - Provides information about processing configuration items, including software updates.

• LocationServices.log - Provides information about the location of the WSUS server when a scan is initiated on the client.

• PatchDownloader.log - Provides information about the process for downloading software updates from the update source to the download destination on the site server. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

• PolicyAgent.log - Provides information about the process for downloading, compiling, and deleting policies on client computers.

• PolicyEvaluator - Provides information about the process for evaluating policies on client computers, including policies from software updates.

• RebootCoordinator.log - Provides information about the process for coordinating system restarts on client computers after software update installations.

• ScanAgent.log - Provides information about the scan requests for software updates, what tool is requested for the scan, the WSUS location, and so on.

• ScanWrapper - Provides information about the prerequisite checks and the scan process initialization for the Inventory Tool for Microsoft Updates on Systems Management Server (SMS) 2003 clients.

• SdmAgent.log - Provides information about the process for verifying and decompressing packages that contain configuration item information for software updates.

• ServiceWindowManager.log - Provides information about the process for evaluating configured maintenance windows.

• smscliUI.log - Provides information about the Configuration Manager Control Panel user interactions, such as initiating a Software Updates Scan Cycle from the Configuration Manager Properties dialog box, opening the Program Download Monitor, and so on.

• SmsWusHandler - Provides information about the scan process for the Inventory Tool for Microsoft Updates on SMS 2003 client computers.

• StateMessage.log - Provides information about when software updates state messages are created and sent to the management point.

• UpdatesDeployment.log - Provides information about the deployment on the client, including software update activation, evaluation, and enforcement. Verbose logging shows additional information about the interaction with the client user interface.

• UpdatesHandler.log - Provides information about software update compliance scanning and about the download and installation of software updates on the client.

• UpdatesStore.log - Provides information about the compliance status for the software updates that were assessed during the compliance scan cycle.

• WUAHandler.log - Provides information about when the Windows Update Agent on the client searches for software updates.

• WUSSyncXML.log - Provides information about the Inventory Tool for the Microsoft Updates synchronization process. This log is only on the client computer configured as the synchronization host for the Inventory Tool for Microsoft Updates.

Windows Update Agent Log File

• WindowsUpdate.log - Provides information about when the Windows Update Agent connects to the WSUS server and retrieves the software updates for compliance assessment and whether there are updates to the agent components

In this article, I’ll show you how to use the SCCM feature update option to perform a Windows 10 22H2 upgrade. We will use Windows Servicing in SCCM to upgrade Windows 10 devices to version 22H2 via the enablement package.

Windows 10, version 22H2, also known as the Windows 10 2022 Update, is available for eligible devices running Windows 10, versions 20H2 and newer. Microsoft released Windows 10, version 22H2 (KB5015684) on 18th October 2022, and it is an enablement package.

For home users running Windows 10 version 20H2 and later, the recommended way to get the Windows 10 22H2 is via Windows Update. Go to Start > Settings > Windows Update and run Check for Updates. Select the Feature update to Windows 10, version 22H2 and install it.

When you want to upgrade multiple Windows 10 devices to version 22H2, Configuration Manager is the best tool. It simplifies the way you deploy and manage updates and saves a lot of time. With Configuration Manager, you can select the “Feature Update to Windows 10 Version 22H2 via Enablement Package” and deploy it to a set of devices.

Ways to upgrade to Windows 10 22H2

There are multiple ways that you can use to upgrade to Windows 10 version 22H2.

• Get the Windows 10 22H2 update via Windows Update.
• Use Servicing Plans to upgrade eligible Windows 10 devices to version 22H2.
• Upgrade Windows 10 21H2 to Windows 10 22H2 using ConfigMgr Windows Servicing feature.
• Deploy the Windows 10 22H2 update using the SCCM task sequence.
• Using the Intune to upgrade to Windows 10 22H2 upgrade for WUfB managed devices.

We will use the Configuration Manager feature update option to deploy the Windows 10 22H2 enablement package out of all the above methods. This is the easiest and quickest way I can think of to update Windows 10 to version 22H2.

Recommended: Upgrade to Windows 10 21H2 using SCCM | ConfigMgr

Can I use SCCM Servicing Plans to Upgrade to Windows 10 version 22H2?

Yes, you can use the Servicing Plans in SCCM to upgrade the computers running Windows 10 to version 22H2. With Configuration manager servicing plans you can ensure that all the Windows 10 systems are kept up-to-date when new builds are released. Servicing plans are ADR that can help you to upgrade Windows 10 to version 22H2. Take a look at detailed guide on Windows 10 Servicing Plans in SCCM.

If you are unsure whether to upgrade to Windows 10 22H2 using a Servicing Plan or a feature update deployment, I would advise choosing the latter. There are only a few steps involved in deploying a Windows 10 22H2 feature update, making it much simpler than a servicing plan. You get to make the final decision.

Related Article: Windows 11 22H2 upgrade using SCCM | ConfigMgr

About Windows 10 version 22H2

Windows 10 22H2 is an enablement package and this is good news for admins. The enablement package is a great option for installing a scoped feature update like Windows 10, version 22H2. You can upgrade from version 2004, 20H2, 21H1, or 21H2 to version 22H2 with a single restart, reducing update downtime. Since Windows 10 22H2 is an enablement package, the devices currently on Windows 10, version 20H2 or newer will have a fast installation experience because the update will install like a monthly update.

Prerequisites

With Configuration Manager, you need few things to be configured before you deploy the feature updates to computers. If you have deployed the feature updates before, it means most of the prerequisites are already taken care of. If your SCCM setup is new, you may have to configure them once before deploying the upgrades.

Listed below are all the prerequisites required for Windows 10 22H2 upgrade using SCCM.

• Configure Software Update Point by enabling the upgrades for Windows 10 and Windows 11.
• Ensure the service connection point is online.
• Enable dynamic update for feature updates in Configuration Manager Client Settings.
• Windows 10 1903, and later product must be enabled under Software Update Point > Products.

Download Windows 10 22H2 Enablement Package

Let’s look at steps for downloading Windows 10 22H2 enablement package using SCCM. First of all ensure you have synchronized the updates in Configuration Manager. You can either download the feature first and deploy or directly deploy the feature update. I prefer to download it first, let the content get distributed to distribution points and then deploy it.

Go to Software Library > Overview > Windows 10 Servicing > All Windows 10 Updates. Look for the update “Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package“. You can also search the updates with article ID 5015684.

Download Windows 10 22H2 Enablement Package

If you have got both x64-based systems and x86-based systems, you must download Feature Update to Windows 10 Version 22H2 x64-based and x86-based. In my lab, all my Windows 10 VMs are running Windows 10 64-bit OS, and therefore I am going to download only Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package.

Create Deployment Package

On the Deployment package window, specify the deployment package for Windows 10 22H2 upgrade files. This deployment package that you create will contain the software update files that will be deployed to the clients.

Select Create a new deployment package and specify the package name as “Windows 10 22H2 Deployment Package.” Add a brief description and specify the package source – a shared folder where you want to download the updates. Enabling the binary differential replication is optional. Click Next.

Download Windows 10 22H2 Enablement Package

Click on Add button and select the distribution point servers to which you would like to distribute the Windows 10 22H2 upgrade files. Click Next.

Download Windows 10 22H2 Enablement Package

On the Distribution Settings page, you can specify the general distribution settings for the deployment package. Click Next.

Specify the Deployment Package Distribution Settings

The download location lets you select an option to download the updates from. For example, you can download the software updates directly from internet or choose to download the software updates from the location on network. Select the option “Download software updates from the internet“. Click Next.

Choose the Download Location for Updates

Specify the update language for the products. The default language is English US. Click Next.

Select Update Languages for Products

Review the Windows 10 22H2 deployment package settings and close the Download software updates wizard.

Close Download Software Updates Wizard

Note: In case you encounter issues while downloading the Windows 10 22H2 enablement package update, review the PatchDownloader.log located in the %temp% folder. This log file will log all the errors that occur during the download of Windows 10 feature updates.

In the above step, the files required to upgrade Windows 10 to version 22H2 are downloaded to the specified location. If you browse to the downloaded location, you will notice that Windows 10 22H2 enablement package contains only one update which is Windows10.0-KB5015684-x64. The size of the Windows 10 22H2 enablement package is 32 KB. This one file is sufficient to upgrade Windows 10 computers to version 22H2.

Windows 10 22H2 Enablement Package

Deploy Windows 10 22H2 Feature Update using SCCM

In this step, using the Windows Servicing, we will perform the Windows 10 22H2 feature update deployment using Configuration Manager. You can deploy the feature update to a single client or to multiple devices using device collection.

If you are deploying the Windows 10 22H2 update for the first time, I suggest testing the upgrade on a Pilot device collection. A few devices that are intended to test the upgrade to 22H2 should be included in this device collection. Use the following guide to create a device collection for Windows 10 computers in SCCM.

Recommended Article: Upgrade Windows 10 21H1 using SCCM | ConfigMgr

Use the following steps to deploy the Windows 10 22H2 feature update using SCCM:

• In the ConfigMgr console, navigate to Software Library\Overview\Windows Servicing\All Windows Feature Updates.
• Right-click Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package update, and select Deploy.

Deploy Windows 10 22H2 Feature Update using SCCM

On the General page, enter the details for Windows 10 22H2 feature update deployment.

• Deployment Name: Enter a suitable name such as Deploy Windows 10 22H2 Enablement Package.
• Description: Although it’s optional, you may add a brief description.
• Software Update Group: This is created automatically and is visible under Software Update Groups in Configuration Manager console.
• Collection: Click Browse and select a device collection consisting of few pilot devices selected for testing Windows 10 2022 upgrade.

Click the Next button to continue.

Deploy Windows 10 22H2 Feature Update using SCCM

On the Deployment Settings page, specify the type of deployment. Choose whether you want to make the Windows 10 22H2 upgrade available for users in the Software Center or deploy it as required. Read more about SCCM Available vs. Required to know the differences. Click Next.

Deploy Windows 10 22H2 Feature Update using SCCM

The Scheduling page lets you configure schedule details for the deployment. Configure the following settings:

• Schedule Evaluation | Time Based on: Select Client Local Time.
• Software Available Time: As soon as possible.

If you want to make the Windows 10 22H2 upgrade available at a specific date and time, select Specific time and define them. Define the deadline installation to ensure the upgrade happens in the defined period.

Click Next to continue.

Deploy Windows 10 22H2 Feature Update using SCCM

Specify the following user experience settings for the deployment.

• User Notifications: Display in Software Center and show all notifications
• Commit changes at the deadline or during a maintenance window (requires restarts): Yes
• If any update in this deployment requires a system restart, run updates deployment evaluation cycle after restart: No.

Click Next.

Deploy Windows 10 22H2 Feature Update using SCCM

On the Download settings page, specify the download settings for the current deployment:

• Client Computers can use distribution points from neighbor boundary: No
• Download and install software updates from the fallback content source location: Yes

Click Next to continue.

Deploy Windows 10 22H2 Feature Update using SCCM

Review the deployment settings of Windows 10 22H2 on Summary page and click Next. On the Completion window, click Close.

Deploy Windows 10 22H2 Feature Update using SCCM

Windows 10 22H2 Servicing: End-User Experience for Upgrade

After you have deployed Windows 10 22H2 enablement package update using Windows Servicing, it’s time to test the upgrade installation on end computers. The end-user experience is similar to other feature upgrades.

On the client computer, first launch the Software Center. Once the Software Center has been opened, select Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package update by clicking the Updates tab. Click on the Install button.

Windows 10 22H2 Upgrade Servicing: End-User Experience

Confirm you want to upgrade the operating system on this computer. It will take only few minutes to upgrade the operating system as this is an enablement package. Note that this is an in-place upgrade to version 22H2, and the setup automatically migrates your apps, data, and settings. Click on the Install button to begin the Windows 10 22H2 upgrade.

Windows 10 22H2 Upgrade Servicing: End-User Experience

The Feature Update to Windows 10 Version 22H2 x64-based systems 2022-10 via Enablement Package is installed in less than 2 minutes. Click on Restart.

Restart the Computer to Complete Windows 10 22H2 Upgrade

On the confirmation box, click Restart.

Restart the Computer to Complete Windows 10 22H2 Upgrade

The Windows 10 22H2 upgrade is complete. Log in to the Windows 10 computers and click Start > About My PC. Under Windows Specifications, you will find the build number and version of Windows 10. In the below screenshot, we see the Windows version is “22H2” and the OS build number is 19045.2006.

Verify the Windows 10 22H2 Version and Build Number

After you have upgraded multiple Windows 10 computers to version 22H2, you can create a device collection in SCCM. Refer to this article to learn how to create Windows 10 22H2 device collection using WQL Query. If you want to get to Windows 11, you can upgrade to Windows 11 using different methods.

1. 역할(Role)과 기능(Feature) 설치
서버관리자를 열어 몇가지 추가 기능들을 설치만 하면 윈도우8과 같은 UI를 얻게 됩니다. 권장 설치 목록은 Hyper-V, 닷넷프레임워크, 데스크톱경험(Desktop Experience) 정도이고, 필요시에 텔넷클라이언트와 무선랜서비스를 추가하면 됩니다.
설치를 진행하면 두번 이상 자동으로 재부팅되며 Metro 타일화면까지 진행됩니다. 바탕화면을 우클릭해보면 개인설정(Personalize)가 생겨 있습니다.

2. ping 허용, ipv6 제거
C:\> netsh advfirewall firewall add rule name="ICMP Allow incoming V4 echo request" protocol=icmpv4:8,any dir=in action=allow

C:\> services.msc 명령어를 통해 서비스관리자를 호출하여 "IP Helper" 서비스를 중단(disable)시키고, 랜카드 속성에서 TCP/IPv6 부분을 체크해제

3. IE 보안 강화 구성 해제

Server 를 설치하고 난뒤 몇몇 어플리케이션을 다운로드 받아서 설치해야하는데 기본적으로 IE를 실행하게 되면 보안 강화 구성 때문에 사이트 연결때마다 알림창이 떠서 귀찮게 하죠

서버 관리자 창 -> 로컬 서버 선택 -> 속성 창의 오른쪽 중앙 -> IE 보안 강화 구성 선택 -> 관리자/사용자 모두 사용안함으로 선택

4. 계정 암호 복잡성 규칙 및 유효기간 해제하기

Windows Server는 암호를 정할때 대문자 소문자 특수문자 숫자가 꼭 포함이 되어야만 복잡성을 통과해서 암호 설정이 됩니다.

서버 관리자 창 -> 우측 상단의 도구 -> 로컬 보안 정책 -> 계정 정책 -> 암호 정책

암호는 복잡성을 만족해야함 : 해제
최대 암호 사용기간 : 0 으로 설정

5. 사용자 계정 추가 및 Administrator 계정 이름 변경

Admin 권한을 가진 계정을 새로이 생성하고 Adminitrator 계정은 그 이름을 바꿔주는 것이 보안 측면이 좋다고 하기에 새로운 계정을 생성하고 Admin계정 권한을 부여한뒤 Administrator 이름을 변경하였습니다.

계정 추가 방법은 제어판 -> 사용자 계정 -> 다른 계정 관리 -> 사용자 계정 추가 를 선택 하시면 됩니다.

    Admin 계정 변경 방법 : 서버 관리자 창 -> 우측 상단의 도구 -> 로컬 보안 정책 -> 로컬 정책 -> 보안 옵션

     -> Administrator 계정 이름 바꾸기 -> 변경하고자 하는 이름으로 변경

6. 원격 데스크톱 활성화

홈서버에는 모니터와 키보드, 마우스를 연결하지 않고 본체만 항상 켜두기때문에 서버 관리를 위해서 RDP를 활성화 해줘야만 Windows Server 2012에 접속해서 이것저것 관리를 할 수가 있습니다.

서버 관리자 창 -> 로컬 서버 선택 -> 속성창 왼쪽 중앙 -> 원격 데스크톱 선택 -> 이 컴퓨터에 대한 원격 연결 허용 선택 -> 네트워크 수준 인증을 사용하여 원격 데스크탑을 실행하는 컴퓨터에서만 연결 허용(권장) 해제

끝.

SCCM 2007 Client Push Installation 시 Windows firewall 에서 아래 항목이 예외로 설정되어야 합니다.

·         File and Printer Sharing

·         Windows Management Instrumentation (WMI)

  그리고, Client push 시 사용되는 포트입니다.

SCCM-2012-prereq-install.PS1

파워쉘을 메모장으로 연 후 25번 라인 수정한다. 

 $folderpath0 = 'C:\Source'   

해당 파워쉘은 아래와 같은 수행을 시작한다.

#Download Windows Assessment and Deployment Kit (ADK) 8.1

#Download Microsoft Deployment Toolkit 2013 

# Install Windows Features.

  Get-Module servermanager

  Install-WindowsFeature Web-Windows-Auth

  Install-WindowsFeature Web-ISAPI-Ext

  Install-WindowsFeature Web-Metabase

  Install-WindowsFeature Web-WMI

  Install-WindowsFeature BITS

  Install-WindowsFeature RDC

  Install-WindowsFeature NET-Framework-Features

  Install-WindowsFeature Web-Asp-Net

  Install-WindowsFeature Web-Asp-Net45

  Install-WindowsFeature NET-HTTP-Activation

  Install-WindowsFeature NET-Non-HTTP-Activ

끝.