CCMTune

Presentation During the registration phase of the device at the Windows Autopilot service level, we may encounter the following error: This error comes from the fact that the user is probably not authorized to join his machine through the Windows Autopilot service. Resolution For resolved this issue, I invite you to carry out the following procedure : You go to Portal.azure.com Devices section Device setting And active " Users may join devices to Azure AD ", two possibilities : All                 OR Selected (select one or many user groups)

Presentation This tool aims to gather and provide the end user with options to perform simple actions without having to search everywhere in Windows. Github link :   https://github.com/ChrisMogis/EndUser_assistant.ps1/blob/main/EndUser_Assistant.ps1 Options available List of actions : Computer information (Device Name, IP, @Mac, OS) Run remote control (msra) Data backup Internet connection test Clear cache DNS Reset network connection Restart SCCM service (Only if the Intune service is available on your computer) Restart Intune Service (Only if the Intune service is available on your computer) Quick scan with Windows Defender Full Scan with Windows Defender Logs All actions are logged to C:\Tools_CCMTune\Logs Convert to EXE For converting this script to exe file, I recommend that you use the tool made available by Damien Van Robaeys Github Link :  https://github.com/damienvanrobaeys/PS1-To-EXE-Generator/tree/master/New_Version/Sources Website Link :  https://www.systanddeploy.com/2020/

Presentation In this article, we will see how to change the PIN of your FIDO 2 security key in Windows 11. This action must be performed from a computer on which the security key is configured Process Go to Settings / Account / Sign-in options / PIN (Windows Hello) Click Manage Tab Insert your FIDO 2 Security key Touch your security key In the Security Key PIN section , click Change tab Enter your old PIN code,  Set a new PIN code and click OK Tab

Presentation Windows Hello allows the use of many authentication methods, known as passwordless. Here we will see how to configure a FIDO2 security key in Windows 10/11. Prerequisites Have internet access to configure the key Multi-Factor authentication activated on Azure Services A FIDO2 security Key The following network streams must be accessible * .microsoftonline.com * .microsoftonline-p.com * .msauth.net * .msauthimages.net * .msecnd.net * .msftauth.net * .msftauthimages.net * .phonefactor.net enterpriseregistration.windows.net management.azure.com policykeyservice.dc.ad.msft.net secure.aadcdn.microsoftonline-p.com Configuration  Go to  https://mysignins.microsoft.com/ Click Security info Select Add sign-in method Select Security Key and click Add Click Next Enter your account credentials and click Verify Select the type of security key used Click Next Select External Security Key or built-in sensor Click OK Click OK Insert your Security Key Enter the security key PIN Code

Presentation This script allows you to have a first glimpse of the compatibility of your computer with Windows 11.  It was built on the basis of information available at the following address  https://www.microsoft.com/en-US/windows/windows-11-specifications Lien Github :   https://github.com/ChrisMogis/W11_PrerequisitesCkeck.ps1/blob/main/W11-PrerequisitesCheck.ps1 List of checked components : Architecture CPU RAM Screen resolution Hard drive Secure boot TPM version Script execution : The script must be run in a Powershell console with Admin rights .\W11_PrerequisitesCkeck.ps1 Results : If your computer is compatible Windows 11 : If your computer is not compatible Windows 11 :

Presentation This script runs and loads the contents of a file to recover a list of devices to ping. If the device does not respond, an alert is issued on the desktop. In addition, a log file containing the list of available perimeters is created in the C:Logs directory. Github link :   Script Script exécution powershell.exe -executionpolicy ByPass -file C:\Temp\PingInfra.ps1 Result For each computer that is not available, you received a desktop alert A log file is created to the repository C:\Logs folder

Presentation This article describes how to update Microsoft Teams Room devices from the Teams admin portal. by default the updates are made 30 days after the availability of the firmware.  However, consideration may be given to deploying the update more quickly to fix a bug or equipment security flaw. Update method     1.  Go to https://admin.teams.microsoft.com      2. And click on Teams Devices / Teams Rooms on android (for example)      3. Click on targeted device     4. Click Health tab and click to See available updates     5. Two possibilities for updated the equipment         a. Manual method Check the box Firmware and click Update Key           b. Schedule install Click on the schedule button Select your Time Zone Select the date Select time  Check the Box Firmware Click Update 

This script is used to manage rights on users' calendars on Office 365 with Powershell. Github link :  Download Script Script exécution This script has three options for reading or changing rights on a user's calendar.  Command line : O365-ManageCalendarPermissions.ps1 -Choose Info Displays calendars and rights associated with the user's default calendar O365-ManageCalendarPermissions.ps1 -Choose Add Adds rights to a user in the organization on another user's calendar O365-ManageCalendarPermissions.ps1 -Choose Remove Remove rights to a user in the organization on another user's calendar Calendar permissions Exemple Add calendar permission 1. .\O365-ManageCalendarPermissions.ps1 -choose add 2. Enter your admin account information 3.  Enter verification code 4. Enter the name of the account to which you want to delegate a right 5. Enter the account name of the user to whom you want to assign rights 6. Specify permission type Result

Présentation This script allows to send a status mail when a server restarts or stops. All actions are logged to C:\Logs. Github Link :  https://github.com/ChrisMogis/Scripts/blob/main/Alert_State_Server.ps1 Exécution command line for reboot status :  powershell.exe -executionpolicy ByPass -file .\ScriptName.ps1 -Option Reboot Exécution command line for shutdown status :  powershell.exe -executionpolicy ByPass -file .\ScriptName.ps1 -Option Shutdown #Script Parameters Param ( [Parameter(Mandatory= $true )] [ValidateSet( "Reboot" , "Shutdown" )] [String[]] $Option ) #Function create Log folder     Function CreateLogsFolder {     If (!( Test-Path C:\Logs))     {     New-Item -Force -Path "C:\Logs\" -ItemType Directory } else {     Write-Host "The folder " C:\Logs\ " already exists !"     } } #Create Log Folder     CreateLogsFolder #Declaration of script variables     $Client = "Client Name"     $Server = (Get