Microsoft has recently released a new tool aimed to simplify the configuration files required to make a custom deployment of Office in an organization. The tool, called Office Customization Tool for Click-To-Run, is currently in preview and provided as a cloud service available here.
Disable-PnpDevice “ACPI\NTN0530\0” -Confirm:$false
Set-MailContact -UseMapiRichTextFormat:Never
<Configuration> <Display Level=“Full” AcceptEULA=“True” />
<Property Name=“SharedComputerLicensing” Value=“1” />
<Add SourcePath=“C:\Office2016Install” OfficeClientEdition=“64” >
<Product ID=“O365ProPlusRetail”> <Language ID=“en-us” />
</Product> <Product ID=“VisioProRetail”> <Language ID=“en-us” />
</Product>
</Add>
</Configuration>
5. From a command prompt (with admin rights), run:
cd \Office2016Install setup.exe /download configuration.xml
6. Now run:
setup.exe /configure configuration.xml
The setup will now install.
$Server = remoteHostName
Invoke-Command -ComputerName $Server -ScriptBlock {(Get-WmiObject -class Win32_TSGeneralSetting -Namespace root\cimv2\terminalservices -Filter "TerminalName='RDP-tcp'").SetUserAuthenticationRequired(0)} #-Credential (Get-Credential)
https://support.microsoft.com/da-dk/help/4093492/credssp-updates-for-cve-2018-0886-march-13-2018″>https://support.microsoft.com/da-dk/help/4093492/credssp-updates-for-cve-2018-0886-march-13-2018
https://vorkbaard.nl/how-to-set-up-pfsense-high-availability-hardware-redundancy/
While Windows installed with Terminal Server role it does work without License for 120 Days on trail license, where within 120 days if the License server is not Connected the server will stop accepting connection with below error and event ID
The solution was to delete the REG_BINARY in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server\RCM\GracePeriod
Only leaving the default.
for ($i=1; $i -le "3"; $i++)
{
"Loop"
}
@%SystemRoot%\System32\inetsrv\appcmd set config -section:staticContent -+”[fileExtension=’.’, mimeType=’text/plain’]”
Generally the recommended path for upgrading a High Availability cluster is to first upgrade the secondary node. After it comes back up, disable CARP on the primary node under Status > CARP, and run on the secondary for a period of time. If the secondary node is running comfortably as desired, upgrade the primary node and it will switch back to MASTER status after rebooting for the upgrade.