Kayıtlar

Export all distribution Group and All members using PS Script-Exchange 2007&2010

Resim
Script Supports - Exchange 2007,2010,2013 In some situations we had to Export all the Distribution group and all the members of it to a CSV file I have wrote a script which will make Exchange Administrators life Easy Change LogV1.1, 02/07/2014 - Added "Enter the Distribution Group name with Wild Card" .Requires -version 2 – Runs in Exchange Management Shell .\DistributionGroupMemberReport.ps1 – It Can Display all the Distribution Group and its members on a List Or It can Export to a CSV file Download the Script Browse the Shell to the Appropriate Location Run it as above Output of CSV file look like Below You can add some more entries if required PowerShell <#    .Requires -version 2 - Runs in Exchange Management Shell    .SYNOPSIS  .\DistributionGroupMemberReport.ps1 - It Can Display all the Distribution Group and its members on...

How to reset the SA password in SQL Server

Resim
Getting locked out of a SQL Server can happen in a number of ways.  You could inherit a server that was managed by someone that left the company and only that person had System Admin rights for example. A recent encounter I had was were a database server was built and provisioned in one active directory domain and then moved and joined to another non trusted domain. All the accounts provisioned within the server include those for the DBA admins were basically useless since they couldn’t be authenticated.  The built in SA account is locked down per policy so no one knows the password. What do you do if you find that you are locked out of a SQL Server instance? The way I handle it is to start SQL Server in single user mode, launch SQLCMD and create a new user. I then still using SQLCMD grant the new user the system admin role.  Once I have the new user created I restart SQL Server Service and log in using the new credentials. I can then clean up the instance by granting ...

Adobe PDF preview handler 64-bit fix

Preview handlers are lightweight components which let you view various file types within programs like Windows Explorer (in Windows Vista and Windows 7) and Outlook 2007.  Adobe Reader comes with Adobe’s PDF preview handler but the installer has a mistake which means the preview handler does not work on 64-bit systems.  It turns out the problem can be fixed via a simple registry change. About the issue respectively about the fix The fix should only be applied to 64-bit versions of Windows that have Adobe Reader installed.  Don’t apply the fix to 32-bit versions of Windows. If you’re not sure what you have use  Start -> Control Panel -> System and Security -> System  and look at the reported  system type . You will need  Administrator  access to apply the fix. You may need to re-apply the fix if you update/re-install Adobe Reader, unless Adobe get around to fixing their installer. What the fix does is explicitly documented in Mic...

Create an Adobe Acrobat Reader Package including Updates (MSP)MSI to deploy

This post will show you how to create an Adobe Acrobat Reader MSI Package to deploy using a software deployment tool like LANDesk, Microsoft System Center Configuration Manager, Altiris or a similar tool.  First we create an administrative install, then we patch the administrative install with the MSPs (patches).. Download the Adobe Acrobat Reader Setup files. You can either go to http://get.adobe.com/de/reader/  or use FTP to download the MSI / setup.exe from ftp.adobe.com  – i prefer the latter.  ftp://ftp.adobe.com/pub/adobe/reader/win/ When using the FTP site, you can usually grab the MSI directly. If so, steps 2 to 5 are not necessary and you can proceed with step 6. Save it to the Desktop Choose Start > Run. In the Open text box type:  "%UserProfile%\Desktop\AdbeRdr9x_en_US.exe" -nos_ne  change the filename to meet the name of the downloaded setup.exe .. Click OK to start decompressing the file. When the Adobe Reader 9.x Setup screen clears,...

Solution: SQL Server Enterprise Manager General OLE Error 16386

Tried to start Microsoft SQL Server Enterprise Manager and got stuck at the error message  General OLE Error 16386 : try this, maybe this solves the issue.. a. Stop all SQL Server services (MSSQLServer, SQLServerAgent, MSSEARCH) b. Open command prompt and go to the %ProgramFiles%\Microsoft SQL Server\80\Tools\Binn directory c. Unregister the following .dll files (Ex. regsvr32 /u dtsui.dll): dtsui.dll,sqlns.dll, sqldmo.dll, sqllex.dll, sqlmmc.dll d. Copy and paste the .dll files from a CD (under x86\Binn directory) to the Program Files\Microsoft SQL Server\80\Tools\Binn e. Register the .dll files (Ex. regsvr32 sqldmo.dll)

Debugging Group Policy Processing

Resim
Group Policy Debug Log Settings The below article has got information about enabling different debug loggings which are required for troubleshooting various Windows issues. USERENV DEBUG LOGGING Userenv logging is useful when troubleshooting group Policy application related issues or User profile related issues. ENABLING USERENV LOGGING IN WINDOWS XP Use Registry Editor to add or to modify the following registry entry: Subkey: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon Entry: UserEnvDebugLevel Type: REG_DWORD Value data: 10002 (Hexadecimal) UserEnvDebugLevel can have the following values: NONE 0×00000000 NORMAL 0×00000001 VERBOSE 0×00000002 LOGFILE 0×00010000 DEBUGGER 0×00020000 The default value is NORMAL|LOGFILE (0×00010001). Note  To disable logging, select NONE (0×00000000). You can combine these values. For example, you can combine VERBOSE 0×00000002 and LOGFILE 0×00010000 to get 0×00010002. Therefore, if UserEnvDebugLevel...

Truncate Logfile in SQL Server

Using the code Step 1. Copy/type the below given SQL. Step 2. Change @DBName to < Database Name>, @DBName_log to Step 3. Execute the SQL. ALTER DATABASE @DBName SET RECOVERY SIMPLE WITH NO_WAIT DBCC SHRINKFILE(@DBName_log, 1) ALTER DATABASE @DBName SET RECOVERY FULL WITH NO_WAIT GO In SQL Server data is stored using two physical files:  (.mdf)  extension  which contains the data.  (.ldf) extension which contains log. Log file size increases very rapidly and depend on the operation performed on the data. After a long time period this file becomes too large. When log file is too large it takes time to perform some operations like ( attach , de-attach, backup, restore … etc ).