I got this error while deploying Windows OS to my environment. It should be straightforward process, but somehow I got stuck with this. Clicking OK will restart the machine, and it still won't resolve the issue. Workaround? run msoobe.exe manually. Issue :  Windows setup could not configure Windows to run on this computer's hardware. Workaround :  Press Shift + F10 , command prompt window will opened  Change the directory to C:\Windows\System32\oobe CMD : cd C:\Windows\System32\oobe  execute msoobe.exe CMD :  msoobe or msoobe.exe  This screen appeared. Proceed with deployment.   Once all done, we'll be back to this screen, restart the machine by using command prompt or just click OK at the message box.

One line script - a quick note for myself. To find the service display name based on service name get-service -Name "<serviceName"> To find the service name based on service display name get-service -DisplayName "<serviceDisplayName">

It is a common practice for applications to have configurations set in INI file. It may contain information such as language, key, connection setting, version, and so forth. Updating INI file might not affect the application coding, but it may affect on how the application behave. There are multiple ways to update the file, one of it is by using Group Policy Preference ( GPP ).  In this example, I want to update a key file at a specific location with a specific information. Information :  File Location : C:\Temp\key\keyfile.key Content of AppsKey.key :           [Setup]           Key=XXXX-XXXX-XXXX-XXXX As mentioned by Microsoft here , below format must be followed : [SectionName] PropertyName1=PropertyValue1 PropertyName2=PropertyValue2 How To Do :  Edit the policy. Navigate to Preference | Windows Settings  Right click INI Files | New | Ini File  This screen will appear... Action = Different action will do different thing. Refer to the table below File Path =

This happened to my environment anew days ago, where I was not able to edit my group policy with below error. The GPO is working fine, just that I could not make any changes on it. Issues : Failed to open the Group Policy Object. You might not have the appropriate rights. Details : The system cannot find the path specified. Troubleshooting : Manually assigned delegated permission (with Edit settings, delete & modify security) - not working Tried to edit the policy from PDC Emulator server - not working Checked the availability of the GPO folder in SYSVOL, the GPO folder is available. Resolution : A bit of Googling, I got this : This is the issue, I executed the Procmon & found that process is trying to access the Registry.pol file under User folder under the policy path & it is failing to access, even though user configuration are not configured. It turned out, a folder named ' User ' was missing from the GPO folder, wh

Orait.. Let's talk about Enterprise Vault Outlook Plugin again... The project that I involved requires a few versions jump - from EV ver 9 to EV ver 12. The planning was to upgrade Plugin to version 12 first, followed by servers upgrade. According to EV Compatibility List ( https://www.veritas.com/support/en_US/article.000097605 ), the plugin will be supported if the server is either the same version(n), n-1 or n+1.  Now back to the issue. Due to version incompatibility between the plugin and the server, during my testing, there was an information box appeared whenever I opened my MS Outlook, as documented below. Issue : Received below error after upgrading EV Outlook Plugin from version 9 to version 12 (where the EV server was still at ver 9). This version of the Enterprise Vault Outlook Add-In is not compatible with the Enterprise Vault server version. Contact your Help Desk for details of how to resolve the issue. At the same time, the Enterprise Vault plugin