Jairo Cetina

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

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

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

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

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

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.

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

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

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

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

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

Problem: When you try to install the Operations Manager 2007 SP1 agent Server Core installations of the 64-bit edition of Windows Server 2008 R2, the operation fails, and you receive the following error message: Windows Installer Service could not be accessed This issue occurs because the Operations Manager 2007 SP1 setup for 64-bit systems has some components that must run in 32-bit emulation, and the required subsystem is not installed by default in a Server Core installation of Windows Server 2008 R2. Workaround: You can upgrade to Operations Manager 2007 R2. Or, follow these steps on each system on which this issue occurs: Log on to the computer on which you want to install the agent. Run the following command to install the necessary subsystem: Start /w ocsetup ServerCore-WOW64 Note The Ocsetup.exe program takes case-sensitive parameters. Therefore, you must use type "ServerCore-WOW64" with the capitalization exactly as it appears here.

Problem: After you upgrade the operating system from Windows Server 2003 to Windows Server 2008 R2, the Adtserver service does not start. Additionally, the following event is logged: Event ID: 4672 AdtServer encountered the following problem during startup: Task: Open Audit Database Failure: An error occurred connecting to the database Error: 0x00000002 Error Message: The system cannot find the file specified. Error2: The system cannot find the file specified when we attempt to start the service manually. Impact: The service that performs the audit collection service (ACS) Server functions cannot start. This occurs for both Operations Manager SP1 and Operations Manager R2. During ACS startup, the location of the Open Database Connectivity (ODBC) driver that is used for the data source is queried to make sure that it matches the location that is used in setting up the data source name (DSN). In Windows Server 2008 R2, the registry parameter for the l

Problem: After you upgrade the operating system on a Root Management Server to Windows Server 2008 R2, the following services may continue to stop unexpectedly: In Operations Manager 2007 SP1: The OpsMgr Config service and the OpsMgr SDK service In Operations Manager 2007 R2: System Center Management Configuration and System Center Data Access In this case, some events are logged for these service terminations in the System log. These events have a source of "Service Control Manager" and an Event ID of 7031. Impact: No SDK connectivity will be available. The Operations Console, Connectors, and any other SDK client connections will fail. Additionally, the Root Management Server will be unable to calculate or distribute new configurations, such as updates to group memberships, new or updated overrides, or management pack distribution. Workaround: This issue is resolved for Operations Manager 2007 SP1 by applying the update rollup that is docume