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.
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.
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
Firstly I take no credit for this, the original article can be found here.
When you connect to a network for the first time in Windows, Windows saves the network profile and assigns a name to it.
Connections using Ethernet (wired) use a generic name such as Network 7 usually while wireless networks the SSID of the Wi-Fi network the device connected to.
Some users and administrators may dislike the non-descriptive nature of wired network connections on Windows.
Good news is that it is possible to rename network profile names to make them more descriptive on the operating system.
The following guide was written for Microsoft’s Windows 10 operating system but the process should work in previous versions of Windows as well.
Changing the network name on Windows
You can check the current name in the Network and Sharing Center on Windows or in the Settings application on Windows 10.
Tap on Windows-I to open the Settings application.
Go to Network & Internet > Ethernet or Wi-Fi depending on the connection type.
The name of the network is displayed at the very top of the page.
To display the name in the Control Panel instead, do this:
Tap on the Windows-key to activate the Start menu.
Type Control Panel and select the result.
Go to Network and Sharing Center
The name is listed under “view your active networks”.
Windows administrators and users have two main options to change a network name. The first involves editing the Windows Registry using Local Security Policy. Note that Local Security Policy is only available in professional versions of Windows, e.g. Windows 10 Pro.
Using the Windows Registry
I recommend that you back up the Windows Registry before you make any changes to it. Check out ghacks.net Windows Registry backup guide to find out how to do that.
Open the Start Menu.
Type regedit.exe and select the result to open the Registry Editor.
Confirm the UAC prompt that is displayed.
Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Profiles
The next step requires some trial and error. Windows lists all network connections with a unique ID and you need to click on each to check the ProfileName variable of it until you find the network name that you want to change.
Double-click on ProfileName once you have found the right entry and type the new name of the network that you want used on the device. The change is only active on the device.
The change takes affect immediately. You can verify that by opening the Settings app or the Network and Sharing Center to verify that the name change was successful.
Repeat the process for any other network name that you want to change.
I was trying to figure out how many lenghts of skirting board i’ll need to finish off my loft conversion and found the following useful tool.
This online linear cut calculator is designed to solve problems of cutting stock material into pieces of specified lengths with minimal material waste, named as cutting stock problem. In general, it’s a kind of length optimization software, in other words, it’s 1D nesting optimizer or linear cut calculator.
Recently my webcam had been playing up when joining Microsoft Teams meetings. Sometimes i’d connect to a call, audio works but video doesn’t. I could toggle the show/hide video icon and it would start working but it got worse and wouildn’t work at all.
After a bit of digging I found this article on the web and it was the following Powershell command that fixed it…
A team owner in Microsoft Teams can add and manage guests in their teams via the web or desktop. Anyone with a business or consumer email account, such as Outlook, Gmail, or others, can participate as a guest in Teams, with full access to team chats, meetings, and files. Only people who are outside of your organisation, such as partners or consultants, can be added as guests. People from within your organisation can join as regular team members.
By default, guest access is turned off. So, before guests can join a team, an admin must turn on guest access in Teams. To do that, use the link below…