Jairo Cetina

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

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

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

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:

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.

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

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