Procedure to clearing the ConfigMgr (SCCM) client local cache (CCM cache) -Resolving Disk space isssue

Essentially the client cache is a temporary download location for software, applications and software updates that are deployed to a client.

By default, the client cache is located %windir%\ccmcache but you do have the option of changing this at install time by using the SMSCACHEDIR parameter e.g. CCMSetup.exe SMSCACHEDIR=C:\Temp.

By default, the cache size is 5120 MB, but again we can change this by using the SMSCACHESIZE parameter at install time e.g. CCMSetup.exe SMSCACHESIZE=10240. 

This would install the client with a cache size of 10GB. You can also change these settings post install either directly on the client itself using the Control Panel applet (See below), or for larger scale changes, by deploying a script.

Procedure

Navigate to Configuration Manager in Control Panel of the client computer, and then double-click to open its properties.

Click the cache button.

                                       .

To delete all of the files currently stored in the temporary program download folder, click Delete Files. Click Yes and close the screen

Windows Server 2008 R2: Procedures to cleanup WINSXS folder

Applied operating systems

Windows Server 2008 R2

Prerequisites

It is not recommended to delete the winsxs folder directly. Deleting this folder may cause BSOD error and OS may crash permanently.

• Download and install the Windows Update Pack Windows6.1-KB2852386-v2-x64.msu from the below link:  http://download.microsoft.com/download/2/A/3/2A3FD850-E45F-47D4-AFF8-8048333CBA7D/Windows6.1-KB2852386-v2-x64.msu 

• Disk cleanup utility

 The disk cleanup utility will be added by installing the Desktop Experience feature from Windows Server manager.

Procedures

Please follow the below procedures to install the desktop Experience feature

Step1: Go to server manager and select add features.

Step2: Select desktop Experience feature from the list and follow the installation.

Step3: When installing Desktop Experience, it does require additional features. Select the 

button to Add Required Features and click next and then Install.

  Step 4: A reboot is required to finalize the install.

  After reboot, a Disk Cleanup option can be found under Start --> All Programs --> 

Accessories --> System Tools:

On launch, Disk Cleanup prompts for the drive you want to clean up

Select the C drive and click OK.

Several options are provided for cleanup, including a new option for Windows Update 

Cleanup:

 

After preceding the cleanup a reboot is required to complete the cleanup process.

Here we will show one of the examples from the server USCHCVMP365AD08.us.na.ey.net

We were faced a disk space issue on this server which is showing only 19.1 MB free space

 on its C drive.

While checking the Winsxs folder, it consumes around 12 GB of size as shown in the below image:

While using the disk cleanup it showing around 4.71 GB of Windows update cleanup data.

After rebooting the server the winsxs folder consumed space reduced to 7.32 GB from 12 
GB.

Windows cluster Troubleshooting: Cannot assign new shares on file servers

Applies to

• Windows Server 2008 R2
• Windows Server 2008

Problem

In a two-node cluster, the cluster node 1 shows the correct disk size and we can share any folder as required. But for cluster node 2, we cannot initiate new shares from a particular disk. For our scenario, in node 2, the currently assigned size for the application folder is 250 MB, and there is no free space on that.





The worst case is that, whenever we fail over the cluster, it will not happen because of the application folder size is only 250 MB. Event logs will generate for the same.

Solution

Check the event ID numbers as shown below
Event ID:1037

The file system for one or more partitions on the disk for resource 'Cluster Disk 2' may be corrupt.

Run the Validate a configuration wizard to check your storage configuration. Optionally, you want to run 'Chkdsk' to verify the integrity of all volumes on this disk.
Event ID:1038:

Ownership of cluster Disk 2has been unexpectedly lost by this node. Run the Validate a configuration wizard to check your storage configuration.

From the cluster node 1, we can assign the new shares to the cluster resources.
Check the Shared storage management in both nodes for shared disks and folders information.
 The Disk size showing the correct figure.

We found that the Disk Quota is enabled for all drives.

Open server manager. Expand file services. Expand Share and storage management. Open file server resource. Expand Quota Management.

Open Quotas. It will list the quota assigned to the server.

Right-click the particular drive. Select Edit Quota properties.

 

The assigned Disk Quota limit is 250 MB instead of 250 GB from the drop-down list.

Change the Disk Quota space. In our case, it is 250 GB.

 Verify again the resource disk size by opening fail-over cluster management console. It 

will display the correct disk resources and we can create the new shares for applications.

Windows: How to check previous IP address details

Operating system

Windows 2008 Server/ Windows 7

Scenario

After replacing the motherboard, need to assign old IP configurations But unfortunately, customer is not aware of previous IP address details.

Solution

In this case, using registry we can find out previous IP address details. Windows Registry path should be specified below:

Open the registry editor and locate the interfaces path.

Current and previous IP address details will list under:

“HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Prameters\Interfaces”


There is a chance of multiple interfaces when we installed VMware or any other related application