Archive for the ‘Windows Server 2008 R2 SP1’ Category
Do you know the problem reboot your server and you can’t RDP to it but you can ping and if you are in the same subnet you can RDP ?
Well maybe you hit a bug , yes I was surprised to where is my DGW ? try bing and you find more of the same problems but easy to fix with a hot fix but why one server does this and others don’t ?
See in google / Bing / Yahoo
The default gateway setting is lost when you reboot the server
for some reason my LAN just suddenly lost its Default Gateway
No Default Gateway ?
Default Gateway Missing After Reboot
my tcpip default gateway gets reset on reboot
It looks like this after a reboot your Ip and subnet and DNS is there but no default Gateway
And if you looked it up in the registery
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipPara
metersInterfaces<GUID>DefaultGateway
Where <GUID> is the interface value for the network card.
It is not there , sure you can put it in but after a reboot it is gone.
Yes a scheduled task 
No there is a hot fix for this.
Or you can reset the IP stack.
netsh int ip reset
netsh: this is a Windows utility that allows one to display or change network settings locally or remotely.
int: this argument specifies that you wish to use the “interface” context within the netsh utility.
ip: this argument specifies that you wish to use the “ip” context within the “interface” context of netsh. An example of another context that could have been specified here instead would be “ipv6.”
reset: this argument is an instruction within the previously-specified context and subcontext means what it says, to reset to default.
Consider the following scenario:
- You use the netsh command to enable a network interface on a computer that is running Windows Server 2008 or Windows Vista. The computer retrieves IP addresses from a DHCP server.
- You use the netsh command to set a default gateway for the network interface.
In this scenario, the default gateway is set successfully. You can verify it by running the ipconfig /all command. However, the default gateway of the network interface is missing after the computer restarts. If you double-click the following registry entry, you find that a null character exists in the value data of the DefaultGateway subkey:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesTcpipParametersInterfaces<GUID>DefaultGateway
Note <GUID> is the interface value of the network card.
To work around the issue, use the following command to set the default gateway on the interface:
Netsh int ipv4 set address <Interface Name> source=dhcp
Go here to get the HOTFIX :
Article ID: 973243 – Last Review: February 16, 2011 – Revision: 6.0
Technorati Tags: Lost,Default,Gateway,Windows,Yahoo,Reboot,HKEY_LOCAL_MACHINE,SYSTEM,CurrentControlSet,Services,Tcpip,Para,Interfaces,GUID,DefaultGateway,Where,interface,display,argument,context,Consider,scenario,computer,Server,Vista,DHCP,double,data,Parameters,Note,issue,Netsh,Name,HOTFIX,Article,Last,Review,February,Revision,same,subnet,find,reset,value,network,card,specifies,wish,within,here,command,restarts
WordPress Tags: Lost,Default,Gateway,Windows,Yahoo,Reboot,HKEY_LOCAL_MACHINE,SYSTEM,CurrentControlSet,Services,Tcpip,Para,Interfaces,GUID,DefaultGateway,Where,interface,display,argument,context,Consider,scenario,computer,Server,Vista,DHCP,double,data,Parameters,Note,issue,Netsh,Name,HOTFIX,Article,Last,Review,February,Revision,same,subnet,find,reset,value,network,card,specifies,wish,within,here,command,restarts
Well It sounds nice install SP1 and you get new features and it is SP1 greats new stuff for your Hyper-V server. But It can be a disaster for your server. Make sure you always got a backup of your server.!
these are the errors and the errors are not fixable ! there is a work around with a *
Faulting Application Path: C:WindowsservicingTrustedInstaller.exe
Problem signature
Problem Event Name: APPCRASH
Application Name: TrustedInstaller.exe
Application Version: 6.1.7600.16385
Application Timestamp: 4a5bc4b0
Fault Module Name: cbscore.dll
Fault Module Version: 6.1.7601.17514
Fault Module Timestamp: 4ce7c541
Exception Code: c0000005
Exception Offset: 000000000005bc2e
Problem signature
Problem Event Name: CbsPackageServicingFailure2
Stack Version: 6.1.7601.17514
Package: Package_for_KB976932
Version: 6.1.1.17514
Architecture: amd64
Culture: unknown
Status: 800705b4
Failure Source: CBS Other
Start State: Partially Installed
Target State: Installed
Client Id: SP Coordinater Engine
If you have the errors above and you are trying to logon to your server it is pending for uninstalling the Service pack and stays there forever. What can you do ?
Well you can boot in safe mode or get the ownership of the pending.xml and rename it.
mm sounds easy connect to your server \servernamewindowswinsxspending.xml
take ownership if you need and rename this file. Poweroff your server and you can logon again.
Easy but your server is fucked up beyond any repair
Now you think you can start the setup again and yes you can but the next error is “ Wait for the Windows Modules Installer “ ?
yes see where the pending.xml file is ? well it is not there anymore. Just poweroff the server start in safe mode and reboot.
But what now ? This server is fried I have not found a solution to fix this or to recreate this issue. Next week I’m in redmond and will ask the Team how to solve this.
The problem is the HKLMcomponents hive is still loaded in the register. and you can’t do a unload. So therefor any update will fail. I has not finished the update the machine thinks it is still pending
well I tired another setup with out the auto reboot I do this manual 
Service Pack installation failed with error code 0x80070bc9. and Initiating changes for package KB976932. Current state is Partially Installed. Target state is Absent. Client id: SP Coordinater Engine.
Well this means I need to reboot the server.
So there is direct fix but you can use your server everything works but there is still a problem with this server.
hope this helps if I find a solution I will let you know.
Technorati Tags: Service,Pack,Ends,features,Hyper,server,disaster,Make,backup,Application,Path,TrustedInstaller,Problem,signature,Event,Name,APPCRASH,Version,Timestamp,Fault,Module,Exception,Code,Offset,Stack,Package,Architecture,Culture,Status,Failure,Source,Start,State,Target,Client,Coordinater,Engine,boot,mode,ownership,Poweroff,Easy,setup,error,Wait,Installer,Just,solution,Team,HKLM,components,machine,auto,installation,Current,Absent,errors,Modules,rename,reboot
WordPress Tags: Service,Pack,Ends,features,Hyper,server,disaster,Make,backup,Application,Path,TrustedInstaller,Problem,signature,Event,Name,APPCRASH,Version,Timestamp,Fault,Module,Exception,Code,Offset,Stack,Package,Architecture,Culture,Status,Failure,Source,Start,State,Target,Client,Coordinater,Engine,boot,mode,ownership,Poweroff,Easy,setup,error,Wait,Installer,Just,solution,Team,HKLM,components,machine,auto,installation,Current,Absent,errors,Modules,rename,reboot
You are receiving this invitation based on the quality of feedback you have provided on previous Windows programs and the Microsoft Windows release team would like you to participate in the Microsoft Windows 7 and Windows Server 2008 R2 Service Pack 1 (SP1) release program, to be available shortly, as announced at the Microsoft’s TechEd conference.
Accepting this invitation will allow you to access pre-release versions of the Service Pack for the purposes of validating the release readiness. We highly value your past feedback and know we can count on you again to help us build a great new version of Windows!
The SP1 release version is not available quite yet but we need to assemble a great team of program peers early so you are ready to go when we are! If you accept this invitation you’ll be notified when the release version becomes available.
What you will get if you choose to participate
• Early access to downloadable Windows 7 SP1 and Windows Server 2008 R2 SP1 releases
• Access to private newsgroups to share information about the release with other program peers and with Microsoft staff
• The ability to report bugs and track their status
• An opportunity to help us build a better Windows by validating the release readiness
What we will ask of you if you choose to participate
• Download and install Windows 7 SP1 or Windows Server 2008 R2 SP1 on at least one PC each
• File bugs if you encounter them as well as respond to surveys as you can.
• Validation we are seeking
o Set-up and installation
o Application Experience/Compatibility
o Device Experience/Compatibility
• We ask that you actively participate in discussions on the newsgroups and share your opinions with us and others
Read more : zdnet.com
