cube maia

We recently configured this scenario to facilitate some internal testing. The below screen shots show the main areas to configure to get 2 or more back-end App Services hosting websites, Apis, etc, published via Azure Application Gateway and a single host name. This can be configured in various ways, and there are many other ways to do effect this functionality, e.g. API management. However, for our purposes the below worked ok for the situation.

You may already know that Azure Site Recovery (ASR) is encrypting data to ensure your data stay safe and secure.

Azure Site Recovery (ASR) is the disaster recovery solution from Microsoft running on Azure to help you manage and recover from disaster for your on-premises infrastructure.

As you may know, it is possible to use Azure Active Directory (Azure AD or AAD) for your consumer’s application authentication and user profile; this is called Azure Active Directory B2C (Business to Consumer).

More often than not we may have a large SCCM environment with thousands of collections. A common occurrence that I see in environments are when collections are created to report on applications that are installed that have multiple architectures (x86 and x64). An example may be that a collection has been created to find all instances of any family of Microsoft Office 2013 (x86 and x64) as part of an upgrade rollout planning.

Scenario

I recently had a customer who was having issues importing drivers into their SCCM environment.

Microsoft has released a security update to address CVE-2020-0601 to fix a dangerous flaw in Crypt32.dll impacting the Windows 10 and Windows Server 2016/2019 systems. Based on the advisory, “A spoofing vulnerability exists in the way Windows CryptoAPI (Crypt32.dll) validates Elliptic Curve Cryptography (ECC) certificates”. This also falls on the same day that the Windows 7 support has ended. This places many organisations that are still running Windows 7 systems in a vulnerable state.

We have all seen this in the past and no matter how hard we try to fix this BAU issue, and often we are pressed for time because this blocks a Task Sequence deployment, we find ourselves pulling our hair and having to buy a new keyboard (?).