Windows 2012/Windows 2012R2 - RDP lagująca myszka

Q: Jeśli podczas połączenia RDP laguje Ci myszka w oknie zdalnego pulpitu.
A: Wyłącz cień dla kursora :)

Windows 10 BSOD with video_tdr_failure igdkmd64.sys

That "igdkmd64.sys" is related to Intel HD Graphics 4600 Kernel Mode Driver. For me it looks like "igdkmd64.sys" file is corrupted. So I have tried below options,

1. Uninstall the Intel HD Graphics Drivers and reboot PC
2. Open Device Manager and navigate to Display Adapters-> Intel Graphics (right click) -> Disable.

After PC reboot you will not get any BSOD with video_tdr_failure.

Błąd 0x00000709 podczas wyboru drukarki na domyślną.

Jak Rozwiązać Problem:
należy zmienić uprawnienia wpisu w rejestrze dotyczącego drukarki domyślnej

w jaki sposób:

wpisujemy w pasku menu start regedit i przyznajemy akcji uprawnienia Admina.

odszukujemy :

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows

i prawym przyciskiem myszki na powyższym Kluczu (który przypomina katalog) wybieramy  uprawnienia.

nadajemy bieżącemu użytkownikowi i administratorowi i pewnie systemowi pełną kontrolę

następnie w:

HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows

usuwamy wartość podklucza device (w sensie nie cały podklucz tylko wartość przypisaną)

oraz jeśli występuje jakaś ścieżka do sterownika poniżej to też usuwamy wartość przypisaną.

Zapisujemy i resetujemy.

Następnie Wybieramy w drukarkach domyślną drukarkę. (tym razem bez błędu)

U mnie Działa...

Pozdrawiam mam nadzieje, że komuś się przyda. Jeśli tak proszę o komentarz.

VMware 5.5 - Windows Server 2012R2 losing network

If you use network card: e1000 or e1000e

You must install update:

https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2109922

Better options change NIC to: VMXNET3 (better and faster)
If you change NIC to VMXNET3, must install VMware tools (driver to NIC)

HP ProCurve - switch update firmware

swx# show version
Image stamp:    /sw/pre/build/nemo(ndx)
                Jan 25 2008 13:54:14
                R.11.07
                104
Boot Image:     Primary
BL-C234-AS01# show flash
Image           Size(Bytes)   Date   Version
-----           ----------  -------- -------
Primary Image   : 3689315   01/25/08 R.11.07
Secondary Image : 3689315   01/25/08 R.11.07
Boot Rom Version: R.10.06
Current Boot    : Primary

We see that’s we’re running firmware version R.11.07. When copying the firmware to my TFTP server, I’ll use the same filename convention that HP does, so our filename will be R\_11\_07.swi. Let’s save a copy to the TFTP server:

swx# copy flash tftp 192.168.1.12 R_11_07.swi

I always like to verify that the file actually shows up on the TFTP server, regardless of any error messages (or lack thereof) from the switch:

$ ls -l /tftpboot/R_11_07.swi
-rw-r--r-- 1 nobody nogroup 3689315 2009-02-02 23:28 /tftpboot/R_11_07.swi

In the meantime, I’ve downloaded the latest version of the software, R.11.25, from HP’s FTP server and saved it as R\_11\_25.swi on the TFTP server. Let’s go ahead and copy it over to the primary flash on the switch:

swx# copy tftp flash 192.168.1.12 R_11_25.swi primary
The Primary OS Image will be deleted, continue [y/n]?  y

Here we tell the switch to copy from a TFTP server to flash memory, the TFTP server has IP address 192.168.1.12, the filename on the TFTP server is R\_11\_25.swi, and that we want that file saved to the primary flash on the switch. You’ll see a progress counter as the file is transferred, then:

Validating and Writing System Software to FLASH...

which takes a moment. After it has completed, we can verify success by examining the contents of flash:

swx# show flash
Image           Size(Bytes)   Date   Version
-----           ----------  -------- -------
Primary Image   : 3790986   01/14/09 R.11.25
Secondary Image : 3689315   01/25/08 R.11.07
Boot Rom Version: R.10.06
Current Boot    : Primary

We can now reboot the switch with the new firmware:

swx# reload
Device will be rebooted, do you want to continue [y/n]?  y

After the switch boots back up, we can verify that it is running the latest firmware:

swx# show version
Image stamp:    /sw/pre/build/nemo(ndx)
                Jan 14 2009 15:31:02
                R.11.25
                301
Boot Image:     Primary

HINT: Always read the release notes before upgrading firmware, especially on a production device!

MegaCLI - rebuild

While replacing a bad drive with a drive that used to be part of another RAID array configuration, the RAID refused to automatically rebuild, thinking that I might want to import the configuration from this disk (or that there's data on there that I might need).

Simply inserting the drive doesn't make the controller rebuild the array with that disk. Here's how to manually make the drive get along with the rest of the new array:

(Note: this is a 64 bit server, so the MegaCli client I'm using is called "MegaCli64", if you are not running x64, you can simply substitute the commands below with the path to your megacli binary.)

server:~# MegaCli64 -PDlist -aALL -a0
[...]
Enclosure Device ID: 32
Slot Number: 4
[...]
Firmware state: Unconfigured(bad)
[...]
Secured: Unsecured
Locked: Unlocked
Foreign State: Foreign
[...]

Based on the information obtained above, I now know that the disk drive I just replaced is [32:4] ([enclosureid:slotnumber]) and is currently being reported as 'Unconfigured(bad)'.

To bring this drive back online run:

server:~# MegaCli64 -PDMakeGood -PhysDrv[32:4] -a0
Adapter: 0: EnclId-32 SlotId-4 state changed to Unconfigured-Good.

The controller will now recognize the disk as being a "foreign" one. This does not mean it was made in Japan (though, it likely was). It means it has detected some RAID configuration/data on it and thus, considers it as a disk being part of an array that may be imported into current controller configuration. Because of this, it will not automatically rebuild until you force it to.

Now you can ask the controller to scan for foreign configurations and remove them:

server:~# MegaCli64 -CfgForeign -Scan -a0
There are 1 foreign configuration(s) on controller 0.

server:~# MegaCli64 -CfgForeign -Clear -a0
Foreign configuration 0 is cleared on controller 0.

The disk should now be available for rebuilding into your new RAID array. To confirm, run this:

server:~# MegaCli64 -PDList -a0
[...]
Enclosure Device ID: 32
Slot Number: 4
[...]
Firmware state: Unconfigured(good), Spun Up
Foreign State: None
[...]

Excellent. We have a good, recognized (yet still unconfigured) drive now. Now we have all we need to add the disk back into the new array, and rebuild:

Get the disk [32:4] back into array 1, as disk 4:

server:~# MegaCli64 -PdReplaceMissing -PhysDrv[32:4] -array1 -row4 -a0
Adapter: 0: Missing PD at Array 1, Row 4 is replaced

And finally start rebuilding it:

server:~# megacli -PDRbld -Start -PhysDrv[32:4] -a0
Started rebuild progress on device(Encl-32 Slot-4)

Now, sit back, relax, grab a smoke and wait for it to rebuild itself into your new RAID array. Not so foreign anymore, huh?

Edit the registry inside a WIM file

An oldie but a goodie – this came about again when creating Windows 7 WIM files for SCCM. It really does save a lot of time – otherwise you would need to deploy your image, make changes to the registry and then recapture. This process is much quicker! I use the DISM tool from the WAIK toolkit but you could also use imageX to mount the image.
Steps:
Mount the WIM
Open the Deployment Tools Command prompt and enter:
dism /mount-wim /wimfile:d:temptest.wim /index:1 /mountdir:c:mount

Result:

D:>dism /mount-wim /wimfile:d:temptest.wim /index:1 /mountdir:c:mount

Deployment Image Servicing and Management tool

Version: 6.1.7600.16385

Mounting image

[==========================100.0%==========================]

The operation completed successfully.

Load the registry hive
From a command prompt enter:
reg load HKLMtest c:mountwindowssystem32configsoftware
Result:
D:>reg load HKLMtest c:mountwindowssystem32configsoftware
The operation completed successfully.

Open regedit
You will then see the registry that is contained in the WIM file, in this case it is called test. Make your changes, then exit regedit.


Unload the registry hive
From a command prompt enter:
reg unload HKLMtest
Result:
D:>reg unload HKLMtest
The operation completed successfully.

Unmount the image
Open the Deployment Tools Command prompt and enter:
dism /unmount-wim /mountdir:c:mount /commit
Result:
D:>dism /unmount-wim /mountdir:c:mount /commit
Deployment Image Servicing and Management tool
Version: 6.1.7600.16385
Image File : d:temptest.wim
Image Index : 1
Saving image
[==========================100.0%==========================]
Unmounting image
[==========================100.0%==========================]
The operation completed successfully.