21Sep 2018 by Ceyhun Kirmizitas No Comments
Do you want to go to http://SiteName? – Disable One-word Intranet Site Suggestion – Internet Explorer

Do you want to go to http://SiteName? – Disable One-word Intranet Site Suggestion – Internet Explorer

Microsoft
Internet Explorer 9 will not navigate directly to an intranet site for a one-word entry in the Address bar. When you attempt to browse to this site using Internet Explorer 9, it responds by taking you to your default search engine to look for that word. Cause: Internet Explorer 9 combines the address bar and the search box. The default behavior is to use a single word entry as search criteria. This can be changed by Users or Group Policy Settings as described in the Solution section. Solution 1  - Using Tools Menu in IE9 : 1-  Click Internet Options 2- click the Advanced tab, check the option Go to an intranet site for a single word entry in the Address bar. Solution 2 - Using Group Policy : 1- Expand User Configuration,…
Read More
13Sep 2017 by Ceyhun Kirmizitas No Comments

KB373931- Srv2.sys SMB 2.0 Server Driver Fix – Windows Server 2008 R2 BSoD Problem – Windows6.1-KB373931-x64

Windows Server
Some Windows 2008 R2 servers may experience BlueScreen and Reboot problem. If these servers are using File Share or SMB v.2, srv2.sys may cause this problem. There is problem related to Srv2.sys driver. This is SMB 2.0 server driver. You can install this hotfix KB373931 for Windows Server 2008 R2 SP1 with your own risk.  
Read More
16Aug 2015 by Ceyhun Kirmizitas No Comments
WinRM service failed to create the following SPNs: WSMAN – Event ID:10154

WinRM service failed to create the following SPNs: WSMAN – Event ID:10154

Linux, Windows Server
I was getting an error " The WinRM service failed to create the following SPNs: WSMAN/hostname; WSMAN/hostname. " at startup on Windows 2008 R2 Domain Controllers. Additional Data Log Name: System Source:  Microsoft-Windows-WinRM Event ID: 10154 Level:  Warning Solution: WinRM runs under " Network Service " account. You can eliminate this problem by giving Validated Write to Service Principal Name  permission to the NETWORK SERVICE using the ADSIEDIT.msc. This will allow WinRM to auto create the necessary SPNs on that domain controller. After granting this permission, re-sync all DCs and do a reboot to each domain controller where you did the change,  after that reboot you will see that the warning is gone and the required SPNs were created successfully. Steps: 1- Use ADSIEDIT.msc 2- Choose Default naming context and…
Read More