Work out how much Space

https://rps.dewin.me/

work out bandwidth

https://rps.dewin.me/bandwidth/

Refs Calculator

http://dewin.me/refs/

 

 

  1. It is not a good idea to target the primary and backup copy job to the same repository as this negates the 321 rule and if an issue was to occur on that repository the primary and secondary copies of data would be lost.
  2. Instead it would be better to use a primary repository configured with ReFS and then have a secondary location configured with Windows Deduplication (Compression should be off instead of auto).
  3. It is not generally considered a good idea to have deduplication for the primary backup chain as this effects performance and increases RTPOs.
  4. The actual space savings depend on the change rate of the source data and the types of chains that are used on the ReFS repository. Also ReFS savings don’t show when viewed through file explorer. To learn more about checking the files savings please take a look at these links;

https://www.virtualtothecore.com/how-much-space-am-i-saving-thanks-to-refs-blockclone/

http://dewin.me/refs/

  1. Some limitation worth mentioning are Windows deduplication is for 4TB files so larger files will not be completely deduped. Also GFS doesn’t show ReFS savings until the point is synthesized as up to this point it will only shows as an incremental and changed blocked cannot be reused by ReFS pointers.

 

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

I needed to allows N-able Take Control 

The guide online showed that we had to whitelist  *.mspa.n-able.com , however the firewall could not whitelist Wildcard address. The static address’ are

  • melgw-mct01.mspa.n-able.com
  • sydgw-mct04.mspa.n-able.com
  • sydgw-mct05.mspa.n-able.com
  • sydgw-mct06.mspa.n-able.com
  • sydgw-mct07.mspa.n-able.com
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

VERBOSE: PowerShell meta provider initialization failed.
VERBOSE: PowerShell meta provider initialization failed.
PackageManagement\Import-PackageProvider : No match was found for the specified search criteria and provider name
‘NuGet’. Try ‘Get-PackageProvider -ListAvailable’ to see if the provider exists on the system.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:7302 char:25
+ …     $null = PackageManagement\Import-PackageProvider -Name $script:Nu …
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidData: (NuGet:String) [Import-PackageProvider], Exception
    + FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.ImportPackageProv
   ider

 

Run this before

 

To enabled TLS 1.2,  you may need to run this before

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

Sender Rewriting Scheme (SRS) functionality was added to Office 365 ( and other platforms ) to resolve a problem in which autoforwarding is incompatible with SPF.

SRS rewriting does not fix the issue of DMARC passing for forwarded messages. Although an SPF check will now pass by using a rewritten P1 From address, DMARC also requires an alignment check for the message to pass. For forwarded messages, DKIM always fails because the signed DKIM domain does not match the From header domain. If an original sender sets their DMARC policy to reject forwarded messages, the forwarded messages are rejected by Message Transfer Agents (MTAs) that honor DMARC policies.

 

So if you are forwarding emails , you can set SPF to Hard Fail , but DMARC you will not be able to fail due to DKIM

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

https://docs.microsoft.com/en-us/microsoft-365/admin/misc/become-the-admin?view=o365-worldwide

Had to go through this process for a customer, because their VLSC account was setup at some stage in the past using [email protected] VLSC account as a work or school account, the domain  was already registered against an unmanaged Azure AD directory, so we couldn’t set them up to use Teams. It’s a straight forward process just follow the article.

To find out if a domain is part of an unmanaged Azure AD directory, you can follow https://docs.microsoft.com/en-us/power-platform/admin/powerapps-gdpr-dsr-guide-systemlogs#determining-tenant-type as specified in the article.

 

VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)

For auditing purposes you will need to report on the updates install on a server and the install status. 

Below is a  powershell script that does just that

 

[email protected]('Unk','Installation','Uninstallation','Other')
[email protected]('Unk','In Progress','Succeeded','Succeeded With Errors','Failed','Aborted')

$updateSession=New-Object -ComObject Microsoft.Update.Session
$updateSearcher=$updateSession.CreateUpdateSearcher() 
$historyCount=$updateSearcher.GetTotalHistoryCount() 
$updateSearcher.QueryHistory(0, $historyCount) | 
    Select-Object Date,
                @{N='Operation';E={$operation[$_.operation]}},
                @{N='Status';E={$resultCode[$_.resultcode]}},
                Title |
    Format-Table -AutoSize
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)
  1. Download this on the phone : https://magiskmanager.com/
  2. Obtain your Phones most up-t0-date boot rom online ( e.g. boot.img ) 
  3. Copy this file to the phone
  4. Open up Magisk and choose install and Patch File Option
  5. Find the boot.img you just copied to the phone , once done it should create magisk_patched.img
  6. Copy magisk_patched.img back to the computer 
  7. Download https://www.getdroidpro.com/download-the-latest-adb-fastboot-android-sdk-platform-tools/ on your computer and navigate to directory, copy magisk_patched.img here 
  8. Put the phone into USB Debugging model – Go to About Phone, tap on the build number and tap 5 times  , Go back to setting and go to Developer Mode
  9. Accept the RSA key on the phone and trust 
  10. Navigate to the folder from step 7 in Command Prompt ( CMD )
  11. Enter “adb devices” to make sure the phone appaears
  12. Enter “adb reboot bootloader” to reboot the phone 
  13. Once booted enter “fastboot flash boot magisk_patched.img”
  14. One complete enter “fastboot reboot”
  15. Done
VN:F [1.9.22_1171]
Rating: 0.0/10 (0 votes cast)
VN:F [1.9.22_1171]
Rating: 0 (from 0 votes)