How to See Which Group Policies are Applied to Your PC and User Account

After completing the configuration of Group policy we need to check the user account and the computer that the applied policies are effectively working.

To check that the following are the command fulfills this requirement.


1. Go to run and type the command rsop.msc
















In command prompt

1. Policies applied for User account run the following command in command prompt

C:\>gpresult /Scope User /v








2. Policies applied for Computer, run the following command in command prompt

C:\>gpresult /Scope Computer /v


Unable to remove failover cluster feature in Windows2008R2


When you try to remove the Failover cluster features you will get an error message “This server is an active node in a failover cluster. Uninstalling the Failover Clustering feature on those nodes may impact the availability of clustered service and applications. It is recommended that you first evict the server from cluster membership. This can be done through the Failover Cluster Management snap-in by expanding the console tree under Nodes, selecting the node, clicking More Actions, and then clicking Evict.”


1. Run powershell as an administrator and type the following command

2. Import-Module FailoverClusters

3. clear-clusternode

Ref url:

SCCM Installation procedure and prerequisite

I have come across various errors while I try to install SCCM and finally I got the installation successful.
The following are the prerequisite for installing the SCCM 2012.

1. The Windows 2008R2 server should be a member of domain server. (You can install in a domain controller, but MSSQL recommends installing in member server only).

2. Net framework 4.0 should be installed.

3. IIS component should be installed.

4. MSSQL 2008R2 Standard / Enterprise edition (depends on your requirement) if you plan to install SCCM 2012 as Primary. Please go through the url given below.  or

If you install sqlexpress edition in the primary site, you will come across this error while SCCM check the prerequisite.
a.Required Sql server collation Failed.

b.Sql server service running account failed.

c.Sql server service sys admin rights failed.




5.  Windows Assessment and Deployment kit (ADK ) – To download this please find the url below

The installation procedure is given below in the blog

and the document also enclosed for documentation.

Note : In this blog the ADK prerequiste is not mentioned, but we need to install the prerequisite. After the successful installation we can proceed with SCCM installation.

Document url:



WDS service unable to start


You will get an error in the event log “The Windows Deployment Services Server service terminated with service-specific error Only one usage of each socket address (protocol/network address/port) is normally permitted” when the WDS service fails to start.

Problem Root cause:

The problem occurs when you install DHCP and WDS service on the same server. This problem rises to very few cases; else both DHCP and WDS service can work on the same server.


Change the registry values manually such that the WDS services not to use or to avoid conflict with DHCP ports. The procedures are listed

1. Open Regedit and go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WDSServer\Providers\WDSPXE






2. On the right hand side you can see “Use DHCP Ports” normally the value is 1 should be changed to 0.







Now the problem is fixed.

VMware vCenter Single Sign On install error 32010. Failed to create database users

I planned to upgrade Vcenter 5.0 to 5.1 but it throws an error when I try to install SSO. The error message and screen shot given below.

 Error Message: Error 32010. Failed to create database users. There can be several reasons for this failure. For more information, see the vmMSSQLCmd.log file in the system temporary folder.






I opened Windows Explorer and browsed to %TEMP% folder and opened the vmMSSQLCmd.log file in Notepad as instructed.

The file contained the following text:
Changed database context to ‘master’.
Msg 15118, Level 16, State 1, Server VCENTER01\VIM_SQLEXP, Line 1
Password validation failed. The password does not meet Windows policy requirements because it is not complex enough.

The issue was simply that the password provided by the customer for the Single Sign On accounts were not complex enough.

Provide complex password with alpha numeric and also special characters with minimum of 10 which helps successful installation of SSO.