ComputerMan

 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

I am trying to run the Lignering Object Liquidator (LoL) on my Domain Controllers. But some DC's are Server Core and don't have .Net installed. So I have to run it on a DC with a GUI and connect to the DC with server core. But then I found this error message:  "Failed to create event log subscription to target DC". win rmquickonfig reports WinRM is already set up for remote management on this computer. So I tried turning off the firewall altogether:- Set-NetFirewallProfile -Profile Domain,Public,Private - Enabled True And run the LOL again.  That worked! Of course don't forget to turn the firewall back on again immediately afterwards.

 If you have a server running in Azure you cant log into anymore. You can use the Serial Console to get into the server. But there are not many commands, espeically if you can't log into a command prompt. I wanted to set the network adapter, as it had lost the Gateway. Here is the command to see the network adapters config: SAC>i Net: 4, Ip=172.22.10.9  Subnet=255.255.255.0  Gateway=0.0.0.0 As you can see, the Gateway has been set to 0.0.0.0 To set a new Gateway, issue the command: i 4 172.22.10.9 255.255.255.0 172.22.10.1 Where the number 4 is the identified for the network adapter. Now I can ping my VM again!

Updates may be available for your Azure AD trust.  Update your trust now to ensure you have the latest recommended settings. Don't Panic!