Cut 4427 disallow main folders path redirection (#150)

[kmaranionjc]

Issues

• CUT-4427 - CUT-4427

What does this solve?

Prevents migration if the user have redirected folder/s (Documents, Desktop, Downloads, etc...) to a network shared drive

Is there anything particularly tricky?

Setting up a network shared folder and redirecting path for Desktop or Documents can be time consuming. There is an alternative to this by changing the path values in the registry:

1. Login to the user account that you are going to migrate
2. Open registry and go to the user shell folder: HKEY_USERS:\USERSID\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders
3. Edit the value for Desktop to \\192.168.50.78\SharedFolder\USERNAME\Desktop

4. Save, sign out of the user then login to the admin account to run the migration

How should this be tested?

1. Run Start-Migration as a cmd:

Start-Migration -JumpCloudUserName USERNAME -SelectedUserName “AzureAd\Reid.Sullivan” -TempPassword "Temp123!Temp123!" -UpdateHomePath $false  -LeaveDomain $true

• Should throw an error and prevent the migration:

2. Migrate using the GUI (.\Start-JCADMU.ps1)

• Should throw an error and prevent the migration:

3. Run Start-Migration as a cmd and use -ValidateUserShellFolder $false to skip the user folder validation:

Start-Migration -JumpCloudUserName USERNAME -SelectedUserName “AzureAd\Reid.Sullivan” -TempPassword "Temp123!Temp123!" -UpdateHomePath $false  -LeaveDomain $true -ValidateUserShellFolder $false

• This should allow the migration even if the user has a folder that is redirected to a network share location

Screenshots

[jworkmanjc]

I think everything makes sense but only because we've spent the time talking about this. The variable names are a bit confusing to read through, and I'm in favor of just testing the redirect directory as a default behavior within Test-UserRegistryLoadState. Just less complexity overall, if there's a use case that I've missed, let me know?