Stay Connected
Microsoft
Windows Server 2003: Disable Internet Explorer Enhanced Security by script?
Oct 26th
After 6 years of working with Windows Server 2003 I finally made this script to disabe the restricted IE mode. Microsoft already fixed this feature for Windows Server 2008 and it can be easly switched off in Server Manager. For Windows Server 2003 you still need to open appwiz.cpl and run the steps.
The screenshot below made me creating this script:

Microsoft Internet Explorer’s Enhanced Security Configuration is currently enabled on your server. This enhanced level of security reduces the rish of attach from Web-based content that is not secure.
This message make sense but not when I need to update latest firmware, drivers or work on a CA as shown in my example.
Create new file named disable “IE-Security.txt” and paste text below.
[Components]
IEHardenUser=Off
IEHardenAdmin=OffSave the file and run SYSOCMGR.EXE /i:%windir%\inf\sysoc.inf /u:c:\IE-Security.txt
This made my server now less secure but my life easier to get this done.
Sharepoint 2007: Office SharePoint Server Search service missing??
Oct 23rd
For last couple of hours I am struggling with installing the SSP provider for Sharepoint 2007 server. During the creation of a new SSP provider a Indexer is required; well I can’t select any because it is empty. Searched on google and found out that I need to start “Office SharePoint Server Search” service in Central Administration website “Central Administration > Operations > Services on Server” and enable that service. Guess what? The service is missing.
Example screenshot:
Than I found my mistake. During the installation of Sharepoint 2007 I choose for Server type"Web Front End" instead of “Complete”.
I went back to my notes I created during the installation and I saw in the screenshot “Web Front End” server type was selected…
Related links:
OCS: Office Communications Server down after KB974571
Oct 19th
Last week Microsoft released serveral security updates and KB974571 broke our production OCS 2007 server at our hosted environment. Serveral events were shown in the Systemlog:
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7038
Date: 10/17/2009
Time: 7:04:25 PM
User: N/A
Computer: OCS
Description:
The RtcSrv service was unable to log on as domain\RTCService with the currently configured password due to the following error:
Logon failure: unknown user name or bad password.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 10/19/2009
Time: 8:52:23 AM
User: N/A
Computer: OCS
Description:
The Office Communications Server Front-End service terminated with service-specific error 3286842403 (0xC3E93C23).10/19/2009 5:37:19 AM OCS Server 1000 12290
The evaluation period for Microsoft Office Communications Server 2007 has expired. Please upgrade from the evaluation version to the full released version of the product.
Please make sure you don’t install the “MS09-056: Vulnerabilities in CryptoAPI could allow spoofing” KB974571 until this problem has been fixed.
MS09-056: Vulnerabilities in CryptoAPI could allow spoofing:
Known issues that affect this security update
Services that are required by Communications Server are not started after you install this update and then restart a computer that is running any of the following versions of Communications Server:
- Live Communications Server 2005 (LCS)
- Live Communications Server 2005 SP1
- Office Communications Server 2007 Enterprise edition (OCS)
- Office Communications Server 2007 Standard edition
- Office Communications Server 2007 R2 Enterprise edition
- Office Communications Server 2007 R2 Standard edition
- Office Communicator 2007 Evaluation version only*
- Office Communicator 2007 R2 Evaluation version only*
When this problem occurs, the required services behave as if an expired trial version of the product is installed. This behavior affects the whole Communications Server enterprise that is hosted by the affected server or servers.
Microsoft is investigating this issue, and will determine the most appropriate way to address it. Customers who are not running OCS or LCS server are not affected by this known issue, and can safely ignore this issue.
Customers who have deployed the OCS or LCS product on a server should assess the risk that is involved to decide whether to install the security update on that server. These customers should revisit this Knowledge Base article often, because this article will be updated as soon as more information and a resolution are available.
Windows 7: Release to Manufacturing
Jul 29th
Development of Windows 7 has completed and Microsoft announced release to manufacturing (RTM).
It’s almost here! We’re very happy to tell you that we’ve hit the last big milestone on the way to Windows 7: Release to Manufacturing. We’re packaging copies and manufacturers are putting it on new PCs. On October 22, you’ll be able to get the final shipping product. Pat yourself on the back for a job well done; you helped make this an operating system we’re all going to enjoy.
Don’t miss the good stuff. With the final release rapidly approaching, make sure you learn about special offers and other news including details about launch events in your area. A great way to keep up with what’s going on is to sign up for one of our free newsletters. Not only will you get the scoop on the Windows 7 launch, you’ll get useful news throughout the year.
Last week I bought my first MAC ever and just started learning MacOS, but still looking forward to get Windows 7 loaded on all my systems.
Windows 2003: Windows could not start?
Jul 14th
Last night we lost our Openfiler SAN with a “kernel panic” stop message and all virtual machines located on the VMWare ESX cluster were frozen. After I found the problem and I reboot the SAN box; I than encountered another problem on one of our development SQL server. Just after the POST phase a black screen was shown and boot process stopped. I did not create any screenshot of this window but it was something like:
Windows Server could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM
Last time I had this error I was not able to fix this problem without reinstalling the OS. No recent backup of this VM and I run out of my options to get this VM up and running again.
What I did than:
- Shutdown the VM
- Shutdown another working VM
- Mount the virtual disk of the failed Windows installation on the second VM and boot.
- After Windows was boot of the second vm I assigned a disk letter of the failed Windows instllation.
I went to E:\Windows\System32\config and got the following error message.
\Windows\System32\config is not accessible. The file or directory is corrupted and unreadable.

I than right clicked on the volume; went to properties and opened tools tab. I clicked “check now” to repair the volume. After 9% I got warning volume and the process stopped. I was lost again. But than I remembered one tool which I tried than.
chkdsk e: /f

After the process and check & fix were finished I was able to access all folders. I than shutdown the VM disconnected the virtual disk and boot the development SQL server. After 5 minutes the machine was up and running. This saved me at least couple of days of work to restore the configuration and make everything working.

Windows showed me the warning ” Windows-Registery Hive Recovered”. I was again being able to logon on the server and make sure proper backup was in place now. Same can be done with physical disk but make sure you install the HDD into another machine!




