Fix Event ID 4015
In follow up to our previous posting in regards to the event ID 4015 error in windows 2003 or windows 2008 we have created a registry file. You may use this to fix the error however please consult with your IT support department and use the file at your own risk.What is Error Event ID 4015?
The general message is " The DNS server has encountered a critical error from the Active Directory. Check that Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error. ...." This error will result in a considerably long delay when you boot your server. Thus to resolve the issue we need to fix the registry entry for windows timing. This may be one of the possible solutions but in our case it worked fine. Here is a snap shot of the error:
How to fix Event ID 4015?
Download the following registry file:

Error Event 4004 and 4015 Windows Server Stuck in Apply Settings
In one of our servers that runs Windows 2003 we noticed that the reboot time has significantly increased and it takes up to 30 minutes to reboot the server. In another post we will discuss how to reduce the shutdown or restart time for windows server however looking at the events we noticed multiple error event ID 4004 and error event ID 4015. Here is the solution that worked for us. We did change the registry inputs. Make sure you consult with your IT manager before making any registry changes as it can cause irreversible damage to your server if you are not fully aware of what change you are making. Solution: Step 1- You need to run the regedit.exe. For example in Windows 2003 or Windows 2008 click on "Start" then click on "Run" and type "Regedit" and press enter. This will open up the registry view. Step 2- Create a backup of your registry by clicking on "File" then "Export" and save the registry file to a safe location that you can recover even if the windows is not booting. Step 3- Locate the following registry keys. Just remember these errors generally are caused by the windows time provider protocol (W32Time). HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\TimProviders\NtpClient\ On the right pane you will see an entry called "Enabled" (type is "REG_DWORD"). Edit the value by double clicking on the entry and change the value from "1" to "0" Please make sure the base is "Hexadecimal". After the settings are applied close the registry settings. Restart the server and your problem should be resolved. Disclaimer: Please use the above instructions fully at your own risk. Changing windows registry may cause irreversible damages to your operating system thus you should discuss any of the steps with your system administrator.You were not connected because a duplicate name exists on the network. Go to System in Control Panel to change the computer name and try again.
In your network you may decide to update the name of a computer. Your computer can be part of a domain or workgroup. However in some cases you may have an old computer that you need to replace. After replacing that computer you may want to update the name of a new machine to match the name of the previous computer. In some cases then you may see the error of
Offsite computer support

Run command prompt as administrator in windows 2003

Contact Us
If you need any help with your server maintenance please contact us and we will do our best to help you with your requests.Mapped Drives Keep Disconnecting
For the users in a network that is controlled by a Server 2000 or Server 2003 you may notice that the mapped drives keep disconnecting. This will cause a lot of problems as many of the workstations may use the servers as a storage server therefore the mapped drive serve as a storage device. For example, in dental offices a dental management software like EagleSoft require the workstations to have access to the shared folders on the server as a mapped drive. To resolve the issue you need to take two steps. First you need to adjust the workstation to keep the connection alive (KeepConn). Next you need to set the server to ignore the autodisconnect option for idle connections.WorkStation (client) side:
You need to change some settings in your windows registry. Please STOP! If you are not familiar with these you may cause serious problem and damage your operating system. Please do these at your own risk! in the command prompt type (regedit) and presse "Enter" to start windows registry. In windows xp you need to click on Run first and then type "Regedit". In windows Vista and 7 just click on the start button (windows logo generally located on the bottom left of your screen). In the registry find the following path: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Parameters Look for KeepConn (It should be in blue color and the type is "REG_DWORD") If you don't have one right click on the right panel and define a new "REG_DWORD" and call that KeepConn Set the value of KeepConn to (Decimal 86400).Server Side:
On your windows 2000 or 2003 start your command prompt as administrator and run the following command: net config server /autodisconnect:-1 If you see access denied that means you have not run the command prompt as administrator. Please visit our posting to know how to do run the command prompt as administrator in windows 2003. By performing the above steps your problem of disconnecting mapped drives should be resolved and your drives should be always connected.Disable or Bypass Shutdown UI notification after Server 2003 Crash
You may have noticed that if a server 2003 crashes unexpectedly after the reboot there is a User Interface (UI) will show up to record the exact reason for the unexpected shut down. In this article we discuss how to bypass this UI automatically; this might be needed for the users who need their servers to automatically login to the admin account to start a program. To do so follow these steps:- Click on start menu
- Click on Run
- Type: gpedit.msc and press Enter
- the Group Policy Object Editor will be opened.
- On the left pane find "Computer Configuration"
- Expand "Administrative Templates" by double clicking on that or pressing the + sign.
- Click on "System"
- On the right pane find "Display Shutdown Event Tracker".
- Double click on "Display Shutdown Event Tracker" and in the Setting tab click on "Disabled".
- Press "Ok"