ComputerMan

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 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.

 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 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.

If you enable Barracuda Cloud-to-Cloud backup, you might come across this error when trying to set it up: AADSTS7000112: Application '3450a114-871f-4057-b591-f0a8e3c50287'(Cloud-to-Cloud-Backup) is disabled. and if  you log into Azure AD and try the command: (Get-MsolServicePrincipal -AppPrincipalId 3450a114-871f-4057-b591-f0a8e3c50287).accountenabled you get the result $false. Then you can enable Barracuda Cloud-to-cloud Backup by typing: Get-MsolServicePrincipal -AppPrincipalId 3450a114-871f-4057-b591-f0a8e3c50287 | Set-MsolServicePrincipal -AccountEnabled $true

Does the security you have in place match the technology you are using? Is there a gap between your level of security, and the technology the security is there to protect? How do you measure that gap? If you have no security in place, but you are using latest technology in your business, are you putting that technology at risk? Why and how should you close the gap?

 Checklist of roles to move when decommissioning the Active Directory PDC - DNS (inc wpad blocking removal) - DHCP (remember to add helper to L3 switches first)  - A.D. PDC, RID Master, Schema Master, Domain naming master, Infrastructure Master - Any references to LDAP - If this is the root domain controller, remember to add a time source to the internet