Raise a call with MICROSOFT .

1. Call 800-936-3100, and provide your Access ID to the customer service representative who will create your support incident and route you to the appropriate support engineer to work on the issue immediately. The support line is open 24x7x365.

2. Logon to https://premier.microsoft.com and click on “Submit Incident” on the left pane


Contact HP for hardware issues

Procedure to raise a case with HP for hardware issues :

1. Call HP @ 1800-633-3600
2. Option 1
3. Option 2
4. Say Shortcut – Proliant running microsoft
(If the server hardware is proliant with microsoft OS)
5. Else follow the IVR and select the appropriate Hardware and OS.
6. Note the Case ID and followup for hardware replacement.

How to check if a Windows server is running Microsoft Cluster Server.

1. Login to the server.
2. Open the services Console (Start>Run>Services.msc)
3. Check for the existence of the service “Cluster Service”
4. If this service exists, the serevr is running a Microsoft Cluster Server.
5. Follow these steps to check the status of Cluster Node and Cluster Group.
o Open Command prompt and type “CLUSTER NODE /status” -> This command will list the status of the nodes in the cluster
o Open Command prompt and type “CLUSTER GROUP /status” -> This command will list the status of the cluster groups in the cluster

Event logs not generated on the server.

Try to reboot the server if that does not work follow the below mentioned steps
1. Right-click on %SystemRoot%\System32\winevt\logs and select Properties.
2. Select the Security tab.
3. Click Edit button and click the Add button in the permissions dialog box.
4. In Select users, computers, or Groups dialog box ensure that under object types Built in Security Principals and the location as local computer name is selected.
5. Enter the object name as “NT SERVICE\EventLog” without quotes. And click OK. This group should have full control on the folder.
6. Once EventLog group is added add the rest of the groups with above mentioned permissions.

How to delete Files/Folders which are being blocked by the system.

You will get the following error messages when you try to delete a file/folder which is being blocked by the System or Application Processes running in the Task manager:

Access Is Denied
Sharing Violation Error
File/Folder is being used by applications. Please close the application and then try again.

You need to kill the handle. To kill the handle, use Process Explorer from Sysinternals (at URL: http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx)

How to delete the handle:

Run Process Explorer
Go to Find menu > Enter File/Folder name and then click on Search. You will see a list of processes blocking the file/folder.
Right click on the process and then click on Close Handle > Click Ok for confirmation.
Now you can successfully delete the file.

Remove terminal services license keys from client machine.

Terminal Services server issues temporary licenses to all the client machines connecting to terminal services. It is required for the terminal services to process the request in timely fashion and will generate the hardware ID to keep the licensing information for client machine. This hardware ID is stored on client machine. This hardware ID is used to check the expiry of license. If license is expired terminal services server can not re-issue license to same computer account. Generally all the temporary license are valid till 90 days.

There are two ways to get rid of this when a client machine needs to have access to Terminal Services session but its license has expired:

Change the computer name.
Remove the License key from client computer.
The second method is very useful. It just requires a registry setting to be removed from client computer. The following registry settings must be removed from client computer:


After deleting above sub-keys try connecting to your Terminal Services server you should be able to get in.

Problem with the extensible counter or the service

The timeout waiting for the performance data collection function “TermService” in the “C:\\WINDOWS\\system32\\perfts.dll” Library to finish has expired. There may be a problem with this extensible counter or the service it is collecting data from or the system may have been very busy when this call was attempted.

Restart the service Termservice. It will work fine.