We have  custom APP that is used internally only, and even though the UAC is disabled it was throwing this annoying error:

security warning.zoom60

The fix is relatively easy, you just have to be cautious as it might cause potential harm.

1. Navigate to: (REGJUMP is your best friend for that!)

2. Add a new ‘String Value’, call it ‘LowRiskFileTypes’ and give it the value ‘.exe’.
3. Make sure to remove the ‘.exe’ from the ‘HighRiskFileTypes’ list.
4. Reboot.

Again, the warning, it poses extra risk as it will not warn when the user opens another ‘.exe’ file. We have great backups, users only use the same apps and have no rights to install things, so I am comfortable applying it this way.

We have a huge cloud migration coming up and have been syncing data for weeks now. It finally finished syncing, however the sync tool that we use broke the NTFS permissions… so I was looking for a way to export and import the NTFS permissions only.

ICACLS seem to work pretty good for that.

Just a word of warning, the more files and folders you have, the longer it takes. The import took several hours for me.

Source:
– https://marckean.wordpress.com/2013/01/03/copy-ntfs-permissions-only-and-no-data-from-source-to-target/

I run today into an odd issue, a user was not able to to RDP into their new Terminal Server.

RDC1

 

When you check on the RDP connection tab it says NLA is not supported.

RDC2

The cause seems to be an issue with a DLL file in the Registry.

And here is fix:

Configure Network Level Authentication
1. Click Start, click Run, type regedit, and then press ENTER.
2. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3. In the details pane, right-click Security Packages, and then click Modify.
4. In the Value data box, type tspkg. Leave any data that is specific to other SSPs, and then click OK.
5. In the navigation pane, locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders
6. In the details pane, right-click SecurityProviders, and then click Modify.
7. In the Value data box, type credssp.dll. Leave any data that is specific to other SSPs, and then click OK.
8. Exit Registry Editor.
9. Restart the computer.

 

Sources:
– http://www.powercram.com/2009/07/enabling-network-level-authentication.html#
– https://community.dynamics.com/gp/b/gpdynland/archive/2013/07/26/windows-7-remote-desktop-connection-error-remote-computer-requires-network-level-authentication