Jump to content


Westlander

Established Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Westlander

  • Rank
    Newbie
  • Birthday 06/02/1988

Contact Methods

  • Website URL
    http://

Profile Information

  • Location
    Netherlands
  1. Hello, Did you also see error 53?: Error 53 occurs when the client did get a DHCP address, but failed to get a response from a PXE server. A few things could cause this: 1) PXE server is on a different network segment from the PXE client and no DHCP Proxy or helper address is installed (on the router). 2) PXE Serer service has stopped (apperently not in your case). 3) Your PXE server and DHCP server are on the same server and your DHCP scope option does not include the option 60 that it needs for this configuration. Re-add option 60 to the scope with the value of "PXEClient". If option 60 is not available to add, re-install the PXE service by running PXE.EXE from the RDP CD. 4) No Boofiles were created during setup. Open BootDisk creator and check that you have atleast 2 bootfiles (a managed and an Initial). In 1.4 they are called defpxemg and defpxenc, respectively. In 1.3, the images were created, but did not appear in boot disk creator. Re-create them to be sure. Cheers, Westlander
  2. Yesterday I was doing an installation of SCOM 2007 SP1, and i get an Install error. The client was a Windows Server 2003 SP2 Enterprise edition. I get the following error in the event viewer: Event Type: Error Event Source: MsiInstaller Event Category: None Event ID: 10005 Date: 11/26/2008 Time: 12:12:57 PM User: xxx Computer: xxx Description: Product: System Center Operations Manager 2007 Agent -- Error 25218.Failed to uninstall SDK MOF. Error Code: -2147217407 (IDispatch error #3585). For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. Data: 0000: 7b 45 37 36 30 30 41 39 {E7600A9 0008: 43 2d 36 37 38 32 2d 34 C-6782-4 0010: 32 32 31 2d 39 38 34 45 221-984E 0018: 2d 41 42 38 39 43 37 38 -AB89C78 0020: 30 44 43 32 44 7d 0DC2D} Searching at Google learned that it appeared to be a problem with WMI on the Windows Server 2003 target clients. I build a fix.bat file that you must run before you install the Agent Client. The script does the follows: He copied the *.mof and the *.mfl from a working Server 2003 Enterprise SCOM Agent, and overwrote the existing copies in the failed Agent. You do this with the following batch file: rem Copy files Xcopy \\servername\AgentFix\Wbem c:\windows\system32\wbem /i /y rem change dir and do mofcomp c: cd \windows\system32\wbem For /f %%s in ('dir /b *.mof *.mfl') do mofcomp %%s rem restart services net stop ccmexec net stop winmgmt net start winmgmt net start ccmexec pause When he's completed, you must restart the WMI service and you're finished. SCOM Agent install was able to complete successfully. Fix.bat: http://rapidshare.de/files/41007869/Agent_fix.rar.html
  3. Westlander

    Hello!

    SCCM 2007 SP1 is allready deployed and configured for servers of the company. The company have a datacenter that is for customers. I must configure the part of the datacenters. That's also SCCM 2007 SP1. Cheers
  4. Westlander

    Hello!

    Hello, My name is "westlander". I'm from the Netherlands. Right now I must implementate a SCCM infratructure for a Datacenter with 250 bare metals and 650 virtual servers. I found your site by Google. I must say, your site and your howto's are great! I hope in the future I will add some howto's or tools that deal with SCCM. Cheers, Westlander
×
×
  • Create New...