Showing posts with label Windows 2008 server R2. Show all posts
Showing posts with label Windows 2008 server R2. Show all posts

Thursday, January 11, 2018

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

Thursday, March 22, 2012

Error message when you try to perform a system state backup in Windows Server 2008 and Windows Server 2008 R2


When you try to perform a system state backup to a volume on which the system state file resides, you receive an error, as mentioned below:


In Windows Server 2008, you receive the following error:
ERROR - The location for backup is a critical volume.


In Windows Server 2008 R2, you receive the following error:
ERROR - The backup storage location is invalid. You cannot use a volume that is included in the backup as a storage location


This behavior occurs because system state backups to critical volumes are blocked in 
Windows Server 2008 and Windows Server 2008 R2.


You can change the default behavior of Windows Server 2008 and Windows Server 2008 R2 by adding a registry entry. You must also verify that the following prerequisites are met before you perform a system state backup to a critical volume.



Prerequisites to perform system state backups to critical volumes


Make sure that the target volume has no shadow copy before the backup starts.


If a system state backup is stored on a source volume, backup settings should be configured for full backups. By default, settings are configured for full backups.


Periodically check that no other user or program maintains a shadow copy on the target 
volume.


Do not keep volume level backups and system state backups in the same location.


The volume used to store the system state backup needs twice the amount of free space as the size of the system state backup until the backup completes.




Notes


Any writes on target volume with shadow copies will increase the diff area size. 


If the diff area is bounded, it may cause deletion of shadow copies.




Incremental backups leaves shadow copies behind, it will cause side effect as point 1.


Backup stores different versions as shadow copies, it will cause side effect as point 1.



Registry entry to enable system state backups to critical volumes




To enable the system state backup files to be targeted to critical volumes, you must set the


 value of the AllowSSBToAnyVolume registry entry under the following registry subkey:




HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wbengine\SystemStateBackup\


Set the value of this entry as follows:


Name: AllowSSBToAnyVolume


Data type: DWORD


Value data: 1


Note When this value is set to 1, system state backups to any volume are enabled. To revert


 to the default behavior, set the value to 0.





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 clie...