A lot of installations don’t clean the old MSI and MSP files in the c:\Windows\Installer folder.
There is a nice tool to clean that mess in 2 mouse clicks with the name patchcleaner. URL: http://www.homedev.com.au/free/patchcleaner
By: Thomas Faddegon
A lot of installations don’t clean the old MSI and MSP files in the c:\Windows\Installer folder.
There is a nice tool to clean that mess in 2 mouse clicks with the name patchcleaner. URL: http://www.homedev.com.au/free/patchcleaner
Method #1
Won’t work with a maximized Window.
Method #2
Will move your Window to the right or left half of the screen in the same manner as dragging a window to the right or left of the screen will.
Method #3
will move your Window one display to the right or left.
This is an copy paste from a website. All credits to: http://www.sevenforums.com/tutorials/77361-move-window-keyboard.html
If you follow these steps you can create a self signed certificate with the following specifications:
Be aware that self-signed certificates can manipulate by a man-in-the-middle. You should not use this in critical production environments.
Please use windows 10 powershell in admin mode. Otherwise you will get errors
New-SelfSignedCertificate -certstorelocation cert:\localmachine\my -dnsname *.domain.local -NotBefore $([datetime]::now.AddDays(-15)) -NotAfter $([datetime]::now.AddDays(3560))
Now export the certificates. Before you copy/paste change the thumbprint with the thumbprint you get from the above command.
$CertPassword = ConvertTo-SecureString -String "YourPassword" -Force –AsPlainText Export-PfxCertificate -Cert cert:\LocalMachine\My\C6B46CEB7D3A40DB08E78B19FEDD3A24EA7A7919 -FilePath C:\test.pfx -Password $CertPassword Export-Certificate -Cert Cert:\LocalMachine\My\C6B46CEB7D3A40DB08E78B19FEDD3A24EA7A7919 -FilePath C:\tstcert.cer
Now you can import the PFX with IIS and bind the certificate in IIS.
And import the *.CER in your MMC > Certificates > Computer account > trusted root Certification authority > Certificates
Have fun with your certificate the next 10 years 😀
Today our domain controller had a very bad day and had a bootloop after a reboot. I used recording software to capture the blue screen error: STOP: c00002e2 Directory Services could not start
Then we found a nice article to fix this issue. We had a second working domain controller so if you have the same setup you can use this how to, to fix this problem also. All the credits go to dbutch1976
This should complete the repair. To verify that the repair has worked successfully:
You have bought een new system and the first thing what you want to do is check the disk performance (ehhh that’s always the first thing I want to know 😛 )
There is one tool I always use: ATTO Disk Benchmark
This is a very nice tool to quickly see how fast your troughput is of your new system.
But sometimes you want to check your IOPS. Then you can use another nice microsoft commandline benchmark tool DiskSpd
You can use this parameter to benchmark:
diskspd -b8K -d30 -o4 -t8 -h -r -w25 -L -Z1G -c20G testfile.dat
This example command line will run a 30 second random I/O test using a 20GB test file located on the T: drive, with a 25% write and 75% read ratio, with an 8K block size. It will use eight worker threads, each with four outstanding I/Os and a write entropy value seed of 1GB. It will save the results of the test to a text file called DiskSpeedResults.txt. This is a pretty good set of parameters for a SQL Server OLTP workload.
Example:
If you get errors like:
Results for timespan 1:
*******************************************************************************
The test was interrupted before the measurements began. No results are displayed.
Error generating I/O requests
Or file creation errors like “Error opening file: testfile.dat” please try to replace the minus “-” characters with your keyboard. Sometimes your browser copy the wrong character.
Happy benchmarking 😀
copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da\cleanmgr.exe to %systemroot%\System32
copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63\cleanmgr.exe.mui to %systemroot%\System32\en-Us
Run cmd > cleanmgr and remove all the nasty update files!
After I cleaned up the server I had to stop the windows installer service (trustedinstaller.exe) to remove the c:\windows\logs\cbs\CBS.log (6GB file) manually. Maybe a restart of the server do the same but I cannot test it on a production environment.
Have fun!
On my windows 2008 r2 server, Windows update was running forever 🙁
I tried a lot of things but fixing the problem was really simple:
Then your problem will be fixed automatically 🙂
Still problems? Try this post: http://superuser.com/questions/951960/windows-7-sp1-windows-update-stuck-checking-for-updates
Note: If you have a WSUS server and you still have problems to find windows updates you can try to temporary disable the WSUS client to change the registry key UseWUServer to dword:00000000
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU]
"UseWUServer"=dword:00000000
The ThinState USB disk is split into 2 partitions. And the second partition isn’t accessible in Windows so it was very hard to build a stick from scratch. There are a lot of Windows USB clone tools but because I had to clone the ThinState 16GB to a 8GB stick also, it was impossible to do it from my windows workstation. But when some things get more difficulty what do you do? Use Linux 🙂
$sudo dd if=/dev/sdb of=/dev/sdc bs=512
First resize the partitions with gparted to the minimum size. Then find out the last sector of the /dev/sdb2 (where sdb2 is my USB stick)
$sudo fdisk -u -l /dev/sdb
Output:
Disk /dev/sdb: 14,9 GiB, 16026435584 bytes, 31301632 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x6a60ab98 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 2099199 2097152 1G b W95 FAT32 /dev/sdb2 2099200 14131199 12032000 5,8G 7 HPFS/NTFS/exFAT
Now use dd with sector 12032000 + 1.
dd if=/dev/sdb of=/home/myusername/usbimage.img count=12032001
and write the *.img file back to your new USB stick:
dd if=/home/myusername/usbimage.img of=/dev/sdb
Copy the following files:
> copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.1.7600.16385_none_c9392808773cd7da\cleanmgr.exe C:\Windows\System32\
English:
> copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_en-us_b9cb6194b257cc63\cleanmgr.exe.mui C:\Windows\System32\en-US\
Dutch:
> copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31bf3856ad364e35_6.1.7600.16385_nl-nl_72d752f33b5fc86a c:\Windows\System32\nl-NL\
Run the cleanmgr.exe:
> cleanmgr.exe