El conocimiento al alcance de todos.

Thank to: https://tweaks.com I'm sure you are familiar with the traditional way to kill or end a process in Windows using Task Manager.  This method is effective but not nearly as fun as killing a process in Command Prompt.  Additionally, killing processes in Command Prompt provides much more control and the ability to end multiple processes at once. All of this is possible with the TaskKill command. First, let's cover the basics.  You can kill a process by the process ID (PID) or by image name (EXE filename). Open up an Administrative level Command Prompt and run  tasklist  to see all of the running processes: C:\>tasklist Image Name                     PID Session Name        Mem Usage ========================= ======== ================ ============ firefox.exe                  26356 Console             139,352 K regedit.exe                  24244 Console               9,768 K cmd.exe                      18664 Console               2,380 K conhost.exe     

Thanks to: Nubeinformatica.com Campo autonumérico ¿Qué son? Campo cuyo valor va aumentando secuencialmente con un incremento de 1 o a partir de una secuencia aleatoria de números. Utilizados normalmente para definir el campo clave ( ID del registro ) de la tabla. Ventajas Inconvenientes Nos aseguran obtener valores únicos para un campo. Valor ofrecido y no utilizado, valor perdido. Jamás repiten un valor. No permiten crear combinaciones con otros formatos. Son controlados por Acces, por lo que nos permiten desentendernos de ellos. Sólo se permite un campo por tabla. Campo autonumérico personalizado ¿Qué son? Campo cuyo valor se obtiene del último valor asignado al campo con un incremento definido por el usuario, al que le podemos aplicar un diseño de formato. Ventajas Inconvenientes Nos permiten personalizar la autonumeración de los campos. Los tenemos que generar por medio de expresiones introducidas en cuadros de texto de un formulario. Si ofrecen un

Thank to: https://www.itprotoday.com/ Q: Why am I receiving an error when trying to protect a SQL Server 2012 server using System Center 2012 Data Protection Manager? A:  If you have performed a fresh SQL Server installation and are trying to protect it with System Center 2012 Data Protection Manager (DPM), you might get an error in DPM that the server can't be protected. If you open Event Viewer and look in the Application log, you might see an error similar to the following: Log Name: DPM Alerts Source: DPM-EM Date: 5/6/2013 3:53:08 PM Event ID: 3170 Task Category: None Level: Error Keywords: Classic User: N/A Computer: savdaldpm12.savilltech.net Description: DPM could not start a recovery, consistency check, or initial replica creation job for SAVDALSQL01\AppController on savdalsql01.savilltech.net for following reason: (ID: 3170) The DPM job failed for SAVDALSQL01\AppController on savdalsql01.savilltech.net because the protection agent did not have sysadmin priv

Thank to: https://www.itprotoday.com If you have an agent in DPM that you cannot remove from the console you can remove using the following: Launch the DPM Management Shell on the DPM Server Type the name of the remove script - remove-productionserver.ps1 Enter the name of the DPM server Enter the name of the machine to remove

Thank to: https://www.enjoysharepoint.com/ This SharePoint workflow tutorial explains how to solve error: Register-SPWorkflowService: Workflow XAML failed validation due to the following errors: Invalid typ (s) ‘Microsoft.Activities.CacheScope’. HTTP headers received from the server – ActivityId. New to Office 365 SharePoint Online? Get  Office 365 Enterprise E3 Subscription  & Try out all the features   The error comes while Registering SPWorkflowService while  configuring Workflow manager 1.0 for SharePoint 2016 . After configuring workflow manager 1.0, while running the PowerShell command to register workflow service, I got the below error. Register-SPWorkflowService -SPSite “http://mypc/sites/MySP2016SiteCollection/” -WorkflowHostUri “http://localhost:12291” -AllowOAuthHttp -Force After running the above PowerShell command, the error comes as: Register-SPWorkflowService: Workflow XAML failed validation due to the following errors: Invalid type(s) ‘Microsoft.Activit

Thank to: https://knowledge.digicert.com Problem When installing an SSL certificate using Microsoft IIS 7.0 or 7.5 on Windows Server 2008 / 2008R2, the following error may occur: Cause This error occurs because IIS Manager performs a lookup operation to search for the friendly name of the certificate during installation. However, the code that performs this lookup operation misses this specific case, and it does not know how to retrieve the friendly name of a certificate in a PKCS#7 file. Therefore, the lookup operation fails, and the error message is displayed. Solution To resolve this problem, verify if the certificate was installed by performing the following steps: Step 1: Create a Certificate snap-in within the MMC on the server Click  Start  >  Run  > type  MMC From the  Microsoft Management Console (MMC) , click   File  >  Add/Remove Snap-in From the list of snap-ins, select  Certificates Click  Add Select  Computer Account