Sunday, 17 December 2017

Update multiple user’s profiles in O365 using PowerShell

Or, Updating bulk user’s job title, phone, title, email ID etc... In O365 using PowerShell
Or, How to update user’s profile in O365 using PowerShell with csv import function?

Descriptions: This is one of the very common task that you may be doing on very frequent intervals. Generally when promotions or appraisal are announced in an organization, the Exchange server administrator and AD administrators are requested to update the user’s profiles as per the current designation, extension, department etc...
If you are looking for PowerShell command to update user’s profiles in bulk, you are at the right place and you may refer the steps below.

Connect to Microsoft Azure AD > Open Windows PowerShell (Run as Administrator) > Type the command below and hit Enter


Once you have the sign-in pop, please feed in your O365 credentials

Feed in all the info as per your requirement in a CSV file, as reference shown below.

Run below command now and hit Enter
$users = Import-Csv 'D:\temp\UsersInfoUpdate\profileupdate1.csv'

Now run below command to update all the details you have selected
$users | ForEach-Object { Set-MsolUser -UserPrincipalName $_.Email -Title $_.Jobtitle -PhoneNumber $_.OfficePhone -MobilePhone $_.MobilePhone }

Reference screenshot of PowerShell command execution with all commands in sequence:

Cheers, Please write me back if you have any query or feedback on this…

Friday, 24 November 2017

US-CERT Windows ASLR Vulnerability (registry fix)

Or, How to fix Windows ASLR vulnerability on multiple domain computers

Vulnerability Notification Summary

Original release date: November 20, 2017
The CERT Coordination Center (CERT/CC) has released information on a vulnerability in Windows Address Space Layout Randomization (ASLR) that affects Windows 8, Windows 8.1, and Windows 10. A remote attacker could exploit this vulnerability to take control of an affected system.

US-CERT encourages users and administrators to review CERT/CC VU #817544 and apply the necessary workaround until a patch is released.

How to fix this vulnerability?

Open a Notepad > Copy and Paste the contents given below:
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\kernel]


Save this notepad file as .reg (In my case, I saved this file with name as ASLAR.reg)

To deploy this registry setting on single computer, just double click on this file and Say Yes if prompted.

You can use the same registry key values in GPO to apply it on multiple domain computers.

GPO registry configurations should appear like below:

Cheers, let me know if you have any query of feedback on this..