Skip to content

Commit 824a5cb

Browse files
Update README.md
1 parent 0bde0f1 commit 824a5cb

1 file changed

Lines changed: 6 additions & 4 deletions

File tree

README.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -58,23 +58,25 @@ the script will then clean their profile as well. It is up to the system admini
5858
this script and when to discontinue using it. The script will automatically determine if it has been previously executed
5959
under the logged on user profile as well as administrator to prevent itself from re-execution.
6060

61-
### HOME USERS.
61+
### HOME USERS (Non-Domain).
6262
Simply run this script on each of the profiles on the computer, with an Administrator account being the
6363
first to execute the script and non-Administrators (or other Administrators) thereafter.
6464

6565
### WINDOWS 10 HOME EDITION.
66-
Sorry but once you run this script you will lose the ability to manage local users on your computer. I fixed this by releasing Windows 10 Local user Manager on 3/23/2021 and you can find it here. https://github.com/MegaphatNetworks/Windows-10-Local-User-Manager
66+
Sorry but once you run this script you will lose the ability to manage local users on your computer. I wrote a piece of code on 3/23/2021 to help with called the [Windows 10 Local user Manager](https://github.com/MegaphatNetworks/Windows-10-Local-User-Manager)
6767

6868
### DOMAIN/AD SYSTEMS.
6969
If you are using this in a domain environment, I would suggest including this script in your logon script.
7070
Execution could be as simple as launching from a batch file such as: powershell.exe -ExecutionPolicy Bypass -File .\ThisScript.ps1
71-
Be sure it executes the first time logged in as a Domain Admin.
71+
Be sure it executes the first time logged in as a Domain Admin. It will detect if it has been executed previously to avoid repeat execution.
7272

7373
### NON-DOMAIN/AD BUSINESS SYSTEMS.
7474
Run the script the same way as listed above for Home Users.
7575

7676
### HIPAA Compliancy Notice.
77-
Windows 10 is NOT a HIPAA-compliant OS. Why? Because of all of the phone-home telemetry included.
77+
Windows 10 is NOT a HIPAA-compliant OS unless you are running Enterprise edition and even then you need to be in an Active Directory and customize your policies.
78+
*What do you mean non HIPAA compliant?* Exactly that! Computer information will be transmitted to MS. Why? Because of all of the phone-home telemetry included.
79+
7880
While I have not performed any network sniffing to determine if Windows 10 is actually sending any sensitive data back to MS,
7981
the mere fact that it phones home with your activity and has access to your information makes it inherently not HIPAA compliant.
8082
Will this script make your system compliant with HIPAA requirements? To some degree yes. It will disconnect the OS from having

0 commit comments

Comments
 (0)