I came across the following error whilst trying to install Veeam Backup & Replication 11.0.0.837 on Windows Server 2022:
|
1 |
Setup Failed. Installation was interrupted before application could be installed. You need to restart the installer to try again… |
Installation logs are saved under:
|
1 |
C:\ProgramData\Veeam\Setup\Temp |
in BackupSuite_DD_MM_YYY_HH_MM_SS.txt format but they do not necessarily give away the reason for the setup failure:
Continue reading
This guide explains how to configure Windows Server 2022 to synchronise time with an external Network Time Protocol (NTP) source in an Active Directory environment. The normal design is to configure the PDC Emulator in the forest root domain to use an external time source. Other domain controllers, member servers and workstations should normally continue to synchronise through the Active Directory domain hierarchy.
If you are maintaining an older environment, see the companion guide for configuring external NTP time synchronisation on Windows Server 2008 R2 SP1.
Accurate time is important for Active Directory and Kerberos authentication. If clocks drift too far apart, users and services can experience authentication problems.
Important: These instructions are for a conventional AD DS domain. Do not configure every domain controller to use an external NTP server. In a multi-domain forest, identify the PDC Emulator in the forest root domain, not simply the PDC Emulator in the domain you happen to be working in.
Continue reading
If you’re about to upload Hyper-V or VMware vSphere virtual machine(s) to Microsoft Azure you need to properly configure the connection in Microsoft Virtual Machine Converter.
Subscription ID (which everyone should hopefully know), as well as Certificate Thumbprint are required to make this happen. Subscription ID can be retrieved either via the management portal or Get-AzureSubscription commandlet but Certificate Thumbprint is not so easy.
Here is the MVMC screen I’m on about:
If you have connected to your Azure subscription in the past using Powershell, chances are you already have the certificate that’s required. In my case, I like to keep things separated so thought it would be best to generate a new cert and use that cert specifically for MVMC related tasks.
Continue reading
You would have thought that installing .NET 3.5 on Windows 8 will be relatively straight forward – wrong answer!
The easiest way to do this is to go to Control Panel –> All Control Panel Items –> Programs and Features and simply add .NET Framework 3.5 (includes .NET 2.0 and 3.0)
but you are likely to hit one of the following errors:
“Windows couldn’t complete the requested changes. Windows couldn’t connect to the internet to download necessary files. Make sure that you’re connected to the internet, and click ‘Retry’ to try again. Error code: 0x800F0906”
“Update NetFx3 of package Microsoft .NET Framework 3.0 failed to be turned on. Status: 0x800F0906.”
“Update NetFx3 of package Microsoft .NET Framework 3.0 failed to be turned on. Status: 0x800F081F.”
“Update NetFx3 of package Microsoft .NET Framework 3.0 failed to be turned on. Status: 0x800F0907.”
Continue reading
My workplace has finally decided to start encrypting their mobile devices with BitLocker. After number of laptops completed successfully (and without any major issues) today we have hit problems when BitLocker wizard would fail with the following message:
So far only one machine was affected but there could easily be others. Solution to this issue was not immediately obvious but its essentially due to Windows (or BitLocker wizard) not being able to shrink the drive to create the system partition that’s required for BitLocker (there was only one partition). Trying to manually shrink the drive using Disk Management would not work too as “Size of available shrink space in MB:” was equaling to 0:
Now this number was showing 44MB before I ran Windows Defrag tool but now is 0MB meaning you cannot shrink the drive at all (not even by 1MB!) In Windows Explorer, internal hard drive was showing 120GB in size with roughly 60GB free so there was plenty of free disk space available in order to re-size the partitions.
Two quick fixes that were applied to finally resolve this are as follows:
After this I re-run BitLocker drive encryption wizard and all was happy again!
Side note – trying to manually prep the drive using bdehdcfg i.e. bdehdcfg -target c: shrink -size 300 -quiet -restart was not working too.
Something rather strange crept up today and its do to with non-Unicode language settings in Windows 7 which weren’t working properly. Basically some of our printers didn’t print barcodes properly and after some extensive troubleshooting the culprit was language in Windows that was set to English (United States) instead of English (United Kingdom) You can find system locale settings for non-Unicode programs under:
|
1 |
<strong>Control Panel --> Region and Language --> Administrative tab --> Change system locale...</strong> |
Another quick post to show how you can quickly deploy fully working DHCP server with multiple scopes in a matter of seconds. In my case it was a single server with 90 very different scopes and doing this manually would be just soo boring and long that’s unreal. Unfortunately Windows Server 2012 wasn’t an option so no PowerShell love but Windows Server 2008 R2 is still pretty decent and using netsh wasn’t as painful as it seemed. To get us started we need to install the DHCP Server role and start the required service (dhcpserver):
|
1 2 3 |
<strong>start /w ocsetup DHCPServer sc config dhcpserver start= auto net start dhcpserver</strong> |
Next step is to authorize DHCP server in the enterprise so we can actually use it to dish out IP addresses:
|
1 |
<strong>netsh dhcp add server %COMPUTERNAME% ip_address_goes_here</strong> |
Other useful commands here would include:
To deauthorize the server –
|
1 |
<strong>netsh dhcp delete server %COMPUTERNAME% ip_address_goes_here</strong> |
and to list all authorized servers –
|
1 |
<strong>netsh dhcp show server</strong> |
This is an older Windows Server 2008 R2 SP1 walkthrough. For a current Windows Server deployment, see the updated guide to configuring external NTP time synchronisation on Windows Server 2022.
Quick post to show how you can sync your domain controllers with external time source (time.windows.com or ntp.pool.org for example). By default, all machines in the domain will sync time from the domain controller which is the internal time server – if you have more than one DC then time will sync from the DC that holds the PDC emulator FSMO role. To check which DC is PDC emulator in your domain you need to run netdom /query fsmo command like so:
Once PDC emulator role is established there is few commands we need to run in order for time to sync, these are (run on PDC emulator):
Windows Server 2008 R2 VMs started giving me errors while joining the domain recently, here is the exact error message that comes up:
netsetup.log (%SystemRoot%\debug\netsetup.log) shows no errors and my VMs appears to be joined properly:
Now to fix this there are two potential solutions/recommendations:
Continue reading
Another quick post to show how to list installed programs in Add/Remove programs on local and/or remote machine(s).
wmi is what makes this possible and the command we need on local machine is as follows:
wmic product get name,version
– on remote one we have to add node parameter to our wmi statement:
wmic /node:”FQDN_Goes_Here” product get name,version
Either one can be exported by adding:
/format:csv > Export.csv
at the end.
That’s it!