Below you will find 2 zip files that can be used to get your Digital Persona U.are.U 4500 up and running. The first 4500_wbf_driver_5.0.0.5_rs3.zip is smaller in size and is just the basic drivers, probably all you need to get up and running on Windows 10. The second DP_UareU_WSDK223.zip I believe is the SDK kit and has all the drivers and full software.
Microsoft 365 tenant, mainly using Exchange Online (Plan 1) licenses. I enabled MFA for a couple of users which works fine logging in to https://office.com
Users can access Outlook on the web without any problems and get notifications sent to the “Microsoft Authenticator” app to approve or SMS if they choose one of the other authentication options.
When it comes to Outlook 2019 they just repeatedly get asked for their email credentials in a standard type popup box as opposed to the newer MFA style popup that you see like when you login to https://office.com where it asks for email, then password, then MFA option.
I know this type of problems exists with older versions of Outlook 2013 and lower and there are workarounds for it but this is Office 2019!
After raising a support ticket with Microsoft and getting a call back pretty much straight away from a very knowledgeable “Support Ambassador” we managed to sort the problem. Turns out that if your tenant was created before 2017 (ours was 2014) then the default policies in place for the basic Azure type licenses that come with the lower tiered licenses like Exchange Online might not work very well when enabling MFA on a user account! Tenants created later than 2017 tend to work just fine.
Here’s what we did…
$MFA = New-Object -ComObject InternetExplorer.Application -Property @{Navigate2="https://cmdletpswmodule.blob.core.windows.net/exopsmodule/Microsoft.Online.CSE.PSModule.Client.application"}
The command above installs a module which then launches another PowerShell window.
Connect-EXOPSSession
Enter your tenant administrator login information.
Set-OrganizationConfig -OAuth2ClientProfileEnabled $true
This pretty much enables the use of MFA now for your Exchange Online tenant. It can take a few hours for things to propagate and for Outlook 2019 to make use of this. If you need to speed this process up you can add the following registry key to the users computer. Make sure to close Outlook first.
Open Outlook and you should now get the MFA type prompt as you would expect. I think if you continue to have problems then it’s worth deleting the Outlook profile on the computer and starting again.
The following article may also be of use as it goes into a lot more detail about how to enable or disable modern authentication for Outlook in Exchange Online https://docs.microsoft.com/en-us/Exchange/clients-and-mobile-in-exchange-online/enable-or-disable-modern-authentication-in-exchange-online
One last thing… enabling modern authentication for Outlook in Exchange Online wont affect any of your other users who may not have MFA setup.
Hopefully this may help someone somewhere one day!
Here’s a useful video from Microsoft on how to fully setup guest access in teams. It involves changing settings in Azure Active Directory, Teams Admin, Microsoft 365 Groups, SharePoint Admin and individual SharePoint sites.
https://docs.microsoft.com/en-us/microsoft-365/solutions/collaborate-as-team?view=o365-worldwide
PROBLEM: I need to stop users saving data to a bitlocker usb flash drive that they use to unlock their laptop.
SOLUTION: Use the DiskPart command line utility to enable read only access to the USB flash drive in question.
STEPS:-
Please note that the above method will only enable write protection for that particular usb flash drive on that specific windows machine. If you were to put the same usb flash drive in a different machine you can still write files to it.
After owning a Specialized Camber Expert 2011 for nearly 9 years it was about time for a change! I ride plenty of local trails with a mix of uphill, downhill, dirt jumps, drop off’s, descents and everything in between. I also regularly visit trail centres such as Gisburn, Whinlatter, Hamsterley, Llandegla and plenty of other places that Wales & Scotland have to offer.
Bikes have changed quite a lot since my last purchase and I wanted a bigger hitting more capable bike based on the different types of riding I do. More travel, slacker head angle, bigger wheels, 1×12 blah blah blah.
The COVID pandemic was upon us so it was a going to be a struggle to find any bikes in stock but after a bit of shopping around I found that Trek Bicycle Sheffield Fox Valley had x2 Trek Remedy 8’s in stock so I organised a visit and went over. As soon as I saw the bike I was wowed! It just looked a beast compared to my old one! It looked beefy with it’s 27.5 / 2.6″ tires, wide bars and extra travel, it just looked like it could handle some abuse.
Took it out for a quick blast down the road and round the car park and was sold. £200 deposit and it was secured. Couple of weeks later I had managed to sell the Specialised and got the rest of the cash together to make a purchase. No better feeling than NBD!
| Fork | RockShox Lyrik Select+, DebonAir spring, Charger 2.1 RC damper, tapered steerer, 46 mm offset, Boost110, 15 mm Maxle Stealth, 160 mm travel |
|---|---|
| Shock | RockShox Super Deluxe Select+, 230×57.5 mm |
| Max compatible fork travel | 170mm |
| Wheel front | Bontrager Line Comp 30, Tubeless Ready, 6-bolt, Boost110, 15 mm thru axle |
|---|---|
| Hub front | Bontrager alloy, sealed bearing, alloy axle, 6-bolt, Boost110, 15 mm thru axle |
| Spokes | DT Swiss Champion, J-Bend, Black |
| Tyre | Bontrager XR4 Team Issue, Tubeless Ready, Inner Strength sidewalls, aramid bead, 120 tpi, 27.5×2.60″ |
| Bontrager XR5 Team Issue, Tubeless Ready, Inner Strength sidewalls, aramid bead, 120 tpi, 27.5×2.60″ | |
| Tyre part | Bontrager TLR sealant, 180 ml/6 oz |
| Bontrager TLR valve, 50 mm | |
| Max tyre size | Frame: 27.5×2.80″ Fork: See manufacturer |
| Shifter | SRAM GX Eagle, 12-speed |
|---|---|
| Rear derailleur | SRAM GX Eagle |
| Crank | |
| SRAM X1 Eagle, DUB, 30T steel ring, Boost, 175 mm length | |
| Bottom bracket | SRAM DUB, 92 mm, PressFit |
| Cassette | SRAM Eagle XG-1275, 10-52, 12-speed |
| Chain | SRAM GX Eagle, 12-speed |
| Max. chainring size | 36T |
| Saddle | Bontrager Arvada, hollow chromoly rails, 138 mm width |
|---|---|
| Seatpost | |
| Size: M, M/L, L, XL Bontrager Line Dropper, 150mm travel, internal routing, 31.6 mm, 440mm length |
|
| Handlebar | Bontrager Line, alloy, 35 mm, 27.5 mm rise, 820 mm width |
| Grips | Bontrager XR Trail Pro, alloy lock-on |
| Stem | Bontrager Line, 35 mm, Knock Block, 0-degree, 50 mm length |
| Brake | SRAM Code R hydraulic disc |
| Brake rotor | SRAM CenterLine, 6-bolt, round edge, 180 mm |
| SRAM CenterLine, 6-bolt, round edge, 200 mm |
| Weight | 14.07 kg (with TLR sealant, no tubes) |
|---|---|
| Weight limit | This bike has a maximum total weight limit (combined weight of bicycle, rider and cargo) of 136 kg (300 lb). |
Windows 10 allows you to join your computer to the Azure Active Directory and login with your cloud credentials. The first account that joins the AAD becomes a local administrator. Subsequent users are not.
To add additional azure accounts as local admins you need to do the following…
net localgroup administrators /add "AzureAD\<users office 365 email address>"
You should see “The command completed successfully”, now go check it worked by going into computer management > Local Users and Groups > Groups > Administrators and check to see if the user is listed.
Starting in Outlook 2016 version 16.0.6741.2017, Microsoft has enabled a new feature called Direct Connect to Office 365. What this feature does is connect Outlook directly to Office 365 if Autodiscover is not working. This is great feature but a network hiccup may cause your mailbox to connect to Office 365 rather than your on premise Exchange, even with a valid autodiscover record.
For Direct Connect to take effect the user must have an active mailbox on Office 365 with a valid license. Typically Direct Connect would be a neat feature unles you are in the middle of a migration to 365, but a network hiccup could incorrectly connect you to 365 even though you havent completed your migration yet.
During 365 migrations deom Hosted Exchange or On-Premise, we recommend disabling this option from the user computer registry:
You can stop Outlook from checking Office 365 for settings by setting a registry key.
HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover DWORD: ExcludeExplicitO365Endpoint Value = 1
Then restart your computer and it should stop trying to connect to Office 365. When you are ready to flip the switch on your migration, remove this registry key.
Heres a great article describing the whole thing in more detail…
https://www.enowsoftware.com/solutions-engine/autodiscover-dilemma
While working on an Azure ADConnect deployment we had a few users with export errors. The users seemed to sync into the cloud so I was not fully aware of what the export error actually affected but… it was still there..
Anyway I found the following article that explains why you get the error and how to fix it. Its basically down to the security settings of the users profile in AD. Basically, enabling the inheritance solved the issue and the ADConnect was able to export these identities.
User > Properties > Security > Advanced > Enable Inheritance
https://evotec.xyz/azure-ad-connect-completed-export-errors-permission-issue/