I don’t know who Brian is but calling his blog a joke is completely unprofessional.
WAIK is modular and requires you to import the install.wim before creating the unattend.xml file.īrian Desmond was showing how to generate the unattended answer file using WAIK in the following blog: The setupmgr.exe is like a wizard in which you answer series of question and it will generate an unattend.txt file. In Windows, you use the WAIK to create the unattended answer file. For XP and 2003, setupmgr.exe is used to create the unattended answer file called “sysprep.inf”. This is true in Windows XP and 2003, too. For mass deployments, an unattended answer file will be a huge help. You can sit in front of the PC and answer the questions. It’s not a big deal if you only have one or two PCs to clone.
The generalize and OOBE installation phases will prompt you with lot of questions. When you reboot the PC, you will start from the generalize phase followed by OOBE.
Learn about the terminology that Microsoft uses to describe software updates.On the GUI above, when you select the “OOBE”, check the “Generalize” box and select the “shutdown”, you are basically doing this: Troubleshooting Windows volume activation If you experience issues with any of these steps, call the customer support number 1-800-Microsoft (642-7676) to receive support. Reference the blog article to check the ESU key status. Verify that the ESU key is installed and activated successfully by using your script or the slmgr /dlv that you typically use.
Make sure that you are installing this update on the ESU eligible edition and supported architecture. Also, make sure that there is no restart pending on any of the updates. To do this, you can use the command Get-hotfix -id KB. Make sure that all the prerequisites mentioned in the "Prerequisites" section are installed successfully. If the installation of this update is unsuccessful, follow these troubleshooting steps: This update does not replace any previously released update. You do not have to restart your device after you apply this update. Note After activation, you can then continue to use your current update and servicing strategy to deploy ESU through Windows Update, Windows Server Update Services (WSUS), or whichever update management solution that you prefer.
For information about how to install and activate the ESU key, see the How to get Extended Security Updates for eligible Windows devices blog on the Microsoft Tech Community website. Install the following servicing stack update (SSU) and monthly rollup:Ĥ517134 Servicing stack update for Windows Server 2008 SP2: September 10, 2019Ĥ520002 October 8, 2019-KB4520002 (Monthly Rollup)
Stand Alone security update KB4474419 released to introduce SHA-2 code sign support on May 14, 2019. Stand Alone update, KB4493730 that introduce SHA-2 code sign support for the servicing stack (SSU) was released as a security update on Ap. Install the following SHA-2 code signing support update and servicing stack update (SSU) or a later SSU update: You must have the following installed on your on-premise device before you apply this update: Verify the successful installation of this update by using your regular process such as Update History. Install this update from one of the Release Channels such as Microsoft Update Catalog or Windows Server Update Services. This update is no longer available. See note at the top of the article. How to get this update Install this update Please call 1-800-Microsoft (642-7676) to receive support. Installing this update has no impact on getting security updates between now and January 14, 2020.įor technical support, customers must purchase Extended Security Updates and have an active support plan in place to get technical support on a product that has moved beyond the Extended Support date. This update is not applicable for Windows 7 Virtual Desktop (WVD) and Windows 7 Embedded OS.
This update can be installed on 圆4-based architecture for Windows Server 2008 SP2 and the Windows editions mentioned in Lifecycle FAQ-Extended Security Updates. Install this update on your on-premise devices that are eligible for ESU. This update is a test package we recommend that you deploy in your test environment. This update has no actual security content. This optional nonsecurity update will help you verify that your eligible Windows Server 2008 Service Pack 2 (SP2) devices can continue to get Extended Security Updates (ESUs) after the end of support date of January 14, 2020. Customers who have purchased the Extended Security Update (ESU) for on-premises versions of this OS must follow the procedures in KB4522133 to continue receiving security updates after extended support ends on January 14, 2020. For more information on ESU and which editions are supported, see KB4497181.To verify ESU eligibility, please use any Monthly Rollup or Security Only update released Februor later, such as KB4537810 or KB4537822.