For this Assignment write a Powershell script to create a Windows user account that is a non-admin user. 1. This user must be able to login to a desktop! 2. Your script must accept an argument to set the username (eg. I should be able to run your script Powershell.exe - Execution Policy Bypass -file .\Assignment8a.ps1 "Ellie" and it should function and create a user that meets all the criteria here.) 3. Your script must first check that no user exists that already uses that name.

Pelase slove

do the following in the codeThe shell environment should contain shell=<pathname>/myshell where <pathname>/myshell is the full path for the shell executable (not a hardwired path back to your directory, but the one from which it was executed). #!/bin/bashflag=0echo "Welcome to myshell"while [[ $flag == 0 ]]doread -p "myshell > " str#spilliting the textIFS=' ' #setting space as delimiterread -ra ARR <<<"$str" #reading str as an array as tokens separated by IFScommand=0 # >>>>>>>>>>>>>>>>>>>>>>>>>> 1. cd <<<<<<<<<<<<<<<<<<<<<<<<<if [[ ${ARR[0]} == "cd" ]]thencommand=1word=$(echo ${ARR[@]} | wc -w) # after cd hav no argument then report to current directoryif [[ $word == 1 ]]thencd $PWDelseif [[ -d ${ARR[1]} ]]thencd ${ARR[1]}elseecho "[${ARR[1]}] path is not correct"fififi…

find The find command takes a pattern as a command-line argument and recur- sively searches through directories to find a filename matching that pattern. It should print a relative path starting with "./" for every file/directory that matches. For example, running ./find 1s.c from within the hw2 directory should print ./1s.c. If run from the parent directory, the output would be . /hw2/1s.c. There may be multiple matches. If we run ./find .c from within the hw2 directory, we should see: ./find.c ./1s.c ./tree.c The output does not need to be sorted. If nothing matches, it shouldn't print anything. Pattern matching should be case sensitive.