The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

  • My Flickr Stream

    20140508-Delphi-2007--Project-Options--Cannot-Edit-Application-Title-HelpFile-Icon-Theming20140430-Fiddler-Filter-Actions-Button-Run-Filterset-now20140424-VMware-Fusion-6.0.3.-no-reclaimable
    More Photos

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 1,444 other followers

Archive for the ‘Windows 8’ Category

« Previous Entries

Adding Windows machines to Samba domains and security

Posted by jpluimers on 2018/12/07

If adding a Windows machine to a Samba domain fails and the below “solves” your issue, then you need to tighten the security on the Samba side:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters]
; Enable NT-Domain compatibility mode
; Default:
; [value not present]
; "DomainCompatibilityMode"=-
"DomainCompatibilityMode"=dword:00000001

; Disable required DNS name resolution
; Default:
; [value not present]
; "DNSNameResolutionRequired"=-
"DNSNameResolutionRequired"=dword:00000000


[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Netlogon\Parameters]
; Disable requirement of signed communication
; My Samba (3.0.33) works with signed communication enabled, so no need to disable it.
; Default:
; "RequireSignOrSeal"=dword:00000001
; Disable the usage of strong keys
; Default:
; "RequireStrongKey"=dword:00000001
"RequireStrongKey"=dword:00000000

–jeroen

Posted in *nix, *nix-tools, Power User, samba SMB/CIFS/NMB, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows 9 | Leave a Comment »

Saving windows command prompt history to a file – Charlie Arehart’s ColdFusion Troubleshooting Blog

Posted by jpluimers on 2018/11/14

Dumping the command prompt history

From [WayBack] Saving windows command prompt history to a file – Charlie Arehart’s ColdFusion Troubleshooting Blog:

doskey /history

gives you the command history.

Redirecting with >, >> or piping with | allows you to save this to a file or filter the output.

Found via: [WayBack] How I can export the history of my commands in Windows(7) Command Prompt? – Stack Overflow

Shells that do support persistent history

Note that the command history is not persistent. If you want that, then there are two other shells that support persistent history:

Both of these found through [WayBack] windows – Is there a global, persistent CMD history? – Server Fault.

–jeroen

Posted in Microsoft Surface on Windows 7, MS-DOS, Power User, Windows, Windows 7, Windows 8, Windows 8.1 | Leave a Comment »

DISM fix for Windows 8.1 high CPU usage of TiWorker.exe

Posted by jpluimers on 2018/07/27

This worked for Windows 8.1 as well: Trying fix for Windows 8 high CPU usage of TiWorker.exe (via: bit-tech.net) « The Wiert Corner – irregular stream of stuff

DISM /online /cleanup-image /restorehealth

 

After more than one hour of running, it:

  • freed up more than a gigabyte of disk space. Which on an SSD based VM is a lot.
  • solved the huge memory footprint of TiWorker.exe on the right.

–jeroen

Posted in Power User, Windows, Windows 8, Windows 8.1 | Leave a Comment »

VM disk sizes

Posted by jpluimers on 2018/06/29

I forgot to schedule the post below. It is still relevant if you create a machine with lots of Delphi versions on it.

Read the rest of this entry »

Posted in .NET, .NET 2.0, .NET 3.0, .NET 3.5, Database Development, Delphi, Delphi 2007, Delphi XE, Delphi XE2, Delphi XE3, Delphi XE4, Delphi XE5, Development, Firebird, InterBase, Power User, Software Development, Windows, Windows 8 | 2 Comments »

When you cannot RDP to a target because of “CredSSP-encryption Oracle remediation”: apply your target security patches.

Posted by jpluimers on 2018/06/29

If you get the below error, then your RDP target server needs to be patched.

You can choose to stay vulnerable and modify your policy or registry settings as explained in the first linked article below: that is a temporary “workaround” which I do not recommend. Please update your RDP target servers in stead.

English:

[Window Title]
Remote Desktop Connection

[Content]
An authentication error has occurred.
The function requested is not supported

Remote computer: rdp.example.org
This could be due to CredSSP-encryption Oracle remediation.
For more information, see https://go.microsoft.com/fwlink/?linkid=866660

[OK]

Read the rest of this entry »

Posted in Power User, Windows, Windows 10, Windows 7, Windows 8, Windows 8.1, Windows 9, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016 | Leave a Comment »

« Previous Entries
 
%d bloggers like this: