kb.mihelj.net
Petja's technical blog

A few days ago I came across a problem, where a client computer which was in a Windows 2k3 SBS domain was not willing to synchronize with WSUS. I found a simple resolution: using the command ‘wuauclt /detectnow’. This step is
actually called “detection”. The term “synchronization” usually implies the communication between the WSUS server and microsoft.com.  The updates are then downloaded to the client (automatically).

If you have ever used a real remote computer system like Citrix, then you have probably been craving multiple Remote Desktop sessions since you first fired up Windows XP Professional and/or Media Center Edition. Here is a HACK (translated: USE AT YOUR OWN RISK), to enable multiple Remote Desktop sessions on your XP Pro or MCE 2005 box:

NOTE: You will have to have knowledge of the Windows operating system and more specifically the Windows Registry. If you have no experience with the registry, then I would recommend you find someone who does or leave these alone. I do not make any kind of warranty that this will work for you or your friends. This is provided for entertainment purposes only. Don’t call me if your computer stops working. Got it?

1. Print these directions so that you have them to work from.
2. Restart your computer in Safe Mode
3. Turn off/disable Remote Desktop Connection (RDC) and Terminal Services
4. Right click My Computer
5. Select Properties
6. Click on the Remote tab at the top of the window
7. UNCHECK the box next to, “Allow users to connect remotely to this computer“
8. Click OK
9. Go to Start -> Control Panel -> Administrative Tools -> Services
10. Find Terminal Services in the list
11. Right click on Terminal Services and click Properties
12. In the Startup Type box, select Disabled
13. Click OK to close the window

1. Here is a copy of the Terminal Services DLL – Save it to your Desktop or other suitable location
2. Using a file manager like Windows Explorer open C:\Windows\system32\dllcache
3. Rename the file termsrv.dll to termsrv_dll.bak or whatever you would like.
4. Copy the downloaded termsrv.dll file (the one you just downloaded from the web) to C:\Windows\system32\dllcache
5. Open the C:\Windows\system32 folder
6. Delete the file termsrv.dll in C:\Windows\system32

You should be good to go.

The status of the NUM LOCK key is specific for each user, and it is disabled by default. If you want the NUM LOCK key enabled for use before a user presses CTRL+ALT+DEL to log on (the logon desktop), you need to edit the registry.

To enable NUM LOCK for the Logon desktop (shown when no user is logged on), use the steps below:

• Click Start, Run and type regedit.exe
• Navigate to the following location:

HKEY_USERS\.Default\Control Panel\Keyboard

• Double-click the value InitialKeyboardIndicators
• Set the value-data from 0 to 2
• Close Regedit

To undo the above, change the InitialKeyboardIndicators value back to 0

Automate the above task using these REG files – enable_or_disable_num.zip

To do so follow these steps:

1. Open Registry Editor.

2. In Registry Editor, navigate to the following registry key:

          HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters

3. Create the following value (DWORD):

          NegativeCacheTime

          and give it a value of 0 (zero).

Note As always, before making changes to your registry you should always make sure you have a valid backup. In cases where you’re supposed to delete or modify keys or values from the registry it is possible to first export that key or value(s) to a .REG file before performing the changes.

4.Close Registry Editor.