Kevin Oppihle's Tech Notes

PEC is an Italian Certified Email service or posta elettonica certificata I learned about PEC while doing an email migration for an Italian client. They were concerned about PEC email flow using Office 365. What I found is that PEC email is not a service Office365 offers. My understanding of PEC email is that it is a hosted email service that must be Certified as a PEC email provider. That provider uses certificates to verify that email created by the end user when in transit to the email service provider and to the end recipient is "certified" by the PEC service provider. To get a PEC account they will have to fill in their personal information and likely upload identification documents and Italian tax code. They will then have an address such as username@PEC.it or username@legalmail.it as you can see this is not the same as a standard business or third party domain such as a username@business.com so it is its own email flow. Long story short relating this to regular

When you attempt to open a Microsoft Access file you receive the error “Network Access Interrupted”. If the file is truly on the network this issue may be caused by the file being locked by another PC. You can close the file and confirm with an Admin that the file is not locked and reattempt access. However if it is a local file and you get this error when trying to open an existing file. Try to create a new local Access DB file and see if the issue persists. If it does it is likely related to a corrupted file in the Access AppData directory. A full re-installation of Office does not appear to resolve the issue. To purge the corrupted file go to C:\Users\%username%\AppData\Roaming\Microsoft\Access and delete the file in that directory. Reopen Access and attempt to create a new Access DB and it will recreate that file as necessary. Now the error should be gone when you open your other local Access files. Note: This was caused in my case by migrating a users profile from one PC t

After successfully migrating from FRS to DFSR you get the File Replication NtFrs service is Stopped error on the local servers AD DS Services list. In the Event logs you may see Event id 13575 13577. You can confirm your migration completed by opening a cmd prompt as administrator and typing in: dfsrmig /getmigrationstate After your migration to DFSR is completed and you have given your servers ample time to propagate this service is no longer required. Since it is set to “Automatic”, as shown below” it shows in logs as a false positive error. Edit the File Replication Service and change it to “Disabled”, as shown below: Once it is listed as “Disabled” it will no longer show in the Console as an “error” Note : it may take some time to clear from the active view

Open Powershell as an Administrator and run “Get-ADSyncScheduler” as shown below: Note SyncCycleEnabled is “False” you want that to be “True” for automated Synchronization. To change that type in “Set-ADSyncScheduler –SyncCycleEnabled $True” as shown below and enter. To confirm the setting applied run “Get-ADSyncScheduler” again and review results. Your Azure AD Sync automation should now be back online Credit: https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler

Local permissions will not properly delegate to Office 365 One drive as of the creation of this doc. I recommend setting up groups locally and do not sync those to 365 for local permissions. You will then need to mirror those permissions in One Drive. To do that the easiest way is to use Teams on 365. Create Microsoft Teams for each group needing access to OneDrive cloud share: Create Team and set permissions to Private so random domain users cant join without proper approval: Add Members: Change anyone that should have admin control to “owner” all others should remain members: Open up the OneDrive share to set permissions. Select Files and to select Details: Select Manage Access in the right hand window: Select “Grant Access” at the top and enter in your Team Group name: You can uncheck Notify People so they don’t get lots of random invites and select “Grant Access”: The members of that group can then access that share. The easiest way to navigate to it is to copy that share from the

When I setup multiple offsite backup jobs they were set to run only on Monday-Thursday due to a larger backup job running on Friday that takes over 36 hours to complete, due to limited internet bandwidth. However, the backup jobs would run on Saturday? The first clue is when you view the last backup you see at the top “Active Full” In Storage> Advanced I forgot that under the Backup Job settings I designated Saturday as the day to run “Active Full”: That setting overrides the settings on “On these days”. I changed my Active full backup on all the Monday-Thursday backup jobs to run on Monday instead, which will run on the schedule needed and not conflict with my other Friday-Saturday backup job.