Recently we had an issue where a Office 365 Hybrid Environment where a local user would reset their expired Local Password and the ADDconnect service would disconnect the user and delete the Mailbox and User account. We could restore the Mailbox from deleted Users in the Admin Panel however it was only restoring “In Cloud” rather than “Synced with Active Directory”

I checked the ImmutableId for the User in 365

Get-MSOLUser -UserPrincipalName user@domain.com |flGet-ADUser -Filter {UserPrincipalName -like user@domain.com } -Properties ObjectGUID | select ObjectGUID

which is the unique value AADconnect uses to sync between on-premise and 365 and it was the same.

Running through the ADDconnect “Customize Synchronisation Options” showed the AD group created for selective Users to be Synced had been moved to a different OU and it could not reference this anymore.

Fixing the OU location of the Group resolving this fixed the accounts back to 

 

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

Recently I tried to boot an hp elite 8200 Compaq desktop from USB, however, pressing the f9 key on bootup was not showing me any USB key. 

Upgrading the BIOS did not fix the issue

I have to Reset the BIOS to factory defaults which then showed the USB Key

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

Previously, we used a development instance of Azure AD Connect with a development Azure AD tenant to investigate the rules. However, Microsoft has created new functionality in the adfshelp.microsoft.com ADFSHelp Portal:

The ADFSHelp Portal in Microsoft Edge (click for larger screenshot)

ADFSHelp ToolsIn the Tools section, there is now a Claims Generator wizard labeled Azure AD RPT Claim Rules, that will help you get optimized claims rules for the ‘Office 365 Identity Platform’ RPT.

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

The event log shows the below error : 

Faulting application name: WINPROJ.EXE, version: 16.0.9126.2072, time stamp: 0x5aa71b2d Faulting module name: mso20win32client.dll, version: 0.0.0.0, time stamp: 0x5aa6e4e7 Exception code: 0x010d5840 Fault offset: 0x00152808 Faulting process ID: 0x18b4 Faulting application start time: 0x01d3bffa8580d681 Faulting application path: C:\Program Files (x86)\Microsoft Office\root\Office16\WINPROJ.EXE Faulting module path: C:\Program Files (x86)\Common Files\Microsoft Shared\Office16\mso20win32client.dll Report ID: 15fb1e4a-ee75-4217-9a89-1e75433a8b0a Faulting package full name: Faulting package-relative application ID:

Resetting the Registry and User App data for MS project does not resolve this 

You will have to go into Control Panel and do an Online Repair ( quick repair does not fix this ) 

VN:F [1.9.22_1171]
Rating: 10.0/10 (1 vote cast)
VN:F [1.9.22_1171]
Rating: +1 (from 1 vote)

The first delay is a long cycle of checking every file mentioned in the VSS writers metadata. There are 8 million of FILESTREAM blobs on that server. This must be what causes this cycle to be so long for that volume.

 

Please download the bundle here: https://storage.veeam.com/Fix_125973_aebe4c1eb0.zip

To install, do the following on Veeam server and any Guest Interaction proxies that you have:
1. Locate C:\Program Files (x86)\Veeam\Backup Transport\GuestInteraction\VSS\VeeamGuestHelpers
2. Rename VeeamVssSupport2003_X86.dll to VeeamVssSupport2003_X86.dll_old
3. Rename VeeamVssSupport2008R2_X64.dll to VeeamVssSupport2008R2_X64.dll_old
4. Rename VeeamVssSupportXP_X86.dll to VeeamVssSupportXP_X86.dll_old
5. Extract new versions of these 3 DLL files from the archive.

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

On setting up a new surface for a user , which was enabled for modern authentication MFA 2fa in 365 , when asked in Outlook for Need Password the login prompt would come up blank and disappear.

  • Signing out and back in to Outlook did not fix this
  • Proxy Configuration was checked

**** Update ***** Make sure you have the following Reg Keys

[HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Identity\DisableADALatopWAMOverride] – REG_DWORD “1”

[HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Identity\EnableADAL] – REG_DWORD “1”

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


Installing N-able on a windows machine is as simple as running an MSI with the customer ID and creates an activation key for you 

On a Mac you would think this would be the same however not! 

  1. Add the Device Manually on the N-able server under your client



Enter the Device Name and IP Address ( address should be fully qualified domain pc.domain.local ) , change the machine Workstation OSX and class to correct

Set Local Agent Tab to Manual Click Save Button

Navigate to the nearly created device and go to Settings and sub Tab Local Agent

Download the  agent-macosx.tar.gz file from the link it gives you and copy the Activation Key

Extract the  agent-macosx.tar.gz on the Mac after downloading 

Open “agent-macos.pkg”

If you getcan’t be open because the identity of the developer cannot be confirmed”, please change Security and Privacy settings as follow ?nd try again:

1. Open “System Preferences”
2. Select “Security & Privacy”
3. Go to General tab
4. Click the Lock (bottom-left corner) to unlock it (administrative password is required)
5. Set “Allow apps downloaded from” to Anywhere
6. Close the dialog
7. Repeat agent installation
8. Change “Security & Privacy” to the initial setting if needed

Once running it might fail to generate an Activation Key , if you go back you can choose to authenticate with a key , use the Key you copied from previous step and this should activate


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