Posts

Server Manager will not start, error .NET Framework: "This application requires one of the following versions of the .NET Framework:"

Server Manager will not start on Windows Server 2019 after installing ADConnect. Error ServerManager.exe: This application could not be started. .NET Framework: "This application requires one of the following versions of the .NET Framework:xxxxx Do you want to install .NET framework now?" Of course it's already installed automatically on the server, so if you try and install it again you can't, error "already installed". Try the .NET repair package, can't repair the install. Try dsim.exe to install the package, error "Microsoft .NET Framework is already part of this installation". .NET Runtime version : 4.0.30319.0 - This application could not be started.This application requires one of the following versions of the .NET Framework:  v4.0.30319 The answer is to re-create the registry entries deleted when you installed ADConnect:- [HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\.NETFramework\v4.0.30319] "AspNetEnforceViewStateMac"=dw

Start virtualised domain controller in DSRM (Active Directory Restore Mode).

If you have a totally virtualised Active Directory infrastructure in Hyper-V, you can't boot the VM into  Directory Services Restore Mode  using F8. The keypress is not recognised. To get around this, in a elevated command prompt, type: bcdedit /set {globalsettings} advancedoptions true Now when you reboot the DC, it will ask if you want to boot into restore mode, and you can restore A.D. After rebooting, type the command: bcdedit /set {globalsettings} advancedoptions false and it will boot normally again. Now you have to find the restore mode password....

KB5017379 and KB5017270 delayed by 1 week

Microsoft updates KB5017379 and KB5017270 seem to have been delayed by a week, for some reason. They didn't appear in the normal patch Tuesday updates on 14 September 2022, but a week later on 21 September. Could be because of the Time Zone change for Chile in August?

Azure Site Recovery: The registration key has expired. Download a new registration key from Azure Site Recovery and select it. The downloaded file shouldn't be more than 5 days old.

When you are registering Microsoft Azure Site Recovery server you might get this message:- The registration key has expired. Download a new registration key from Azure Site Recovery and select it. The downloaded file shouldn't be more than 5 days old. It's really difficult to find this key, it took me more than an hour to find. Here is the location:- Log on to the Azure portal and browse to your Recovery Services Vault. Browse to  Manage/Site Recovery Infrastructure  >  Hyper-V Hosts   Click the  +Server  button at the top. Click the "Download the vault registration key to register the host" button.

Windows Server: File Server Resource Manager tasks: error occurred details: 0x8007007b

 Windows Server: File Server Resource Manager tasks: error occurred details: 0x8007007b I found this error after trying to save a task in the File Server Resource Manager / File Management Tasks: An error occurred while trying to persist changes to the file management task. Details: 0x8007007b, the filename, directory name or volume label syntax is incorrect. What this means to anybody who doesn't speak Microsoft, is that you used invalid characters in your name of the task. Re-create the task with only text and numbers, don't use anything that is not text or a number. none of these:- 0x00000022 (quotation mark) 0x0000002A (asterisk) 0x0000002F (forward slash) 0x0000003A (colon) 0x0000003C (less than) 0x0000003E (greater than) 0x0000003F (question mark) 0x0000005C (backslash) 0x0000007C (pipe or bar)  This happened to me because I had created the task in Server 2008R2 and then upgraded to 2012R2. After the upgrade the File Management Task no longer works.

P to V conversions of Window server

 Yes, we are still doing the occasional P to V conversion from hardware Windows Server to Hyper-V VM! You can still use Mark Russinovich's PtoV converter to do this, Sysinternals Disk2VHD. After you have done the P-toV the hardware, create a new VM in Hyper-V using Generation 1 machines. When booting, you need to create a BCD / Boot partition. Boot into recovery mode using the same Windows Server ISO, and boot to the CD/DVD. Select Recover and Command Prompt. Then type: bootrec /fixmbr bootrec /fixboot bootrec /rebuildbcd After that, you can boot again to the C drive.

Windows Server Servicing stack 10.0.17763.2170 rebooted our server

 Windows Server Servicing stack 10.0.17763.2170 rebooted our server automatically, no warnings. The process C:\Windows\system32\svchost.exe (xxxxx) has initiated the restart of computer xxxxx on behalf of user NT AUTHORITY\SYSTEM for the following reason: Operating System: Service pack (Planned)  Reason Code: 0x80020010  Shutdown Type: restart  Comment:  Thanks Microsoft. It wans't planned. More downtime caused by your automatic reboots.