Error: 0x800f0818 when installing SP1
Specifically this applies to: Windows 2008R2
If you look in:
%windir%\Logs\CBS\CheckSUR.log
You may see an error similar to:
Unavailable repair files:
servicing\packages\Package_for_KB2483614_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum
servicing\packages\Package_for_KB2483614_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
When you run "sfc /scannow" to repair the files they say nothing is wrong
but something is....
After you find out which files are causing the issues from the CheckSUR.log (from above) do a quick search on download.microsoft.com for this patch, in my case: "KB2483614" down load the right one for your version of Windows and then extract it from a command prompt:
Windows6.1-KB2483614-x64.msu /extract
Now you have to do some permission mojo, take permission of the files your going to replace in the "packages" directory:
Take Ownership!
takeown /f c:\Windows\servicing\Packages\package_for_kb2483614_rtm~31bf3856ad364e35~amd64~~6.1.1.1.cat
SUCCESS: The file (or folder): "c:\Windows\servicing\Packages\package_for_kb2483
614_rtm~31bf3856ad364e35~amd64~~6.1.1.1.cat" now owned by user "<your user here>".
takeown /f c:\Windows\servicing\Packages\Package_for_KB2483614_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat
SUCCESS: The file (or folder): "c:\Windows\servicing\Packages\Package_for_KB2483
614_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat" now owned by user "<your user here>".
Change Permissions!
icacls c:\Windows\servicing\Packages\Package_for_KB2483614_RTM~31bf3856ad364e35~amd64~~6.1.1.1.cat /GRANT Administrators:F
processed file: c:\Windows\servicing\Packages\Package_for_KB2483614_RTM~31bf3856
ad364e35~amd64~~6.1.1.1.cat
Successfully processed 1 files; Failed processing 0 files
icacls c:\Windows\servicing\Packages\Package_for_KB2483614_RTM~31bf3856ad364e35~amd64~~6.1.1.1.mum /GRANT Administrators:F
processed file: c:\Windows\servicing\Packages\Package_for_KB2483614_RTM~31bf3856
ad364e35~amd64~~6.1.1.1.mum
Successfully processed 1 files; Failed processing 0 files
All Gravy!
Change a Dynamic disk to Basic
I just got a usb -> sata reader and going through some old drives I found one that was a dynamic and, as you may know, dynamic disks don't work via USB. So I could hook it up to a sata interface or....
I downloaded HxD, a disk hex editor and opened the disk in it (uncheck read only after you've verrified your looking at the right disk). In sector 0, location 1C2 (sort by 10), the value should read "42" for a dynamic drive. Just edit the value to "07" and saved the changes. Since it was a usb drive I just dismounted an and rebooted. Back to the basics
Disk WEI of 5.9 on a new SSD
I'm on my 3rd SSD after these two died:
- Died in:< 7 days OCZ Technology 120 GB Vertex 2 Series SATA II 2.5-Inch Solid State Drive (SSD) OCZSSD2-2VTXE120G
- Died in:< 1month Patriot Inferno 120 GB SATA II 2.5-Inch Solid State Drive (SSD) with TRIM Support PI120GS25SSDR
- 3rd replacement:
Crucial Technology 128 GB Crucial RealSSD C300 Series Solid State Drive CTFDDAC128MAG-1G1
To note the two that died are both running the: SandForce SF-1222 and MLC NAND memory
So this time, I'm went with a brand that's tried and true and I trust. The Crucial C300, has a Marvell controller and Micron NAND memory.
The only problem I was having is when I ran WEI tests (Windows Experience Index) I got a 5.9 for the Disk performance. How could this be? I thought It was supposed to be an awesome drive?! Well, digging in deeper its worth noting that if one of the Disk tests fail during the benchmarking, the report defaults to a 5.9 for the WEI index for the Disk category.
To dig deeper I started running the command line equivalent to see if I can get more details: Winsat.exe
When running winsat disk I get the error:
> Running: Storage Assessment '-scen 2009 -drive C:'
Error: Failed to properly assess the disk.
The operation completed successfully.
When running the command directly:
I get the error:
C:\WINDOWS\system32>winsat disk -scen 2009
Windows System Assessment Tool
> Running: Feature Enumeration ''
> Run Time 00:00:00.00
> Running: Storage Assessment '-scen 2009 -drive C:'
Error: Failed to properly assess the disk.
The operation completed successfully.
> Run Time 00:00:00.08
> Total Run Time 00:00:04.34
Looking at the log: C:\Windows\Performance\WinSAT\winsat.log
I see:
3461474 (10280) - storage\diskprof.cpp:2324: Unable to open temporary file. Largest available contiguous space was: 802MB
3461474 (10280) - storage\diskprof.cpp:0283: Error: Failed to properly assess the disk.
The operation completed successfully.
3461506 (10280) - winsat\processresults.cpp:1480: > Wrote disk score to the registry 0
Going into this I wouldn't think that I would ever need to use Defrag anymore but for WinSat.exe and WEI to properly analyze the disk it needs to find a contiguous space large enough to perform this type of test. After running defrag the issue was fixed.
The WEI Disk score now: 7.7
To note:
- I could find very little documentation that goes beyond the "winsat /?" command to find more info on the triggers and what, specifically the trigger "-scen 2009" does. I've altered the "2009" only to get a failure: "Unable to open file: 0009" My guess is this is some type of argument that gets passed to diskprof.cpp
- I also saw some references to the prefetch folder when digging deeper into this with procmon. I'll need to dig deeper but I thought that Windows 7 automatically disables these on detection of an SSD as this is a fresh Win7 install.
SkipRearm
In Server 2008 R2 SkipRearm is now located in:
HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindows NTCurrentVersionSoftwareProtectionPlatform
If you activate Windows and change "SkipRearm" to 1 before you sysprep you won't have to reactive your new image.
http://www.computerperformance.co.uk/vista/vista_activation_hack_skiprearm.htm
http://technet.microsoft.com/en-us/library/cc721973%28WS.10%29.aspx
http://technet.microsoft.com/en-us/library/cc766514%28WS.10%29.aspx
Why does a CSS send a RST instead of a FIN on Keep Alive
Cisco Content Services Switch Basic Configuration Guide
http://theether.net/download/Cisco/ccmigration_09186a0080117623.pdf
keepalive type ssl - SSL HELLO keepalives for this service. Use this keepalive for all backend services supporting SSL. The CSS sends a client HELLO to connect the SSL server. After the CSS receives a HELLO from the server, the CSS closes the connection with a TCP RST.
keepalive type tcp - A TCP session that determines service viability (3-way handshake and reset (RST)). By default and in compliance with RFC 1122, the CSS sends a RST to close the socket on a server port for TCP keepalives. A RST is faster than a FIN, because a RST requires only one packet, while a FIN can take up to four packets. If your servers require a graceful closing of a socket using a FIN, you can use a script keepalive.
Use the advanced-balance command to specify an advanced load-balancing method for a content rule that includes stickiness. A content rule is “sticky” when additional sessions from the same user or client are sent to the same service as the first connection, overriding normal load balancing. By default, the advanced balancing method is disabled.
source:
http://theether.net/kb/100005
Longest Uptime on a Windows server?
Found this today. This is a database server running SQL 2000 and activly running websites.
1362 days, 12 hours, 16 minutes of uptime!
Windows Server 2003 with no Service Packs.
Yes... although the saying goes... if it isn't broke don't fix it, we are going to patch it
Restarting Terminal services, without reboot
notes:
You will need console/drac access to the server
Microsoft decided to disable the ability to restart terminal services. In article KB 278657 Microsoft states that this behavior is by design... well that doesn't help, if its down, does it.
Thankfully there is a great tool that many of you are familiar with, Process Explorer.
1. DRAC or get console access to the server
2. go to http://live.sysinternals.com and download procexp.exe
3. open process explorer
4. open the "View" menu and click on, "Select Columns" and choose "Command Line"
5. sort by "Process" and look for the "svchost.exe". If you expand the "Command Line" column, you will see a line *"svchost.exe -k termsvcs"
6. End this "svchost.exe" process by right clicking and "Kill Process".
7. Now you can just go to "services.msc" and restart Terminal Services!
note: In 2008 you will have to start procexp.exe with "Administrator rights" in order to kill processes.
WMI 80070776: The object exporter specified was not found
hey guys, I've been researching this issue and found many topics on this in the forums so i wanted to let you guys know how i fixed it. I was getting this error to all the servers i was trying to make WMI calls to, as well as the WMI Tester tool. http://www.paessler.com/tools/wmi_tester
80070776: The object exporter specified was not found
While capturing TCP dumps using Wireshark i was noticing that in the traffic the server being monitored was sending its server name to my monitoring server for some reason. I thought this was quite odd, so I added the shortname of "server" and NOT the FQDN name to my HOST file along with the public ip addresses of the server and this worked like charm!






