Archive

Archive for April, 2014

How to uninstall SCCM client Remotly

April 29, 2014 Leave a comment

By default SCCM do not provide an uninstall feature from the console. Uninstall the client from the SCCM console is “out of the box”. But it can be archive remotely by following steps

Step 1 : Download PSEXEC tool from Here

PSEXEC tool is used to connect to the remote computer and run the command line to uninstall SCCM client.Please run this tool from where having appropriate permission to connect remote workstations

Step 2 : Navigatte the download folder and run psexec \\remote computer name cmd ( This command launches an interactive remote compouter command prompt.

1

Step 3 : Then just run ccmsetup.exe /uninstall after connecting PSExec to remote PC.

2

Ccmsetup should exist on all clients, usually under the windows folder.

Step 4 : To verify that client uninstallation has succeeded, check the log file CCMSetup.log in the folder %windir%\ccmsetup folder on the client computer

Advertisements

SQL Server is running out of disk space due to transaction logs size

April 20, 2014 Leave a comment

In many cases its has been noticed that SQL transaction log may become very large and run out of space or become full. In this post describe how to fix when SQL transaction logs consumed disk space

Scenario

 

SQL server running out of disk space due to transaction logs

SQL transaction logs is not truncating after VERITAS backup

How Truncating the Transaction Log.

Note : Verify database recovery model is full by select the database -> right click ,select properties ->select Options -> view the Recovery Model .
If the database recovery model is full or Bulk logged , then we can reduce the log file size by shrinking the log file as below

Action Plan by using SQL Server Management Studio.

Step 1 Check the log space use
Run DBCC command to find out the database whose log space used percentage is the lowest and log size if the largest.
DBCC SQLPERF(LOGSPACE);
4

Step 2 Do a full backup for the required databases log.

Select the database ->right click, select task ->click backup ->select “Transaction Log ” as Backup type ->click OK.
1

Step 3 Run “CHECKPOINT” command as follows.

2

Step 4 Shrink the log file.

Select database, right click ->tasks ->shrink ->files ->select “log” as file type ->select “Reorganize Pages before releasing unused space”->Shrink file to a target size ->click OK.
The target size should be set to a value that approximately equal Currently allocated space minus Available free space
3
If the target size is smaller than the minimum size that the log file can shrink to ,it will get the minimum size. For example ,we want to reduce the log file size to 1MB, but if the log file requires 20 GB at least, then the log file size will be 20GB after we shrink it.

Reference Read more…

What are the Netbackup Logs & how to enbale them ?

April 16, 2014 1 comment

Its require to analyze logs in order to determine root cause of most if backup/restore issues especially the hardware related problems such drive, media..etc.

This post mainly describes important types of Netbackup logs and will see here how to enable them .

By default, log files are placed in the \veritas\netbackup\logs directory on a NetBackup server. To enable logging on any of the NetBackup processes, a directory must be created in the \veritas\netbackup\logs directory on the NetBackup server

bptm overview and how to collect?:

The bptm process handles interactions with the tape device. bptm logs to be enbled in order to collect backup media issues

Go to the media server, and create a folder named bptm under \veritas\netbackup\logs\

On the Netbackup console, go to Host properties – Media server.

Open the affected media server properties.

Click on logging.

Increase the verbosity on bptm log to 5.
Read more…

Categories: Veritas Netbackup

Lync 2013 Enterprise Pool Front-End Service don’t start

April 14, 2014 2 comments

Issue

There are two lync 2013 front end server in the pool and lync front end service is not stating in one of the server .The follwoing error are looged in the eventvwr.

Server startup is being delayed because fabric pool manager has not finished initial placement of users.

Currently waiting for routing group: 04D3F0D5-0BE1-5C12
Number of groups potentially not yet placed: 22.
Total number of groups: .
Cause: This is normal during cold-start of a Pool and during server startup.
If you continue to see this message many times, it indicates that insufficient number of Front-Ends are available in the Pool.
Resolution:
During a cold-start of a large Pool it can take upto an hour for the placement process to finish as it needs to populate all the Front-End databases with data from the Backup Store. If the Pool is running and the Front-End is just started, this is normal for some time. If this repeats for a long time, ensure that all the Front-Ends configured for this Pool are up and running. If multiple Front-Ends have been recently decommissioned, run Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery to enable the Pool to recover from Quorum Loss and make progress.

Resolution

1) Open Lync server management shell as an administrator

2) Then type the below command

Reset-CsPoolRegistrarState -PoolFqdn ” frondendpool name” -ResetType FullReset

Replace ‘ frondendpool name’ with your lync 2013 frond end server pool.This will reset the pool fabric state and will start lync frond end sevices on afected server .

The encryption type requested is not supported by the KDC

April 6, 2014 Leave a comment

Issue

Getting the error ‘An Authentication Error Has Occurred .The encryption type requested is not supported by the KDC’ when RDP to windows servers

Resolution

Restart the KDC ( ( KERBEROS DISTRIBUTION KEY ) ) services on your domain controllers. The issue occurred after raising the functional level from windows 2003 to Windows R2. Then its resolved after restarting the KDC services on domain controllers.

Categories: Active Directory Tags:
%d bloggers like this: