Jairo Cetina

The vulnerability could allow remote code execution if a user opened a specially crafted AVI file. An attacker who successfully exploited this vulnerability could take complete control of an affected system. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights. More Info: http://www.microsoft.com/technet/security/Bulletin/Ms10-013.mspx Security Update for Windows Server 2008 R2 x64 Edition (KB975560) Start download

The vulnerabilities could allow remote code execution if an attacker sent a specially crafted SMB response to a client-initiated SMB request. To exploit these vulnerabilities, an attacker must convince the user to initiate an SMB connection to a malicious SMB server. *Server Core installation affected. This update applies, with the same severity rating, to supported editions of Windows Server 2008 or Windows Server 2008 R2 as indicated, whether or not installed using the Server Core installation option. More Info: http://www.microsoft.com/technet/security/Bulletin/MS10-006.mspx Security Update for Windows Server 2008 R2 x64 Edition (KB978251) Start download

  The Forefront TMG 2010 Capacity Planning Tool, a Microsoft Excel spreadsheet with built-in workflow, allows you to calculate the WAN bandwidth and number of users a particular a hardware configuration will support, and can recommend server hardware based on the features, bandwidth and users your deployment needs to support. Start download

Source: NLB Logged: <Time> Event ID: 119 Task Category: None Level: Warning Keywords: User: N/A Computer: <computer name> Description: NLB cluster [<IP or host name>]: The NLB driver has detected an inconsistency in the Extended Affinity configuration between cluster host <ID> and cluster host <ID>. A client IP address is on the Extended Affinity exception list on both hosts. You should run the Powershell cmdlet ‘Set-NlbClusterNode-Reload’ followed by ‘Start-NlbClusterNode’ Resolution: Install the hotfix. Restart WLBS service See: http://support.microsoft.com/kb/978943/en-us

To use DCPromo, We need a .txt file with configuration apply to server. For Example add un DC server in a site named NewYok: [DCINSTALL] UserName=MyAdminUser UserDomain=Mydomain Password=Password123 SiteName=NewYork ReplicaOrNewDomain=replica ReplicaDomainDNSName=mydomain.loc DatabasePath=N:\ADDS\NTDS LogPath=N:\ADDS\NTDS\Log SYSVOLPath=N:\ADDS\SYSVOL InstallDNS=yes ConfirmGC=yes SafeModeAdminPassword=Password123 RebootOnCompletion=yes Execute in command Prompt: DCPROMO /unattend:C:\MyUnattendFile.txt See: http://support.microsoft.com/kb/947034/en-us

To configuring a Windows server 2008 or 2008 R2, execute in command prompt: WINRM quickconfig Make these changes [y/n]? , type y . In a remote computer execute in command prompt: WINRS -r:ServerName ApplicacionName.exe See: http://msdn.microsoft.com/en-us/library/aa384372(VS.85).aspx http://technet.microsoft.com/en-us/library/dd163506.aspx

Event Type:       Error Event Source:    MsiInstaller Event Category: None Event ID:           10005 Date:                2/11/2010 Time:                6:50:33 PM User:                NT AUTHORITY\SYSTEM Computer:         SERVERNAME Description: Product: 32 Bit HP BiDi Channel Components Installer -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2753. The arguments are: ipm12.CF34E983_546C_421F_A494_3C30281E4CF3, For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp . Solution: Zero-byte the MSI Installer Package, which will eliminate the symptomatic behaviors of the issue noted in this document. Complete the following steps: Open Notepad and save the file as hpzbdi32.msi or hpzbdi64.msi . This zero-byte file will not contain any data. Navigate to the %WINDOWS%\system32\spool\drivers\w32x86 (32-bit operating

Went you renew or replace the Remote Desktop licenses Per Device sometimes receive errors in RDP Clients to delete actual licenses in your clients follow this procedure: Backup the registry entry: HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing Delete the registry entries: HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing In Macintosh: Delete the contents of this folder: /users/Shared/Microsoft/RDC Crucial Server Information/ See: http://support.microsoft.com/kb/187614/en-us http://technet.microsoft.com/en-us/library/cc756826(WS.10).aspx

Event Type: Warning Event Source: OpsMgr SDK Service Event Category: None Event ID: 26371 Date: 12/13/2007 Time: 2:58:24 PM User: N/A Computer: RMSCOMPUTER Description:The System Center Operations Manager SDK service failed to register an SPN. A domain admin needs to add MSOMSdkSvc/rmscomputer and MSOMSdkSvc/rmscomputer.domain.com to the servicePrincipalName of DOMAIN\sdkaccount Every time the SDK service starts, it tries to update the SPN’s on the AD account that the SDK service runs under. It fails, because by default, a user cannot update its own SPNs. Therefore we see this error logged Procedure: Run ADSIEdit as a domain admin. Find the SDK domain account, right click, properties. Select the Security tab, click Advanced. Click Add. Type “SELF” in the object box. Click OK. Select the Properties Tab. Scroll down and check the “Allow” box for “Read servicePrincipalName” and “Write s

In some situations we need to move OperationsManger Database to another computer for different reasons, for example: Hardware Limitations Database and Root Management server is on the same server. Fault Tolerance Procedure: Back up Operations Manager database including the Master. Back up the encryption key on the root management server by using the SecureStorageBackup.exe utility. Verify you have installed and configured the new SQL Server Instance as the existing one. Stop the Operations Manager Services (OpsMgr Config Service, OpsMgr SDK Service, and OpsMgr Health Service for Root Management Servers and OpsMgr Health Service for Management Servers) on the Management Servers in the Management Group before proceeding. In a clustered root management server environment, use Cluster Administrator (Windows Server 2003) or Failover Cluster Management (Windows Server 2008) to configure each of the three services listed above with the Take Offline opt