Kevin Oppihle's Tech Notes

If a user attempts to run a report and receives the following in a SQL base application. You may need to add the user to SSRS 2019   Unexpected Error The request failed with the HTTP status 401:Unauthorized or  Unexpected Error The permissions granted to user 'username' are insufficient for performing this operation (rsAccessDenied) To add a user or group to a system role: Start the web portal. Select the Gear icon in the upper right and then select Site Settings from the dropdown menu. Select Security. Select Add group or user. In Group or user, enter a Windows domain user or group account in this format: <domain>\<account>. Then to give the users access to SSRS reports? Click Home Folder settings Create a new role assignment so that you can grant access to the “Content Manager” role. (that will grant access so that the user can edit or build reports) Note: You can give them additional permissions in SSRS, such as the Report Builder permission to the Home fol...

Here is an older article on SPF Basics https://koppihle3.blogspot.com/2016/04/dns-spf-basics-what-you-need-to-know-to.html  to add to that... While you can only have ONE official SPF record for your domain, If your domain requires more include statements than you can fit on one SPF record (limit should be10).  It is DNS acceptable to create references to additional txt records that can include other SPF references but it is important to end all of them with a ~all. This is a common issue if you have several marketing or other services sending email for your domain or a monster domain such as Microsoft.com .  Note: Subdomains are handled separately and can have their own official SPF record. for Example for Microsoft using MXtoolbox.com to lookup the data: References include statements to other records:  So Rules are still. Put SPF records in priority access for example if your email primarily comes from proofpoint, put that first then any third party references such ...

If you are using a local account rather than having MS created one from the wizard for better auditing and control. You may have to make some AD permissions changes via powershell. If you are seeing the following Export Errors: Caution- you are modifying AD permissions to grant an account high level access. Do not use a regular user/admin account! Security best practices requires creating a separate  service account that can be used exclusively for this process to allow proper auditing trail and security.  I have found the following 3 commands give permissions needed to access the attributes: $accountName = " Domain-Name \ User-Name " $ForestDN = "DC= Domain-Name ,DC= Domain-Extension " $cmd = "dsacls '$ForestDN' /I:S /G '`"$accountName`":WP;ms-ds-consistencyGuid;user'" Invoke-Expression $cmd accountName = " Domain-Name \ User-Name " $ForestDN = "DC= Domain-Name ,DC= Domain-Extension " $cmd = "d sacls ...

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