Entradas

Test SMTP/e-mail Server relay with PowerShell

To test your SMTP/e-mail Server relay using Powershell, execute: Send-MailMessage –From mailbox1@domain.com –To alejandra.restrepo@mailbox1@domain.com –Subject “Test PowerShell” –Body “Test E-mail (body)” -SmtpServer smtp-relay.gmail.com -port 25 You can use a powershell script .ps1: $EmailFrom = "sender@gmail.com" $EmailTo = "recipient@email.com" $Subject = "Subject" $Body = "Body" $SMTPServer = "smtp.gmail.com" $SMTPClient = New-Object Net.Mail.SmtpClient($SmtpServer, 587) $SMTPClient.EnableSsl = $true $SMTPClient.Credentials = New-Object System.Net.NetworkCredential("sender@gmail.com", "YourGmailPassword"); $SMTPClient.Send($EmailFrom, $EmailTo, $Subject, $Body) If you have problems with the execution policy, run: Powershell.exe -executionpolicy remotesigned -File C:\Users\myusername\myfile.ps1

Simple Way to Delete all Snapshots on vSphere - PowerCLI

Have our virtualization environment free of snapshots is a best practice to prevent low storage problems and performance degradation. Check you environment for snapshots older than 7 day's, using the command: Get-VM | Get-Snapshot |Where { $_ .Created -lt ( Get-Date ).AddDays(-7)}| Select-Object VM,Name,Created, @ {N= "SizeGB" ; E={ [math] :: round( $_ .SizeGB, 1)}} | FT Delete all snapshots for a specific VM run: Get-VM MYVM-NAME| Get-Snapshot | Remove-Snapshot -RemoveChildren -Confirm : $False If you want delete all snapshots for all VM's use: Get-VM | Get-Snapshot | Remove-Snapshot -RemoveChildren -Confirm : $False  Sometimes delete snapshots fail in consolidation process and snapshot manager don't show snapshots. To check if all VM's are OK run: Get-VM | Where-Object { $_ .Extensiondata.Runtime.ConsolidationNeeded}  To start consolitation process execute: Get-VM | Where-Object { $_ .Extensiondata.Runtime.Consolidation...

V-79-10000-11233 - VSS Snapshot error. Symantec Backup Exec.

Error: V-79-10000-11233 - VSS Snapshot error. A Microsoft Volume Shadow Copy Service (VSS) snapshot is already running on the target computer. Only one snapshot can run at a time.  Try running the job later. Error using NTBackup Backup Status Operation: Backup Active backup destination: File Media name: "TitanSystemState.bkf created 12/03/2010 at 06:00" Volume shadow copy creation: Attempt 1. Error returned while creating the volume shadow copy:0x80042316. Error returned while creating the volume shadow copy:80042316 Aborting Backup. Cause This warning is given typically when the Volume Shadow Copy Service (VSS) is unable to run due to another instance of VSS already running. When Backup Exec System Recovery (BESR) and Backup Exec (BE) backup conflicts. Solution BE jobs use Microsoft VSS service and BESR jobs use Symantec SymSnap VSS provider. To resolve this issue, unregister the Symantec SymSnap VSS provider and BESR will als...

The com.vmware.converter item in the vCenter Service Status Page is Displayed in Red

Error: Unable to retrieve health data from “https://<VC servername or IP address>/converter/health.xml” in VMware vCenter Server 4.1. Note: The URL https://xx.xx.xx.xx/converter/health.xml can be accessed via an Internet browser on the vCenter Server machine. Resolution: This issue has been resolved in vCenter Server 4.1 Update 1. Workaround: To solve this issue, try using a fully qualified domain name or IP address to register vCenter Converter with vCenter Server. This may help in some cases. Alternatively, replace the thumbprint entry of Converter in the ADAM LDAP database with the vCenter Server thumbprint. To replace the Converter thumbprint with the vCenter Server thumbprint: Caution: This workaround has only been tested for configurations where vCenter Server and Converter co-exist on the same machine. Do not perform this workaround if vCenter Server and Converter are on different servers. To connect to the LDAP server running on vCenter Server: ...

Which PDI (Process ID) is SQL Server running.

Imagen
There was an interesting question posted on a forum recently, asking how can you tell which sqlservr.exe process (shown in task manager) is mapped to which specific instance of SQL Server running on a server, if you have a multi-instance server and the account running each separate SQL Service is the same. I won’t go into the details of the post, but I thought the answer worth of a post of my own. As with most things in SQL Server there is more than one way to obtain this information. Hands-on: Open up SQL Configuration Manager On the SQL Services tab right click on the SQL instance that you want to match up to a process Select <Properties> and click the <Services> tab On the general tab you should see a process id property.

Continuous Grow file Setupapi.log, WINLOGON High CPU usage and takes a long time to log on to a Windows.

Use filemonitor or ProcessExplorer to diagnostic. C:\WINDOWS\setupapi.log contains information about application installation, it log file is used to trace the cause of problems should they arise after an installation of a device or drivers. Incident: In my case file C:\WINDOWS\setupapi.log is big and WINLOGON. EXE consume high CPU went users login in the server. Workaround: Open your registry editor. Go to “HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Curr entVersion\Setup\LogLevel” registry key. Set LogLevel key to 0 Restart server. More Info: http://msdn.microsoft.com/en-us/library/ff550845(v=vs.85).aspx http://support.microsoft.com/kb/958909/es

Symantec Backup Exec 11d exceed limit Selection list

Error: Error "unable to create selection list" occurs while editing or creating a selection list associated with a backup job in Backup Exec for Windows Servers. Workaround: Open the registry editor and go to HKLM\Software\Symantec\Backup Exec for Windows\Backup Exec\Server Create a new DWORD value "MaxRpcDatablockSize" and set the Hexadecimal value to "ffffffff". Restart the BE services. Check if the issue still persists. More Info: http://www.symantec.com/docs/TECH59032 http://www.symantec.com/connect/forums/selection-list-limitation

Calculate IOPS in a Disk or Storage Array for beginners

Imagen
IOPS (Input/Output Operations Per Second, pronounced i-ops) is a common performance measurement used to benchmark computer storage devices like hard disk drives (HDD), solid state drives (SSD), and storage area networks (SAN). As with any benchmark, IOPS numbers published by storage device manufacturers do not guarantee real-world application performance.   IOPS can be measured with applications such as Iometer (originally developed by Intel), as well as IOzone and FIO and is primarily used with servers to find the best storage configuration.   The specific number of IOPS possible in any system configuration will vary greatly depending upon the variables the tester enters into the program, including the balance of read and write operations, the mix of sequential and random access patterns, the number of worker threads and queue depth, as well as the data block sizes. There are other factors which can also affect the IOPS results including the system setup, storage dri...

High CPU utilization of inactive Windows virtual machines

Problem: My server's CPU utilization high when my Windows virtual machine is mostly inactive. Workaround: To determine what HAL your virtual machine is using, then determine if you are running with the correct vCPU count for the HAL: Right-click the My Computer icon, and choose Properties . Click the Hardware tab. Click the Device Manager tab. Double-click the Computer icon to see which HAL is currently loaded. In the vSphere or VMware Infrastructure client, click on the virtual machine, then click the Summary tab and see how may vCPU's are configured. If you have 1 vCPU and your virtual machine operating system is configured for a Uniprocessor ACPI, your configuration is correct. If your virtual machine operating system is configured for 2 or more vCPUs and it is running with a Multiprocessor ACPI, your configuration is correct. Note : Downgrading the HAL from multiprocessor to uniprocessor is ...

VMware ESX/ESXi 4.1 and Active Directory Integration

Imagen
Configure your ESX/ESXi IP address and FQDN: Goto: Configuration tab > Authentication Services > Properties Type your domain and you OU if you want: Type your Domain User and Password See you Active Directory Domain. Now you can manage your security groups by adding some groups under “Assign Permissions”: Assign Administrator permissions to Domain Admins: More Info: Configure a Host to Use a Directory Service

How to transfer logins and passwords from SQL Server 7.0 to SQL Server 2000 or between servers that are running SQL Server 2000

To transfer logins and passwords from a SQL Server 7.0 server to an instance of SQL Server 2000, or between two instances of SQL Server 2000, you can use the new DTS Package Transfer Logins Task in SQL Server 2000. To do this, follow these steps: Connect to the SQL Server 2000 destination server, move to the Data Transformation Services in SQL Server Enterprise Manager, expand the folder, right-click Local Packages , and then click New Package . After the DTS package designer opens, click Transfer Logins Task on the Task menu. Complete the information about the Source , Destination and Logins tabs as appropriate. More Info: http://support.microsoft.com/kb/246133/en-us

Error message when you install SQL Server 2005 or SQL Server 2008: "The file C:\Windows\Microsoft.NET\Framework\[version_number]\mscorlib.tlb could not be loaded"

Problem: The file C:\Windows\Microsoft.NET\Framework\ version_number \mscorlib.tlb could not be loaded. An attempt to repair this condition failed because the file could not be found. Please reinstall this program. Workaround: For SQL Server 2005 To work around this problem, you must manually specify the correct path of the Mscorlib.tlb file in the registry. To do this, follow these steps: Click Start , click Run , type regedit, and then click OK . Locate the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Tools\Shell\TlbAutoRepair\mscorlib.tlb Notes If you install SQL Server 2005 on 64-bit operating systems, locate the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server\90\Tools\Shell\TlbAutoRepair\mscorlib.tlb If you install SQL Server 2005 Express Edition with Advanced Services, locate the following registry subkey: HKEY_L...

How do Check the MSI Version on your Computer

Imagen
To detect the MSI or Microsoft Installer version check the version of MSI.DLL in the %SystemRoot%\System32 folder, Example: Or Execute: msiexec.exe /?

"Database diagram support objects cannot be installed because this database does not have a valid owner" SQL Server 2005

Imagen
Problem: ”Database diagram support objects cannot be installed because this database does not have a valid owner. To continue, first use the Files page of the Database Properties dialog box or the ALTER AUTHORIZATION statement to set the database owner to a valid login, then add the database diagram support objects.” Workaround: EXEC sp_dbcmptlevel 'database_name', '90'; go ALTER AUTHORIZATION ON DATABASE::database_name TO 'login' go use [database_name] go EXECUTE AS USER = N'dbo' REVERT go More Info: sp_dbcmptlevel http://msdn.microsoft.com/es-ar/library/ms178653.aspx ALTER AUTHORIZATION http://msdn.microsoft.com/es-ar/library/ms187359.aspx

Excessive Registry Entries in HKCU Causing Problems in Terminal Server 2003 Environment – HP(Hewlett Packard) Problem.

Problem: HKEY_CURRENT_USER\Software\Hewlett-Packard as well as the \HKEY_USERS\.DEFAULT\Software\Hewlett-Packard have excessive registry entries and: NTUSER.DAT ser.dat had grow up in size around 2.5MB to over 10MB Long delays on login/logout processes Msiexec process running every time user logs in. In event viewer I've got message "Product: xx Bit HP CIO Components Installer -- Configuration completed successfully." for every user. So it installs as many times as users are on TS. And it consumes about 25% of our 4 core CPU (so 1 core is loaded at 100%) Workaround: The following keys should be backed up and then removed :[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\Install\RefHive\Hewlett-Packard] and: [HKEY_USERS\.DEFAULT\Software\Hewlett-Packard] Now reboot the system. Note: If you want recreate profile to gain free space in HKCU registry and user can log in quickly.

System Center Operations Manager 2007 SP1 - Processing Backlogged Events Taking a Long Time

Problem: Alert: Processing Backlogged Events Taking a Long Time Source: SERVERNAME Status: New Path: SERVERNAME Last modified by: System Last modified time: 10/23/2010 10:34:28 AM Alert description: The Windows Event Log Provider monitoring the Application Event Log is 679802383 minutes behind in processing events. This can occur when the provider is restarted after being offline for some time, or there are too many events to be handled by the workflow. Workaround: Install Update Rollup for Operations Manager 2007 Service Pack 1 (KB971541) More Info: http://www.microsoft.com/downloads/en/details.aspx?FamilyID=05d7785d-fe69-48bc-8dfa-72a77c8936bf http://support.microsoft.com/kb/971541

Installation of the Web Console role on Windows Server 2008 R2 servers fails with "Unknown error (0x80005000)"

Problem: Installation of the Web Console role on Windows Server 2008 R2 fails with an "Unknown error (0x80005000)" error message. Impact: The Web Console role cannot be installed. Workaround: You must add the IIS 6 Management Compatibility component because it contains the prerequisites that are required for the installation and operation of the Operations Manager 2007 Web Console. To install the IIS 6.0 Management Compatibility Components by using Server Manager, follow these steps: Click Start , click Administrative Tools , and then click Server Manager . In the console tree, expand Roles , right-click Web Server (IIS) , and then click Add Role Services . In the Select Role Services pane, scroll down to IIS 6 Management Compatibility . Click to select the IIS 6 Metabase Compatibility check box and the IIS 6 Management Console check box. Click Next on the Select Role Services page, and then click Install on the Confirm Installati...

Agent push installations fail occasionally on Windows Server 2008 R2 and Win7 with the error "A COM Proxy was called from the wrong context"

Problem: When you use the Discovery Wizard to perform a push installation of the Operations Manager 2007 SP1 agent on a Windows Server 2008 R2 or Window 7 system, the installation task may fail with an "A COM Proxy was called from the wrong context" error message. Impact: You cannot install the agent on this system by using the Operations Manager 2007 Discovery Wizard. Workaround: Log on to the system locally and perform a manual agent installation. For more information, visit the following Microsoft TechNet Web site: http://technet.microsoft.com/en-us/library/cc950516.aspx This issue is resolved for Operations Manager 2007 SP1 by applying the update rollup that is documented in the KB article 971541. More Info: http://support.microsoft.com/kb/971541 http://support.microsoft.com/kb/974722

Event ID 26017 from source "Health Service Modules" will be raised for Operations Manager 2007 SP1 agents, indicating "Event log Provider monitoring the Event Log is # minutes behind," and the number of minutes is in the hundreds of millions.

Problem: When an Operations Manager 2007 SP1 agent is installed on a computer that is running Windows 7 or Windows Server 2008 R2, the following event may be logged in one or more event logs. Additionally, value for the number of minutes is very large. Log Name: Operations Manager Source: Health Service Modules Event ID: 26017 Level: Warning Description: The Windows Event Log Provider monitoring the %1 Event Log is %2 minutes behind in processing events. This can occur when the provider is restarted after it is offline for some time, or there are too many events to be handled by the workflow. Impact: None. These events are generated because of the delta between timestamps is calculated incorrectly. The event log processing is actually working correctly, and the events can be ignored. Workaround: No workaround is required. Ignore the events or upgrade to Operations Manager 2007 R2. This issue will be fixed in updates that will be available in the futur...

"Backward Compatibility Script Error" alerts are generated with the description of "An error occurred on line 123 while executing script 'MOM Backward Compatibility Service State Monitoring Script'"

Problem: When an Operations Manager 2007 SP1 agent is installed on a computer that is running Windows 7 or Windows Server 2008 R2, an alert may occur in the Operations console or an event may be logged on the computer that is being monitored. The alert reports that backward compatibility scripts failed. The following are the details that are present in the alert and its corresponding event on the agent. Collapse this tableExpand this table Alert field Value Alert Backward Compatibility Script Error Alert description An error occurred on line 123 while executing script 'MOM Backward Compatibility Service State Monitoring Script' Source Microsoft VBScript runtime error ...