e-micra
środa, 12 lutego 2025
piątek, 24 stycznia 2025
poniedziałek, 16 grudnia 2024
stupid office.com as a blank page
I don't know how and why but for sometime I had blank page on edge set to office.com. Without a reason it was set without option to change in settings. At first I thought to download admx package because in local policy I couldn't find settings for Edge. Today I come to my sense and in registry I removed NewTabPageLocation pointing to office.com on computer settings policies Software/Microsoft/Policies...
Still no solution - only forced gpupdate helps.
Still no solution - only forced gpupdate helps.
poniedziałek, 9 grudnia 2024
huge netbios traffic
according to this link from spiceworks maybe some old printer causing huge network traffic on NetBIOS - 137 tcp/udp:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider\Servers*oldservername*
I've got such scenario - near 20k workstations with some missing printers causing huge network - netbios - traffic. Maybe there are resposible for it?
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\Client Side Rendering Print Provider\Servers*oldservername*
I've got such scenario - near 20k workstations with some missing printers causing huge network - netbios - traffic. Maybe there are resposible for it?
poniedziałek, 4 listopada 2024
exhausted connections? exhausted sockets?
Windows 2019, Windows 2022 by default has got port available from 49152 to 65535 - available 16384 ports. On another server I've got the same issue - no connection to domain controller or to different server, connections reamains intact, I can connect to server remotely - by C$ or by some ports, on server I can't establish new rdp connection with message that there are no available domain controllers, gpupdate is not working, zabbix monitoring is not working, but... after change of available ports by expanding range to 32768-65535 magically everything start works.
netsh intreface ipv4 tcp set dynamicportrange
netsh intreface ipv4 tcp set dynamicportrange
wtorek, 22 października 2024
memory considerations for Active Directory
Location: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
Name: EDB max ver pages (increment over the minimum)
Type: REG_DWORD
Value:
Note The value for the setting is the number of 16KB memory chunks (or 32KB memory chunks on a 64-bit processor) that will be reserved. For example:
9600 = ~150 MB 32-bit, ~600 MB 64-bit
12800 = ~200 MB 32-bit, ~800 MB 64-bit
16000 = ~250 MB 32-bit, ~1000 MB 64-bit
19200 = ~300 MB 32-bit, ~1200 MB 64-bit
When to increase? When allocated buckets are on high values...
Name: EDB max ver pages (increment over the minimum)
Type: REG_DWORD
Value:
Note The value for the setting is the number of 16KB memory chunks (or 32KB memory chunks on a 64-bit processor) that will be reserved. For example:
9600 = ~150 MB 32-bit, ~600 MB 64-bit
12800 = ~200 MB 32-bit, ~800 MB 64-bit
16000 = ~250 MB 32-bit, ~1000 MB 64-bit
19200 = ~300 MB 32-bit, ~1200 MB 64-bit
When to increase? When allocated buckets are on high values...
performance tunning for Active Directory
NTDS\Request Latency - should be as low as possible - at the end is the defined timeout - by default - 120 seconds, but we don't want to be there...
Number of LDAP threads - by default is 4 per cpu core, so in environment with 4 cores is 16 - so if we have current value of 16 and cpu use at 100% so maybe we have bottleneck? CPU queue is another sign of issues.
NTDS\Estimated Queue Delay - shoud be 0 - is higher we have a problem - querries are wainting to process
Number of LDAP threads - by default is 4 per cpu core, so in environment with 4 cores is 16 - so if we have current value of 16 and cpu use at 100% so maybe we have bottleneck? CPU queue is another sign of issues.
NTDS\Estimated Queue Delay - shoud be 0 - is higher we have a problem - querries are wainting to process
Subskrybuj:
Posty (Atom)