Hi everyone, hope you guys are having a blast weekend. Today I would like to bring to you Azure AD Connect.
In the past, the 1.0 in-place upgrade, I would have to kept a record of the “before” changes of settings, such as the organization units, and etc. This would likely need me to schedule a day to capture the settings.
Anyway, not all of the 1.0 version can support the in-place upgrade to 2.0 version, if you have an older Azure AD Connect, that do not support in-place upgrade you would need to plan a migration or transition, to the 2.0 version. It may sounds simple, but there are few things you would need to take note of, that is avoiding duplicated records sync to Office 365, and duplicated service accounts, else you will likely get more stuff to clean up in the end. Is good to plan your transition and your clean-up first.
*Note: 31st August 2022, 1.0 version will be end of life
For those who are on the supported version of 1.0, that can perform in-place upgrade to 2.0 version, here are some tips or hint you can take note of before performing the upgrade,
Full backup on the server
Make sure you know what are the impacts
Make sure the existing service account has the required permissions based on the 2.0 prerequisites
During the upgrade, the wizard will request you to re-enter the global administrator account from Office 365
You do not need to keep a record of the existing organizational unit because it will automatically bring forward the settings to your 2.0, same goes with your SSO, password hash settings, or device join settings
Yes, version 2.0 does support single-label domain
If you would like to know more about the prerequisites of version 2.0, feel free to refer the references below,
Hi guys and ladies, today I’m going to write about the hidden guru in your Exchange Online Protection, a.k.a Office 365 Mail Security or Microsoft Defender for Office 365.
Why improving your mail security configuration is important? Well, malicious attacks gets improve from time to time, so does security too. In the past, scammers used to send fake letters to houses claiming to be from the bank or police officer, to lure you into turning yourself in with money. Now 2022, scammers are sending blast mails to any IP address or available legit domain in the world, claiming to be an authorized organization and to seek their victims.
There are times you would like to compare what your vendors recommendation and the global recommendation of mail security configuration, now you have it in your Microsoft Exchange Online portal. Basically configuration analyzer scans your existing policies and provide either Standard or strict recommendation to improve your mail policies.
Do not make changes to default policies by Microsoft. Recommended to create new ones.
At the left taskbar, you can see the “Email and collaboration” category
Select the “Policies & rules”
Select “Threat policy”
Select “Configuration Analyzer”
As you can see they do scan your default policies by you can ignore them. The most important thing inside this table, is the structured and convenient information that provide you understanding on how you can improve your existing policies.
You may refer to the references below to know whether is your license has this feature available.
Hey guys and girls, hope you guys are having a great weekend! Remember to stay healthy and stay safe as your priority.
Today’s blog is more towards talking about the Microsoft information protection labels, how to plan before deploying it. Each organization has their own preferences and requirements. Planning is a crucial part of every deployment especially when the deployment would have to roll-out to the users to use it for their daily work. Layman is the key to the users understanding.
Some organization have a compliance team and some does not have it. Having a compliance team would able to make this deployment much more clearer in terms of what the organization needs. If the organization does not have a compliance team, then we would help to identity together in terms what do they require only. Labels are structure in the form of priorities, so best to make it simple, and easier for administrator to manage too.
Phase 1: Give them the feel and look
Microsoft do provide default labels to organization, you can roll-out these default labels to smaller team or compliance team, allowing them to play around with it for a period of time. This allows them to have an idea how sensitive labels works and coming out a template would be easier for them. Having a template is the quickest way and easier way to roll-out the labels.
Phase 2: Feedback and Drafting Template
Getting feedback and drafting template phase, is a closer phase to rolling out the labels that suits the organization needs. In this phase, there are few items that you would need to involve into and would take a bit of time,
Categories the labels based on location (Exchange online, SPO, OneDrive and etc)
There is difference in terms of protection features for each location
What can or can’t do in the labels
Users description about the labels (keep it as layman as you can)
Priority of the labels
Design structure of the labels/sub-labels (Simple is better)
Permissions (Flexible or Set)
Action for the priority labels (Flexible, Warning or Strict-Justification)
Customization notifications (Majority would decide to maintain the default, so you don’t need to spend too much time on this part)
Here are some design types that you can reference,
Design type 1
This design is for organization that would like to remain some default labels, and has new labels for other departments and its purposes. No sub-labels to be manage.
Design type 2
This design is for organization that would wish to keep some default labels but does not want to have other new labels to manage. Has sub-labels to manage.
Design type 3
This design is for organization that would like to manage their labels in the form of departments and with each department has their own labels. I wouldn’t recommend this though, because is complicated. As I mention earlier, labels are arrange in the form of priority.
Phase 3: Final Template
This is the phase where you can start to roll-out the final template of the labels back to the small team or compliance team to give it one last confirmation.
Hey guys and girls, happy new year and hope you guys are healthy and safe! I’ve come across of issues of users kept login their own corporate user accounts into a meeting room device through Microsoft Teams. Thus, this will also registered the meeting room device under the user’s account.
Kept manually deleting the devices objects from the user account is not flexible to administrators. Clean up is really not something that as administrators has to do every time a user uses that meeting room device. Our meeting room devices are not hybrid join. So this solution does not really impact the Windows license but this does not mean it would not cause issue for your environment. Recommended that you test it out at your lab environment. Our meeting room devices are custom made/design.
I was able to came across an article that really helps my situation. This solution require to modify the device’s registry editor.
Please run a lab test.
Launch the registry editor on the affected machine
Direct to this location HKLM\SOFTWARE\Policies\Microsoft\Windows\WorkplaceJoin
Create a new DWORD item and name it BlockAADWorkplaceJoin with the value of 1
Reboot the machine
You may run a command line “dsregcmd /status” to check the MDM status
SSO state: No
If you have multiple devices that you would need to apply this settings you could export and save this registry settings or use PowerShell method. You may refer the PowerShell method via the references below.
Good day everyone, hope you all are taking care of your health and safety during this pandemic. Hope you guys are also getting your booster shots.
Today’s issue is related to Microsoft Endpoint Manager, on hybrid device joined. I notice that when a device’s Azure AD Registered icon is removed from the Endpoint Manager portal and if the machine didn’t reboot immediately and leaving the device there for more than an hour after I have made the changes in the portal, the device will have issue in joining/registering as hybrid join.
There is this cache that the device stored, I’m not too sure about what is the refresh time that the device retrieve the new update from portal.
Symptoms that your hybrid join was not successful:
The device’s Register status keeps showing/stuck at Pending, at Endpoint Manager
The device’s MDM status keeps showing/stuck System Center Configuration instead of Microsoft Intune, at Endpoint Manager
Command prompt keeps showing the MDM warning, when I perform “gpupdate /force” even though the machine’s object is no longer found in Endpoint Manager
In the dsregcmd /status shows the DeviceAuth: Failed.Device is either disconnected or deleted.
Steps to resolve:
First clear the machine object from Endpoint Manager
Run an Azure AD Connect synchronization from on-premises
Once the Azure AD Connect synchronization completed then proceed to the next step…
Reboot the machine
Launch the command prompt as administrator on the affected machine, and run the following command “dsregcmd /leave”
Then run “dsregcmd /status”, check to make sure the the device is unjoined
Go to the registry editor, “HKLM\SOFTWARE\MICROSOFT\Enrollments” delete all the GUID looking keys
Reboot the machine
Try again the hybrid join procedure
If you can’t delete some of the keys due to the system not allow, then it is fine, you can proceed deleting the ones that can delete.
It seems that after we turn off the modern authentication, there was no more further prompt issues with Windows 7 but Windows 10 on the next day is receiving prompt and with the user name shows as “contoso.onmicrosoft.com” domain instead of the “contoso.com” registered domain or default domain.
After research, we notice Microsoft just recently release an enforcement towards basic authentication on 1st October 2021. Hence, we have no choice to look for workarounds for Windows (7 and 10) to support Modern Authentication. The only workaround is to create a registry and amend them to the Windows machines.
Create a Group Policy Object in your Active Directory environment
Under the Computer > Preferences > Windows Settings > Registry
Recently I deployed Azure AD Connect server and I notice there are lots of updates and changes made to the latest version of Azure AD Connect application.
The latest version of Azure AD Connect is 2.0. There are few conditions required to follow before setting up the Azure AD Connect application to be running smoothly.
Now there is a new requirement for the service account that is assign for Azure AD Connect application purpose only, the service account must be a member of Administrators group in your local Active Directory. Without this permission, you will faced the synchronization status shows as “completed-with-error” and “permission-denied-access“. You will have trouble in terms of password synchronization.
To further view of what’s new with the version 2.0, you may refer to the references below.
Hi guys and girls, hope you are doing well, as the pandemic is still on-going, hope that you guys are keeping cleanliness and safety first.
Today’s topic is about exchange migration of mailboxes from on-premises to Office 365. This issue is where the legacy windows client or legacy office apps has issue with their outlook applications keeps prompting for credentials and showing disconnection. The issue also do happen to Windows 10 machines but not as aggressive as the Windows 7 machines.
This environment has the following items,
Exchange server: 1 unit, version 2013, CU23 (latest)
Windows client: Combination of Windows 7 and Windows 10
Office applications: Combination of 2013, 2016, 2019 and Microsoft 365 apps for business in both windows 7 and windows 10 categories
Migration method: Remote move migration
Hybrid establishment: Yes
Microsoft 365 license: Business standard/basic
As we all know that the major pre-requisites must met before starting the hybrid and perform migration.
We notice intermittent connections while running the Wireshark on Windows 7 with M365 business apps, while trying to login using the migrated account credential on an Outlook app. We ran a re-creation of the outlook profile and the prompt for credential has stops. This is definitely not the right solution. Solutions is dependent with what caused the issue.
At first we suspected something got to do whitelisting on the network layer but we had confirmed that the whitelisting are correctly configured. Next, we suspected something go to do with compatibility on windows with/or office apps version. This is not a very good idea. After quick research, I came about modern authentication could be the caused, and there where I had an idea on suggesting to turn off the security default in Azure portal and then turn off the modern authentication in Office 3655 tenant. After 10 to 15 mins, the intermittent connections no longer shows up on the Wireshark.
Modern authentication is enabled by default for every new Office 365 tenants, so please be aware if your environment has legacy windows client running or legacy office applications, do consider to turn them off first before proceeding to deploy Microsoft 365 apps.
Modern authentication was the one the interfered with the machines and it kept challenging the users to key in credentials due to the compatibility was not met. Once the modern authentication is turn off, the environment now is running basic authentication.
I think playing with Rows and Columns is every beginner programmer’s nightmare. Rows and Columns concept is all the same for all coding languages. There’s no black magic here.Is all about the basic understanding and common sense. I’ve seen many fresh graduate find it difficult to understand the rows and columns and tend to overthink and turn their codes into a complex dark hole.
What you understand?
You come about FOR LOOP, WHILE LOOP or DO…WHILE LOOP. To identify Rows and Columns in loops form, let’s take FOR Loop as example, so below image is how you use the FOR Loop concept to get or apply table values. Inner FOR loop is define as your column, and the outer FOR loop define as your row.
So clear about it? In PowerShell, the concept is the same but it has been simplify with a command “Import-csv“.
What the beginners does?
This is the sample code that I have seen too much, in the beginners.
By apply this you will get duplicated result;
How PowerShell does it?
Now, let’s see the code for PowerShell, I’m going to show you how you get value list of rows and columns from Excel file, aka CSV file format.
This is the csv file for example, we have 2 columns with naming/attribute, UserPrincipalName and EmailAddresses as the first row. This is the view from excel and the view from notepad is different. Notepad, the columns are separated by a delimiter “,”
To put them into PowerShell, you just need a single FOR Loop to perform.
Lets output the result you will get is this, if you want to beautify your result is possible.