Showing posts with label Windows Server. Show all posts
Showing posts with label Windows Server. Show all posts

Thursday, March 12, 2015

Windows Update Failed: Error Downloading Update

Windows update is a used by many IT Admin to keep the servers they manage to be updated with the latest patches so that it is compliant.
There could be times when the update failed to download for whatever reason and looking deeping into the issue can be done by going through the WindowsUpdate.log file located at C;\Windows.

For this instance, the update failed to download and you will see the error "0x80070005 occured while downloading update"

To resolve this issue, what is needed is just to stop the indexing service.
Once it id stopped, you can go ahead to attempt the Windows Update again.

Thursday, February 27, 2014

Clipboard not working in Windows 2008 RDP Session


There maybe instances that you find that you are unable to use the clipboard operations in a Remote Desktop Session in Windows 2008.

To resolve the issue, please follow the below

 Ensure that the fDisableClip set to 0 under
HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Winstations\RDP-Tcp

If fDisableClip is set to 1 rdpclip.exe will terminate, because clipboard mapping is disabled. Check that rdpclip is still listed under Addins

HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\Addins\Clip Redirector
Name REG_SZ RDPClip
Type REG_DWORD 0x00000003

Wednesday, February 8, 2012

Windows cannot log you on because your profile cannot be loaded

Log Name: Application
Source: Microsoft-Windows-User Profiles Service
Event ID: 1500
Level: Error
Description:
Windows cannot log you on because your profile cannot be loaded. Check that you are connected to the network, and that your network is functioning correctly.

Solution:

Note: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry

You only have to do these steps:
1- Logon with local admin profile. (or other account different that you want to use, but with admin privileges).

2- Back up all data in the current user's profile folder if the profile folder still exists, and then delete the profile folder. By default, the profile resides in the following location: %SystemDrive%\Users\UserName

3- Open regedit and go to HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList. Here you can see all SIDs of loaded profiles and probably you'll have some of them repeated but with .bak extensions.
4- So if you want to recover your profile, desktop icons, ect... you only have to delete the profile with no .bak extension and rename the other, deleting only the .bak extension of it:
Note SID is a placeholder for the security identifier (SID) of the user account that is experiencing the problem. The SID.bak subkey should contain a ProfileImagePath registry entry that points to the original profile folder of the user account that is experiencing the problem.

Ex: In Regedit (HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList) I have:

SID-1292428093-343818398-2115-158554 (1º Delete this Key)
SID-1292428093-343818398-2115-158554.bak (2º Rename This Key to SID-1292428093-343818398-2115-158554).

4- Restart your computer or Logoff and Logon with the profile that you want to restore and that's all, your profile will be restored Perfectly.

How to resolve black screen on Servers


We have had some Windows 2003 systems logon screens turn black no more gray background or the username and password fields turn from white to black so you can't see what your typing (this effects RDP and the console). They all still work if you can find them. As with the screenshot below you can see the problem is a nuisance.

The following maybe encountered in RDP, console or even DRAC access




The Fix:

Note: Always make a backup of your system before changing the registry

On a working windows 2003 system

1) open regedit
2) connect to remote registry
3 navigate to HKEY_USERS\.DEFAULT\Control Panel\Colors (on the effected system)
4) create a export of the current key
5) go to the working system, create a export of HKEY_USERS\.DEFAULT\Control Panel\Colors
6) import the working registry settings to the remote registry system that is effected by the black screen
7) Reboot the effected system the color should be restored now.


What the registry settings should be by default:

Windows Registry Editor Version 5.00
[HKEY_USERS\.DEFAULT\Control Panel\Colors]
"ActiveBorder"="212 208 200″
"ActiveTitle"="10 36 106″
"AppWorkSpace"="128 128 128″
"Background"="102 111 116″
"ButtonAlternateFace"="181 181 181″
"ButtonDkShadow"="64 64 64″
"ButtonFace"="212 208 200″
"ButtonHilight"="255 255 255″
"ButtonLight"="212 208 200″
"ButtonShadow"="128 128 128″
"ButtonText"="0 0 0″
"GradientActiveTitle"="166 202 240″
"GradientInactiveTitle"="192 192 192″
"GrayText"="128 128 128″
"Hilight"="10 36 106″
"HilightText"="255 255 255″
"HotTrackingColor"="0 0 128″
"InactiveBorder"="212 208 200″
"InactiveTitle"="128 128 128″
"InactiveTitleText"="212 208 200″
"InfoText"="0 0 0″
"InfoWindow"="255 255 225″
"Menu"="212 208 200″
"MenuText"="0 0 0″
"Scrollbar"="212 208 200″
"TitleText"="255 255 255″
"Window"="255 255 255″
"WindowFrame"="0 0 0″
"WindowText"="0 0 0″