Recently has a user on a terminal server trying to change their login and licenses account to active Office 365. The user logged into Office , but Office came up with “couldn’t verify account”

 
Had to change the cache : 
 
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\Configuration
Change Key: SCLCacheOverride to “1”
 
Set SCLCacheOverride to 1 if you’re using shared computer activation and you want to roam the licensing token.
 
and whipe files in
In my case, affected users had 4 files/tokens in
C:\Users\%username%\AppData\Local\Microsoft\Office\16.0\Licensing
GD Star Rating
loading...
GD Star Rating
loading...

AADSync installed on a domain controller running as “Auto-generated standalone Managed Service Account”

Domain controller was rebooted as part of another task then “Microsoft Azure AD Sync” couldn’t start.

Searching for the above error, no solution except reinstalling, but unfortunately no configuration details to replicate. Repair also did not fix the issue.

Digging deeper in application logs, noticed SQL errors which turned out to be the cause

SOLUTION:

 

Replace two files, model.mdf and modellog.ldf.

 

Copy from: C:\Program Files\Microsoft SQL Server\150\LocalDB\Binn\Templates

 

Copy to: C:\Users\ADSyncxxxxx$\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ADSync2019

Or

Copy to: C:\Windows\ServiceProfiles\ADSync\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\ADSync2019

 

Destination varies according to installed version.

GD Star Rating
loading...
GD Star Rating
loading...

# config system link-monitor

 (link-monitor) # show
config system link-monitor
edit “1”
set srcintf “wan1”
set server “8.8.8.8”
next
end

GD Star Rating
loading...
GD Star Rating
loading...

Recently restricted an AWS Elastic Beanstalk App so it could only be accessed through a specific DNS host name which was routed through Cloudflare for Security

This parameter is located in archive.xml in \site_content\archive.xml

<binding protocol=”http” bindingInformation=”*:80:subdomain.domain.com” sslFlags=”0″ MSDeploy.sslFlags=”1″ />

GD Star Rating
loading...
GD Star Rating
loading...

SQL Licensing

Software Assurance

 License Mobility refers to the ability to move virtual instances from host to host and between server farms. SQL server needs Software Assurance for License Mobility.

Software Assurance can only be added after the fact if the above 90 day condition is met. Otherwise it must be purchased alongside the license itself. Software Assurance also cannot be added to existing License only volume licensing regardless of when it was purchased. 

SQL Server

Please note that there are 2 ways of licensing SQL Server Standard:

  • Per-Core Model
    • All physical cores must be licensed if run on the physical host or
    • All cores assigned to the virtual machine must be licensed if run in a virtual environment
    • A minimum of 4 cores must be licensed per virtual OSE or per physical processor (depending on how it will be deployed)
    • The core licenses come in packs of 2, so a minimum of 2 are required to be purchased.
    • No SQL Server CAL’s are required to access the server
  • Server / CAL Model
    • One license is needed to run one instance of SQL Server on the host
    • SQL Server User or Device CAL’s are required to connect to the Server either directly or indirectly

 

GD Star Rating
loading...
GD Star Rating
loading...

Recently had a site to site tunnel randomly drop , fix was to  Set set npu-offload disable 

 

config vpn ipsec phase1-interfaceeditset npu-offload disableend

GD Star Rating
loading...
GD Star Rating
loading...