Here is the steps for solving the 80245003 error when you do Windows Update in Vista.
1. Start > Control Panel > System and Maintenence, then (under Windows Update) > Turn automatic updating on or off, then click “never check for updates”
2. Close Control Panel
4. Goto My Computer
5. Click on C: (or your Primary Drive)
6. Open the “Windows” folder
7. Rename the Folder called “SoftwareDistribution” to SoftwareDistributionOLD
8. Create a new folder named SoftwareDistribution
9. Close all windows and any running programs.
11. Go back to Step 1 (and back to > Turn automatic updating on or off), then turn the Automatic Updates back On.
12. Close all windows and any running programs.
14. then click on Start and type in Windows Automatic Updates
15. Click on the “Windows Automatic Updates” folder
16. Run Windows Automatic Updates.
- Disable the Windows Update Service (Settings > Control Panel > Administrative Tools > Services). Just stop the service.
- Navigate to: C:\Windows (or whereever you Windows system is)
- Find the folder named: “SoftwareDistribution”
- Rename that folder to something like “SoftwareDistribution.old”
- Create a new folder called “SoftwareDistribution”
- Go back to your Services panel and start the Windows Update service
- Rerun Windows Update
I find a good guide on sync GAL between AD Forest.
Microsoft has removed HyperTerminal from Windows Vista, if you need to connect to a Cisco router through a local COM port, you can get HyperTerminal from Hilgraeve, the company that Microsoft licensed the application through.
You could also use the old XP Hyper terminal. Just extract two files hypertrm.dll and hypertrm.exe. You can put them anywhere on the disk, no installation required. Of course, for that you need to have XP to extract files from.
Besides, puTTY and SecureCRT are great too! I would prefer puTTY as it is FREE! :-p
PuTTY can now connect to local serial ports as well as making network connections!!!
Hilgraeve HyperTerminal for Personal Use
If you install VNC through Remote Desktop, you will face a problem that VNC Server can’t run as a service even you choose the “Run As Services” option during the installation. To work around to this problem, I search through the net and find a solution which work on my server(W2K /w SP4):
1. Logon the Server by using Remote Desktop and install VNC, run the VNC Server by clicking it’s icon in the VNC program group.(It may prompt you to configure the default password if it’s a new installation. However, my case is not a new installation, so it don’t prompt for configuring the default password).
Configure the default setting by clicking the “Show Default Settings” inside the UltraVNC program group(I configure my VNC password at that time) and click OK.
If it does not work, try copy the HKEY_CURRENT_USER\Software\ORL\WinVNC3\Password to HKEY_LOCAL_MACHINE\SOFTWARE\ORL\WinVNC3\Default\Password
2. Then, created the registry value “AuthRequired” under HKEY_LOCAL_MACHINE\Software\ORL\WinVNC3 and set it to 0 (a DWORD value). That enabled “passwordless” VNC access(Remark: It’s DANGER to do so!!!)
3. Go to the services console and start the VNC service.
Now since VNC is hooking video as if we were sitting in front of a console rather than RDP’s session stuff, we can attach to the newly started vnc service. Go to start->program files->Ultra VNC->Ultra VNC Server [folder]->Show Default Settings (Assuming everything is in the default places/names at least…)
Now set your password. Do a save and get outta there. Exit VNC client locally, and reconnect – now it prompts for password. Remove the “authrequired” key.