Jairo Cetina

I never try this utitlity but today I was testing this in a new deployment process and Now I say, it is wonderfull, really we can join member servers and workstations from instalation media with Setup /unattend:AutoAttend.XML and Djoin.exe for example: 1. In a domain controller or member of your domain Windows 7 or WIndows 2008 R2, run in Command Prompt: C:\>Djoin /provision /domain mydomain.loc /machine WorkstationName1 /savefile JoinWorkstationName1.txt Note: You should be administrative rights to join machines in you domain. 2. In the new workstation or member server run in Command Prompt: C:\>Djoin /requestODJ /loadfile JoinWorkstationName1.txt /windowspath %SystemRoot% /localos 3. Restart the new machine or run  shutdown /r /t 00 if you run a Windows Server Core installation. Requirements: Windows 7 or Windows 2008 R2. Administrative rights in domain to join computers and adminstrative rights in the new member machine. See: http://technet.microsoft.com/en-us/

When I was migrating exchange 2000 to exchange 2007, the system prompt this problem: "The Exchange server address list service failed to respond. This could be because of an address list or email address policy configuration error. " "El servicio de lista de direcciones de servidor de Exchange no respondió. Esto puede ser debido a un error en la configuración de la directiva de dirección de correo electrónico o de la lista de direcciones." Cause 1 The CN=Public Folders object is missing under CN=All Address Lists in the Active Directory directory service. Cause 2 The Allow inheritable permissions from the parent to propagate to this object and all child objects check box is not selected on the CN=All Address Lists object and on the CN=Public Folders object. Note This may be the cause in an organization in which you modify permissions to configure separate address lists for different groups. Cause 3 There is a parenthesis or an ampersand in a recipient

[ERROR] Cannot find at least one domain controller running Windows Server 2003 Service Pack 1 or later in domain 'DC=DCName,DC=com,DC=DCName'. This could be the result of moving domain controller objects in Active Directory. Check that at least one domain controller running Windows Server 2003 Service Pack 1 or later is located in the 'Domain Controllers' organizational unit (OU) and rerun setup. It happen when you are installing or upgrading Exchange 2007 in an Active Directory that has only Windows Server 2008 R2 Domain Controllers or yours Windows Server 2003 domain controllers that are not updated to at least Windows Server 2003 SP1. Fix: Download the updated ExBPA.PreReqs.xml and ExBPA.Readiness.xml, then replace this files in "Setup\ServerRoles\Common\ ". http://www.microsoft.com/products/servers/exchange/code/ExBPA/Exchange2007/12.2/en/ExBPA.PreReqs.Xml http://www.microsoft.com/products/servers/exchange/code/ExBPA/Exchange2007/12.2/en/ExBPA.Readi

Hace un par de días me encontré un servidor HP DL-380 G6 con Windows server 2008 R2 que se estaba reiniciando sin razón lógica alguna. El único evento que teníamos era el HPQILO2 ID 57 hasta que de tanto buscar encontramos que es necesario actualizar los siguientes componentes por problemas del fabricante de hardware: Integrated Lights-Out 2 (iLO 2) Firmware Version 1.70 (or earlier) iLO 2 Management Controller Driver Version 1.9.0 or 1.11 Online Flash Component - System Programmable Logic Device Actualizar a las versiones: Integrated Lights-Out 2 (iLO 2) Firmware Version 1.78 (or later) iLO 2 Management Controller Driver Version 1.11.2.0 (or later). Problem or Error: HP Proliant Server may unexpectedly reboot, event ID 57 duplicate sensor error messages may be displayed in the Windows Server Event Log. Resolution: http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?locale=en_US&objectID=c01955503 http://h20000.www2.hp.com/bizsupp

This security update resolves two privately reported vulnerabilities in Microsoft Windows. The more severe of these vulnerabilities could allow remote code execution if messages received by the Internet Authentication Service server are copied incorrectly into memory when handling PEAP authentication attempts. On Windows Server 2008, the Internet Authentication Service is replaced by Network Policy Server (NPS). An attacker who successfully exploited either of these vulnerabilities could take complete control of an affected system. Servers using Internet Authentication Service or Network Policy Server are only affected when using PEAP with MS-CHAP v2 authentication. This security update is rated Critical for Windows Server 2008 for 32-bit Systems Service Pack 2 and Windows Server 2008 for x64-based Systems Service Pack 2. For all other affected and supported releases of Windows, see the subsection, Affected and Non-Affected Software , in this section. See: http://support

Overview Securing servers, client computers, and mobile devices becomes even more vital as workers and contractors connect from multiple wired and wireless networks that may employ varying levels of security features. Employees can inadvertently put their businesses at risk by connecting to mission-critical systems over mobile networks and applications and unintentionally transmitting viruses or corrupt data. In addition, passing critical corporate data through an outside network operations center may increase the risk of compromise or unavailability. With the right technologies and network architecture in place, however, network administrators can help dramatically improve the security and management of mobile device connections. The key to a successful deployment is carefully planning how to handle permissions and security rights for these mobile workers. Microsoft® products offer a broad set of security-related technologies to help you construct a sound defense against in

Si recibes una linda pantalla rosa cuando estas actualizado tu ESX 4.0 a ESX 4.0 U1 con VMware Update Manager o VMware Host Update Utility, debes reiniciar y detener los HP Insight Manager agents antes de realizar el proceso. Esto solo sucede en los servidores HP que tiene estos agentes. See: http://kb.vmware.com/kb/1016070

  Hace algunos días, me preguntaban como configurar los DNS primario y secundario de los controladores de dominio, pues bien aquí dejo las opciones que tenemos al realizar esta configuración: Configure the Preferred DNS server in TCP/IP properties on each Domain Controller to use itself as Primary DNS Server. Advantages: Ensures that DNS queries originating from the Domain Controller will be resolved locally if possible. Will minimize impact of Domain Controller’s DNS queries on the network Disadvantages: Dependant on Active Directory replication to ensure that DNS zone is up to date. Lengthy replication failures may result in an incomplete set of entries in the zone. Configure all Domain Controllers to use a centralized DNS server as their Preferred DNS Server. Advantages: Minimizes the reliance on Active Directory replication for DNS zone updates of Domain Controller locator records. This includes faster discovery of new or

Exchange Server 2007 SP1 no es consciente de los cambios ordenación NLS en  (National Language Support) de Windows Server 2008. Por lo tanto, hay un bucle infinito en el proceso Store.exe y registros de transacciones se generan rápidamente. Para solucionar el incidente es necesario instalar el Update Rollup 9 for Exchange Server 2007 Service Pack 1 Ver: http://support.microsoft.com/kb/959559/en-us