On one fine day when I was busy with one of my project, one of my collegue tapped my shoulder, a bit panicking. He : Heiry, take a look at this... Me : Dude, what on earth have you done? (serious face) He : I dont know man, I uninstalled .Net Fx 4.5, reboot the machine and this happened Me : Dude, What on earth was the reason you uninstalled .Net Fx 4.5? He : Well, I thought .... Me : (Evil Smile) So here is the thing. When we uninstalling .Net Fx 4.5, those related features would be uninstalled as well, including a feature called User Interfaces and Infrastructure. Please refer to  here . There are 2 ways to get it done - locally or remotely. For the purpose of this post, I will do it remotely from another Windows Server 2012 member server. Issues : Unable to view GUI in Server 2012. Troubleshooting : it is straight forward, GUI is disabled, RDP to the server, the only screen one can see is : Resolution :  RDP to another Serv

There are 2 types of Windows Activation - KMS and MAK. However, for this post, I won't be discussing on what are those or their differences, as this post is to discuss an error in regards to KMS implementation.  Issues : The following error has occurred. Please resolve the error and try again. Description : Access is denied Troubleshooting   Used multiple IDs (Domain Admins as well as Local Admins), however issue stll persist. Thus, it is safe to rule out User ID privilege from the root cause.  UAC is enabled. Resolution :  Go to Volume Activation Tools again, but right click at it and choose Run as Administrator ( not Pin to taskbar, sorry for that ) Browse to your server name ,and press Next. Punch in alternative credential if needed.  If you need to activate your KMS, get it activated. In this case, I already activated my KMS, so I will skip to Configuration.  Once all steps above compl

I am pretty sure this issue occurred to almost all Wintel or Service Desk Engineers - User came to us, make a report saying that his or her ID was locked, and he or she did not know why (or did they?). Nevertheless, I have compiled on how I checked and resolved this issue in my environment, hopefully it will help yours too. Issues : Troubleshooting Account Locked Troubleshooting   Download Account Lockout and Management Tools from here . Get it extracted. Launch LockoutStatus.exe Go to File | Select Target... Put in target user name, domain, and if needed alternate domain admin credential. Press OK once done. Collecting data...

One of my user came to me and told me that he was unable to transfer a file (big  size file) to his external drive. He even bought a new one just for that - unfortunately, still failed. The error was : The file <File Name> is too large for the destination file system. as always, mark the key point there : file system. Issues : User was not able to copy large file to external drive due to above error. Troubleshooting   Right click at Computer > Manage  Computer Management console appeared. Go to Storage > Disk Management    At the right side, you will see more or less this screen. Note the Free Space for the external drive was so large, so logically there should not be any issue to copy any files. At the same time, please also note at the File System type (FAT32) If we look at the disk, the format also listed as FAT32 Resolution :   Copy all files inside the external storage to another location, as a backup. Next steps wi

In normal implementation, it is always a best practice to provide permission per group, rather than per individual ID. Simple reason is, it is easy to administer and manage. Therefore, it was what I did in one of my vCenter implementation, but I could not make it work. It just did not allow me to login using my Domain ID (which configured as part of Local Administrators members in vCenter server), although local ID (part of Local Administrators members as well) worked as expected. Issues : Error while connecting to vCenter Server using VMware vSphere Client. Error is : Error Connecting The vSphere Client could not connect to  "vCenter Server Name" You do not have permission to login to the server : "vCenter Server Name"   Troubleshooting   Assigned appropriate domain ID (MyDomain\DomainAdminID) to a Domain Group (MyDomain\Domain Admins)  Assigned that Domain Group to Local Administrators in vCenter server (Double kill!) Assign