Skip to main content

Posts

RDP error: This computer can’t connect to the remote computer in Windows 2012 r2

The problem looks like this: when you are trying to connect via RDP to a remote Windows server, the  mstsc.exe  client freezes for a minute and a window with the following message RDP error appears: Remote Desktop Connection This computer can’t connect to the remote computer. Try connecting again. If the problem continues, contact the owner of the remote computer or your network administrator .   If you can configure Remote Desktop setting using local group policy editor ( gpedit.msc ). The necessary policies are located in the following section: Local Computer Policy -> Computer Configuration -> Administrative Templates -> Windows Components -> Remote Desktop Services -> Remote Desktop Session Host. RDP security level can be specify using policy named  Require user of specific security layer for remote (RDP) connections . Enable this policy and in dropdown select  RDP Security  level.

ESM Log size is full - How to clear

                                            ESM log Size is full ---- How to Clear If your getting the below error in event viewer you can follow the below steps and solve it. Generally when we open Dell open manage console, suddenly we see that Hardware log status is showing critical and event logs are filling saying ESM log is full... We need to clear the ESM logs regularly before it reaches 100%. However please follow the below command and procedure before clearing the logs. Open Dell Manage console, go to logs tab. Then select ESM logs, you will see an export option. Export the logs and save it on local drive for future use. Now open command prompt and Runas administrator. Type omconfig system esmlog action=clear Done, your logs are cleared. Come back to Dell open manage console. Now hardware logs will show green which is normal. :-) :-)

Disk Cleanup on Windows Server 2008 Without Installing Desktop Experience

Windows Server 2008 is something every admin likes to work with (sense the sarcasm over the internet, Dr Cooper?).  The Problem Believe me or not, but an essential (Windows) tool, cleanmgr.exe, is not present in Windows Server 2008 and Windows Server 2008 R2 by default. This is by Microsoft’s, at the very least hard-to-explain, design, who likely believe it’s more of a desktop experience feature than a must-have tool. Why on Earth would I want to install Windows Photo Gallery and Windows Media Player on a server just to have Disk Cleanup? Moreover, it requires a server restart. Bonus: if you want to use WebClient service, you need to have Desktop Experience feature installed too. The Solution Windows Server 2008 (64-bit) Copy the following files: > copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr_31bf3856ad364e35_6.0.6001.18000_none_c962d1e515e94269\cleanmgr.exe C:\Windows\System32\ > copy C:\Windows\winsxs\amd64_microsoft-windows-cleanmgr.resources_31b

Script to Compress WinSXS

Compress WinSXS: A Script to compress WinSXS folder resided in Windows directory. if you are concern about the growing size of WinSXS folder taking so much of space then you can use this powershell script to reduce the size by compressing WinSXS folder data. This script is very usefull in the case when you need to compress WinSXS folder in large number of Servers/Desktops environment. #——————————————– # Script to compress WinSXS folder try { $winDir = “$($env:windir)” $winSxSDir = “$winDir\WinSxS” $aclPath = “$winDir\WinSxS.acl” $serviceMSI = “msiserver” $serviceTI = “TrustedInstaller” Stop-Service $serviceMSI Stop-Service $serviceTI Set-Service -Name $serviceMSI -StartupType Disabled Set-Service -Name $serviceTI -StartupType Disabled icacls.exe $winSxSDir /save $aclPath /t takeown /f $winSxSDir /r icacls $winSxSDir /grant “$($env:USERDOMAIN)\$($env:USERNAME)”:”(F)” /t compact /s:$winSxSDir /c /a /i * icacls $winSxSDir /setowner “NT SERVICE\TrustedInstall

Script to get the Uptime of multiple workstation and servers

Guys, Here is another script with which you will get the uptime of multiple workstation or server in just seconds. once you download the folder just copy list of server names in the notepad  named "ListOfServers"and run the batch script named "checkuptime" with elevated privileges once you run this script the result will be stored in the folder named Log. Please find the script below. https://www.dropbox.com/s/d0hon0rsek7x1sn/Uptime.rar?dl=0 Thanks for reading this. Enjoy Maddi........

Create Multiple Folders Through Script

Guys,Today I am going to share you a script which will help you create multiple folders. Just add the names of the folder which needs to be created in the FILE.TXT file. Copy Both the Text file and script in the folder where you want to create new folders and then run the script and see the Magic. All the folders will be created in seconds. Below is the link to the script. https://www.dropbox.com/s/fv01s5ipemgh00e/Folder%20creation%20script.rar?dl=0 Thanks for reading  more scripts will be coming up.

System Volume Information is taking more space

On one of the servers (running Windows Server 2012 R2) I faced a problem with the lack of free space on a system drive. I have cleared all resource-consuming locations ( WinSxS , TEMP directories, user profiles,  outdated updates , etc.), but it didn’t have any evident effect. At last, I have found that a large part of a system disk has been occupied by  System Volume Information  folder. Let’s consider why we need System Volume Information folder in Windows systems, what is stored in it and how to clean up it. Note . The instructions given in this article are applicable to other Windows versions as well:   Windows 10, Windows 7, Windows 8, Windows 2008 R2, Windows 2012 / 2012 R2. System Volume Information  folder is in the root of each disk. System data related to system recovery and Shadow Copy Service are stored in it. By default it is hidden and only the SYSTEM has access to it. Even the administrator cannot open it and look through the contents of the folder. To view the co