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!
No ASP.NET tab in IIS x64
We have Windows Server 2003 R2 Enterprise x64 Edition
Some of our web applications require .NET framework 1.1 while others require framework 2.When we tried to migrate our applications from the old server to new server, we encountered the issue that 64-bit IIS can not run 32-bit ASP.NET v1.1, without running IIS in 32-bit mode.
We followed the solution described at the following link:
http://support.microsoft.com/kb/894435
Though this seems to work but this has made ASP.NET tab on website properties disappear.
I did some searching around and it seems this is a known issue. Here is a link from a msdn blog:
http://blogs.msdn.com/pmanchan/archive/2007/02/13/asp-net-tab-is-missing-in-the-iis-mmc-in-the-web-server-running-windows-xp-pro-x64-edition-with-net-framework-2-0-wow64.aspx
It seems that the only work around is the following:
"To configure the virtual directories to use specifc ASP.NET versions, you will have to use the command line tool.
aspnet_regiis -s <path of the application>
(Install scriptmaps for this version at the specified path, recursively. Existing
scriptmaps of lower version are upgraded to this version.)
E.g. aspnet_regiis.exe -s W3SVC/1/ROOT/SampleApp1
OR
aspnet_regiis -sn <path of the application>
(Install scriptmaps for this version at the specified path, non-recursively.
Existing scriptmaps of lower version are upgraded to this version.)"
DCOM Problems – Explorer Unresponsive
When the server boots, it goes all the way to the CTRL+ALT+DEL window.
After logging in, the Windows Desktop and Taskbar just seem to never
appear. It just sits there. Eventually, after several minutes, the
desktop appears but is generally unresponsive.
After some research and troubleshooting, I was able to get to the
desktop by disabling the Computer Browser service and the DCOM Server
Process Launcher service. By doing so several applications no longer
work.
In the Event Log you see errors such as:
Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10010
Date: 7/22/2008
Time: 2:30:35 PM
User: N/A
Computer: 168612-TS1
Description:
The server
did not register with DCOM within the required timeout.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
If you go to http://live.sysinternals.com and download regmon.exe you are able to see that you have major problems in the registry with permissions!
It appears as some MS patch changed the permissions on the following
registry key:
HKEY_CLASSES_ROOT\CLSID
In order to resolve the problem, the following permissions were added
Registry Key: HKEY_CLASSES_ROOT\CLSID (and all child keys and values)
Permissions Added:
Authenticated users: Read access
Network Service: full control
MS Article (unrelated):
FIX: A COM+ application stops responding, and desktop icons and the taskbar may not appear as expected on a computer that is running Windows Server 2003
http://support.microsoft.com/kb/904388/en-us
SQL Analysis Server: The peer permaturely closed the connection
Problem:
When trying to connect to the analysis server using our program i'm getting a connection error. "The peer permaturely closed the connection"
Solution:
I found that Analysis Server was indeed started and setup correctly. what resolved the issue is setting the "Anonymous" user account in IIS for the website to a domain account. This resolved the issue. I found that the application was on the web server was trying to connect to the domain server with an "anonymous" account. You can see this by running a SQL Trace on the DB server on Analysis Services ending in an error. After turning off anonymous access on IIS for this Virtual Directory, It worked as IIS forced me to specify my credentials, which was a domain account, and everything worked fine, as you can also see in the SQL trace that the web application is now connecting via my domain account instead of the "Anonymous" account.
Also, you have to create a "role" membership to have the "domain account" account for that cube inside analysis services.
Understanding MTU on Windows
In Windows or Linux, the highest packet you can specify before fragmentation is 1472. Linux is a little better and reports the complete packet size:
user@server:~$ ping 67.192.224.122 -M do -s 1472 -c 1
PING 67.192.224.122 (67.192.224.122) 1472(1500) bytes of data.
1480 bytes from 67.192.224.122: icmp_seq=1 ttl=119 time=13.3 ms
You can notice that on this linux server it shows the size you specified: 1472 and in addition the total size: 1500
As you can see I pinged with 1472 which is the maximum size you can ping with before the 28 bytes IP/ICMP header information is added, which brings it up to 1500.
When you specify the packet size in windows:
Pinging www.dslreports.com 209.123.109.175 with 1472 bytes of data:
Reply from 209.123.109.175: bytes=1472 time=42ms TTL=49
It does not show the actual packet size but only the size you specified.
You can ping with a much bigger packet size than 1500 but this is the maximum size before the packet is fragmented which you can limit fragmentation by specifying the "-f" option when pinging:
C:\>ping -f -l 1473 www.dslreports.com
Pinging www.dslreports.com 209.123.109.175 with 1473 bytes of data:Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
Packet needs to be fragmented but DF set.
As you can see the "-f" option was specified, ping was set to not fragment the packet when sending.
By default most net devices have a MTU value of 1500:
You can verify this on the firewall:
sh run | i mtu
mtu outside 1500
mtu inside 1500
References:
TCP/IP and NBT configuration parameters for Windows
http://support.microsoft.com/kb/314053/en-us
Max MTU: How do I find mine? (#695)
http://www.dslreports.com/faq/695
Windows TCP/IP Registry Entries
http://support.microsoft.com/kb/158474/en-us
Tools:
http://www.dslreports.com/tweakr
http://www.dslreports.com/drtcp






